LOR in network

Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Juraj Lutter <otis_at_FreeBSD.org>
Date: Mon, 24 Jul 2023 11:53:24 UTC

Hi,

I’ve seen following LOR in -CURRENT (3a46fe226193) on GENERIC arm64.aarch64:

lock order reversal:
 1st 0xffff000041af89e8 tcphash (tcphash, sleep mutex) @ /usr/src/sys/netinet/tcp_usrreq.c:1513
 2nd 0xffff000000f91648 in6_ifaddr_lock (in6_ifaddr_lock, rm) @ /usr/src/sys/netinet6/in6_src.c:305
lock order tcphash -> in6_ifaddr_lock attempted at:
#0 0xffff0000004d64bc at witness_checkorder+0xa98
#1 0xffff00000045fce4 at _rm_rlock_debug+0x130
#2 0xffff00000063f5e8 at in6_selectsrc+0x33c
#3 0xffff00000063f260 at in6_selectsrc_socket+0x44
#4 0xffff00000063d314 at in6_pcbconnect+0x228
#5 0xffff000000621f40 at tcp6_connect+0x9c
#6 0xffff00000061fa80 at tcp6_usr_connect+0x230
#7 0xffff00000051003c at soconnectat+0xc8
#8 0xffff000000516cfc at kern_connectat+0xc8
#9 0xffff000000516c14 at sys_connect+0xb0
#10 0xffff0000007fa3cc at do_el0_sync+0x520
#11 0xffff0000007d6910 at handle_el0_sync+0x44


—
Juraj Lutter
otis@FreeBSD.org