From: Mark Gross <markgross@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Mark Gross <markgross@kernel.org>,
linux-rt-users@vger.kernel.org, stable-rt@vger.kernel.org,
Salvatore Bonaccorso <carnil@debian.org>
Subject: Re: [PATCH 0/9 v4.9-RT] Backports to fix random core
Date: Fri, 19 Aug 2022 08:14:18 -0700 [thread overview]
Message-ID: <Yv+oyqiBmKwtwH6t@T470> (raw)
In-Reply-To: <20220819092446.980320-1-bigeasy@linutronix.de>
On Fri, Aug 19, 2022 at 11:24:37AM +0200, Sebastian Andrzej Siewior wrote:
> Hi,
>
> in v4.9.320 some random-core patches broke RT. This is a series of
> backports to align with later RT versions and keep things working again.
>
> Sebastian
Thanks so much!
--mark
next prev parent reply other threads:[~2022-08-19 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 9:24 [PATCH 0/9 v4.9-RT] Backports to fix random core Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 1/9] random: Bring back the local_locks Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 2/9] random: schedule mix_interrupt_randomness() less often Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 3/9] Revert "workqueue: Use local irq lock instead of irq disable regions" Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 4/9] Revert "workqueue: Prevent deadlock/stall on RT" Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 5/9] timers: Keep interrupts disabled for TIMER_IRQSAFE timer Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 6/9] timers: Don't block on ->expiry_lock for TIMER_IRQSAFE timers Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 7/9] rcu: Intrdroduce rcuwait Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 8/9] workqueue: Use rcuwait for wq_manager_wait Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 9/9] workqueue: Convert the pool::lock and wq_mayday_lock to raw_spinlock_t Sebastian Andrzej Siewior
2022-08-19 15:14 ` Mark Gross [this message]
2022-09-01 21:16 ` [PATCH 0/9 v4.9-RT] Backports to fix random core Mark Gross
2022-09-02 6:52 ` Sebastian Andrzej Siewior
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=Yv+oyqiBmKwtwH6t@T470 \
--to=markgross@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=carnil@debian.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=stable-rt@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.