[Bug 201700] netstat -s segmentation fault after pfkey section

2015-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201700 Bug ID: 201700 Summary: netstat -s segmentation fault after pfkey section Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New

[Bug 201700] netstat -s segmentation fault after pfkey section

2015-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201700 Mark Johnston ma...@freebsd.org changed: What|Removed |Added CC||ma...@freebsd.org

[Bug 201700] netstat -s segmentation fault after pfkey section

2015-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201700 Mark Johnston ma...@freebsd.org changed: What|Removed |Added Attachment #158989|0 |1 is

[Bug 201700] netstat -s segmentation fault after pfkey section

2015-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201700 --- Comment #3 from Jason Unovitch jason.unovi...@gmail.com --- (In reply to Mark Johnston from comment #2) Mark, Thanks again for the quick response! Your patch worked for me for what I opened the PR for. This was on the following

[Bug 201700] netstat -s segmentation fault after pfkey section

2015-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201700 --- Comment #4 from Jason Unovitch jason.unovi...@gmail.com --- (In reply to Jason Unovitch from comment #3) Regarding the output... does this look a sign of another issue with random memory being read? histogram by message type:

[Bug 201700] netstat -s segmentation fault after pfkey section

2015-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201700 Mark Johnston ma...@freebsd.org changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|ma...@freebsd.org

[Bug 201700] netstat -s segmentation fault after pfkey section

2015-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201700 --- Comment #5 from Mark Johnston ma...@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