From: Germano Massullo <germano.massullo@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: AMD RDRAND
Date: Tue, 12 Jan 2021 13:07:22 +0100 [thread overview]
Message-ID: <a4125417-7217-fbf2-5611-6742f56f6867@gmail.com> (raw)
In-Reply-To: <CAHmME9qzEYxA6uES=Mq8zUrUCogsrP_BmSasVH++_T=2VvennA@mail.gmail.com>
Il 12/01/21 00:20, Jason A. Donenfeld ha scritto:
> Hi Germano,
>
> I fixed this already, by removing the use of RDRAND from
> get_random_{u32,u64,int,long} entirely:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69efea712f5b0489e67d07565aad5c94e09a3e52
>
> This happened almost a year ago back in February, and was backported
> to the stable kernels too, which means you should have no issues
> finding a working kernel for your brand new Ryzen.
>
> Is this actually a problem you're experiencing or is your report
> mostly just speculation based on that systemd issue you linked to?
>
> Jason
Hi Jason, I did not know you already addressed the problem in the Linux
kernel, I just made a quick search in Wireguard mailing list but I did
not find any discussion related to RDRAND
I did not experience the problem (I haven't run proper tests yet), and I
haven't studied yet in detail all new replies in the thread. I just
wanted to let Wireguard developers know about this problem because I
thought it may affect Wireguard
prev parent reply other threads:[~2021-01-12 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 21:52 Germano Massullo
2021-01-11 23:20 ` Jason A. Donenfeld
2021-01-12 12:07 ` Germano Massullo [this message]
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=a4125417-7217-fbf2-5611-6742f56f6867@gmail.com \
--to=germano.massullo@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/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).