Displaying 3 results from an estimated 3 matches for "433479e6".
2023 Jul 14
2
[libnbd PATCH 1/2] api: Tighten rules on completion.callback
...| 26 ++++++++++++++++----------
> > lib/handle.c | 3 +++
> > tests/closure-lifetimes.c | 14 ++++++++++++++
> > 3 files changed, 33 insertions(+), 10 deletions(-)
> >
> > diff --git a/docs/libnbd.pod b/docs/libnbd.pod
> > index 72f74053..433479e6 100644
> > --- a/docs/libnbd.pod
> > +++ b/docs/libnbd.pod
> > @@ -904,9 +904,12 @@ same nbd object, as it would cause deadlock.
> > =head2 Completion callbacks
> >
> > All of the asychronous commands have an optional completion callback
> > -function th...
2023 Jul 16
1
[libnbd PATCH 1/2] api: Tighten rules on completion.callback
...++++++++++----------
>>> lib/handle.c | 3 +++
>>> tests/closure-lifetimes.c | 14 ++++++++++++++
>>> 3 files changed, 33 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/docs/libnbd.pod b/docs/libnbd.pod
>>> index 72f74053..433479e6 100644
>>> --- a/docs/libnbd.pod
>>> +++ b/docs/libnbd.pod
>>> @@ -904,9 +904,12 @@ same nbd object, as it would cause deadlock.
>>> =head2 Completion callbacks
>>>
>>> All of the asychronous commands have an optional completion callback
>...
2023 Jul 13
2
[libnbd PATCH 0/2] Fix docs and testing of completion callback
This is my proposal for fixing the documentation to match practice
(namely, that completion.callback is not invoked in the cases where
the aio call itself reports errors); we could instead try to go the
other direction and tweak the generator to guarantee that both
completion.callback and completion.free are reached no matter what,
but that felt more invasive to me.
Eric Blake (2):
api: Tighten