Date: Sun, 18 Jan 2026 01:10:51 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 292547] uipc_soreceive_stream_or_seqpacket() - repeatable panic Message-ID: <bug-292547-227-vNiEG1x99L@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-292547-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=292547 --- Comment #8 from Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> --- Thank you for your guidance Mark. The offending commit was 14d93f612f26f4e8454e393b75b0e4b "iflib: Drop tx lock when freeing mbufs using simple_transmit". After reverting it, CURRENT runs fine (GENERIC + RSS). I will eventually revert it back and provide more debugging info later. BTW, now with WITNESS and INVARIANTS enabled, I spotted one LOR: lock order reversal: 1st 0xfffffe001bb2d4f0 netlink lock (netlink lock, rm) @ /usr/src/sys/netlink/netlink_domain.c:219 2nd 0xfffff800190725e0 so_rcv (so_rcv, sleep mutex) @ /usr/src/sys/netlink/netlink_io.c:230 lock order netlink lock -> so_rcv attempted at: #0 0xffffffff80c55591 at witness_checkorder+0xbe1 #1 0xffffffff80bb6011 at __mtx_lock_flags+0x91 #2 0xffffffff80e71ac8 at nl_send+0xb8 #3 0xffffffff80e6d91f at nl_send_group+0x1df #4 0xffffffff80e71ee2 at _nlmsg_flush+0x22 #5 0xffffffff80e7b487 at report_operation+0xd7 #6 0xffffffff80e7b1bd at rtnl_handle_newroute+0x60d #7 0xffffffff80e73432 at rtnl_handle_message+0x132 #8 0xffffffff80e7163d at nl_taskqueue_handler+0x52d #9 0xffffffff80c47432 at taskqueue_run_locked+0x1c2 #10 0xffffffff80c48323 at taskqueue_thread_loop+0xd3 #11 0xffffffff80b8cae2 at fork_exit+0x82 #12 0xffffffff81114bfe at fork_trampoline+0xe -- 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-292547-227-vNiEG1x99L>