From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
Jeff Barnes <jeffbarnes@microsoft.com>,
Vladis Dronov <vdronov@redhat.com>,
"marcelo.cerri@canonical.com" <marcelo.cerri@canonical.com>,
Tyler Hicks <Tyler.Hicks@microsoft.com>,
Shyam Saini <shyamsaini@microsoft.com>
Subject: Re: Intermittent EHEALTH Failure in FIPS Mode - jitterentropy jent_entropy_init() in Kernel 6.6.14
Date: Thu, 08 Aug 2024 08:13:56 +0200 [thread overview]
Message-ID: <2416186.INgNo8UaUA@tauon.atsec.com> (raw)
In-Reply-To: <ZrRhR-IRZPrQ5DSe@gondor.apana.org.au>
Am Donnerstag, 8. August 2024, 08:10:15 MESZ schrieb Herbert Xu:
Hi Herbert,
> On Thu, Aug 08, 2024 at 07:56:39AM +0200, Stephan Mueller wrote:
> > The user-space version uses an OSR of 3. Using this value, I have not
> > heard of any problems. I will prepare a patch.
>
> Thanks Stephan. Jeff, could you please let us know if the value of 3
> fixes your problems?
However, the heart of the problem is the following: This failure mode is
probabilistic in nature. A number of folks trying to push rules that the
failure does not need to be handled with a panic.
A changed OSR only changes the probability, but that probability is always
strictly higher than zero.
>
> Cheers,
Ciao
Stephan
next prev parent reply other threads:[~2024-08-08 6:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM4PR21MB360932816FA7B848D7D8F7B0C7B82@DM4PR21MB3609.namprd21.prod.outlook.com>
2024-08-07 13:21 ` Intermittent EHEALTH Failure in FIPS Mode - jitterentropy jent_entropy_init() in Kernel 6.6.14 Stephan Mueller
2024-08-08 5:17 ` Herbert Xu
2024-08-08 5:56 ` Stephan Mueller
2024-08-08 6:10 ` Herbert Xu
2024-08-08 6:13 ` Stephan Mueller [this message]
2024-08-08 6:20 ` Herbert Xu
2024-08-08 14:08 ` [EXTERNAL] " Jeff Barnes
2024-08-12 6:25 ` [PATCH] crypto: JENT - set default OSR to 3 Stephan Mueller
2024-08-24 13:48 ` Herbert Xu
2024-08-07 13:07 Intermittent EHEALTH Failure in FIPS Mode - jitterentropy jent_entropy_init() in Kernel 6.6.14 Jeff Barnes
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=2416186.INgNo8UaUA@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=Tyler.Hicks@microsoft.com \
--cc=herbert@gondor.apana.org.au \
--cc=jeffbarnes@microsoft.com \
--cc=linux-crypto@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=shyamsaini@microsoft.com \
--cc=vdronov@redhat.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