From: Douglas Gilbert <dgilbert@interlog.com>
To: Todd Poynor <toddpoynor@google.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] sg: recheck MMAP_IO request length with lock held
Date: Tue, 22 Aug 2017 17:37:10 -0400 [thread overview]
Message-ID: <db6faa64-7ef2-9a72-f186-8691313ad18a@interlog.com> (raw)
In-Reply-To: <20170816044843.96697-1-toddpoynor@google.com>
On 2017-08-16 12:48 AM, Todd Poynor wrote:
> Commit 1bc0eb044615 ("scsi: sg: protect accesses to 'reserved' page
> array") adds needed concurrency protection for the "reserve" buffer.
> Some checks that are initially made outside the lock are replicated once
> the lock is taken to ensure the checks and resulting decisions are made
> using consistent state.
>
> The check that a request with flag SG_FLAG_MMAP_IO set fits in the
> reserve buffer also needs to be performed again under the lock to
> ensure the reserve buffer length compared against matches the value in
> effect when the request is linked to the reserve buffer. An -ENOMEM
> should be returned in this case, instead of switching over to an
> indirect buffer as for non-MMAP_IO requests.
>
> Signed-off-by: Todd Poynor <toddpoynor@google.com>
Acked-by: Douglas Gilbert <dgilbert@interlog.com>
Thanks.
> ---
> drivers/scsi/sg.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/sg.c b/drivers/scsi/sg.c
> index d7ff71e0c85c..3a44b4bc872b 100644
> --- a/drivers/scsi/sg.c
> +++ b/drivers/scsi/sg.c
> @@ -1735,9 +1735,12 @@ sg_start_req(Sg_request *srp, unsigned char *cmd)
> !sfp->res_in_use) {
> sfp->res_in_use = 1;
> sg_link_reserve(sfp, srp, dxfer_len);
> - } else if ((hp->flags & SG_FLAG_MMAP_IO) && sfp->res_in_use) {
> + } else if (hp->flags & SG_FLAG_MMAP_IO) {
> + res = -EBUSY; /* sfp->res_in_use == 1 */
> + if (dxfer_len > rsv_schp->bufflen)
> + res = -ENOMEM;
> mutex_unlock(&sfp->f_mutex);
> - return -EBUSY;
> + return res;
> } else {
> res = sg_build_indirect(req_schp, sfp, dxfer_len);
> if (res) {
>
next prev parent reply other threads:[~2017-08-22 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 4:48 Todd Poynor
2017-08-22 21:37 ` Douglas Gilbert [this message]
2017-08-23 1:46 ` Martin K. Petersen
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=db6faa64-7ef2-9a72-f186-8691313ad18a@interlog.com \
--to=dgilbert@interlog.com \
--cc=hare@suse.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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
all inboxes | Powered by JetHome®