Date: Fri, 13 Jan 2006 01:30:13 GMT From: Robert Huff <roberthuff@rcn.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/86427: LOR / Deadlock with FASTIPSEC and nat Message-ID: <200601130130.k0D1UDJX036947@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/86427; it has been noted by GNATS. From: Robert Huff <roberthuff@rcn.com> To: bug-followup@FreeBSD.org, mike@sentex.net Cc: Subject: Re: kern/86427: LOR / Deadlock with FASTIPSEC and nat Date: Thu, 12 Jan 2006 20:23:11 -0500 I'm getting what seems to be either the same problem or its fraternal twin ... only without either IPSEC (any flavor) or any vpn. Running FreeBSD 7.0-CURRENT #0: Wed Jan 4 13:41:21 EST 20 I get this Jan 12 19:27:51 jerusalem kernel: lock order reversal: Jan 12 19:27:51 jerusalem kernel: 1st 0xc364a090 inp (divinp) @ /usr/src/sys/netinet/ip_divert.c:327 Jan 12 19:27:51 jerusalem kernel: 2nd 0xc07655cc in_multi_mtx (in_multi_mtx) @ /usr/src/sys/netinet/ip_output.c:291 Jan 12 19:27:51 jerusalem kernel: KDB: stack backtrace: Jan 12 19:27:51 jerusalem kernel: kdb_backtrace(c06b7a91,c07655cc,c06b7470,c06b7470,c06c0886) at kdb_backtrace+0x2f Jan 12 19:27:51 jerusalem kernel: witness_checkorder(c07655cc,9,c06c0886,123,c06bead6) at witness_checkorder+0x6e1 Jan 12 19:27:51 jerusalem kernel: _mtx_lock_flags(c07655cc,0,c06c0886,123,c05427bd) at _mtx_lock_flags+0x85 Jan 12 19:27:51 jerusalem kernel: ip_output(c33c0b00,0,d56e5afc,22,0) at ip_output+0x460 Jan 12 19:27:51 jerusalem kernel: div_output(c35ff000,c33c0b00,c341d970,0,d56e5bb8) at div_output+0x1d5 Jan 12 19:27:51 jerusalem kernel: div_send(c35ff000,0,c33c0b00,c341d970,0) at div_send+0x5d Jan 12 19:27:51 jerusalem kernel: sosend(c35ff000,c341d970,d56e5be4,c33c0b00,0) at sosend+0x49e Jan 12 19:27:51 jerusalem kernel: kern_sendit(c339c900,3,d56e5c64,0,0) at kern_sendit+0x106 Jan 12 19:27:51 jerusalem kernel: sendit(c339c900,3,d56e5c64,0,bfbeedb0) at sendit+0x1a8 Jan 12 19:27:51 jerusalem kernel: sendto(c339c900,d56e5d04,18,43c,6) at sendto+0x5b Jan 12 19:27:51 jerusalem kernel: syscall(3b,3b,3b,bfbeed90,2) at syscall+0x2a6 Jan 12 19:27:51 jerusalem kernel: Xint0x80_syscall() at Xint0x80_syscall+0x1f Jan 12 19:27:51 jerusalem kernel: --- syscall (133, FreeBSD ELF32, sendto), eip and startup continues. If this is a problem with ipfw, it's one that happened since approximately the middle of December.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601130130.k0D1UDJX036947>