https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289184
--- Comment #4 from [email protected] --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3f10e5985044001a68761995474f1100aca648e1 commit 3f10e5985044001a68761995474f1100aca648e1 Author: Jonathan T. Looney <[email protected]> AuthorDate: 2025-12-05 17:34:31 +0000 Commit: Jonathan T. Looney <[email protected]> CommitDate: 2025-12-06 19:58:46 +0000 ip6: Add explicit lock order information to catch LOR Over the past several years, we have had sporadic reports of a lock order reversal between the tcphash lock and the in6_ifaddr_lock. These seems to be hard to reproduce reliably, and the WITNESS backtrace points to code which uses the correct locking order. This commit adds the correct lock order explicitly to help us detect the call stack which uses the incorrect locking order. PR: 289184 Reported by: bz, gbe Reviewed by: bz, glebius Differential Revision: https://reviews.freebsd.org/D54088 sys/kern/subr_witness.c | 6 ++++++ 1 file changed, 6 insertions(+) -- You are receiving this mail because: You are the assignee for the bug.
