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.
(In reply to David Milburn from comment #4)
> Hi Yi,
>
> Do you want to clone for RHEL8 and qa_ack the BZ?
>
> We should need the same fix. Thanks.
Yes, I've cloned it. :)
Thanks
YI
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:2317
Description of problem: [RHEL7]nvme show-regs /dev/nvme0 failed with nvme-cli-1.8.1-1.el7 Version-Release number of selected component (if applicable): nvme-cli-1.8.1-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: [FAIL][16:38:09][storageqe-62.rhts.eng.pek2.redhat.com]nvme show-regs /dev/nvme0 -H STDOUT: STDERR:*** Error in `nvme': double free or corruption (top): 0x0000000000f02fe0 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x81679)[0x7f35ecce5679] nvme[0x41a1e7] nvme[0x40ca21] nvme[0x420580] nvme[0x401c41] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f35ecc86505] nvme[0x401d23] ======= Memory map: ======== 00400000-00453000 r-xp 00000000 fd:00 34453526 /usr/sbin/nvme 00652000-00653000 r--p 00052000 fd:00 34453526 /usr/sbin/nvme 00653000-00655000 rw-p 00053000 fd:00 34453526 /usr/sbin/nvme 00655000-00656000 rw-p 00000000 00:00 0 00f02000-00f23000 rw-p 00000000 00:00 0 [heap] 7f35e0000000-7f35e0021000 rw-p 00000000 00:00 0 7f35e0021000-7f35e4000000 ---p 00000000 00:00 0 7f35e6524000-7f35e6539000 r-xp 00000000 fd:00 33554508 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7f35e6539000-7f35e6738000 ---p 00015000 fd:00 33554508 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7f35e6738000-7f35e6739000 r--p 00014000 fd:00 33554508 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7f35e6739000-7f35e673a000 rw-p 00015000 fd:00 33554508 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7f35e673a000-7f35ecc64000 r--p 00000000 fd:00 1902 /usr/lib/locale/locale-archive 7f35ecc64000-7f35ece27000 r-xp 00000000 fd:00 33599881 /usr/lib64/libc-2.17.so 7f35ece27000-7f35ed027000 ---p 001c3000 fd:00 33599881 /usr/lib64/libc-2.17.so 7f35ed027000-7f35ed02b000 r--p 001c3000 fd:00 33599881 /usr/lib64/libc-2.17.so 7f35ed02b000-7f35ed02d000 rw-p 001c7000 fd:00 33599881 /usr/lib64/libc-2.17.so 7f35ed02d000-7f35ed032000 rw-p 00000000 00:00 0 7f35ed032000-7f35ed036000 r-xp 00000000 fd:00 33600005 /usr/lib64/libuuid.so.1.3.0 7f35ed036000-7f35ed235000 ---p 00004000 fd:00 33600005 /usr/lib64/libuuid.so.1.3.0 7f35ed235000-7f35ed236000 r--p 00003000 fd:00 33600005 /usr/lib64/libuuid.so.1.3.0 7f35ed236000-7f35ed237000 rw-p 00004000 fd:00 33600005 /usr/lib64/libuuid.so.1.3.0 7f35ed237000-7f35ed259000 r-xp 00000000 fd:00 33599874 /usr/lib64/ld-2.17.so 7f35ed44a000-7f35ed44d000 rw-p 00000000 00:00 0 7f35ed456000-7f35ed458000 rw-p 00000000 00:00 0 7f35ed458000-7f35ed459000 r--p 00021000 fd:00 33599874 /usr/lib64/ld-2.17.so 7f35ed459000-7f35ed45a000 rw-p 00022000 fd:00 33599874 /usr/lib64/ld-2.17.so 7f35ed45a000-7f35ed45b000 rw-p 00000000 00:00 0 7ffe9156d000-7ffe9158e000 rw-p 00000000 00:00 0 [stack] 7ffe915f2000-7ffe915f4000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] RETURN:134 Actual results: Expected results: Additional info: seems bellow patch fixed it. commit d16e1d2784a48c9b25e58a0e821c737670c6cdc8 Author: Minwoo Im <minwoo.im> Date: Wed Apr 24 01:46:29 2019 +0100 ioctl: Fix double-free in a loop of get_property As it was reported, *pbar could be double-freed in case get_property_helper() fails in the middle of the loop. This issue was reported by Ken Heitke on: https://github.com/linux-nvme/nvme-cli/pull/471 Signed-off-by: Minwoo Im <minwoo.im>