From: Thomas Huth <thuth@redhat.com>
To: Sven Schnelle <svens@stackframe.org>, Fam Zheng <fam@euphon.net>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, deller@gmx.de, Alexander Bulekov <alxndr@bu.edu>
Subject: Re: [PATCH] hw/scsi/lsi53c895a: add missing decrement of reentrancy counter
Date: Mon, 29 Jan 2024 05:16:00 +0100 [thread overview]
Message-ID: <a7ee1d55-f550-4ad9-9907-f9dd13600aa0@redhat.com> (raw)
In-Reply-To: <20240128202214.2644768-1-svens@stackframe.org>
On 28/01/2024 21.22, Sven Schnelle wrote:
> When the maximum count of SCRIPTS instructions is reached, the code
> stops execution and returns, but fails to decrement the reentrancy
> counter. This effectively renders the SCSI controller unusable
> because on next entry the reentrancy counter is still above the limit.
>
> This bug was seen on HP-UX 10.20 which seems to trigger SCRIPTS
> loops.
Out of curiosity: What happened there before we introduced the
reentrancy_level fix? Did it end up in an endless loop, or was it finishing
at one point? In the latter case, we might need to adjust the
"reentrancy_level > 8" to allow deeper nesting.
> Fixes: b987718bbb ("hw/scsi/lsi53c895a: Fix reentrancy issues in the LSI controller (CVE-2023-0330)")
> Signed-off-by: Sven Schnelle <svens@stackframe.org>
> ---
> hw/scsi/lsi53c895a.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/scsi/lsi53c895a.c b/hw/scsi/lsi53c895a.c
> index 34e3b89287..d607a5f9fb 100644
> --- a/hw/scsi/lsi53c895a.c
> +++ b/hw/scsi/lsi53c895a.c
> @@ -1159,6 +1159,7 @@ again:
> lsi_script_scsi_interrupt(s, LSI_SIST0_UDC, 0);
> lsi_disconnect(s);
> trace_lsi_execute_script_stop();
> + reentrancy_level--;
> return;
> }
> insn = read_dword(s, s->dsp);
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2024-01-29 4:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 20:22 [PATCH] hw/scsi/lsi53c895a: add missing decrement of reentrancy counter Sven Schnelle
2024-01-29 4:16 ` Thomas Huth [this message]
2024-01-29 6:17 ` Sven Schnelle
2024-01-29 6:24 ` Michael Tokarev
2024-01-30 18:41 ` Helge Deller
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=a7ee1d55-f550-4ad9-9907-f9dd13600aa0@redhat.com \
--to=thuth@redhat.com \
--cc=alxndr@bu.edu \
--cc=deller@gmx.de \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=svens@stackframe.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).