block: expose 'read_keys' and 'read_reservation' PR callbacks
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | block: add 'read_keys' persistent reservation ioctlblock/ include/ include/ | +46 | 0 replies | |
| 2/3 | block: add 'read_reservation' persistent reservation ioctlblock/ include/ include/ | +29 | 0 replies | |
| 3/3 | scsi: return PR generation if no reservation is helddrivers/ | +7 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] block: expose 'read_keys' and 'read_reservation' PR callbacks
Hi all,
the generic persistent reservation framework already has callbacks for 'read_keys' and 'read_reservation', but these callbacks are not exposed via ioctls (unlike the other callbacks). As we need this information if we want to work with persistent reservations reliably add two new persistent reservation ioctls 'IOC_PR_READ_KEYS' and 'IOC_PR_READ_RESV' to expose this information to userspace.
As usual, comments and reviews are welcome.
Hannes Reinecke (3):
block: add 'read_keys' persistent reservation ioctl
block: add 'read_reservation' persistent reservation ioctl
scsi: return PR generation if no reservation is held
block/ioctl.c | 61 +++++++++++++++++++++++++++++++++++++++++ drivers/scsi/sd.c | 10 +++++-- include/linux/pr.h | 12 -------- include/uapi/linux/pr.h | 14 ++++++++++ 4 files changed, 82 insertions(+), 15 deletions(-)
Signature · 1 line
2.35.3