netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 02 Jun 2009 17:40:28 -0700	[thread overview]
Message-ID: <m1r5y2jgjn.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4A194B09.7070900@free.fr> (Daniel Lezcano's message of "Sun\, 24 May 2009 15\:26\:33 +0200")

Daniel Lezcano <daniel.lezcano@free.fr> writes:

> Eric W. Biederman wrote:
>> Daniel Lezcano <daniel.lezcano@free.fr> writes:
>>
>>   
>>> May be you can activate the NETNS_REFCNT_DEBUG in order to check if the timewait
>>> socket
>>> were destroyed at the namespace destruction ? Unfortunately it looks like the
>>> option is not in the Kconfig :(
>>>     
>>
>> Looks like a good starting place.
>>
>> I will enable that when I respin my internal kernel.
>>
>> I don't have a good reproducer at the moment....  So I was hoping we could
>> figure this out with code inspection.
>>   
> Hi Eric,
>
> did you succeeded to reproduce the bug with the test program I sent you ?

Weird.  I finally got around to running your little test app, and I don't trigger
it here.

At the same time I am starting to see what I think is this error more often.

Eric

      parent reply	other threads:[~2009-06-03  0:40 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
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 [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=m1r5y2jgjn.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).