From: Ewan Milne <emilne@redhat.com>
To: dgilbert@interlog.com
Cc: SCSI development list <linux-scsi@vger.kernel.org>,
James Bottomley <james.bottomley@hansenpartnership.com>,
Christoph Hellwig <hch@infradead.org>,
dcb314@hotmail.com
Subject: Re: [PATCH] scsi_debug: fix sanity check in resp_rsup_opcodes
Date: Mon, 22 Dec 2014 12:13:00 -0500 [thread overview]
Message-ID: <1419268380.3853.128.camel@localhost.localdomain> (raw)
In-Reply-To: <549848BD.6060402@interlog.com>
On Mon, 2014-12-22 at 11:37 -0500, Douglas Gilbert wrote:
> David Binderman pointed out in this post:
>
> http://marc.info/?l=linux-scsi&m=141924469523474&w=2
>
> a sanity check that was flawed. See attached fix. Should
> be applied to lk 3.19.0-rc1 and Christoph's branches.
>
> ChangeLog:
> fix alloc_len sanity check in resp_rsup_opcodes()
>
>
> ---
> drivers/scsi/scsi_debug.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Signed-off-by: Douglas Gilbert <dgilbert@interlog.com>
Reviewed-by: Ewan D. Milne <emilne@redhat.com>
prev parent reply other threads:[~2014-12-22 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 16:37 [PATCH] scsi_debug: fix sanity check in resp_rsup_opcodes Douglas Gilbert
2014-12-22 17:13 ` Ewan Milne [this message]
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=1419268380.3853.128.camel@localhost.localdomain \
--to=emilne@redhat.com \
--cc=dcb314@hotmail.com \
--cc=dgilbert@interlog.com \
--cc=hch@infradead.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@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