Re: [Nbd] another?
- To: Alex Bligh <alex@...872...>
- Cc: Wouter Verhelst <w@...112...>, nbd-general@...72...
- Subject: Re: [Nbd] another?
- From: Paul Clements <paul.clements@...856...>
- Date: Fri, 16 Sep 2011 08:33:33 -0400
- Message-id: <CAECXXi4ZuifP97mp3VYa=m73NB48u+jZEHx9mcVT+P+wNYFY0Q@...18...>
- In-reply-to: <849464DBE06235024D26571C@...873...>
- References: <CAFDOyVDgN4Zo0=LDnWbJ5zBPb9gmLgg-80kuqpN6TjKWGbpRSw@...18...> <3910BC1A8D0D52DED33F94E3@...873...> <CAFDOyVBXr=nAMH7jRorSHBKFMskXbfPnkD7XwDvL5ZZxPp402A@...18...> <20110916083445.GB19601@...3...> <955E7D4A79C020EE6FC1B797@...873...> <20110916103623.GU19601@...3...> <4174751764B4DC4C2F6DACAD@...873...> <20110916113506.GV19601@...3...> <849464DBE06235024D26571C@...873...>
On Fri, Sep 16, 2011 at 7:59 AM, Alex Bligh <alex@...872...> wrote:
>
>
> --On 16 September 2011 13:35:06 +0200 Wouter Verhelst <w@...112...> wrote:
>
>> No, I think this should be fixed in the server, not the tester client.
>> This is a condition that the server needs to be able to deal with. The
>> fact that it doesn't is a bug in the server which the tester client only
>> exposed, it's not a bug in the tester client. If anything, it's a
>> feature of the tester client that it exposes a bug in the server.
>
> Amusing as it is for this to be a 'it's my bug not your bug' discussion
> (the other way around from normal), I think it *is* my bug.
>
> Essentially tester-client is not reading stuff if the write socket
> is blocked. The kernel never does this.
Correct. The kernel always has the nbd-client process reading replies
back from the server while other processes are doing I/O.
Reply to: