Re: [Nbd] [PATCH] Swap options and option name
- To: Eric Blake <eblake@...696...>
- Cc: firstname.lastname@example.org
- Subject: Re: [Nbd] [PATCH] Swap options and option name
- From: Wouter Verhelst <w@...112...>
- Date: Sat, 22 Apr 2017 23:44:19 +0200
- Message-id: <20170422214419.ntcibav4tcddtxv5@...3...>
- In-reply-to: <20170421074751.faapjvzs565pa5tl@...3...>
- References: <20170414124637.lloiojthqzpiilty@...3...> <596b5e4f-16c8-b010-dd15-06933e9d93e6@...696...> <20170416094239.dyztgcneb6h26tuo@...3...> <16cb07fc-0432-b251-c756-cada111dac0c@...696...> <20170421071735.2mvbxl4di3q5vr6j@...3...> <20170421074751.faapjvzs565pa5tl@...3...>
On Fri, Apr 21, 2017 at 09:47:51AM +0200, Wouter Verhelst wrote:
> On Fri, Apr 21, 2017 at 09:17:35AM +0200, Wouter Verhelst wrote:
> > I haven't been able to reproduce this either, so it might be something
> > complicated.
> Actually, scratch that, I have. It appears to happen if I single-step
> through the function that sends the INFO message, rather than allowing
> it to run "normally".
It turns out in the end that this was actually on the master branch, not
the nbd one; and it happens when single-stepping a client that's
connected to a qemu nbd server, regardless of where in the conversation.
It feels like a race condition somewhere, but I haven't been able to
track it down yet.
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
people in the world who think they really understand all of its rules,
and pretty much all of them are just lying to themselves too.
-- #debian-devel, OFTC, 2016-02-12