From: Thomas Huth <thuth@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, cohuck@redhat.com, david@redhat.com
Subject: Re: [PATCH] target/s390x: Fix the accumulation of ccm in op_icm
Date: Sat, 2 Apr 2022 10:38:42 +0200 [thread overview]
Message-ID: <b3df0aa3-46eb-b7ed-93ab-1e5b3ec9f23f@redhat.com> (raw)
In-Reply-To: <20220401193659.332079-1-richard.henderson@linaro.org>
On 01/04/2022 21.36, Richard Henderson wrote:
> Coverity rightly reports that 0xff << pos can overflow.
> This would affect the ICMH instruction.
>
> Fixes: Coverity CID 1487161
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> target/s390x/tcg/translate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/s390x/tcg/translate.c b/target/s390x/tcg/translate.c
> index 5acfc0ff9b..ea7baf0832 100644
> --- a/target/s390x/tcg/translate.c
> +++ b/target/s390x/tcg/translate.c
> @@ -2622,7 +2622,7 @@ static DisasJumpType op_icm(DisasContext *s, DisasOps *o)
> tcg_gen_qemu_ld8u(tmp, o->in2, get_mem_index(s));
> tcg_gen_addi_i64(o->in2, o->in2, 1);
> tcg_gen_deposit_i64(o->out, o->out, tmp, pos, 8);
> - ccm |= 0xff << pos;
> + ccm |= 0xffull << pos;
> }
> m3 = (m3 << 1) & 0xf;
> pos -= 8;
Reviewed-by: Thomas Huth <thuth@redhat.com>
Is this still something for 7.0, or can it wait for the 7.1 cycle?
next prev parent reply other threads:[~2022-04-02 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 19:36 [PATCH] target/s390x: Fix the accumulation of ccm in op_icm Richard Henderson
2022-04-02 8:38 ` Thomas Huth [this message]
2022-04-02 15:30 ` Richard Henderson
2022-04-04 8:36 ` David Hildenbrand
2022-04-27 3:00 ` Richard Henderson
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=b3df0aa3-46eb-b7ed-93ab-1e5b3ec9f23f@redhat.com \
--to=thuth@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.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).