[Bug 265749] bhyve NVMe emulation panic after LLVM 14 import to CURRENT
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 265749] bhyve NVMe emulation after LLVM 14 import to CURRENT"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 14 Aug 2022 16:08:09 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265749
--- Comment #4 from commit-hook@FreeBSD.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=b6ecef28bfd7c1c267442fae1c8f2fe0f699f617
commit b6ecef28bfd7c1c267442fae1c8f2fe0f699f617
Author: Mark Johnston <markj@FreeBSD.org>
AuthorDate: 2022-08-14 15:57:24 +0000
Commit: Mark Johnston <markj@FreeBSD.org>
CommitDate: 2022-08-14 15:59:01 +0000
bhyve: Address uses of uninitialized variables in pci_nvme.c
The debug print in nvme_opc_get_log_page() would print an uninitialized
local variable.
In nvme_opc_write_read(), a failed LBA bounds check would cause
pci_nvme_stats_write_read_update() to be called with an uninitialized
variable as a parameter. Although the parameter is unused when the
check fails (and so status != 0), LLVM 14 emits some bogus machine code
in this path, which happens to result in a segfault when it gets
executed.
PR: 265749
Reviewed by: chuck, emaste
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D36119
usr.sbin/bhyve/pci_nvme.c | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
--
You are receiving this mail because:
You are the assignee for the bug.