From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
netdev@vger.kernel.org, Alexander Graf <graf@amazon.com>,
Jann Horn <jannh@google.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [PATCH 0/3] random: wire up in-kernel virtual machine fork notifications
Date: Wed, 2 Mar 2022 00:10:35 +0100 [thread overview]
Message-ID: <20220301231038.530897-1-Jason@zx2c4.com> (raw)
As discussed, here is the notifier for learning when a virtual machine
forks, as well as a first use case for it, which is unsurprisingly
WireGuard, since I happen to know that case rather well.
The first patch is a small cleanup discovered when working on the second
patch, which is adding the actual notifier. The third case then
trivially adds it to WireGuard.
Jason A. Donenfeld (3):
random: replace custom notifier chain with standard one
random: provide notifier for VM fork
wireguard: device: clear keys on VM fork
drivers/char/random.c | 82 ++++++++++++++--------------------
drivers/net/wireguard/device.c | 27 +++++------
include/linux/random.h | 16 +++----
lib/random32.c | 12 ++---
lib/vsprintf.c | 10 +++--
5 files changed, 69 insertions(+), 78 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-01 23:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 23:10 Jason A. Donenfeld [this message]
2022-03-01 23:10 ` [PATCH 1/3] random: replace custom notifier chain with standard one Jason A. Donenfeld
2022-03-02 5:33 ` Dominik Brodowski
2022-03-02 11:42 ` Jason A. Donenfeld
2022-03-02 14:53 ` Dominik Brodowski
2022-03-01 23:10 ` [PATCH 2/3] random: provide notifier for VM fork Jason A. Donenfeld
2022-03-02 8:53 ` Greg KH
2022-03-02 11:41 ` Jason A. Donenfeld
2022-03-01 23:10 ` [PATCH 3/3] wireguard: device: clear keys on " Jason A. Donenfeld
2022-03-01 23:25 ` Jakub Kicinski
2022-03-02 8:36 ` Michael S. Tsirkin
2022-03-02 11:44 ` Jason A. Donenfeld
2022-03-02 13:06 ` Michael S. Tsirkin
2022-03-13 1:07 ` [PATCH v2] " 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=20220301231038.530897-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=graf@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).