From: Greg KH <gregkh@linuxfoundation.org>
To: Jay Wang <wanjay@amazon.com>
Cc: stable@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Herbert Xu <herbert.xu@redhat.com>,
Samuel Mendoza-Jonas <samjonas@amazon.com>,
Elena Avila <ellavila@amazon.com>
Subject: Re: [PATCH 1/2] crypto: rng - Override drivers/char/random in FIPS mode
Date: Sat, 28 Jun 2025 07:11:59 +0100 [thread overview]
Message-ID: <2025062832-gleaming-tamer-fe0a@gregkh> (raw)
In-Reply-To: <20250628042918.32253-2-wanjay@amazon.com>
On Sat, Jun 28, 2025 at 04:29:17AM +0000, Jay Wang wrote:
> From: Herbert Xu <herbert.xu@redhat.com>
>
> Upstream: RHEL only
> Bugzilla: 1984784
>
> This patch overrides the drivers/char/random RNGs with the FIPS
> RNG from Crypto API when FIPS mode is enabled.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Herbert Xu <herbert.xu@redhat.com>
> (cherry picked from commit 37e0042aaf43d4494bcbea2113605366d0fe6187)
This id is not in Linus's tree, so why is this here?
Are you sure you ment to send this series out? Have you read the stable
kernel rules?
confused,
greg k-h
next prev parent reply other threads:[~2025-06-28 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 4:29 [PATCH 6.12.y 0/2] crypto: rng - FIPS 140-3 compliance for random number generation Jay Wang
2025-06-28 4:29 ` [PATCH 1/2] crypto: rng - Override drivers/char/random in FIPS mode Jay Wang
2025-06-28 6:11 ` Greg KH [this message]
2025-06-28 15:14 ` kernel test robot
2025-06-28 4:29 ` [PATCH 2/2] Override drivers/char/random only after FIPS-mode RNGs become available Jay Wang
2025-06-28 6:12 ` Greg KH
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=2025062832-gleaming-tamer-fe0a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=ellavila@amazon.com \
--cc=herbert.xu@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samjonas@amazon.com \
--cc=stable@vger.kernel.org \
--cc=wanjay@amazon.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