netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <dborkman@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	netdev@vger.kernel.org
Subject: Re: Fw: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt
Date: Wed, 28 May 2014 23:34:19 +0200	[thread overview]
Message-ID: <5386565B.7060209@redhat.com> (raw)
In-Reply-To: <1401312501.3645.18.camel@edumazet-glaptop2.roam.corp.google.com>

On 05/28/2014 11:28 PM, Eric Dumazet wrote:
> On Wed, 2014-05-28 at 14:01 -0700, Stephen Hemminger wrote:
>>
>> Begin forwarded message:
>>
>> Date: Fri, 23 May 2014 00:07:48 -0700
>> From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
>> To: "stephen@networkplumber.org" <stephen@networkplumber.org>
>> Subject: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt
>>
>>
>> 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.
>
> Right, commit 61622cc6f29034d0 is buggy.

Steffen already replied some days ago here:

   http://www.spinics.net/lists/netdev/msg283705.html

  reply	other threads:[~2014-05-28 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28 21:01 Fw: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt Stephen Hemminger
2014-05-28 21:28 ` Eric Dumazet
2014-05-28 21:34   ` Daniel Borkmann [this message]
2014-05-28 21:37   ` Eric Dumazet

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=5386565B.7060209@redhat.com \
    --to=dborkman@redhat.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    --cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).