Date: Mon, 26 Jan 2026 15:57:54 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 270816] kernel panic in sym_hipd.c Message-ID: <bug-270816-227-s4q4PMnfNe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-270816-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270816 --- Comment #9 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=e769bc77184312b6137a9b180c97b87c0760b849 commit e769bc77184312b6137a9b180c97b87c0760b849 Author: Marius Strobl <marius@FreeBSD.org> AuthorDate: 2026-01-26 13:58:57 +0000 Commit: Marius Strobl <marius@FreeBSD.org> CommitDate: 2026-01-26 15:54:48 +0000 sym(4): Employ memory barriers also on x86 In an MP world, it doesn't hold that x86 requires no memory barriers. This change should also fix panics due to out-of-sync data seen with FreeBSD VMs on top of OpenStack and HBAs of type lsiLogic. [1] While at it: - Improve the granularity somewhat by distinguishing between read and write memory barriers as well as refer to existing *mb(9) functions instead of duplicating these [2], unless IO barriers are also used. - Nuke the unused SYM_DRIVER_NAME macro. PR: 270816 [1] Obtained from: BSD-licensed Linux sym53c8xx driver [2] MFC after: 1 week sys/dev/sym/sym_hipd.c | 42 +++++++++++++++--------------------------- 1 file changed, 15 insertions(+), 27 deletions(-) -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-270816-227-s4q4PMnfNe>