From: ebiederm@xmission.com (Eric W. Biederman)
To: Daniel Lezcano <daniel.lezcano@free.fr>
Cc: netdev@vger.kernel.org, "Denis V. Lunev" <den@openvz.org>
Subject: Re: Kernel panic in inet_twdr_do_twkill_work
Date: Thu, 14 May 2009 01:18:53 -0700 [thread overview]
Message-ID: <m1y6t0nlle.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4A0BCE0E.3000206@free.fr> (Daniel Lezcano's message of "Thu\, 14 May 2009 09\:53\:50 +0200")
Daniel Lezcano <daniel.lezcano@free.fr> writes:
> Eric W. Biederman wrote:
>> So far I have only seen this twice. But the backtrace looks
>> almost identical to the one in commit d315492b1a6ba29da0fa2860759505ae1b2db857
>>
>> The kernels I saw this on were patched version of 2.6.28 with some
>> network namespace backports. commit
>> d315492b1a6ba29da0fa2860759505ae1b2db857 was definitely present.
>>
>> Daniel any ideas?
>>
> Hi Eric,
>
> I found this one. May be it could be related to your problem:
>
> commit 2bad35b7c9588eb5e65c03bcae54e7eb6b1a6504
>
> Let me know :)
"netns: oops in ip[6]_frag_reasm incrementing stats" does not look likely.
There is no real ipv6 traffic currently on the our network and the panic
is definitely in inet_twdr_do_twkill_work.
Further we are getting the net of a timewait socket. So I don't see how
a problem with NULL devs could have anything to do with it.
I really suspect the purge code is not being successful.
Eric
next prev parent reply other threads:[~2009-05-14 8:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 1:22 Kernel panic in inet_twdr_do_twkill_work Eric W. Biederman
2009-05-14 7:53 ` Daniel Lezcano
2009-05-14 8:18 ` Eric W. Biederman [this message]
2009-05-14 8:33 ` Daniel Lezcano
2009-05-14 9:13 ` Eric W. Biederman
2009-05-14 9:21 ` Daniel Lezcano
2009-05-14 9:42 ` Daniel Lezcano
2009-05-24 13:26 ` Daniel Lezcano
2009-05-24 13:54 ` Eric W. Biederman
2009-06-03 0:40 ` Eric W. Biederman
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=m1y6t0nlle.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=daniel.lezcano@free.fr \
--cc=den@openvz.org \
--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;
as well as URLs for NNTP newsgroup(s).