From: David Miller <davem@davemloft.net>
To: rlandley@parallels.com
Cc: linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org, netdev@vger.kernel.org,
stable@kernel.org
Subject: Re: 2.6.38 containers bug: Infinite loop in /proc/sys/net/ipv6/neigh/neigh/neigh...
Date: Wed, 30 Mar 2011 03:48:20 -0700 (PDT) [thread overview]
Message-ID: <20110330.034820.124005354.davem@davemloft.net> (raw)
In-Reply-To: <4D9309B4.2000501@parallels.com>
From: Rob Landley <rlandley@parallels.com>
Date: Wed, 30 Mar 2011 05:45:08 -0500
> So you think letting it soak in the merge window and the churn of -rc1
> (which currently doesn't boot for me due to an ide issue) will provide
> more validity than a specific "There was an infinite loop in the
> filesystem, there is now no longer an infinite loop in the filesystem,
> here's the specific test for it" and visual inspection ofthe patch?
Yes I absolutely do think it's better to let it soak somewhere than
to repeat the reason why this patch is necessary in the first place.
This patch is necessary because Eric already screwed up trying to fix
this neigh dirctory under ipv6 once, and he got it wrong.
That patch looked correct and straightforward.
Yet it introduced the bug you're seeing.
Given that consideration, are you still holding steady to your
opinion wise guy? :-)
next prev parent reply other threads:[~2011-03-30 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D92E9DC.3070405@parallels.com>
2011-03-30 9:01 ` 2.6.38 containers bug: Infinite loop in /proc/sys/net/ipv6/neigh/neigh/neigh David Miller
2011-03-30 10:16 ` Rob Landley
2011-03-30 10:35 ` David Miller
2011-03-30 10:45 ` Rob Landley
2011-03-30 10:48 ` David Miller [this message]
2011-03-30 11:27 ` Rob Landley
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=20110330.034820.124005354.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rlandley@parallels.com \
--cc=stable@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