All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Cédric Le Goater" <clg@kaod.org>, qemu-devel@nongnu.org
Cc: Andrew Jeffery <andrew@aj.id.au>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-arm@nongnu.org, Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH-for-5.1] hw/misc/aspeed_sdmc: Fix incorrect memory size
Date: Mon, 20 Jul 2020 19:39:02 +0200	[thread overview]
Message-ID: <f7dc7d48-6fd7-e1ba-f94b-cd2764490eb7@amsat.org> (raw)
In-Reply-To: <ed5e6bd0-0962-b182-3348-d3c6655ef35e@kaod.org>

On 7/20/20 6:07 PM, Cédric Le Goater wrote:
> On 7/20/20 11:58 AM, Philippe Mathieu-Daudé wrote:
>> The SDRAM Memory Controller has a 32-bit address bus, thus
>> supports up to 4 GiB of DRAM. There is a signed to unsigned
>> conversion error with the AST2600 maximum memory size:
>>
>>   (uint64_t)(2048 << 20) = (uint64_t)(-2147483648)
>>                          = 0xffffffff40000000
>>                          = 16 EiB - 2 GiB
>>
>> Fix by using the IEC suffixes which are usually safer, and add
>> a check to verify the memory is valid. This would have catched
>> this bug:
>>
>>     Unexpected error in aspeed_sdmc_realize() at hw/misc/aspeed_sdmc.c:261:
>>     qemu-system-arm: Invalid RAM size 16 EiB
> 
> Indeed :/
> 
>>
>> Fixes: 1550d72679 ("aspeed/sdmc: Add AST2600 support")
>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>> ---
>>  hw/misc/aspeed_sdmc.c | 12 +++++++++---
>>  1 file changed, 9 insertions(+), 3 deletions(-)
>>
>> diff --git a/hw/misc/aspeed_sdmc.c b/hw/misc/aspeed_sdmc.c
>> index 0737d8de81..76dd7e6a20 100644
>> --- a/hw/misc/aspeed_sdmc.c
>> +++ b/hw/misc/aspeed_sdmc.c
>> @@ -256,6 +256,12 @@ static void aspeed_sdmc_realize(DeviceState *dev, Error **errp)
>>      AspeedSDMCClass *asc = ASPEED_SDMC_GET_CLASS(s);
>>  
>>      s->max_ram_size = asc->max_ram_size;
>> +    if (s->max_ram_size >= 4 * GiB) {
>> +        char *szstr = size_to_str(s->max_ram_size);
>> +        error_setg(errp, "Invalid RAM size %s", szstr);
>> +        g_free(szstr);
>> +        return;
>> +    }
>>
> 
> I would put an assert() since the max RAM size is not user configurable. 

As you wish, at this point I'm completely lost with error reporting.
Per the manual
(https://www.mail-archive.com/qemu-devel@nongnu.org/msg723217.html):

 "Many, many devices neglect to clean up properly on error, and get away
  with it only because all callers treat errors as fatal.

  If you decide to take cleanup shortcuts, say because the cleanup is
  untestable, consider adding a comment at least."

So I'll go for address + comment:

  assert(s->max_ram_size < 4 * GiB); /* 32-bit address bus */

> 
> C.
> 
>>      memory_region_init_io(&s->iomem, OBJECT(s), &aspeed_sdmc_ops, s,
>>                            TYPE_ASPEED_SDMC, 0x1000);
>> @@ -341,7 +347,7 @@ static void aspeed_2400_sdmc_class_init(ObjectClass *klass, void *data)
>>      AspeedSDMCClass *asc = ASPEED_SDMC_CLASS(klass);
>>  
>>      dc->desc = "ASPEED 2400 SDRAM Memory Controller";
>> -    asc->max_ram_size = 512 << 20;
>> +    asc->max_ram_size = 512 * MiB;
>>      asc->compute_conf = aspeed_2400_sdmc_compute_conf;
>>      asc->write = aspeed_2400_sdmc_write;
>>      asc->valid_ram_sizes = aspeed_2400_ram_sizes;
>> @@ -408,7 +414,7 @@ static void aspeed_2500_sdmc_class_init(ObjectClass *klass, void *data)
>>      AspeedSDMCClass *asc = ASPEED_SDMC_CLASS(klass);
>>  
>>      dc->desc = "ASPEED 2500 SDRAM Memory Controller";
>> -    asc->max_ram_size = 1024 << 20;
>> +    asc->max_ram_size = 1 * GiB;
>>      asc->compute_conf = aspeed_2500_sdmc_compute_conf;
>>      asc->write = aspeed_2500_sdmc_write;
>>      asc->valid_ram_sizes = aspeed_2500_ram_sizes;
>> @@ -485,7 +491,7 @@ static void aspeed_2600_sdmc_class_init(ObjectClass *klass, void *data)
>>      AspeedSDMCClass *asc = ASPEED_SDMC_CLASS(klass);
>>  
>>      dc->desc = "ASPEED 2600 SDRAM Memory Controller";
>> -    asc->max_ram_size = 2048 << 20;
>> +    asc->max_ram_size = 2 * GiB;
>>      asc->compute_conf = aspeed_2600_sdmc_compute_conf;
>>      asc->write = aspeed_2600_sdmc_write;
>>      asc->valid_ram_sizes = aspeed_2600_ram_sizes;
>>
> 
> 


  reply	other threads:[~2020-07-20 17:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20  9:58 [PATCH-for-5.1] hw/misc/aspeed_sdmc: Fix incorrect memory size Philippe Mathieu-Daudé
2020-07-20 10:04 ` no-reply
2020-07-20 10:04 ` no-reply
2020-07-20 16:07 ` Cédric Le Goater
2020-07-20 17:39   ` Philippe Mathieu-Daudé [this message]
2020-07-21  8:13     ` Markus Armbruster
2020-07-21  9:06       ` Philippe Mathieu-Daudé
2020-07-21  9:55         ` Markus Armbruster

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=f7dc7d48-6fd7-e1ba-f94b-cd2764490eb7@amsat.org \
    --to=f4bug@amsat.org \
    --cc=andrew@aj.id.au \
    --cc=clg@kaod.org \
    --cc=joel@jms.id.au \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.