Date: Sun, 26 Jul 2020 16:39:56 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 248046] if_bridge(4): Panic when creating an interface: malloc(M_WAITOK) in epoch context Message-ID: <bug-248046-7501-XKd7e5PGDG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-248046-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-248046-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=3D248046 --- Comment #21 from Kristof Provost <kp@freebsd.org> --- (In reply to dmilith from comment #20) That's a different operating system... Don't try to hide that during a bug submission please. It'll always come ou= t in the end, and you're just wasting both of our time. This almost certainly also affects base FreeBSD, but *DO NOT HIDE RELEVANT INFORMATION IN BUG REPORTS*. You're just making the people who want to fix these bugs angry, and that's not the right state of mind to fix bug. Or be helpful. The issue here is that the bridge code tries to set the physical interface = in promiscuous mode, which sleeps in the em code. The stable/12 epoch code doe= sn't allow sleeps during epoch sections (head does), which triggers this panic. (Which we wouldn't see on a default FreeBSD stable/12, because that requires INVARIANTS iirc....) I'll see if that can be fixed, but I may end up just reverting the epoch co= de in stable/12. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-248046-7501-XKd7e5PGDG>