From: John Snow <jsnow@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: mreitz@redhat.com, philmd@redhat.com, qemu-devel@nongnu.org,
armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-4.1 1/2] fdc: Fix inserting read-only media in empty drive
Date: Tue, 30 Jul 2019 11:24:17 -0400 [thread overview]
Message-ID: <0a3466d6-4f61-415c-e40d-b6648b62b822@redhat.com> (raw)
In-Reply-To: <20190730145727.28965-2-kwolf@redhat.com>
On 7/30/19 10:57 AM, Kevin Wolf wrote:
> In order to insert a read-only medium (i.e. a read-only block node) to
> the BlockBackend of a floppy drive, we must not have taken write
> permissions on that BlockBackend, or the operation will fail with the
> error message "Block node is read-only".
>
> The device already takes care to remove all permissions when the medium
> is ejected, but the state isn't correct if the drive is initially empty:
> It uses blk_is_read_only() to check whether write permissions should be
> taken, but this function returns false for empty BlockBackends in the
> common case.
>
> Fix floppy_drive_realize() to avoid taking write permissions if the
> drive is empty.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> hw/block/fdc.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/hw/block/fdc.c b/hw/block/fdc.c
> index 77af9979de..9b24cb9b85 100644
> --- a/hw/block/fdc.c
> +++ b/hw/block/fdc.c
> @@ -514,6 +514,7 @@ static void floppy_drive_realize(DeviceState *qdev, Error **errp)
> FloppyDrive *dev = FLOPPY_DRIVE(qdev);
> FloppyBus *bus = FLOPPY_BUS(qdev->parent_bus);
> FDrive *drive;
> + bool read_only;
> int ret;
>
> if (dev->unit == -1) {
> @@ -542,6 +543,12 @@ static void floppy_drive_realize(DeviceState *qdev, Error **errp)
> dev->conf.blk = blk_new(qemu_get_aio_context(), 0, BLK_PERM_ALL);
> ret = blk_attach_dev(dev->conf.blk, qdev);
> assert(ret == 0);
> +
> + /* Don't take write permissions on an empty drive to allow attaching a
> + * read-only node later */
> + read_only = true;
> + } else {
> + read_only = !blk_bs(dev->conf.blk) || blk_is_read_only(dev->conf.blk);
> }
>
> blkconf_blocksizes(&dev->conf);
> @@ -559,9 +566,7 @@ static void floppy_drive_realize(DeviceState *qdev, Error **errp)
> dev->conf.rerror = BLOCKDEV_ON_ERROR_AUTO;
> dev->conf.werror = BLOCKDEV_ON_ERROR_AUTO;
>
> - if (!blkconf_apply_backend_options(&dev->conf,
> - blk_is_read_only(dev->conf.blk),
> - false, errp)) {
> + if (!blkconf_apply_backend_options(&dev->conf, read_only, false, errp)) {
> return;
> }
>
>
Smells correct.
Reviewed-by: John Snow <jsnow@redhat.com>
next prev parent reply other threads:[~2019-07-30 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 14:57 [Qemu-devel] [PATCH for-4.1 0/2] fdc: Fix inserting read-only media in empty drive Kevin Wolf
2019-07-30 14:57 ` [Qemu-devel] [PATCH for-4.1 1/2] " Kevin Wolf
2019-07-30 15:17 ` Max Reitz
2019-07-30 15:24 ` John Snow [this message]
2019-07-30 14:57 ` [Qemu-devel] [PATCH for-4.1 2/2] iotests/118: Test inserting a read-only medium Kevin Wolf
2019-07-30 15:24 ` Max Reitz
2019-07-30 15:25 ` John Snow
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=0a3466d6-4f61-415c-e40d-b6648b62b822@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@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 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).