[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140523091551.GI32371@secunet.com>
Date: Fri, 23 May 2014 11:15:51 +0200
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Daniel Borkmann <dborkman@...hat.com>
CC: <netdev@...r.kernel.org>, <cate@...eee.net>
Subject: Re: Fwd: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173,
fatal exception in interrupt
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@...zilla.kernel.org
> To: dborkman@...hat.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@...ux-foundation.org
> Reporter: cate@...eee.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")
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists