[Bug 268246] crash and panic using pfsync on 13.1-RELEASE

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 08 Dec 2022 16:13:57 UTC

--- Comment #2 from Kristof Provost <kp@freebsd.org> ---
I've not seen that panic before.

It's indeed related to pfsync. pfsyncintr() is in pfsync's output path, and it
seems to be in the process of sending a packet out, during which ip_fragment()
ends up apparently dereferencing a NULL pointer.

It's not immediately obvious how this'd happen.

A few bit of extra information to gather: ifconfig output for pfsync0 and
whatever interface it's using as syndev. (I'm especially interested in MTU
mismatches, but let's get the full output.)

Given that you have a core dump it'd also be good if you could run it through
kgdb (kgdb /boot/kernel/kernel /var/crash/vmcore.last) and get a backtrace (bt)
for starters. Hang on to the core dump, because odds are we're going to want to
look at more things later.

You are receiving this mail because:
You are the assignee for the bug.