From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "scott.bauer@intel.com" <scott.bauer@intel.com>
Cc: "hch@lst.de" <hch@lst.de>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"jack@suse.cz" <jack@suse.cz>, "hare@suse.com" <hare@suse.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] Avoid that scsi_exit_rq() triggers a use-after-free
Date: Thu, 4 May 2017 15:32:44 +0000 [thread overview]
Message-ID: <1493911964.2692.4.camel@sandisk.com> (raw)
In-Reply-To: <20170504151525.GA16489@sbauer-Z170X-UD5>
On Thu, 2017-05-04 at 09:15 -0600, Scott Bauer wrote:
> On Thu, May 04, 2017 at 03:26:37PM +0000, Bart Van Assche wrote:
> > On Thu, 2017-05-04 at 09:30 +0200, Christoph Hellwig wrote:
> > > Please just add a flag to ->flags instead of adding a whole new field.
> > >
> > > Otherwise this looks good to me.
> >
> > Hello Christoph,
> >
> > Thanks for the feedback. I will make the proposed change and post a second
> > version.
>
> BTW, what branch was your last patch based off? I had some hunk errors while
> applying it.
Hello Scott,
That patch was based off kernel v4.11. Did you perhaps use a different kernel
version for your tests?
Bart.
next prev parent reply other threads:[~2017-05-04 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 18:09 [PATCH v2] Avoid that scsi_exit_rq() triggers a use-after-free Bart Van Assche
2017-05-03 18:09 ` Bart Van Assche
2017-05-04 7:30 ` Christoph Hellwig
2017-05-04 15:26 ` Bart Van Assche
2017-05-04 15:15 ` Scott Bauer
2017-05-04 15:32 ` Bart Van Assche [this message]
2017-05-04 15:23 ` Scott Bauer
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=1493911964.2692.4.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=scott.bauer@intel.com \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.