Date: Tue, 30 Jun 2020 16:04:12 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 246951] carp(4): Active CARP member crashes: panic, trap_pfault, ip_input || ip_output when using ipSec, AES-NI (on Intel I350) Message-ID: <bug-246951-7501-n854dIfl6j@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-246951-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-246951-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=3D246951 Ryan Moeller <freqlabs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freqlabs@FreeBSD.org --- Comment #15 from Ryan Moeller <freqlabs@FreeBSD.org> --- I have a FreeNAS bug report where ifa_addr is NULL on 11.3, too. I was suspecting some local patches we have for dealing with various IGMP / multi= cast issues, but I did not find anything in auditing those patches. I haven't fo= und any way to explain ifa_addr being NULL in an ifma that is still linked into= a list. In my user's case the panic is cropping up in igmp_fasttimo. Though the circumstances are different, I wonder if these may be caused by the same underlying problem. One thing I have thought to double-check next is making sure that the maddr locks match up with the correct ifp everywhere the list is modified. --=20 You are receiving this mail because: You are the assignee for the bug. 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-246951-7501-n854dIfl6j>