From: Douglas Gilbert <dgilbert@interlog.com>
To: Roland Dreier <roland@kernel.org>
Cc: "David Milburn" <dmilburn@redhat.com>,
"Jens Axboe" <axboe@kernel.dk>,
"James Bottomley" <JBottomley@parallels.com>,
"Costa Sapuntzakis" <costa@purestorage.com>,
"Jörn Engel" <joern@purestorage.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
"David Jeffery" <djeffery@redhat.com>
Subject: Re: [PATCH v2] [SCSI] sg: Fix user memory corruption when SG_IO is interrupted by a signal
Date: Thu, 15 Aug 2013 13:01:07 -0400 [thread overview]
Message-ID: <520D0953.2020403@interlog.com> (raw)
In-Reply-To: <CAL1RGDVktaz4Y4_bB+uTzjk0R1+RgwF7DNuZ_+zvpLvH90oTQA@mail.gmail.com>
On 13-08-15 12:45 PM, Roland Dreier wrote:
> Jens / James, do you guys plan to send this to Linus for 3.11?
> Triggering this bug is a bit esoteric but the impact is pretty nasty
> (corrupting an unrelated process).
The patch is fine with me. Even though the sg driver is
named in the patch title, I note that the v2 patch is
only against the block layer. Hence it does not need an
ack from me.
Doug Gilbert
next prev parent reply other threads:[~2013-08-15 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 22:02 [PATCH] [SCSI] sg: Fix user memory corruption when SG_IO is interrupted by a signal Roland Dreier
2013-08-05 23:31 ` James Bottomley
2013-08-05 23:38 ` Roland Dreier
2013-08-05 23:43 ` James Bottomley
2013-08-06 0:55 ` [PATCH v2] " Roland Dreier
2013-08-07 14:38 ` David Milburn
2013-08-07 15:50 ` Roland Dreier
2013-08-07 16:17 ` David Milburn
2013-08-07 16:31 ` Douglas Gilbert
2013-08-08 18:27 ` Roland Dreier
2013-08-15 16:45 ` Roland Dreier
2013-08-15 17:01 ` Douglas Gilbert [this message]
2013-08-06 0:19 ` [PATCH] " Douglas Gilbert
2013-08-06 3:54 ` Peter Chang
2013-08-06 14:56 ` Douglas Gilbert
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=520D0953.2020403@interlog.com \
--to=dgilbert@interlog.com \
--cc=JBottomley@parallels.com \
--cc=axboe@kernel.dk \
--cc=costa@purestorage.com \
--cc=djeffery@redhat.com \
--cc=dmilburn@redhat.com \
--cc=joern@purestorage.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=roland@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).