From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-hardening@lists.openwall.com
Subject: Re: [PATCH RFC v2 0/8] get_random_bytes_wait family of APIs
Date: Tue, 6 Jun 2017 14:24:33 +0200 [thread overview]
Message-ID: <CAHmME9rAH5Qj5naSOWEMSaaR7YrP03UnYzeoQJA-0QF9jnPaRg@mail.gmail.com> (raw)
In-Reply-To: <20170606074552.GA10432@kroah.com>
On Tue, Jun 6, 2017 at 9:45 AM, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
> If it's needed no matter what, can you make it the first patch in the
> series? And does it need to go to any older kernels as well?
I believe it does belong in older kernels too. I'll work out precisely
which one those are and note it in the commit, which I'll order as the
first in the series and Cc to stable@. This is, of course, pending
Ted's review.
WARNING: multiple messages have this Message-ID (diff)
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Re: [PATCH RFC v2 0/8] get_random_bytes_wait family of APIs
Date: Tue, 6 Jun 2017 14:24:33 +0200 [thread overview]
Message-ID: <CAHmME9rAH5Qj5naSOWEMSaaR7YrP03UnYzeoQJA-0QF9jnPaRg@mail.gmail.com> (raw)
In-Reply-To: <20170606074552.GA10432@kroah.com>
On Tue, Jun 6, 2017 at 9:45 AM, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
> If it's needed no matter what, can you make it the first patch in the
> series? And does it need to go to any older kernels as well?
I believe it does belong in older kernels too. I'll work out precisely
which one those are and note it in the commit, which I'll order as the
first in the series and Cc to stable@. This is, of course, pending
Ted's review.
next prev parent reply other threads:[~2017-06-06 12:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 3:47 [PATCH RFC v2 0/8] get_random_bytes_wait family of APIs Jason A. Donenfeld
2017-06-05 3:47 ` [kernel-hardening] " Jason A. Donenfeld
2017-06-05 3:47 ` [PATCH RFC v2 1/8] random: add synchronous API for the urandom pool Jason A. Donenfeld
2017-06-05 3:47 ` [kernel-hardening] " Jason A. Donenfeld
2017-06-05 3:47 ` [PATCH RFC v2 2/8] random: add get_random_{bytes,u32,u64,int,long,once}_wait family Jason A. Donenfeld
2017-06-05 3:47 ` [kernel-hardening] " Jason A. Donenfeld
2017-06-05 3:47 ` [PATCH RFC v2 3/8] random: warn when kernel uses unseeded randomness Jason A. Donenfeld
2017-06-05 3:47 ` [kernel-hardening] " Jason A. Donenfeld
2017-06-05 3:47 ` [PATCH RFC v2 4/8] crypto/rng: ensure that the RNG is ready before using Jason A. Donenfeld
2017-06-05 3:47 ` [kernel-hardening] " Jason A. Donenfeld
2017-06-05 3:47 ` [PATCH RFC v2 5/8] security/keys: ensure RNG is seeded before use Jason A. Donenfeld
2017-06-05 3:47 ` [kernel-hardening] " Jason A. Donenfeld
2017-06-05 23:18 ` Jason A. Donenfeld
2017-06-05 23:18 ` [kernel-hardening] " Jason A. Donenfeld
2017-06-05 3:47 ` [PATCH RFC v2 6/8] iscsi: " Jason A. Donenfeld
2017-06-05 3:47 ` [kernel-hardening] " Jason A. Donenfeld
2017-06-05 3:47 ` [PATCH RFC v2 7/8] bluetooth/smp: ensure RNG is properly seeded before ECDH use Jason A. Donenfeld
2017-06-05 3:47 ` [kernel-hardening] " Jason A. Donenfeld
2017-06-05 3:47 ` [PATCH RFC v2 8/8] ceph: ensure RNG is seeded before using Jason A. Donenfeld
2017-06-05 3:47 ` [kernel-hardening] " Jason A. Donenfeld
2017-06-05 23:47 ` [PATCH RFC v2 0/8] get_random_bytes_wait family of APIs Jason A. Donenfeld
2017-06-05 23:47 ` [kernel-hardening] " Jason A. Donenfeld
2017-06-06 7:45 ` Greg Kroah-Hartman
2017-06-06 7:45 ` [kernel-hardening] " Greg Kroah-Hartman
2017-06-06 12:24 ` Jason A. Donenfeld [this message]
2017-06-06 12:24 ` Jason A. Donenfeld
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=CAHmME9rAH5Qj5naSOWEMSaaR7YrP03UnYzeoQJA-0QF9jnPaRg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.