Date: Mon, 20 Jul 2015 02:32:38 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 201700] netstat -s segmentation fault after pfkey section Message-ID: <bug-201700-8-j2zYYUE8yP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-201700-8@https.bugs.freebsd.org/bugzilla/> References: <bug-201700-8@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=201700 --- Comment #5 from Mark Johnston <markj@FreeBSD.org> --- (In reply to Jason Unovitch from comment #4) That's quite interesting. I don't see that on my workstation (all counters are 0), but I tried booting up an i386 VM with IPSEC enabled in the kernel, and lo and behold: pfkey: 0 requests sent from userland 0 bytes sent from userland 0 messages with invalid length field 0 messages with invalid version field 0 messages with invalid message type field 0 messages too short 0 messages with memory allocation failure 0 messages with duplicate extension 0 messages with invalid extension type 0 messages with invalid sa type 0 messages with invalid address extension 0 requests sent to userland 0 bytes sent to userland histogram by message type: #164: 8513580559518937276 0 messages toward single socket 0 messages toward all sockets 0 messages toward registered sockets 0 messages with memory allocation failure I don't see any obvious problems on the userland side of things. Given that this is happening at the same index on both of our systems, it seems more likely that this is a kernel issue. I'll try and track it down. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201700-8-j2zYYUE8yP>