From: Paolo Bonzini <pbonzini@redhat.com>
To: skiver.cloud.yzy@gmail.com, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Ziyue Yang <yzylivezh@hotmail.com>
Subject: Re: [Qemu-devel] [PATCH] hw/block/pflash_cfi*.c: fix confusing assert fail message
Date: Thu, 15 Dec 2016 15:14:39 +0100 [thread overview]
Message-ID: <7a8da28a-25b7-e243-bc72-96d9953619aa@redhat.com> (raw)
In-Reply-To: <1481810693-13733-1-git-send-email-skiver.cloud.yzy@gmail.com>
On 15/12/2016 15:04, skiver.cloud.yzy@gmail.com wrote:
> From: Ziyue Yang <yzylivezh@hotmail.com>
>
> The patch is to fix the confusing assert fail message caused by
> un-initialized device structure (from bite sized tasks).
>
> The bug can be reproduced by
>
> ./qemu-system-x86_64 -nographic -device cfi.pflash01
>
> The CFI hardware is dynamically loaded by QOM realizing mechanism,
> however the realizing function in pflash_cfi01_realize function
> requires the device being initialized manually before calling, like
>
> ./qemu-system-x86_64 -nographic
> -device cfi.pflash01,num-blocks=1024,sector-length=4096,name=testcard
>
> Once the initializing parameters are left off in the command, it will
> leave the device structure not initialized, which makes
> pflash_cfi01_realize try to realize a zero-volume card, causing
>
> /mnt/EXT_volume/projects/qemu/qemu-dev/exec.c:1378:
> find_ram_offset: Assertion `size != 0\' failed.
>
> Through my test, at least the flash device's block-number, sector-length
> and its name is needed for pflash_cfi01_realize to behave correctly. So
> I think the new asserts are needed to hint the QEMU user to specify
> the device's parameters correctly.
>
> Signed-off-by: Ziyue Yang <skiver.cloud.yzy@gmail.com>
> ---
> hw/block/pflash_cfi01.c | 13 +++++++++++++
> hw/block/pflash_cfi02.c | 13 +++++++++++++
> 2 files changed, 26 insertions(+)
>
> diff --git a/hw/block/pflash_cfi01.c b/hw/block/pflash_cfi01.c
> index 62d7a56..5f0ee9d 100644
> --- a/hw/block/pflash_cfi01.c
> +++ b/hw/block/pflash_cfi01.c
> @@ -707,6 +707,19 @@ static void pflash_cfi01_realize(DeviceState *dev, Error **errp)
> int num_devices;
> Error *local_err = NULL;
>
> + if (pfl->sector_len == 0) {
> + error_setg(errp, "attribute \"sector-length\" not specified or zero.");
> + return;
> + }
> + if (pfl->nb_blocs == 0) {
> + error_setg(errp, "attribute \"num-blocks\" not specified or zero.");
> + return;
> + }
> + if (pfl->name == NULL) {
> + error_setg(errp, "attribute \"name\" not specified.");
> + return;
> + }
> +
> total_len = pfl->sector_len * pfl->nb_blocs;
>
> /* These are only used to expose the parameters of each device
> diff --git a/hw/block/pflash_cfi02.c b/hw/block/pflash_cfi02.c
> index 4f6105c..ef71322 100644
> --- a/hw/block/pflash_cfi02.c
> +++ b/hw/block/pflash_cfi02.c
> @@ -600,6 +600,19 @@ static void pflash_cfi02_realize(DeviceState *dev, Error **errp)
> int ret;
> Error *local_err = NULL;
>
> + if (pfl->sector_len == 0) {
> + error_setg(errp, "attribute \"sector-length\" not specified or zero.");
> + return;
> + }
> + if (pfl->nb_blocs == 0) {
> + error_setg(errp, "attribute \"num-blocks\" not specified or zero.");
> + return;
> + }
> + if (pfl->name == NULL) {
> + error_setg(errp, "attribute \"name\" not specified.");
> + return;
> + }
> +
> chip_len = pfl->sector_len * pfl->nb_blocs;
> /* XXX: to be fixed */
> #if 0
>
Looks good, thanks!
Paolo
prev parent reply other threads:[~2016-12-15 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 14:04 [Qemu-devel] [PATCH] hw/block/pflash_cfi*.c: fix confusing assert fail message skiver.cloud.yzy
2016-12-15 14:14 ` Paolo Bonzini [this message]
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=7a8da28a-25b7-e243-bc72-96d9953619aa@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=skiver.cloud.yzy@gmail.com \
--cc=yzylivezh@hotmail.com \
/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).