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:35:29 -0700 (PDT) [thread overview]
Message-ID: <20110330.033529.71582712.davem@davemloft.net> (raw)
In-Reply-To: <4D9302F3.6080206@parallels.com>
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.
I let fixes soak in Linus's tree for a week or even more before I submit
them to -stable.
next prev parent reply other threads:[~2011-03-30 10:35 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 [this message]
2011-03-30 10:45 ` Rob Landley
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=20110330.033529.71582712.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