[Bug 289184] lock order reversal between tcphash (tcp_usrreq.c:1529) and in6_ifaddr_lock (in6_src.c:301)

[email protected]
Newsgroups gmane.os.freebsd.devel.net
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289184

paul vixie <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #5 from paul vixie <[email protected]> ---
similar LOR involving tcphash, 16-CURRENT as of this date (2025-12-28):

wlock order reversal:
 1st 0xfffff8000c4ed5e0 so_rcv (so_rcv, sleep mutex) @
/home/vixie/scratch/freebsd-src/sys/kern/uipc_socket.c:1429
 2nd 0xfffffe00c36cda10 tcphash (tcphash, sleep mutex) @
/home/vixie/scratch/freebsd-src/sys/netinet/tcp_usrreq.c:440
lock order so_rcv -> tcphash attempted at:
#0 0xffffffff80c0f23[Starting cron.]1 at witness_checkorder+0xbe1
#1 0xffffffff80b71011 at __mtx_lock_flags+0x91
#2 0xffffffff80dc555b at tcp6_usr_listen+0xfb
#3 0xffffffff80c4ec61 at solisten+0x41
#4 0xffffffff80c576ff at kern_listen+0x6f
#5 0xffffffff810f1a19 at amd64_syscall+0x169
#6 0xffffffff810c007b at fast_syscall_common+0xf8

it's happening at startup time, see the [Starting cron.] message which i placed
brackets around. restarting cron doesn't re-trigger. nor restarting sshd which
was started just prior.

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.