From: Paul Clements <paul.clements@steeleye.com>
To: Mike Snitzer <snitzer@gmail.com>
Cc: nbd-general@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: nbd: Oops because nbd doesn't prevent NBD_CLEAR_SOCK while sock_xmit() is working on a receive
Date: Thu, 27 Mar 2008 23:17:39 -0400 [thread overview]
Message-ID: <47EC6353.1080602@steeleye.com> (raw)
In-Reply-To: <170fa0d20803271412i6d7dd81ax41e0f77339b5def7@mail.gmail.com>
Mike Snitzer wrote:
> With the nbd_sock_xmit_oops.patch applied this Oops no longer happens.
> I think my original patch's use of EINVAL should be changed to EIO.
> Any other comments on the fix are welcome.
No, EINVAL is fine, so the original patch looks good to me.
> Paul, would you like an updated patch that you push upstream? Or
> should I just submit the patch and Cc: you?
The original one is fine, go ahead and send it.
Thanks,
Paul
prev parent reply other threads:[~2008-03-28 3:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 18:43 nbd: Oops because nbd doesn't prevent NBD_CLEAR_SOCK while sock_xmit() is working on a receive Mike Snitzer
2008-03-27 12:35 ` Paul Clements
2008-03-27 13:21 ` Mike Snitzer
2008-03-27 21:12 ` Mike Snitzer
2008-03-28 3:17 ` Paul Clements [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47EC6353.1080602@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd-general@lists.sourceforge.net \
--cc=snitzer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox