Re: FreeBSD panics possibly caused by nfs clients

On Fri, Feb 09, 2024 at 10:11:14PM +0000, Matthew L. Dailey wrote:
> On 2/9/24 4:18 PM, Mark Johnston wrote:
> > [You don't often get email from markj@freebsd.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> > 
> > On Fri, Feb 09, 2024 at 06:23:08PM +0000, Matthew L. Dailey wrote:
> >> I had my first kernel panic with a KASAN kernel after only 01:27. This
> >> first panic was a "double fault," which isn't anything we've seen
> >> previously - usually we've seen trap 9 or trap 12, but sometimes others.
> >> Based on the backtrace, it definitely looks like KASAN caught something,
> >> but I don't have the expertise to know if this points to anything
> >> specific. From the backtrace, it looks like this might have originated
> >> in ipfw code.
> > 
> > A double fault is rather unexpected.  I presume you're running
> > releng/14.0?  Is it at all possible to test with FreeBSD-CURRENT?
> 
> This is just 14.0-RELEASE, updated to p4. Haven't played with CURRENT 
> before, but I'll give it a shot.
> 
> > 
> > Did you add INVARIANTS etc. to the kernel configuration used here, or
> > just KASAN?
> > 
> 
> This just had KASAN. Are you suggesting that I only add INVARIANTS 
> (along with KASAN), or all the various debug bits:
> options DDB
> options INVARIANT_SUPPORT
> options INVARIANTS
> options QUEUE_MACRO_DEBUG_TRASH
> options WITNESS
> options WITNESS_SKIPSPIN

Please try adding all of them.