public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Romain Francoise <romain@orebokech.com>
To: Willy Tarreau <w@1wt.eu>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, hpa@zytor.com
Subject: Re: Linux 2.6.32.60
Date: Thu, 11 Oct 2012 20:09:00 +0200	[thread overview]
Message-ID: <87vcegq3sz.fsf@silenus.orebokech.com> (raw)
In-Reply-To: <20121011062916.GG8938@1wt.eu> (Willy Tarreau's message of "Thu, 11 Oct 2012 08:29:16 +0200")

Hi Willy,

Willy Tarreau <w@1wt.eu> writes:

> RDRAND certainly qualifies as a source of entropy and I judged it was
> appropriate for a backport for this reason. Nobody has objected about
> this during the review, but maybe you have a different opinion and valid
> reasons for these patches to be reverted ?
> [...]
> 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.

I have no evidence of any problems caused by including these patches. It's
just that they don't match what I expect to find in a longterm release,
and *if* there are issues they will only show up on a limited set of
machines (Ivy Bridge or newer), so they will be more difficult to track
down.

But if you think that including the feature is worth the risk I'm totally
fine with it, it's your call to make anyway. :)

Thanks for maintaining the 2.6.32 series!
-r

  parent reply	other threads:[~2012-10-11 18:09 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
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 [this message]
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=87vcegq3sz.fsf@silenus.orebokech.com \
    --to=romain@orebokech.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --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