From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Theodore Ts'o" <tytso@mit.edu>, LKML <linux-kernel@vger.kernel.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [PATCH cleanups/resubmit 0/4] Cleanups & Resubmissions for Random-dev
Date: Thu, 8 Jun 2017 14:29:28 +0200 [thread overview]
Message-ID: <20170608122932.23769-1-Jason@zx2c4.com> (raw)
Hi Ted,
I'm not super sure what your workflow is like, but yesterday you picked
up my v4 instead of my v5, and as you applied the wrong commits, I sent
you several emails notifying you, along with quick fixes to various issues,
which you also did not see. I assume you have complicated email filters,
or maybe something like offlineimap where you grab snapshots of email,
and thus the only way to make an impact on an in-motion workflow is for me
to just formally resubmit things. So, here's a summary of what's in here:
security/keys: ensure RNG is seeded before use
You had noticed an issue with this in v4/v5, so now this is cleaned up
the way you suggested so that you can merge it.
random: squelch sh compiler warning and ensure safe optimization
This was the biggie -- I had incorporated this fix into v5, but you picked
up v4, so this commit is an additional one to bring your tree up to date,
without having to rebase or rewrite history.
bluetooth/smp: ensure RNG is properly seeded before ECDH use
This one is pending your approval from the bluetooth people.
crypto/rng: ensure that the RNG is ready before using
This one I assume you didn't pick up because it depends on my big_keys
rewrite going through.
Sorry for the procedural back-and-forth. If there's a way to do this flow
better next time, do tell me what it is. Alternatively, if you're ever on
IRC, realtime chat could be useful.
Regards,
Jason
crypto/rng.c | 6 ++++--
drivers/char/random.c | 8 ++++----
net/bluetooth/hci_request.c | 6 ++++++
net/bluetooth/smp.c | 18 ++++++++++++++----
security/keys/encrypted-keys/encrypted.c | 8 +++++---
security/keys/key.c | 8 +++-----
6 files changed, 36 insertions(+), 18 deletions(-)
--
2.13.0
next reply other threads:[~2017-06-08 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 12:29 Jason A. Donenfeld [this message]
2017-06-08 12:29 ` [PATCH cleanups/resubmit 1/4] security/keys: ensure RNG is seeded before use Jason A. Donenfeld
2017-06-08 12:29 ` [PATCH cleanups/resubmit 2/4] random: squelch sh compiler warning and ensure safe optimization Jason A. Donenfeld
2017-06-08 12:29 ` [PATCH cleanups/resubmit 3/4] bluetooth/smp: ensure RNG is properly seeded before ECDH use Jason A. Donenfeld
2017-06-08 12:29 ` [PATCH cleanups/resubmit 4/4] crypto/rng: ensure that the RNG is ready before using Jason A. Donenfeld
2017-06-08 21:58 ` [PATCH cleanups/resubmit 0/4] Cleanups & Resubmissions for Random-dev Theodore Ts'o
2017-06-09 0:57 ` Jason A. Donenfeld
2017-06-09 17:44 ` 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=20170608122932.23769-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--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
all inboxes | Powered by JetHome®