Linux Btrfs filesystem development
 help / color / mirror / Atom feed
* [PATCH 0/2] btrfs: introduce a new ioctl to force updating the device name
@ 2026-09-11  5:38 Qu Wenruo
  2026-09-11  5:38 ` [PATCH 1/2] btrfs: fix the wrong direction for BTRFS_IOC_DEVICES_READY Qu Wenruo
  2026-09-11  5:38 ` [PATCH 2/2] btrfs: introduce a new ioctl to force updating the device name Qu Wenruo
  0 siblings, 2 replies; 3+ messages in thread
From: Qu Wenruo @ 2026-09-11  5:38 UTC (permalink / raw)
  To: linux-btrfs

[CHANGELOG]
v2:
- Add a new patch to fix an existing bug in ioctl read/write direction

- Use the correct _IOW for the new ioctl
  Exposed by Sashiko, and the older wrong direction was copied from the
  only exception.

The first patch is to fix a btrfs_iocl_vol_args user which is using the
incorrect IO direction (the direction is based on if the user space is
doing the read or write).

The second patch add a new ioctl, so that we can push the responsibility
to maintain the btrfs device path to the user space, and blame end users
on the weird device path passed in.

Qu Wenruo (2):
  btrfs: fix the wrong direction for BTRFS_IOC_DEVICES_READY
  btrfs: introduce a new ioctl to force updating the device name

 fs/btrfs/super.c           | 16 +++++++++++-----
 fs/btrfs/volumes.c         | 24 +++++++++++++++++-------
 fs/btrfs/volumes.h         |  6 +++++-
 include/uapi/linux/btrfs.h |  4 +++-
 4 files changed, 36 insertions(+), 14 deletions(-)

-- 
2.55.0


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-09-11  5:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-09-11  5:38 [PATCH 0/2] btrfs: introduce a new ioctl to force updating the device name Qu Wenruo
2026-09-11  5:38 ` [PATCH 1/2] btrfs: fix the wrong direction for BTRFS_IOC_DEVICES_READY Qu Wenruo
2026-09-11  5:38 ` [PATCH 2/2] btrfs: introduce a new ioctl to force updating the device name Qu Wenruo

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox