mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] random number generator fixes for 5.17-rc3
Date: Fri,  4 Feb 2022 19:42:42 +0100	[thread overview]
Message-ID: <20220204184242.106531-1-Jason@zx2c4.com> (raw)

Hey Linus,

Please pull the following fixes for 5.17-rc3. There are a few other patches in
my tree that fix an age old crypto ~vuln, but I think I'll give those a few
more days to stew on the list before submitting. So expect to hear from me
about that next week. For this week, we have:

1) A fix to make more frequent use of hwgenerator randomness, from Dominik.

2) More cleanups to the boot initialization sequence, from Dominik.

3) A fix for an old shortcoming with the ZAP ioctl, from me.

4) A workaround for a still unfixed Clang CFI/FullLTO compiler bug, from me.
   On one hand, it's a bummer to commit workarounds for experimental compiler
   features that have bugs. But on the other, I think this actually improves
   the code somewhat, independent of the bug. So a win-win.

Thanks,
Jason

The following changes since commit 26291c54e111ff6ba87a164d85d4a4e134b7315c:

  Linux 5.17-rc2 (2022-01-30 15:37:07 +0200)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git tags/random-5.17-rc3-for-linus

for you to fetch changes up to 9d5505f1eebeca778074a0260ed077fd85f8792c:

  random: only call crng_finalize_init() for primary_crng (2022-02-04 19:22:32 +0100)

----------------------------------------------------------------
Dominik Brodowski (3):
      random: continually use hwgenerator randomness
      random: access primary_pool directly rather than through pointer
      random: only call crng_finalize_init() for primary_crng

Jason A. Donenfeld (2):
      lib/crypto: blake2s: avoid indirect calls to compression function for Clang CFI
      random: wake up /dev/random writers after zap

 arch/arm/crypto/blake2s-shash.c   |  4 ++--
 arch/x86/crypto/blake2s-shash.c   |  4 ++--
 crypto/blake2s_generic.c          |  4 ++--
 drivers/char/random.c             | 39 +++++++++++++++++++++-----------------
 include/crypto/internal/blake2s.h | 40 ++++++++++++++++++++++++---------------
 lib/crypto/blake2s.c              |  4 ++--
 6 files changed, 55 insertions(+), 40 deletions(-)

             reply	other threads:[~2022-02-04 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 18:42 Jason A. Donenfeld [this message]
2022-02-04 20:34 ` 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=20220204184242.106531-1-Jason@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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®