From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] scsi: add block job opblockers for scsi-block
Date: Mon, 12 Feb 2018 14:52:06 +0100 [thread overview]
Message-ID: <20180212135206.GG5103@localhost.localdomain> (raw)
In-Reply-To: <5ac0b76e-213a-60c3-c010-87512d3a564a@redhat.com>
Am 08.02.2018 um 11:42 hat Paolo Bonzini geschrieben:
> On 08/02/2018 02:35, Fam Zheng wrote:
> > On Wed, 02/07 17:36, Paolo Bonzini wrote:
> >> @@ -2626,6 +2656,36 @@ static void scsi_block_realize(SCSIDevice *dev, Error **errp)
> >>
> >> scsi_realize(&s->qdev, errp);
> >> scsi_generic_read_device_identification(&s->qdev);
> >> +
> >> + /* For op blockers, due to lack of support for dirty bitmaps. */
> >> + error_setg(&sb->mirror_source,
> >> + "scsi-block does not support acting as a mirroring source");
> >> + error_setg(&sb->commit_source,
> >> + "scsi-block does not support acting as an active commit source");
> >
> > An alternative way would be adding BLOCK_OP_TYPE_DIRTY_BITMAP. The error message
> > will not be as nice but it can be useful for another (blockjob) operation that
> > requires dirty bitmap support, or another device that doesn't support dirty
> > bitmaps. Though there isn't one for now.
>
> Yeah, I thought about it. Another possibility is make BLOCK_OP_TYPE_* a
> bitmask. Then you can easily add a single Error * for multiple
> blockers, and BLOCK_OP_TYPE_DIRTY_BITMAP can be defined as
> BLOCK_OP_TYPE_MIRROR_SOURCE|BLOCK_OP_TYPE_COMMIT_SOURCE; likewise for
> notifiers below.
We shouldn't be adding new instances of BLOCK_OP_* at all. I couldn't
find the time yet to remove the existing ones, but any new protections
should be using the permission system.
I propose a new BLK_PERM_BYPASS that allows its users to bypass the
block layer I/O functions. In other words, bdrv_aio_ioctl() would
require that you got this permission. A dirty bitmap would keep a
BdrvChild with perm=0, shared=BLK_PERM_ALL & ~BLK_PERM_BYPASS, so you
can never have a dirty bitmap and a device using ioctls attached to the
BDS at the same time.
Kevin
next prev parent reply other threads:[~2018-02-12 13:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 16:36 [Qemu-devel] [PATCH 0/2] scsi: add block job opblockers for scsi-block Paolo Bonzini
2018-02-07 16:36 ` [Qemu-devel] [PATCH 1/2] scsi: add unrealize method for SCSI devices Paolo Bonzini
2018-02-08 1:35 ` Fam Zheng
2018-02-07 16:36 ` [Qemu-devel] [PATCH 2/2] scsi: add block job opblockers for scsi-block Paolo Bonzini
2018-02-08 1:35 ` Fam Zheng
2018-02-08 10:42 ` Paolo Bonzini
2018-02-12 13:52 ` Kevin Wolf [this message]
2018-02-12 14:00 ` Paolo Bonzini
2018-02-12 14:30 ` Kevin Wolf
2018-02-12 14:32 ` Paolo Bonzini
2018-02-12 14:48 ` Kevin Wolf
2018-02-12 14:50 ` Paolo Bonzini
2018-03-12 11:10 ` [Qemu-devel] [Qemu-block] " Paolo Bonzini
2018-03-12 11:58 ` Kevin Wolf
2018-04-05 11:59 ` Paolo Bonzini
2018-04-05 12:43 ` Kevin Wolf
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=20180212135206.GG5103@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=famz@redhat.com \
--cc=pbonzini@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).