public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: <netdev@vger.kernel.org>, <cate@cateee.net>
Subject: Re: Fwd: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt
Date: Fri, 23 May 2014 11:15:51 +0200	[thread overview]
Message-ID: <20140523091551.GI32371@secunet.com> (raw)
In-Reply-To: <537F09EE.5000703@redhat.com>

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")

      reply	other threads:[~2014-05-23  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140523091551.GI32371@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=cate@cateee.net \
    --cc=dborkman@redhat.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox