Bernd Schubert wrote:
>Hi,
>
>every time when nbd-client disconnects a nbd-device the decoded oops
>from below will happen.
>This only happens after we upgraded from 2.4.20 to 2.4.21,
>so I guess the backported update from 2.5.50 causes this.
>Since the changelog for 2.4.22-rc1 doesn't describe any updates to nbd,
>I think this will be also valid for this kernel version. I will check this
>later on this evening.
>
>
>. . .
>
>
I've seen oops's from nbd disconnect in 2.4 also when some blocks were
still being flushed (using the standard linux kernel distributed nbd
driver). I don't know of any back ported fixes to nbd of the ones I've
been introducing into 2.5+ kernels and have no idea though what could
have changed between 2.4.20 and 2.4.21 that causes the diff you've seen
(unless you just never tried the disconnect while blocks still had to be
flushed before). But a lot of the nbd fixes that have been getting
introduced into 2.5+ could very well close races and eliminate oops's in
2.4 also. Getting some more exposure to these fixes in the 2.5+ kernels
has made a lot of sense since these aren't supposed to be as stable and
things can be tested more acceptably but at some point back-porting
starts making sense too. Are we at that point yet?? I don't know. Paul
Clements is now the NBD maintainer. We should see what he says (I've
CC'd him on this email).
Stay in touch.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 07 2003 - 22:00:38 EST