ioctl: only use io_uring for char devices #1018
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 <yi.zhang@redhat.com> Reported-by: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com> Signed-off-by: Daniel Wagner <wagi@kernel.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 yi.zhang@redhat.com
Reported-by: Shinichiro Kawasaki shinichiro.kawasaki@wdc.com
Fixes: linux-nvme/nvme-cli#2829 linux-blktests/blktests#173