From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: eblake@redhat.com, vsementsov@virtuozzo.com
Subject: Re: [Qemu-devel] [PATCH v4 0/6] dirty-bitmaps: fix QMP command permissions
Date: Tue, 2 Oct 2018 19:08:11 -0400 [thread overview]
Message-ID: <b5b13c24-1510-6d85-cfc4-f9a4fc3bbbc4@redhat.com> (raw)
In-Reply-To: <20181002230218.13949-1-jsnow@redhat.com>
On 10/02/2018 07:02 PM, John Snow wrote:
> based on: jsnow/bitmaps staging branch
>
> This series builds on a previous standalone patch and adjusts
> the permission for all (or most) of the QMP bitmap commands.
>
> V4:
> - Replace "in-use" with "in use"
> - Replace "user_modifiable" version with "user_locked"
> - Remove more usages of frozen-and-or-locked in NBD.
>
> John Snow (6):
> block/dirty-bitmaps: add user_locked status checker
> block/dirty-bitmaps: fix merge permissions
> block/dirty-bitmaps: allow clear on disabled bitmaps
> block/dirty-bitmaps: prohibit enable/disable on locked/frozen bitmaps
> block/backup: prohibit backup from using in use bitmaps
> nbd: forbid use of frozen bitmaps
>
> block/dirty-bitmap.c | 13 +++++---
> blockdev.c | 75 +++++++++++++++++++-----------------------
> include/block/dirty-bitmap.h | 1 +
> migration/block-dirty-bitmap.c | 10 ++----
> nbd/server.c | 4 +--
> 5 files changed, 48 insertions(+), 55 deletions(-)
>
Planning on submitting tests for 3.1, but with the merge queue opened up
again I'm pretty keen on getting some stable commit IDs for these so far.
--js
next prev parent reply other threads:[~2018-10-02 23:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 23:02 [Qemu-devel] [PATCH v4 0/6] dirty-bitmaps: fix QMP command permissions John Snow
2018-10-02 23:02 ` [Qemu-devel] [PATCH v4 1/6] block/dirty-bitmaps: add user_locked status checker John Snow
2018-10-03 12:19 ` Eric Blake
2018-10-03 12:47 ` Vladimir Sementsov-Ogievskiy
2018-10-03 18:28 ` John Snow
2018-10-03 18:39 ` Eric Blake
2018-10-02 23:02 ` [Qemu-devel] [PATCH v4 2/6] block/dirty-bitmaps: fix merge permissions John Snow
2018-10-03 12:20 ` Eric Blake
2018-10-03 13:01 ` Vladimir Sementsov-Ogievskiy
2018-10-02 23:02 ` [Qemu-devel] [PATCH v4 3/6] block/dirty-bitmaps: allow clear on disabled bitmaps John Snow
2018-10-03 12:21 ` Eric Blake
2018-10-03 13:02 ` Vladimir Sementsov-Ogievskiy
2018-10-02 23:02 ` [Qemu-devel] [PATCH v4 4/6] block/dirty-bitmaps: prohibit enable/disable on locked/frozen bitmaps John Snow
2018-10-03 12:23 ` Eric Blake
2018-10-03 13:05 ` Vladimir Sementsov-Ogievskiy
2018-10-02 23:02 ` [Qemu-devel] [PATCH v4 5/6] block/backup: prohibit backup from using in use bitmaps John Snow
2018-10-03 12:28 ` Eric Blake
2018-10-03 13:21 ` Vladimir Sementsov-Ogievskiy
2018-10-03 16:43 ` John Snow
2018-10-03 14:04 ` Vladimir Sementsov-Ogievskiy
2018-10-02 23:02 ` [Qemu-devel] [PATCH v4 6/6] nbd: forbid use of frozen bitmaps John Snow
2018-10-03 12:31 ` Eric Blake
2018-10-03 14:06 ` Vladimir Sementsov-Ogievskiy
2018-10-02 23:08 ` John Snow [this message]
2018-10-17 20:29 ` [Qemu-devel] [PATCH v4 0/6] dirty-bitmaps: fix QMP command permissions Eric Blake
2018-10-03 20:28 ` John Snow
2018-10-17 18:24 ` Eric Blake
2018-10-17 18:28 ` 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=b5b13c24-1510-6d85-cfc4-f9a4fc3bbbc4@redhat.com \
--to=jsnow@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).