From: Eric Blake <eblake@redhat.com>
To: Roman Kagan <rvkagan@yandex-team.ru>, qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <fam@euphon.net>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
qemu-block@nongnu.org, "Paul Durrant" <paul@xen.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Laurent Vivier" <laurent@vivier.eu>,
"Max Reitz" <mreitz@redhat.com>,
"Anthony Perard" <anthony.perard@citrix.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Keith Busch" <kbusch@kernel.org>,
xen-devel@lists.xenproject.org, "John Snow" <jsnow@redhat.com>
Subject: Re: [PATCH v7 6/8] block: make BlockConf size props 32bit and accept size suffixes
Date: Thu, 28 May 2020 16:53:14 -0500 [thread overview]
Message-ID: <0439aa5e-413c-cf7e-83b7-1e942a882f5a@redhat.com> (raw)
In-Reply-To: <20200528213946.1636444-7-rvkagan@yandex-team.ru>
On 5/28/20 4:39 PM, Roman Kagan wrote:
> Convert all size-related properties in BlockConf to 32bit. This will
> allow to accomodate bigger block sizes (in a followup patch).
s/allow to accomodate/accommodate/
> This also allows to make them all accept size suffixes, either via
> DEFINE_PROP_BLOCKSIZE or via DEFINE_PROP_SIZE32.
>
> Also, since min_io_size is exposed to the guest by scsi and virtio-blk
> devices as an uint16_t in units of logical blocks, introduce an
> additional check in blkconf_blocksizes to prevent its silent truncation.
>
> Signed-off-by: Roman Kagan <rvkagan@yandex-team.ru>
> ---
> + if (conf->min_io_size / conf->logical_block_size > UINT16_MAX) {
> + error_setg(errp,
> + "min_io_size must not exceed " stringify(UINT16_MAX)
> + " logical blocks");
On my libc, this results in "must not exceed (65535) logical blocks".
Worse, I could envision a platform where it prints something funky like:
"exceed (2 * (32768) + 1) logical", based on however complex the
definition of UINT16_MAX is. You're better off printing this one with
%d than with stringify().
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-05-28 21:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 21:39 [PATCH v7 0/8] block: enhance handling of size-related BlockConf properties Roman Kagan
2020-05-28 21:39 ` [PATCH v7 1/8] virtio-blk: store opt_io_size with correct size Roman Kagan
2020-05-28 21:39 ` [PATCH v7 2/8] block: consolidate blocksize properties consistency checks Roman Kagan
2020-05-28 21:39 ` [PATCH v7 3/8] qdev-properties: blocksize: use same limits in code and description Roman Kagan
2020-05-28 21:39 ` [PATCH v7 4/8] qdev-properties: add size32 property type Roman Kagan
2020-05-28 21:45 ` Eric Blake
2020-05-28 22:35 ` Roman Kagan
2020-05-28 21:39 ` [PATCH v7 5/8] qdev-properties: make blocksize accept size suffixes Roman Kagan
2020-05-28 21:46 ` Eric Blake
2020-05-28 21:39 ` [PATCH v7 6/8] block: make BlockConf size props 32bit and " Roman Kagan
2020-05-28 21:53 ` Eric Blake [this message]
2020-05-28 21:39 ` [PATCH v7 7/8] qdev-properties: add getter for size32 and blocksize Roman Kagan
2020-05-28 21:57 ` Eric Blake
2020-05-28 21:39 ` [PATCH v7 8/8] block: lift blocksize property limit to 2 MiB Roman Kagan
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=0439aa5e-413c-cf7e-83b7-1e942a882f5a@redhat.com \
--to=eblake@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kbusch@kernel.org \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=laurent@vivier.eu \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rvkagan@yandex-team.ru \
--cc=sstabellini@kernel.org \
--cc=stefanha@redhat.com \
--cc=xen-devel@lists.xenproject.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).