From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Luca Tettamanti <kronos.it@gmail.com>,
netdev@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [Bug #13838] kernel BUG at include/net/netns/generic.h:41!
Date: Mon, 27 Jul 2009 13:29:50 +0800 [thread overview]
Message-ID: <2375c9f90907262229t2def934emb9340c31d3efdc21@mail.gmail.com> (raw)
In-Reply-To: <3zAHs5O6maO.A.B5B.IHObKB@chimera>
On Mon, Jul 27, 2009 at 4:28 AM, Rafael J. Wysocki<rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.30. Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13838
> Subject : kernel BUG at include/net/netns/generic.h:41!
> Submitter : Luca Tettamanti <kronos.it@gmail.com>
> Date : 2009-07-20 15:27 (7 days old)
> References : http://lkml.org/lkml/2009/7/20/105
Hmm, it looks like that 'pfkey_net_id' is still zero after ipsec_pfkey_init()...
Add Herbert and net-dev into Cc.
Luca, would you mind to provide your .config and the steps to reproduce this?
Thanks.
next prev parent reply other threads:[~2009-07-27 5:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 20:23 2.6.31-rc4: Reported regressions from 2.6.30 Rafael J. Wysocki
2009-07-26 20:28 ` [Bug #13835] e1000e massive packet loss Rafael J. Wysocki
[not found] ` <3zAHs5O6maO.A.B5B.IHObKB@chimera>
2009-07-27 5:29 ` Américo Wang [this message]
[not found] ` <2375c9f90907262229t2def934emb9340c31d3efdc21-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-28 8:30 ` [Bug #13838] kernel BUG at include/net/netns/generic.h:41! Luca Tettamanti
2009-07-28 12:46 ` 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=2375c9f90907262229t2def934emb9340c31d3efdc21@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-testers@vger.kernel.org \
--cc=kronos.it@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).