linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Plumb <lkml.mplumb@gmail.com>
To: Willy Tarreau <w@1wt.eu>, Linus Torvalds <torvalds@linux-foundation.org>
Cc: Amit Klein <aksecurity@gmail.com>, George Spelvin <lkml@sdf.org>,
	Eric Dumazet <edumazet@google.com>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	Andy Lutomirski <luto@kernel.org>,
	Kees Cook <keescook@chromium.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Theodore Ts'o <tytso@mit.edu>, Florian Westphal <fw@strlen.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] prandom32 changes for v5.10
Date: Wed, 21 Oct 2020 13:52:51 -0700	[thread overview]
Message-ID: <6700002d-e775-4c6b-5ebc-2d6a872f1a62@gmail.com> (raw)
In-Reply-To: <20201021032725.GB396@1wt.eu>

As one of the participants, I mostly backed off when Spelvin seemed to 
be more aggressively driving a secure solution. I still think that this 
is an important change, both to fix the original network vulnerability 
and to avoid harming dev/random while doing it. I greatly appreciate 
your time and effort on this but didn't want too much chatter on the DL.


On 2020-10-20 8:27 p.m., Willy Tarreau wrote:
> Hi Linus,
>
> On Tue, Oct 20, 2020 at 04:08:03PM -0700, Linus Torvalds wrote:
>> On Tue, Oct 20, 2020 at 12:26 PM Amit Klein <aksecurity@gmail.com> wrote:
>>> Quick question: is this patch still planned for inclusion in 5.10-rc1?
>> It doesn't even build for me, so no. It clearly hasn't been in
>> linux-next or anything like that.
>>
>> Hint: grep for prandom_seed_early.
> I'm a bit surprised, as it worked for me, but thanks for checking. Given
> the lack of responses from many participants on these patches, on several
> occations I feel that this series is really not welcome. Initially I just
> tried to test and fix Spelvin's patch, but if there's not that much
> interest in it, or even reluctance, I'd rather stop. If it's just that
> the current state is ugly with the two PRNGs side by side, I can get
> back to completely removing the original one as I did in my first series,
> and propose a larger series. Or if nobody's interested, I'd rather know
> so that I don't have to put more time on it :-/
>
> Thanks for letting me know,
> Willy

  reply	other threads:[~2020-10-21 20:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 20:32 [GIT PULL] prandom32 changes for v5.10 Willy Tarreau
     [not found] ` <CANEQ_+Jyf-MZEsvT5iMu0a=waJCiAKdLaOfLHe_py6AXOt-hjQ@mail.gmail.com>
2020-10-20 23:08   ` Linus Torvalds
2020-10-21  3:27     ` Willy Tarreau
2020-10-21 20:52       ` Marc Plumb [this message]
2020-10-21 21:20         ` Joe Perches
2020-10-21 21:35           ` Linus Torvalds
2020-10-21 21:41             ` Joe Perches
2020-10-22  2:12               ` Willy Tarreau
2020-10-24 19:34 Willy Tarreau
2020-10-25 18:35 ` pr-tracker-bot

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=6700002d-e775-4c6b-5ebc-2d6a872f1a62@gmail.com \
    --to=lkml.mplumb@gmail.com \
    --cc=Jason@zx2c4.com \
    --cc=aksecurity@gmail.com \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@sdf.org \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --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;
as well as URLs for NNTP newsgroup(s).