From: David Miller <davem@davemloft.net>
To: laurent.riffard@free.fr
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: 2.6.23-rc[68]-mm: network hangs
Date: Sat, 29 Sep 2007 02:35:10 -0700 (PDT) [thread overview]
Message-ID: <20070929.023510.112596666.davem@davemloft.net> (raw)
In-Reply-To: <46FE193E.60200@free.fr>
From: Laurent Riffard <laurent.riffard@free.fr>
Date: Sat, 29 Sep 2007 11:22:06 +0200
> Could a router problem prevent "ping 127.0.0.1" from working ?
Two things that are new and could cause these problems:
1) We dynamically allocate the loopback device now.
2) We have the network namespace stuff.
Another change in this area is that we do routing cache
garbage collection from a workqueue instead of a timer
but that was a pretty straightforward transformation so
it is not high on my list of "suspects".
prev parent reply other threads:[~2007-09-29 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 19:48 2.6.23-rc[68]-mm: network hangs Laurent Riffard
2007-09-29 8:31 ` Andrew Morton
2007-09-29 9:22 ` Laurent Riffard
2007-09-29 9:35 ` David Miller [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=20070929.023510.112596666.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=laurent.riffard@free.fr \
--cc=linux-kernel@vger.kernel.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).