Displaying 5 results from an estimated 5 matches for "0e8e8eb11d".
2020 Mar 17
2
Re: [nbdkit PATCH 2/4] nbd: Normalize return values of can_*
...eated as
> success to the .can_* callbacks, we had a window of releases where
> anything other than 1 could trigger an assertion failure, fixed in the
> previous patch. Update what we return to avoid tripping the bug in
> broken nbdkit.
>
> Our return value has been latent since 0e8e8eb11d (v1.1.17), but the
> assertion failures did not occur until c306fa93ab and neighboring
> commits (v1.15.1). As v1.13.6 was the point where we started
> preferring builds against libnbd, where we always returned 1 on
> success, the problem was not detected until now; but it is still in...
2020 Mar 17
1
Re: [nbdkit PATCH 2/4] nbd: Normalize return values of can_*
...backs, we had a window of releases where
> >>anything other than 1 could trigger an assertion failure, fixed in the
> >>previous patch. Update what we return to avoid tripping the bug in
> >>broken nbdkit.
> >>
> >>Our return value has been latent since 0e8e8eb11d (v1.1.17), but the
> >>assertion failures did not occur until c306fa93ab and neighboring
> >>commits (v1.15.1). As v1.13.6 was the point where we started
> >>preferring builds against libnbd, where we always returned 1 on
> >>success, the problem was not detecte...
2020 Mar 17
0
[nbdkit PATCH 2/4] nbd: Normalize return values of can_*
...ny positive value should be treated as
success to the .can_* callbacks, we had a window of releases where
anything other than 1 could trigger an assertion failure, fixed in the
previous patch. Update what we return to avoid tripping the bug in
broken nbdkit.
Our return value has been latent since 0e8e8eb11d (v1.1.17), but the
assertion failures did not occur until c306fa93ab and neighboring
commits (v1.15.1). As v1.13.6 was the point where we started
preferring builds against libnbd, where we always returned 1 on
success, the problem was not detected until now; but it is still in
the wild for any use...
2020 Mar 17
0
Re: [nbdkit PATCH 2/4] nbd: Normalize return values of can_*
...ss to the .can_* callbacks, we had a window of releases where
>> anything other than 1 could trigger an assertion failure, fixed in the
>> previous patch. Update what we return to avoid tripping the bug in
>> broken nbdkit.
>>
>> Our return value has been latent since 0e8e8eb11d (v1.1.17), but the
>> assertion failures did not occur until c306fa93ab and neighboring
>> commits (v1.15.1). As v1.13.6 was the point where we started
>> preferring builds against libnbd, where we always returned 1 on
>> success, the problem was not detected until now; but...
2020 Mar 17
9
[nbdkit PATCH 0/4] Fix testsuite hang with nbd-stadalone
Either patch 1 or patch 2 in isolation is sufficient to fix the
problem that Rich forwarded on from an archlinux tester (name so I can
credit them?). But both patches should be applied, as well as
backported to appropriate stable branches, to maximize cross-version
interoperability of nbdkit vs. plugins. Patch 3 will let us detect
future similar bugs much faster. I want patch 4 to ensure that