From: Rob Landley <rlandley@parallels.com>
To: David Miller <davem@davemloft.net>
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 05:45:08 -0500 [thread overview]
Message-ID: <4D9309B4.2000501@parallels.com> (raw)
In-Reply-To: <20110330.033529.71582712.davem@davemloft.net>
On 03/30/2011 05:35 AM, David Miller wrote:
> From: Rob Landley <rlandley@parallels.com>
> Date: Wed, 30 Mar 2011 05:16:19 -0500
>
>> Pinging the stable guys to make sure this goes in a dot release.
>
> Please do not do this.
Too late, but presumably they got your NAK.
> I let fixes soak in Linus's tree for a week or even more before I submit
> them to -stable.
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?
*shrug* I hear what you say. It's certainly a point of view.
Rob
next prev parent reply other threads:[~2011-03-30 10:45 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 [this message]
2011-03-30 10:48 ` David Miller
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=4D9309B4.2000501@parallels.com \
--to=rlandley@parallels.com \
--cc=containers@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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