From: "Theodore Ts'o" <tytso@mit.edu>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [PATCH 1/2] random: use chacha20 for get_random_int/long
Date: Sun, 22 Jan 2017 19:33:17 -0500 [thread overview]
Message-ID: <20170123003317.amscbbpxwzqsfyum@thunk.org> (raw)
In-Reply-To: <CAHmME9qeM25q9S6757-fssF5114EfOEhh20A4tZmaAnPRnwM=w@mail.gmail.com>
On Sun, Jan 22, 2017 at 11:49:00PM +0100, Jason A. Donenfeld wrote:
> On Sun, Jan 22, 2017 at 11:28 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> > If there are other changes to the relevant lines from the networking
> > tree, sure.
>
> This patch set has *nothing* to do with the networking tree. That just
> a topic confusion. There shouldn't be more discussion about
> networking, because it doesn't make sense in any way at all.
Well, the reason people do is for hysterical... er, historical
reasons. *Originaly* get_random_int() was introduced for use by the
networking folks, and some people think that get_random_int()
therefore "belongs" to the networking tree, even though there are
other users of get_random_int() and get_random_long() besides the
networking code.
I'd much rather break this obviously historical connection, but
patching people's wetware is a lot harder than getting a patch into
the kernel tree....
- Ted
next prev parent reply other threads:[~2017-01-23 0:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 18:32 Jason A. Donenfeld
2017-01-06 18:32 ` [PATCH 2/2] random: convert get_random_int/long into get_random_u32/u64 Jason A. Donenfeld
2017-01-18 3:49 ` [PATCH 1/2] random: use chacha20 for get_random_int/long Theodore Ts'o
2017-01-20 5:27 ` Jason A. Donenfeld
2017-01-20 14:28 ` Theodore Ts'o
2017-01-20 15:38 ` Jason A. Donenfeld
2017-01-21 0:10 ` Theodore Ts'o
2017-01-21 0:13 ` Jason A. Donenfeld
2017-01-20 15:47 ` Jason A. Donenfeld
2017-01-21 0:15 ` Theodore Ts'o
2017-01-21 0:16 ` Jason A. Donenfeld
2017-01-21 6:24 ` Theodore Ts'o
2017-01-21 14:08 ` Jason A. Donenfeld
2017-01-22 11:24 ` Greg Kroah-Hartman
2017-01-22 12:21 ` Jason A. Donenfeld
2017-01-22 15:20 ` Greg Kroah-Hartman
2017-01-22 15:34 ` Jason A. Donenfeld
2017-01-22 15:34 ` [PATCH 2/2] random: convert get_random_int/long into get_random_u32/u64 Jason A. Donenfeld
2017-01-22 22:28 ` [PATCH 1/2] random: use chacha20 for get_random_int/long Theodore Ts'o
2017-01-22 22:49 ` Jason A. Donenfeld
2017-01-23 0:33 ` Theodore Ts'o [this message]
2017-01-23 8:12 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2016-12-22 18:07 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=20170123003317.amscbbpxwzqsfyum@thunk.org \
--to=tytso@mit.edu \
--cc=Jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
/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
all inboxes | Powered by JetHome®