[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1y6t0nlle.fsf@fess.ebiederm.org>
Date: Thu, 14 May 2009 01:18:53 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Daniel Lezcano <daniel.lezcano@...e.fr>
Cc: netdev@...r.kernel.org, "Denis V. Lunev" <den@...nvz.org>
Subject: Re: Kernel panic in inet_twdr_do_twkill_work
Daniel Lezcano <daniel.lezcano@...e.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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists