* Fwd: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt
[not found] <bug-76781-65011@https.bugzilla.kernel.org/>
@ 2014-05-23 8:42 ` Daniel Borkmann
2014-05-23 9:15 ` Steffen Klassert
0 siblings, 1 reply; 2+ messages in thread
From: Daniel Borkmann @ 2014-05-23 8:42 UTC (permalink / raw)
To: netdev; +Cc: steffen.klassert, cate
-------- Original Message --------
Subject: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt
Date: Fri, 23 May 2014 07:07:40 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: dborkman@redhat.com
https://bugzilla.kernel.org/show_bug.cgi?id=76781
Bug ID: 76781
Summary: unable to handle NULL in xfrm_input+0x173, fatal
exception in interrupt
Product: Networking
Version: 2.5
Kernel Version: 3.15.0-rc6
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: shemminger@linux-foundation.org
Reporter: cate@cateee.net
Regression: No
See also the fatal oops in:
http://cateee.net/kernel/IMG_20140522_225238.jpg
http://cateee.net/kernel/IMG_20140523_082629.jpg
It seems it happens "often": twice in last few hours I used the new kernels.
(the first oops was with 3.15.0-rc5-00270-gfba69f0)
I had also usual debian unstable updates, and I just finished to instal aiccu
(a sixxs program for dynamic ip6to4, so I'm not sure it is a recent bug or just
I forced it to appear in very last HEAD.
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Fwd: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt
2014-05-23 8:42 ` Fwd: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt Daniel Borkmann
@ 2014-05-23 9:15 ` Steffen Klassert
0 siblings, 0 replies; 2+ messages in thread
From: Steffen Klassert @ 2014-05-23 9:15 UTC (permalink / raw)
To: Daniel Borkmann; +Cc: netdev, cate
On Fri, May 23, 2014 at 10:42:22AM +0200, Daniel Borkmann wrote:
>
> -------- Original Message --------
> Subject: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt
> Date: Fri, 23 May 2014 07:07:40 +0000
> From: bugzilla-daemon@bugzilla.kernel.org
> To: dborkman@redhat.com
>
> https://bugzilla.kernel.org/show_bug.cgi?id=76781
>
> Bug ID: 76781
> Summary: unable to handle NULL in xfrm_input+0x173, fatal
> exception in interrupt
> Product: Networking
> Version: 2.5
> Kernel Version: 3.15.0-rc6
> Hardware: x86-64
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> Assignee: shemminger@linux-foundation.org
> Reporter: cate@cateee.net
> Regression: No
>
> See also the fatal oops in:
>
> http://cateee.net/kernel/IMG_20140522_225238.jpg
> http://cateee.net/kernel/IMG_20140523_082629.jpg
>
> It seems it happens "often": twice in last few hours I used the new kernels.
> (the first oops was with 3.15.0-rc5-00270-gfba69f0)
>
> I had also usual debian unstable updates, and I just finished to instal aiccu
> (a sixxs program for dynamic ip6to4, so I'm not sure it is a recent bug or just
> I forced it to appear in very last HEAD.
>
This might be fixed by these two commits:
commit edb666f07e ("xfrm6: Properly handle unsupported protocols")
commit 61622cc6f2 ("xfrm4: Properly handle unsupported protocols")
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-05-23 9:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <bug-76781-65011@https.bugzilla.kernel.org/>
2014-05-23 8:42 ` Fwd: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt Daniel Borkmann
2014-05-23 9:15 ` Steffen Klassert
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox