From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org, Li Qiang <liq3ea@gmail.com>,
Alexander Bulekov <alxndr@bu.edu>
Cc: Fam Zheng <fam@euphon.net>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] scsi: Silence gcc warning
Date: Tue, 9 Feb 2021 16:44:28 +0100 [thread overview]
Message-ID: <2ca3b005-9d9f-dde6-a7d4-b7e08a3e3066@redhat.com> (raw)
In-Reply-To: <20210209152350.207958-1-eblake@redhat.com>
On 2/9/21 4:23 PM, Eric Blake wrote:
> On Fedora 33, gcc 10.2.1 notes that scsi_cdb_length(buf) can set
> len==-1, which in turn overflows g_malloc():
>
> [5/5] Linking target qemu-system-x86_64
> In function ‘scsi_disk_new_request_dump’,
> inlined from ‘scsi_new_request’ at ../hw/scsi/scsi-disk.c:2608:9:
> ../hw/scsi/scsi-disk.c:2582:19: warning: argument 1 value ‘18446744073709551612’ exceeds maximum object size 9223372036854775807 [-Walloc-size-larger-than=]
> 2582 | line_buffer = g_malloc(len * 5 + 1);
> | ^
>
> Silence it with a decent assertion, since we only convert a buffer to
> bytes when we have a valid cdb length.
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
> hw/scsi/scsi-disk.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/scsi/scsi-disk.c b/hw/scsi/scsi-disk.c
> index ed52fcd49ff0..b3311a5657b7 100644
> --- a/hw/scsi/scsi-disk.c
> +++ b/hw/scsi/scsi-disk.c
> @@ -2579,6 +2579,7 @@ static void scsi_disk_new_request_dump(uint32_t lun, uint32_t tag, uint8_t *buf)
> int len = scsi_cdb_length(buf);
> char *line_buffer, *p;
>
> + assert(len > 0 && len <= 16);
> line_buffer = g_malloc(len * 5 + 1);
>
> for (i = 0, p = line_buffer; i < len; i++) {
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2021-02-09 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 15:23 [PATCH] scsi: Silence gcc warning Eric Blake
2021-02-09 15:44 ` Philippe Mathieu-Daudé [this message]
2021-03-08 19:54 ` Eric Blake
2021-03-09 20:22 ` Laurent Vivier
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=2ca3b005-9d9f-dde6-a7d4-b7e08a3e3066@redhat.com \
--to=philmd@redhat.com \
--cc=alxndr@bu.edu \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=liq3ea@gmail.com \
--cc=pbonzini@redhat.com \
--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).