From: Stefan Berger <stefanb@linux.ibm.com>
To: Liam Merwick <liam.merwick@oracle.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tpm_tis: validate locality values don't overrun array
Date: Fri, 8 Feb 2019 15:38:20 -0500 [thread overview]
Message-ID: <cf016219-65e7-a768-91a8-9a674a1ddba4@linux.ibm.com> (raw)
In-Reply-To: <00ba3ef0-896a-81bd-6e89-1761e983881a@oracle.com>
On 2/8/19 3:10 PM, Liam Merwick wrote:
>
>
>>
>>
>>
>>> trace_tpm_tis_abort(s->next_locty);
>>> /*
>>> @@ -531,6 +534,8 @@ static void tpm_tis_mmio_write(void *opaque,
>>> hwaddr addr,
>>> uint16_t len;
>>> uint32_t mask = (size == 1) ? 0xff : ((size == 2) ? 0xffff : ~0);
>>> + assert(TPM_TIS_IS_VALID_LOCTY(locty));
>>> +
>>
>> We also do not need this check here since we are registering 0x5000
>> bytes of MMIO space, which gives us addresses [0x0..0x4fff], from
>> which we calculate the locality with a '>> 12':
>>
>> static uint8_t tpm_tis_locality_from_addr(hwaddr addr)
>> {
>
> In that case would it be good to add this check to enforce the address
> range?
>
> assert(addr < TPM_TIS_ADDR_SIZE);
There would be something fundamentally wrong in how the dispatching of
MMIO addresses works in QEMU. I don't think we should need it...
>
>
>> return (uint8_t)((addr >> TPM_TIS_LOCALITY_SHIFT) & 0x7);
>> }
>>
>> this is where we register the MMIO memory:
>>
>> memory_region_init_io(&s->mmio, OBJECT(s), &tpm_tis_memory_ops,
>> s, "tpm-tis-mmio",
>> TPM_TIS_NUM_LOCALITIES <<
>> TPM_TIS_LOCALITY_SHIFT);
>>
>> The locality cannot be out-of-bounds.
>
>
>
>
> From staring at the code, I do have one other question - why does the
> check of the lower localities below only check 'l < locty - 1' before
> setting s->loc[locty] - it seems like s->loc[locty - 1] is skipped.
>
>
> 627 /* cancel any seize by a lower locality */
> 628 for (l = 0; l < locty - 1; l++) {
> 629 s->loc[l].access &= ~TPM_TIS_ACCESS_SEIZE;
> 630 }
Uuuh. The loop is clearing the SEIZE flag on localities lower than the
current one. This works fine for locty >= 1, but not for locty = 0. I
think there's a bug here.
> 631
> 632 s->loc[locty].access |= TPM_TIS_ACCESS_SEIZE;
>
>
> Regards,
> Liam
>
next prev parent reply other threads:[~2019-02-08 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 14:45 [Qemu-devel] [PATCH] tpm_tis: validate locality values don't overrun array Liam Merwick
2019-02-04 18:05 ` Stefan Berger
2019-02-08 20:10 ` Liam Merwick
2019-02-08 20:38 ` Stefan Berger [this message]
2019-02-08 21:29 ` Stefan Berger
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=cf016219-65e7-a768-91a8-9a674a1ddba4@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=liam.merwick@oracle.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).