From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Alexandra Diupina <adiupina@astralinux.ru>,
Paolo Bonzini <pbonzini@redhat.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: Fam Zheng <fam@euphon.net>,
qemu-devel@nongnu.org, sdl.qemu@linuxtesting.org
Subject: Re: [PATCH] esp: process the result of scsi_device_find()
Date: Tue, 26 Dec 2023 13:08:46 +0100 [thread overview]
Message-ID: <e05e239f-2d1d-4d9b-86bb-a1e9d9b98550@linaro.org> (raw)
In-Reply-To: <20231218150213.27253-1-adiupina@astralinux.ru>
Cc'ing Mark for the logical change (should we rather assert?).
On 18/12/23 16:02, Alexandra Diupina wrote:
> Add a 'current_lun' check for a null value
> to avoid null pointer dereferencing
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Fixes: 4eb8606560 (esp: store lun coming from the MESSAGE OUT phase)
> Signed-off-by: Alexandra Diupina <adiupina@astralinux.ru>
> ---
> hw/scsi/esp.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/hw/scsi/esp.c b/hw/scsi/esp.c
> index 9b11d8c573..3a2ec35f9b 100644
> --- a/hw/scsi/esp.c
> +++ b/hw/scsi/esp.c
> @@ -292,6 +292,11 @@ static void do_command_phase(ESPState *s)
> esp_fifo_pop_buf(&s->cmdfifo, buf, cmdlen);
>
> current_lun = scsi_device_find(&s->bus, 0, s->current_dev->id, s->lun);
> +
> + if (!current_lun) {
> + return;
> + }
> +
> s->current_req = scsi_req_new(current_lun, 0, s->lun, buf, cmdlen, s);
> datalen = scsi_req_enqueue(s->current_req);
> s->ti_size = datalen;
next prev parent reply other threads:[~2023-12-26 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 15:02 [PATCH] esp: process the result of scsi_device_find() Alexandra Diupina
2023-12-26 12:08 ` Philippe Mathieu-Daudé [this message]
2023-12-27 20:02 ` Mark Cave-Ayland
2023-12-29 15:26 ` [PATCH v2] " Alexandra Diupina
2023-12-29 17:51 ` Philippe Mathieu-Daudé
2023-12-30 9:32 ` Paolo Bonzini
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=e05e239f-2d1d-4d9b-86bb-a1e9d9b98550@linaro.org \
--to=philmd@linaro.org \
--cc=adiupina@astralinux.ru \
--cc=fam@euphon.net \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sdl.qemu@linuxtesting.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).