Bug 76781 - unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt
Summary: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt
Status: RESOLVED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Networking
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: Stephen Hemminger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-23 07:07 UTC by Giacomo Catenazzi
Modified: 2014-06-03 05:33 UTC (History)
0 users

See Also:
Kernel Version: 3.15.0-rc6
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Giacomo Catenazzi 2014-05-23 07:07:40 UTC 
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.
Comment 1 Giacomo Catenazzi 2014-06-03 05:33:30 UTC 
As answered in netdev mailing list, the following commits (now merged) should solve the problem:

commit edb666f07e ("xfrm6: Properly handle unsupported protocols")
commit 61622cc6f2 ("xfrm4: Properly handle unsupported protocols")

Because I had no more the bug since many days, I really think it was solved by above commits, so I'm closing the bug.
Note You need to log in before you can comment on or make changes to this bug.