Date: Wed, 03 Jan 2024 07:09:50 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 271101] cxgbe(4): panic due to lock recursion while creating tracing interface Message-ID: <bug-271101-7501-PgKnhrNpDZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271101-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-271101-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271101 Navdeep Parhar <np@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|In Progress |Closed --- Comment #4 from Navdeep Parhar <np@FreeBSD.org> --- This was fixed in e203cb393fe0 some time ago. commit e203cb393fe0 Author: Navdeep Parhar <np@FreeBSD.org> Date: Sat Sep 9 12:39:15 2023 -0700 cxgbe(4): Fix tracing with netlink enabled kernels. 1. The tracing ifnet's name must match the nexus name. One way to do this is to not use a unit number. 2. Do not hold the tracer lock around ether_ifattach or ether_ifdetach. netlink calls back into the driver (see stack below) and that leads to illegal lock recursion. tracer_ioctl if_ioctl get_operstate_ether get_operstate dump_iface rtnl_handle_ifevent rtnl_handle_ifattach if_attach_internal if_attach ether_ifattach t4_cloner_create MFC after: 3 days Sponsored by: Chelsio Communications --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271101-7501-PgKnhrNpDZ>