[Bug 203409] page fault in tcp_do_segment (r287759 suspected)

2015-09-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203409 Hiren Panchasara changed: What|Removed |Added Assignee|freebsd-net@FreeBSD.org |g...@freebsd.org --- Comment #2

[Bug 203409] page fault in tcp_do_segment (r287759 suspected)

2015-09-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203409 --- Comment #1 from Andriy Gapon --- Created attachment 161483 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=161483&action=edit fix / work-around The attached trivial patch seems to make the issue go away. But I am not sure if

[Bug 203409] page fault in tcp_do_segment (r287759 suspected)

2015-09-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203409 Andriy Gapon changed: What|Removed |Added CC||g...@freebsd.org Assignee

Re: page fault in tcp_do_segment (r287759 suspected)

2015-09-23 Thread Adrian Chadd
Yes, file a bug. :) -a On 23 September 2015 at 00:11, Andriy Gapon wrote: > On 22/09/2015 11:33, Andriy Gapon wrote: >> That code actually looks like the following DTrace probe a few lines below: >> >> TCP_PROBE3(debug__input, tp, th, mtod(m, const char *)); >> >> So, it seems like 'm' could b

Re: page fault in tcp_do_segment (r287759 suspected)

2015-09-23 Thread Andriy Gapon
On 22/09/2015 11:33, Andriy Gapon wrote: > That code actually looks like the following DTrace probe a few lines below: > > TCP_PROBE3(debug__input, tp, th, mtod(m, const char *)); > > So, it seems like 'm' could be NULL here. > I see two places in tcp_do_segment() where m gets assigned with NULL

page fault in tcp_do_segment (r287759 suspected)

2015-09-22 Thread Andriy Gapon
I've just got the following panic on amd64 r288066. I never experienced that kind of panic with r286985. Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x10 fault code = supervisor read data, page not present instruction pointer