public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Greg KH <greg@kroah.com>, Romain Francoise <romain@orebokech.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 2.6.32.60
Date: Fri, 12 Oct 2012 07:11:12 +0800	[thread overview]
Message-ID: <50775210.4060007@zytor.com> (raw)
In-Reply-To: <20121011113106.GR8938@1wt.eu>

On 10/11/2012 07:31 PM, Willy Tarreau wrote:
> On Thu, Oct 11, 2012 at 07:58:04PM +0900, Greg KH wrote:
>> On Thu, Oct 11, 2012 at 08:29:16AM +0200, Willy Tarreau wrote:
>>> If you think these patches constitute a regression, I can revert them.
>>> However I'd like convincing arguments since they're here to help address
>>> a real issue.
>>
>> If I missed these when doing the random number generation backport for
>> 3.0, and I should add them there as well, please let me know.
> 
> At least I think they should not be in 2.6.32 without being in 3.0.
> Probably that Peter's opinion will help us decide whether they should
> go into 3.0 or 2.6.32 should revert them.
> 

I would strongly argue for at least one of the RDRAND-enabling versions
being in all supported kernels; the second (with Ted Ts'o's changes) is
better, but touches a *lot* of subsystems; the plain one is
self-contained but only helps RDRAND-enabled hardware.

Without these patches the random subsystem has a critical security flaw,
which puts it into the scope for stable.

	-hpa




  reply	other threads:[~2012-10-11 23:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09  9:44 Linux 2.6.32.60 Willy Tarreau
2012-10-10 14:05 ` Romain Francoise
2012-10-11  6:29   ` Willy Tarreau
2012-10-11 10:58     ` Greg KH
2012-10-11 11:31       ` Willy Tarreau
2012-10-11 23:11         ` H. Peter Anvin [this message]
2012-10-12  6:38           ` Willy Tarreau
2012-10-12  6:42             ` Greg KH
2012-10-17 21:46             ` Greg KH
2012-10-11 18:09     ` Romain Francoise
2012-10-11 18:29       ` Willy Tarreau

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=50775210.4060007@zytor.com \
    --to=hpa@zytor.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romain@orebokech.com \
    --cc=stable@vger.kernel.org \
    --cc=w@1wt.eu \
    /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