Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
please confirm the liburing case io_uring_passthrough.t if support device name like '/dev/nvme0n1'

Version-Release number of selected component (if applicable):
5.14.0-329.el9.x86_64
liburing-2.3-2.el9.x86_64

How reproducible:


Steps to Reproduce:
[root@storageqe-66 test]# ./io_uring_passthrough.t /dev/nvme0n1 
cqe res -95, wanted 0
test_io failed 0/0/0/0
[root@storageqe-66 test]# $?
-bash: 1: command not found
[root@storageqe-66 test]# 
[root@storageqe-66 test]# ./io_uring_passthrough.t /dev/ng0n1 
Device doesn't support polled IO
[root@storageqe-66 test]# $?
-bash: 0: command not found
[root@storageqe-66 test]# 
[root@storageqe-66 test]# cat /proc/cmdline 
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.0-329.el9.x86_64 root=/dev/mapper/rhel_storageqe--66-root ro loglevel=5 resume=/dev/mapper/rhel_storageqe--66-swap rd.lvm.lv=rhel_storageqe-66/root rd.lvm.lv=rhel_storageqe-66/swap selinux=0 console=ttyS0,115200n81 crashkernel=1G-4G:384M,4G-16G:512M,16G-64G:1G,64G-128G:2G,128G-:4G nvme.poll_queues=0 nvme_core.multipath=N io_uring.enable=y
[root@storageqe-66 test]# 


Actual results:


Expected results:


Additional info:

(In reply to guazhang from comment #0)
> Description of problem:
> please confirm the liburing case io_uring_passthrough.t if support device
> name like '/dev/nvme0n1'

No, the nvme pass-through commands must be issued to the generic device, ng<#>n<#>

> Version-Release number of selected component (if applicable):
> 5.14.0-329.el9.x86_64
> liburing-2.3-2.el9.x86_64
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> [root@storageqe-66 test]# ./io_uring_passthrough.t /dev/nvme0n1 
> cqe res -95, wanted 0
> test_io failed 0/0/0/0

As noted above, this is an invalid test.

> [root@storageqe-66 test]# $?
> -bash: 1: command not found

ITYM "echo $?"

> [root@storageqe-66 test]# 
> [root@storageqe-66 test]# ./io_uring_passthrough.t /dev/ng0n1 
> Device doesn't support polled IO

This is expected.  FYI, the upstream added code to the io_uring_passthrough test skip the test when polling isn't supported by the device.  See liburing commit 9e0acb2 ("test/io_uring_passthrough: skip test if bit sqe/cqe support not there").

> [root@storageqe-66 test]# $?
> -bash: 0: command not found

Again, "echo $?"  :)