linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-crypto <linux-crypto@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"Ted Ts'o" <tytso@mit.edu>, Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 1/2] random: always call random ready function
Date: Thu, 19 Oct 2017 23:12:12 +0200	[thread overview]
Message-ID: <CAHmME9oQRTo9b8g+mXuRjjTNMwzfW=u-C-yVDbSo=LERrd7omg@mail.gmail.com> (raw)
In-Reply-To: <CAGXu5jJ_A11aCw04rJ2ktAG+OCL0RiXXGx387mgdHwhUe4P-=A@mail.gmail.com>

Good tips, thanks. I'll wait for more comments before resubmitting v2,
but in-progress changes live here:
https://git.zx2c4.com/linux-dev/log/?h=jd/cleaner-add-random-ready

  reply	other threads:[~2017-10-19 21:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 21:30 [PATCH v5] printk: hash addresses printed with %p Tobin C. Harding
2017-10-18 22:31 ` Kees Cook
2017-10-18 23:45   ` Tobin C. Harding
2017-10-19  1:03 ` Jason A. Donenfeld
2017-10-19  1:31   ` Sergey Senozhatsky
2017-10-19  1:36     ` Jason A. Donenfeld
2017-10-19  1:44       ` Tobin C. Harding
2017-10-19  5:49         ` Jason A. Donenfeld
2017-10-19 17:18           ` Kees Cook
2017-10-19 17:30             ` Jason A. Donenfeld
2017-10-19 20:45               ` [PATCH 1/2] random: always call random ready function Jason A. Donenfeld
2017-10-19 20:45                 ` [PATCH 2/2] crypto/drbg: account for no longer returning -EALREADY Jason A. Donenfeld
2017-10-21 19:22                   ` Stephan Mueller
2017-10-19 20:45                 ` [PATCH 1/2] random: always call random ready function Jason A. Donenfeld
2017-10-19 20:58                 ` Kees Cook
2017-10-19 21:12                   ` Jason A. Donenfeld [this message]
2017-10-22 23:32           ` [PATCH v5] printk: hash addresses printed with %p Tobin C. Harding

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='CAHmME9oQRTo9b8g+mXuRjjTNMwzfW=u-C-yVDbSo=LERrd7omg@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=keescook@chromium.org \
    --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 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).