From: Fam Zheng <famz@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] scsi: Don't deference in_buf if NULL
Date: Fri, 5 Jan 2018 09:49:27 +0800 [thread overview]
Message-ID: <20180105014927.GA8592@lemon.usersys.redhat.com> (raw)
In-Reply-To: <9b5c0137-837a-99ee-7887-996c5dba69fa@redhat.com>
On Thu, 01/04 11:41, Eric Blake wrote:
> On 01/03/2018 08:42 PM, Fam Zheng wrote:
> > scsi_disk_emulate_command passes in_buf=NULL and in_len=0 in the
> > REQUEST_SENSE branch. Inline the fixed_in evaluation and put it after
> > the in_len test.
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> > scsi/utils.c | 4 +---
> > 1 file changed, 1 insertion(+), 3 deletions(-)
>
> Does this patch duplicate
> https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg04964.html ?
Yes. Thanks for pointing out this.
Fam
prev parent reply other threads:[~2018-01-05 1:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 2:42 [Qemu-devel] [PATCH] scsi: Don't deference in_buf if NULL Fam Zheng
2018-01-04 17:02 ` Eric Blake
2018-01-05 16:45 ` Anthoine Bourgeois
2018-01-04 17:41 ` Eric Blake
2018-01-05 1:49 ` Fam Zheng [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=20180105014927.GA8592@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).