From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217122] Regression in xhci driver since 6.1 "Transfer event TRB DMA ptr not part of current TD"
Date: Wed, 10 May 2023 20:06:53 +0000 [thread overview]
Message-ID: <bug-217122-208809-1Fic7BvIGM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217122-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217122
--- Comment #13 from Jürgen Herrmann (t-5@t-5.eu) ---
Another round of bisecting is done. I'm quite sure this result is useless, I
will post it here nonetheless. Please comment!
$ git bisect good
b006c439d58db625318bf2207feabf847510a8a6 is the first bad commit
commit b006c439d58db625318bf2207feabf847510a8a6
Author: Dominik Brodowski <linux@dominikbrodowski.net>
Date: Thu Sep 22 15:59:31 2022 +0200
hwrng: core - start hwrng kthread also for untrusted sources
Start the hwrng kthread even if the hwrng source has a quality setting
of zero. Then, every crng reseed interval, one batch of data from this
zero-quality hwrng source will be mixed into the CRNG pool.
This patch is based on the assumption that data from a hwrng source
will not actively harm the CRNG state. Instead, many hwrng sources
(such as TPM devices), even though they are assigend a quality level of
zero, actually provide some entropy, which is good enough to mix into
the CRNG pool every once in a while.
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Jason A. Donenfeld <Jason@zx2c4.com>
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
drivers/char/hw_random/core.c | 36 ++++++++++--------------------------
1 file changed, 10 insertions(+), 26 deletions(-)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-05-10 20:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 19:53 [Bug 217122] New: Regression in xhci driver since 6.1 "Transfer event TRB DMA ptr not part of current TD" bugzilla-daemon
2023-03-06 2:04 ` [Bug 217122] " bugzilla-daemon
2023-03-06 9:17 ` bugzilla-daemon
2023-03-06 11:35 ` bugzilla-daemon
2023-03-06 13:15 ` bugzilla-daemon
2023-03-06 21:06 ` bugzilla-daemon
2023-03-06 21:09 ` bugzilla-daemon
2023-03-06 21:18 ` bugzilla-daemon
2023-03-07 20:25 ` bugzilla-daemon
2023-03-23 14:00 ` bugzilla-daemon
2023-03-23 14:59 ` bugzilla-daemon
2023-04-19 16:36 ` bugzilla-daemon
2023-05-06 17:31 ` bugzilla-daemon
2023-05-10 20:06 ` bugzilla-daemon [this message]
2023-05-10 20:15 ` bugzilla-daemon
2023-05-10 21:25 ` bugzilla-daemon
2023-05-10 21:51 ` bugzilla-daemon
2023-05-10 21:52 ` bugzilla-daemon
2023-05-10 21:54 ` bugzilla-daemon
2023-05-10 22:23 ` bugzilla-daemon
2023-05-10 22:25 ` bugzilla-daemon
2023-05-10 22:26 ` bugzilla-daemon
2023-05-10 22:28 ` bugzilla-daemon
2023-05-10 22:29 ` bugzilla-daemon
2023-05-12 16:38 ` bugzilla-daemon
2023-05-12 16:45 ` bugzilla-daemon
2023-05-12 16:51 ` bugzilla-daemon
2023-05-12 17:00 ` bugzilla-daemon
2023-08-02 15:48 ` bugzilla-daemon
2023-08-02 16:41 ` bugzilla-daemon
2023-08-02 16:46 ` bugzilla-daemon
2023-08-07 5:12 ` bugzilla-daemon
2023-08-07 7:01 ` bugzilla-daemon
2023-08-07 15:47 ` bugzilla-daemon
2023-08-07 16:15 ` bugzilla-daemon
2023-08-08 0:13 ` bugzilla-daemon
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=bug-217122-208809-1Fic7BvIGM@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.