From: Auger Eric <eric.auger@redhat.com>
To: Simon Veith <sveith@amazon.de>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org
Subject: Re: [PATCH v3 3/6] hw/arm/smmuv3: Check stream IDs against actual table LOG2SIZE
Date: Tue, 17 Dec 2019 09:54:47 +0100 [thread overview]
Message-ID: <51c6ef39-f714-0d6b-7b14-2b49b298e556@redhat.com> (raw)
In-Reply-To: <1576509312-13083-4-git-send-email-sveith@amazon.de>
Hi Simon,
On 12/16/19 4:15 PM, Simon Veith wrote:
> When checking whether a stream ID is in range of the stream table, we
> have so far been only checking it against our implementation limit
> (SMMU_IDR1_SIDSIZE). However, the guest can program the
> STRTAB_BASE_CFG.LOG2SIZE field to a size that is smaller than this
> limit.
>
> Check the stream ID against this limit as well to match the hardware
> behavior of raising C_BAD_STREAMID events in case the limit is exceeded.
> Also, ensure that we do not go one entry beyond the end of the table by
> checking that its index is strictly smaller than the table size.
>
> ref. ARM IHI 0070C, section 6.3.24.
>
> Signed-off-by: Simon Veith <sveith@amazon.de>
> Cc: Eric Auger <eric.auger@redhat.com>
> Cc: qemu-devel@nongnu.org
> Cc: qemu-arm@nongnu.org
Acked-by: Eric Auger <eric.auger@redhat.com>
Thanks
Eric
> ---
> Changed in v2:
>
> * Also check that stream ID is strictly lower than the table size
>
> hw/arm/smmuv3.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/hw/arm/smmuv3.c b/hw/arm/smmuv3.c
> index eef9a18..727558b 100644
> --- a/hw/arm/smmuv3.c
> +++ b/hw/arm/smmuv3.c
> @@ -377,11 +377,15 @@ static int smmu_find_ste(SMMUv3State *s, uint32_t sid, STE *ste,
> SMMUEventInfo *event)
> {
> dma_addr_t addr;
> + uint32_t log2size;
> int ret;
>
> trace_smmuv3_find_ste(sid, s->features, s->sid_split);
> - /* Check SID range */
> - if (sid > (1 << SMMU_IDR1_SIDSIZE)) {
> + log2size = FIELD_EX32(s->strtab_base_cfg, STRTAB_BASE_CFG, LOG2SIZE);
> + /*
> + * Check SID range against both guest-configured and implementation limits
> + */
> + if (sid >= (1 << MIN(log2size, SMMU_IDR1_SIDSIZE))) {
> event->type = SMMU_EVT_C_BAD_STREAMID;
> return -EINVAL;
> }
>
next prev parent reply other threads:[~2019-12-17 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 15:15 [PATCH v3 0/6] hw/arm/smmuv3: Correct stream ID and event address handling Simon Veith
2019-12-16 15:15 ` [PATCH v3 1/6] hw/arm/smmuv3: Apply address mask to linear strtab base address Simon Veith
2019-12-16 15:15 ` [PATCH v3 2/6] hw/arm/smmuv3: Correct SMMU_BASE_ADDR_MASK value Simon Veith
2019-12-17 8:55 ` Auger Eric
2019-12-16 15:15 ` [PATCH v3 3/6] hw/arm/smmuv3: Check stream IDs against actual table LOG2SIZE Simon Veith
2019-12-17 8:54 ` Auger Eric [this message]
2019-12-16 15:15 ` [PATCH v3 4/6] hw/arm/smmuv3: Align stream table base address to table size Simon Veith
2019-12-17 9:40 ` Auger Eric
2019-12-16 15:15 ` [PATCH v3 5/6] hw/arm/smmuv3: Use correct bit positions in EVT_SET_ADDR2 macro Simon Veith
2019-12-16 15:15 ` [PATCH v3 6/6] hw/arm/smmuv3: Report F_STE_FETCH fault address in correct word position Simon Veith
2019-12-17 10:03 ` [PATCH v3 0/6] hw/arm/smmuv3: Correct stream ID and event address handling Auger Eric
2019-12-17 15:25 ` Peter Maydell
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=51c6ef39-f714-0d6b-7b14-2b49b298e556@redhat.com \
--to=eric.auger@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sveith@amazon.de \
/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).