Date: Tue, 21 Dec 2021 14:08:25 -0600 From: Dustin Marquess <dmarquess@gmail.com> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: Mark Johnston <markj@freebsd.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Kernel panic in networking code Message-ID: <CAJpsHY45dqUr50NqWY-=byXrpw29R1oSfMWq=aadadf%2BrBk2cw@mail.gmail.com> In-Reply-To: <20211209183409.2xbfgszx7miw3rhv@mutt-hbsd> References: <20211209152010.z6ofqf3ucpxkijqf@mutt-hbsd> <YbI3Wl/4iViuJSdg@nuc> <20211209183409.2xbfgszx7miw3rhv@mutt-hbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 9, 2021 at 12:35 PM Shawn Webb <shawn.webb@hardenedbsd.org> wrote: > > On Thu, Dec 09, 2021 at 12:05:30PM -0500, Mark Johnston wrote: > > On Thu, Dec 09, 2021 at 10:20:10AM -0500, Shawn Webb wrote: > > > Hey all, > > > > > > It looks like there's a potential deadlock in some networking code, > > > specifically with ipv4 jails. I can reproduce by running Poudriere on > > > 14-CURRENT. > > > > > > I am using HardenedBSD 14-CURRENT, but we don't have any changes to > > > any point in the code paths that would trigger/cause this kind of > > > kernel panic. > > > > > > I've uploaded the crash.txt file here: > > > https://hardenedbsd.org/~shawn/2021-12-09_crash-01.txt > > > > There is some WIP to address this in https://reviews.freebsd.org/D33339 > > and its followup revision. > > Awesome. Thanks for the response! I'll follow along. I'm happy to test > out the patch before it lands if needed/wanted. I've been running glebius's revised D33339 patch from Friday on my HardenedBSD -CURRENT box since he posted it, and I haven't had any jail related issues since. Granted I'm not running pourdriere builds either, but I guess I could kick one off... -Dustin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJpsHY45dqUr50NqWY-=byXrpw29R1oSfMWq=aadadf%2BrBk2cw>