Re: [Nbd] 3.12 BUG() on ext4, kernel crash on nbd-client when nbd server rebooting
- To: nbd-general@lists.sourceforge.net
- Subject: Re: [Nbd] 3.12 BUG() on ext4, kernel crash on nbd-client when nbd server rebooting
- From: Wouter Verhelst <w@...112...>
- Date: Tue, 19 Nov 2013 00:23:19 +0100
- Message-id: <528AA167.9020205@...112...>
- In-reply-to: <CAECXXi7dEzPct6iEWxOFiPf707VOhFKwFFb6Og_G2+qOv-Od-g@...18...>
- References: <8bf7c5db475eefcf17976a36f892200d@...1427...> <20131112214632.GB31763@...1426...> <7c1b2ca40c3abfe805e9e944f21c7016@...1427...> <20131114075827.GA13554@...1426...> <5285D258.9040808@...112...> <CAECXXi6Vt5gAjv=qkrGzLG3iRjNmjYiYZd7+gCXK860a2tonKg@...18...> <52889084.2080700@...825...> <C2E9E8AD-752C-4190-BD4F-45A9482FF400@...872...> <CAECXXi7dEzPct6iEWxOFiPf707VOhFKwFFb6Og_G2+qOv-Od-g@...18...>
Op 18-11-13 23:17, Paul Clements schreef:
[...]
> Right, some rearrangement of the ioctls would be required too...we'd
> probably want alternate versions of SET_SOCK and DO_IT that are
> re-entrant (right now those will error on an already-configured device,
> and they're doing some setup and teardown that is unneeded in the
> reconnect case).
Since all this is a significant departure of the current API, I suppose
it would be good if there would be a way for the client to detect what
the currently-running kernel supports, without having to resort to
things like calling 'uname -r' (or equivalent in C code) or extensive
error handling based on "that ioctl isn't supported, so let's fall back
to previous API versions."
--
This end should point toward the ground if you want to go to space.
If it starts pointing toward space you are having a bad problem and you
will not go to space today.
-- http://xkcd.com/1133/
Reply to: