From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: stable@vger.kernel.org, Douglas Gilbert <dgilbert@interlog.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] scsi: sg: fix SG_DXFER_FROM_DEV transfers
Date: Tue, 18 Jul 2017 09:50:07 +0200 [thread overview]
Message-ID: <20170718075007.GA12382@kroah.com> (raw)
In-Reply-To: <20170718074221.7388-1-jthumshirn@suse.de>
On Tue, Jul 18, 2017 at 09:42:21AM +0200, Johannes Thumshirn wrote:
> (commit 68c59fcea1f2c6a54c62aa896cc623c1b5bc9b47 upstream)
>
> SG_DXFER_FROM_DEV transfers do not necessarily have a dxferp as we set
> it to NULL for the old sg_io read/write interface, but must have a
> length bigger than 0. This fixes a regression introduced by commit
> 28676d869bbb ("scsi: sg: check for valid direction before starting the
> request")
>
> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
> Fixes: 28676d869bbb ("scsi: sg: check for valid direction before starting the request")
> Reported-by: Chris Clayton <chris2553@googlemail.com>
> Tested-by: Chris Clayton <chris2553@googlemail.com>
> Cc: Douglas Gilbert <dgilbert@interlog.com>
> Reviewed-by: Hannes Reinecke <hare@suse.com>
> Tested-by: Chris Clayton <chris2553@googlemail.com>
> Acked-by: Douglas Gilbert <dgilbert@interlog.com>
> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
> ---
> drivers/scsi/sg.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
What stable tree(s) do you want this to be applied to?
thanks,
greg k-h
next prev parent reply other threads:[~2017-07-18 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 7:42 [PATCH] scsi: sg: fix SG_DXFER_FROM_DEV transfers Johannes Thumshirn
2017-07-18 7:50 ` Greg Kroah-Hartman [this message]
2017-07-18 7:52 ` Johannes Thumshirn
2017-07-18 15:45 ` Greg Kroah-Hartman
2017-07-18 15:54 ` Martin K. Petersen
2017-07-18 16:18 ` Greg Kroah-Hartman
2017-07-19 6:48 ` Johannes Thumshirn
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=20170718075007.GA12382@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dgilbert@interlog.com \
--cc=jthumshirn@suse.de \
--cc=martin.petersen@oracle.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 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).