ublk: introduce UBLK_CMD_TRY_STOP_DEV
Subsystems (3)
v6 cover ublk: introduce UBLK_CMD_TRY_STOP_DEV
Changes since v2:
- Address Ming Lei’s comments in patch 2:
- Add a feature flag and some minor comments.
- Patch 1 unchanged, keeps Reviewed-by
Changes since v3:
- Address Caleb's comments in patch 2
- add to kublk.c
- add to auto features
- set feature flag to 17
Changes since v4:
- Selftest added by Ming
- Move kublk.c change to new selftest commit
Changes since v5:
- Return -ENXIO when device is going down instead of -EBUSY
- Update the patch 2 commit msg
Ming Lei (1):
selftests: ublk: add stop command with --safe option
Yoav Cohen (2):
ublk: make ublk_ctrl_stop_dev return void
ublk: add UBLK_CMD_TRY_STOP_DEV command
drivers/block/ublk_drv.c | 50 ++++++++++++++-- include/uapi/linux/ublk_cmd.h | 9 ++- tools/testing/selftests/ublk/Makefile | 1 + tools/testing/selftests/ublk/kublk.c | 53 +++++++++++++++++ tools/testing/selftests/ublk/kublk.h | 1 + .../testing/selftests/ublk/test_generic_16.sh | 57 +++++++++++++++++++ 6 files changed, 165 insertions(+), 6 deletions(-) create mode 100755 tools/testing/selftests/ublk/test_generic_16.sh
Signature · 1 line
2.39.5 (Apple Git-154)
PATCH v6 1/3 ublk: make ublk_ctrl_stop_dev return void
This function always returns 0, so there is no need to return a value.
--- drivers/block/ublk_drv.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/block/ublk_drv.c +3 -3
@@ -3304,10 +3304,9 @@ static inline void ublk_ctrl_cmd_dump(struct io_uring_cmd *cmd) header->data[0], header->addr, header->len); } -static int ublk_ctrl_stop_dev (struct ublk_device *ub) +static void ublk_ctrl_stop_dev (struct ublk_device *ub) {ublk_stop_dev (ub); -return 0 ; } static int ublk_ctrl_get_dev_info(struct ublk_device *ub,
@@ -3780,7 +3779,8 @@ static int ublk_ctrl_uring_cmd(struct io_uring_cmd *cmd, ret =ublk_ctrl_start_dev (ub, header);break ;case UBLK_CMD_STOP_DEV : - ret =ublk_ctrl_stop_dev (ub); +ublk_ctrl_stop_dev (ub); + ret =0 ;break ;case UBLK_CMD_GET_DEV_INFO :case UBLK_CMD_GET_DEV_INFO2 :
Signature · 1 line
2.39.5 (Apple Git-154)
PATCH v6 2/3 ublk: add UBLK_CMD_TRY_STOP_DEV command
In reply to Yoav CohenAdd a best-effort stop command, UBLK_CMD_TRY_STOP_DEV, which only stops a ublk device when it has no active openers.
Unlike UBLK_CMD_STOP_DEV, this command does not disrupt existing users. New opens are blocked only after disk_openers has reached zero; if the device is busy, the command returns -EBUSY and leaves it running.
The ub->block_open flag is used only to close a race with an in-progress open and does not otherwise change open behavior.
Advertise support via the UBLK_F_SAFE_STOP_DEV feature flag.
--- drivers/block/ublk_drv.c | 44 +++++++++++++++++++++++++++++++++-- include/uapi/linux/ublk_cmd.h | 9 ++++++- 2 files changed, 50 insertions(+), 3 deletions(-)
drivers/block/ublk_drv.c +42 -2
@@ -54,6 +54,7 @@#define UBLK_CMD_DEL_DEV_ASYNC _IOC_NR(UBLK_U_CMD_DEL_DEV_ASYNC)#define UBLK_CMD_UPDATE_SIZE _IOC_NR(UBLK_U_CMD_UPDATE_SIZE)#define UBLK_CMD_QUIESCE_DEV _IOC_NR(UBLK_U_CMD_QUIESCE_DEV) +#define UBLK_CMD_TRY_STOP_DEV _IOC_NR(UBLK_U_CMD_TRY_STOP_DEV)#define UBLK_IO_REGISTER_IO_BUF _IOC_NR(UBLK_U_IO_REGISTER_IO_BUF)#define UBLK_IO_UNREGISTER_IO_BUF _IOC_NR(UBLK_U_IO_UNREGISTER_IO_BUF)
@@ -73,7 +74,8 @@ | UBLK_F_AUTO_BUF_REG \ | UBLK_F_QUIESCE \ | UBLK_F_PER_IO_DAEMON \ - | UBLK_F_BUF_REG_OFF_DAEMON) + | UBLK_F_BUF_REG_OFF_DAEMON \ + | UBLK_F_SAFE_STOP_DEV)#define UBLK_F_ALL_RECOVERY_FLAGS (UBLK_F_USER_RECOVERY \ | UBLK_F_USER_RECOVERY_REISSUE \
@@ -239,6 +241,8 @@ struct ublk_device {struct delayed_work exit_work;struct work_struct partition_scan_work; +bool block_open;/* protected by open_mutex */ +struct ublk_queue *queues[]; };
@@ -919,6 +923,9 @@ static int ublk_open(struct gendisk *disk, blk_mode_t mode)return -EPERM ; } +if (ub->block_open) +return -ENXIO ; +return 0 ; }
@@ -3188,7 +3195,8 @@ static int ublk_ctrl_add_dev(const struct ublksrv_ctrl_cmd *header) ub->dev_info.flags |=UBLK_F_CMD_IOCTL_ENCODE |UBLK_F_URING_CMD_COMP_IN_TASK |UBLK_F_PER_IO_DAEMON | -UBLK_F_BUF_REG_OFF_DAEMON ; +UBLK_F_BUF_REG_OFF_DAEMON | +UBLK_F_SAFE_STOP_DEV ;/* GET_DATA isn't needed any more with USER_COPY or ZERO COPY */ if (ub->dev_info.flags & (UBLK_F_USER_COPY | UBLK_F_SUPPORT_ZERO_COPY |
@@ -3309,6 +3317,34 @@ static void ublk_ctrl_stop_dev(struct ublk_device *ub)ublk_stop_dev (ub); } +static int ublk_ctrl_try_stop_dev (struct ublk_device *ub) +{ +struct gendisk *disk; +int ret =0 ; + + disk =ublk_get_disk (ub); +if (!disk) +return -ENODEV ; + +mutex_lock (&disk->open_mutex); +if (disk_openers (disk) >0 ) { + ret = -EBUSY ; + goto unlock; + } + ub->block_open = true; +/* release open_mutex as del_gendisk() will reacquire it */ +mutex_unlock (&disk->open_mutex); + +ublk_ctrl_stop_dev (ub); + goto out; + +unlock: +mutex_unlock (&disk->open_mutex); +out: +ublk_put_disk (disk); +return ret; +} +static int ublk_ctrl_get_dev_info (struct ublk_device *ub,const struct ublksrv_ctrl_cmd *header) {
@@ -3704,6 +3740,7 @@ static int ublk_ctrl_uring_cmd_permission(struct ublk_device *ub,case UBLK_CMD_END_USER_RECOVERY :case UBLK_CMD_UPDATE_SIZE :case UBLK_CMD_QUIESCE_DEV : +case UBLK_CMD_TRY_STOP_DEV : mask =MAY_READ |MAY_WRITE ;break ;default :
@@ -3817,6 +3854,9 @@ static int ublk_ctrl_uring_cmd(struct io_uring_cmd *cmd,case UBLK_CMD_QUIESCE_DEV : ret =ublk_ctrl_quiesce_dev (ub, header);break ; +case UBLK_CMD_TRY_STOP_DEV : + ret =ublk_ctrl_try_stop_dev (ub); +break ;default : ret = -EOPNOTSUPP ;break ;
include/uapi/linux/ublk_cmd.h +8 -1
@@ -55,7 +55,8 @@ _IOWR('u', 0x15, struct ublksrv_ctrl_cmd)#define UBLK_U_CMD_QUIESCE_DEV \ _IOWR('u', 0x16, struct ublksrv_ctrl_cmd) - +#define UBLK_U_CMD_TRY_STOP_DEV \ + _IOWR('u', 0x17, struct ublksrv_ctrl_cmd)/* * 64bits are enough now, and it should be easy to extend in case of * running out of feature flags
@@ -311,6 +312,12 @@*/ #define UBLK_F_BUF_REG_OFF_DAEMON (1ULL << 14) +/* +* The device supports the UBLK_CMD_TRY_STOP_DEV command, which +* allows stopping the device only if there are no openers. +*/ +#define UBLK_F_SAFE_STOP_DEV (1ULL << 17) +/* device state */ #define UBLK_S_DEV_DEAD 0#define UBLK_S_DEV_LIVE 1
Signature · 1 line
2.39.5 (Apple Git-154)
PATCH v6 3/3 selftests: ublk: add stop command with --safe option
In reply to Yoav CohenFrom: Ming Lei <[email protected]>
Add 'stop' subcommand to kublk utility that uses the new UBLK_CMD_TRY_STOP_DEV command when --safe option is specified. This allows stopping a device only if it has no active openers, returning -EBUSY otherwise.
Also add test_generic_16.sh to test the new functionality.
--- tools/testing/selftests/ublk/Makefile | 1 + tools/testing/selftests/ublk/kublk.c | 53 +++++++++++++++++ tools/testing/selftests/ublk/kublk.h | 1 + .../testing/selftests/ublk/test_generic_16.sh | 57 +++++++++++++++++++ 4 files changed, 112 insertions(+) create mode 100755 tools/testing/selftests/ublk/test_generic_16.sh
tools/testing/selftests/ublk/Makefile +1 -0
@@ -23,6 +23,7 @@ TEST_PROGS += test_generic_12.sh TEST_PROGS += test_generic_13.sh TEST_PROGS += test_generic_14.sh TEST_PROGS += test_generic_15.sh +TEST_PROGS += test_generic_16.sh TEST_PROGS += test_null_01.sh TEST_PROGS += test_null_02.sh
tools/testing/selftests/ublk/kublk.c +53 -0
95 lines not on this page · raw message
tools/testing/selftests/ublk/kublk.h +1 -0
@@ -78,6 +78,7 @@ struct dev_ctx { unsigned int auto_zc_fallback:1; unsigned int per_io_tasks:1; unsigned int no_ublk_fixed_fd:1; + unsigned int safe_stop:1;int _evtfd;int _shmid;
tools/testing/selftests/ublk/test_generic_16.sh new file +57 -0
57 lines not on this page · raw message
Signature · 1 line
2.39.5 (Apple Git-154)
Jens Axboe
maintainerPlease rebase this on the current for-7.0/block tree. It doesn't apply at all, and hunks like:
@@ -311,6 +312,12 @@
*/
#define UBLK_F_BUF_REG_OFF_DAEMON (1ULL << 14)
+/*
+ * The device supports the UBLK_CMD_TRY_STOP_DEV command, which
+ * allows stopping the device only if there are no openers.
+ */
+#define UBLK_F_SAFE_STOP_DEV (1ULL << 17)
+
/* device state */
#define UBLK_S_DEV_DEAD 0
#define UBLK_S_DEV_LIVE 1
is a clear sign that your way off base at this point. Why else would STOP_DEV be 1 << 17, with the previous one at 1 << 14?
Signature · 1 line
Jens Axboe
Quoted 18 lines · Jens Axboe
Please rebase this on the current for-7.0/block tree. It doesn't apply at all, and hunks like:
(quoted diff) +6
-0@@ -311,6 +312,12 @@ */ #define UBLK_F_BUF_REG_OFF_DAEMON (1ULL << 14) +/* + * The device supports the UBLK_CMD_TRY_STOP_DEV command, which + * allows stopping the device only if there are no openers. + */ +#define UBLK_F_SAFE_STOP_DEV (1ULL << 17) + /* device state */ #define UBLK_S_DEV_DEAD 0 #define UBLK_S_DEV_LIVE 1
Quoted 2 lines
is a clear sign that your way off base at this point. Why else would
STOP_DEVbe 1 << 17, with the previous one at 1 << 14?
This is due to being developed in parallel with other ublk patch sets which are using feature flags 15 (UBLK_F_BATCH_IO) and 16 (UBLK_F_INTEGRITY). UBLK_F_BATCH_IO is still in development and UBLK_F_INTEGRITY was just applied. So I don't think it's fair to blame Yoav for not having rebased on commits that didn't exist yet when this version of the patch series was sent out :) Should be a trivial rebase, though, since the value of 17 was already chosen to avoid conflicting with the other patch sets.
Best,
Caleb
Jens Axboe
maintainerQuoted 19 lines · Caleb Sander Mateos
Quoted 18 lines · On Mon, Jan 12, 2026 at 8:22?AM Jens Axboe <[email protected]> wrote:
Please rebase this on the current for-7.0/block tree. It doesn't apply at all, and hunks like:
(quoted diff) +6
-0@@ -311,6 +312,12 @@ */ #define UBLK_F_BUF_REG_OFF_DAEMON (1ULL << 14) +/* + * The device supports the UBLK_CMD_TRY_STOP_DEV command, which + * allows stopping the device only if there are no openers. + */ +#define UBLK_F_SAFE_STOP_DEV (1ULL << 17) + /* device state */ #define UBLK_S_DEV_DEAD 0 #define UBLK_S_DEV_LIVE 1
Quoted 11 lines
Quoted 2 lines
is a clear sign that your way off base at this point. Why else would
STOP_DEVbe 1 << 17, with the previous one at 1 << 14?This is due to being developed in parallel with other ublk patch sets which are using feature flags 15 (
UBLK_F_BATCH_IO) and 16 (UBLK_F_INTEGRITY).UBLK_F_BATCH_IOis still in development andUBLK_F_INTEGRITYwas just applied. So I don't think it's fair to blame Yoav for not having rebased on commits that didn't exist yet when this version of the patch series was sent out :) Should be a trivial rebase, though, since the value of 17 was already chosen to avoid conflicting with the other patch sets.
At the time v6 was posted, it did not apply to the current branches. So regardless of how it was developed, that's not a very useful approach as it means I have to hand apply it. Which isn't too difficult for patches 1-2. But now we have the integrity bits in, which means the selftest bits take more work. At that point I just threw my hands up.
Hence please repost against the current tree.
Signature · 1 line
Jens Axboe
Quoted 33 lines · Jens Axboe
Quoted 19 lines · Caleb Sander Mateos
Quoted 18 lines · On Mon, Jan 12, 2026 at 8:22?AM Jens Axboe <[email protected]> wrote:
Please rebase this on the current for-7.0/block tree. It doesn't apply at all, and hunks like:
(quoted diff) +6
-0@@ -311,6 +312,12 @@ */ #define UBLK_F_BUF_REG_OFF_DAEMON (1ULL << 14) +/* + * The device supports the UBLK_CMD_TRY_STOP_DEV command, which + * allows stopping the device only if there are no openers. + */ +#define UBLK_F_SAFE_STOP_DEV (1ULL << 17) + /* device state */ #define UBLK_S_DEV_DEAD 0 #define UBLK_S_DEV_LIVE 1Quoted 11 lines
Quoted 2 lines
is a clear sign that your way off base at this point. Why else would
STOP_DEVbe 1 << 17, with the previous one at 1 << 14?This is due to being developed in parallel with other ublk patch sets which are using feature flags 15 (
UBLK_F_BATCH_IO) and 16 (UBLK_F_INTEGRITY).UBLK_F_BATCH_IOis still in development andUBLK_F_INTEGRITYwas just applied. So I don't think it's fair to blame Yoav for not having rebased on commits that didn't exist yet when this version of the patch series was sent out :) Should be a trivial rebase, though, since the value of 17 was already chosen to avoid conflicting with the other patch sets.
Quoted 1 line
At the time v6 was posted, it did not apply to the current branches. So
I just tried it, and v6 applies just fine at commit 5df832ba5f9d ("Merge branch 'block-6.19' into for-7.0/block") prior to the "ublk:
add support for integrity data" patch set. And v6 was sent at 13:36 UTC, while the integrity patch set was applied at 16:22 UTC. So It looks like v6 in fact did apply to for-7.0/block when posted.
Quoted 6 lines
regardless of how it was developed, that's not a very useful approach as it means I have to hand apply it. Which isn't too difficult for patches 1-2. But now we have the integrity bits in, which means the selftest bits take more work. At that point I just threw my hands up.
Hence please repost against the current tree.
Yes, completely agree it makes sense to resend the patch set rebased on top of for-7.0/block with the integrity changes.
Best,
Caleb