From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>, "Jens Axboe" <axboe@kernel.dk>
Cc: "Demi Marie Obenour" <demi@invisiblethingslab.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel@lists.xenproject.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] xen/blkback: support delete-on-close block devices
Date: Thu, 1 Jun 2023 17:48:21 -0400 [thread overview]
Message-ID: <20230601214823.1701-1-demi@invisiblethingslab.com> (raw)
These two patches allow userspace to provide an expected diskseq of a
block device and discover when blkback has opened the device. Together,
these features allow using blkback with delete-on-close block devices,
such as loop devices with autoclear set.
Demi Marie Obenour (2):
xen-blkback: Implement diskseq checks
xen-blkback: Inform userspace that device has been opened
drivers/block/xen-blkback/xenbus.c | 147 ++++++++++++++++++++++++-----
1 file changed, 124 insertions(+), 23 deletions(-)
--
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab
next reply other threads:[~2023-06-01 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 21:48 Demi Marie Obenour [this message]
2023-06-01 21:48 ` [PATCH 1/2] xen-blkback: Implement diskseq checks Demi Marie Obenour
2023-06-07 7:44 ` Christoph Hellwig
2023-06-07 16:00 ` Demi Marie Obenour
2023-06-01 21:48 ` [PATCH 2/2] xen-blkback: Inform userspace that device has been opened Demi Marie Obenour
2023-06-07 7:46 ` Christoph Hellwig
2023-06-07 16:01 ` Demi Marie Obenour
2023-06-06 9:31 ` [PATCH 0/2] xen/blkback: support delete-on-close block devices Roger Pau Monné
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=20230601214823.1701-1-demi@invisiblethingslab.com \
--to=demi@invisiblethingslab.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=roger.pau@citrix.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