Skip to content

ioctl: only use io_uring for char devices#1018

Merged
igaw merged 1 commit intolinux-nvme:masterfrom
igaw:fix-uring
May 28, 2025
Merged

ioctl: only use io_uring for char devices#1018
igaw merged 1 commit intolinux-nvme:masterfrom
igaw:fix-uring

Conversation

@igaw
Copy link
Copy Markdown
Collaborator

@igaw igaw commented May 28, 2025

The block devices io_uring interface is the generic block subsystem interface and not the nvme one. Thus the nvme io_uring operation only work on a char devices, e.g either nvme0 or ng0n1.

Reported-by: Yi Zhang [email protected]
Reported-by: Shinichiro Kawasaki [email protected]

Fixes: linux-nvme/nvme-cli#2829 linux-blktests/blktests#173

The block devices io_uring interface is the generic block subsystem
interface and not the nvme one. Thus the nvme io_uring operation only
work on a char devices, e.g either nvme0 or ng0n1.

Reported-by: Yi Zhang <[email protected]>
Reported-by: Shinichiro Kawasaki <[email protected]>
Signed-off-by: Daniel Wagner <[email protected]>
@igaw igaw merged commit 0454a99 into linux-nvme:master May 28, 2025
12 checks passed
@igaw igaw deleted the fix-uring branch May 28, 2025 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant