From: Greg KH <gregkh@linuxfoundation.org>
To: Todd Poynor <toddpoynor@google.com>
Cc: stable@vger.kernel.org,
android-kernel <android-kernel@google.com>,
Hannes Reinecke <hare@suse.de>, Hannes Reinecke <hare@suse.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] scsi: sg: protect accesses to 'reserved' page array
Date: Fri, 1 Sep 2017 07:03:55 +0200 [thread overview]
Message-ID: <20170901050355.GC2361@kroah.com> (raw)
In-Reply-To: <CAAW3YpbX25kq3Gh6w1UKK=x81xoAPPcJaSXdz9nOuM-Fb4pHLg@mail.gmail.com>
On Thu, Aug 31, 2017 at 01:11:18PM -0700, Todd Poynor wrote:
> Thanks! A couple more follow-on fixes for sg race conditions are now
> in the linux-next tree (via linux-scsi), in case it's appropriate to
> also queue these for linux-stable trees now or after 4.14 release:
>
> commit 8d26f491116feaa0b16de370b6a7ba40a40fa0b4
> Author: Todd Poynor <toddpoynor@google.com>
> Date: Tue Aug 15 21:48:43 2017 -0700
>
> scsi: sg: recheck MMAP_IO request length with lock held
>
> commit 6a8dadcca81fceff9976e8828cceb072873b7bd5
> Author: Todd Poynor <toddpoynor@google.com>
> Date: Tue Aug 15 22:41:08 2017 -0700
>
> scsi: sg: protect against races between mmap() and SG_SET_RESERVED_SIZE
>
As per:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
I have to wait until they hit Linus's tree, and ideally, show up in a
-rc release, before I can add them to a stable tree.
thanks,
greg k-h
next prev parent reply other threads:[~2017-09-01 5:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 3:09 [PATCH] scsi: sg: protect accesses to 'reserved' page array Todd Poynor
[not found] ` <CAAW3YpbROHL_EXNCRrNOV=K9ywAmBTsxDVBmKHxNCKJPkRnZEA@mail.gmail.com>
2017-08-16 3:32 ` Todd Poynor
2017-08-31 6:19 ` Greg KH
2017-08-31 20:11 ` Todd Poynor
2017-09-01 5:03 ` Greg KH [this message]
2017-09-08 7:10 ` Greg KH
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=20170901050355.GC2361@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=android-kernel@google.com \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=martin.petersen@oracle.com \
--cc=stable@vger.kernel.org \
--cc=toddpoynor@google.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;
as well as URLs for NNTP newsgroup(s).