From: Stefan Hajnoczi <stefanha@redhat.com>
To: util-linux@vger.kernel.org
Cc: kwolf@redhat.com, hare@suse.de, Karel Zak <kzak@redhat.com>,
pizhenwei@bytedance.com, Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH v2 0/3] blkpr: add read-keys and read-reservations commands
Date: Wed, 17 Dec 2025 13:26:04 -0500 [thread overview]
Message-ID: <20251217182607.179232-1-stefanha@redhat.com> (raw)
v2:
- Use #ifdef IOC_PR_... instead of autoconf/meson because it's simpler [Karel]
New <linux/pr.h> ioctls make it possible to fetch the list of registered keys
and the details of the current reservation from a block device. The relevant
Linux commits are:
3e2cb9ee76c27 block: add IOC_PR_READ_RESERVATION ioctl
22a1ffea5f805 block: add IOC_PR_READ_KEYS ioctl
Add the appropriate commands to blkpr. Users can use these for troubleshooting
and cluster management tools may use them to query the state of persistent
reservations during recovery.
Stefan Hajnoczi (3):
blkpr: prepare for _IOR() ioctls
blkpr: add read-keys command
blkpr: add read-reservation command
sys-utils/blkpr.c | 106 ++++++++++++++++++++++++++++++++++++++---
sys-utils/blkpr.8.adoc | 3 +-
2 files changed, 101 insertions(+), 8 deletions(-)
--
2.52.0
next reply other threads:[~2025-12-17 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 18:26 Stefan Hajnoczi [this message]
2025-12-17 18:26 ` [PATCH v2 1/3] blkpr: prepare for _IOR() ioctls Stefan Hajnoczi
2025-12-17 18:26 ` [PATCH v2 2/3] blkpr: add read-keys command Stefan Hajnoczi
2025-12-17 18:26 ` [PATCH v2 3/3] blkpr: add read-reservation command Stefan Hajnoczi
2026-01-14 9:30 ` [PATCH v2 0/3] blkpr: add read-keys and read-reservations commands Karel Zak
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=20251217182607.179232-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=hare@suse.de \
--cc=kwolf@redhat.com \
--cc=kzak@redhat.com \
--cc=pizhenwei@bytedance.com \
--cc=util-linux@vger.kernel.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