From: John Keeping <john@metanate.com>
To: andreadaoud6@gmail.com
Cc: Valentin Schneider <valentin.schneider@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
linux-rt-users@vger.kernel.org
Subject: Re: [RT] BUG in sched/cpupri.c
Date: Mon, 27 Jun 2022 10:51:02 +0100 [thread overview]
Message-ID: <Yrl9hqqwskqVubt+@donbot> (raw)
In-Reply-To: <20220627020204.29132-1-andreadaoud6@gmail.com>
On Mon, Jun 27, 2022 at 10:02:04AM +0800, andreadaoud6@gmail.com wrote:
> I'm encountering this problem today with linux 5.15.5 rt22 kernel.
> This bug leads to an unstable system. Having read all your discussions, I know
> there is a workaround, but it doesn't seem that everybody agrees this.
> I'd like to know if this problem is solved in later rt patch series.
> If yes, could someone be more specific which patch solves it?
> If not, is applying the above mentioned workaround patch the best solution?
Valentin was fixed this in 49bef33e4b87 ("sched/rt: Plug
rt_mutex_setprio() vs push_rt_task() race") which was backported to
v5.15.33, so updating to the latest v5.15 stable release will pull in
the fix.
prev parent reply other threads:[~2022-06-27 10:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 14:25 [RT] BUG in sched/cpupri.c John Keeping
2021-12-20 17:35 ` Dietmar Eggemann
2021-12-21 16:11 ` Valentin Schneider
2021-12-21 16:45 ` John Keeping
2021-12-21 17:22 ` Valentin Schneider
2021-12-21 17:42 ` John Keeping
2021-12-22 17:46 ` Dietmar Eggemann
2021-12-22 18:45 ` John Keeping
2021-12-22 19:48 ` Valentin Schneider
2021-12-23 11:58 ` John Keeping
2021-12-23 14:05 ` Valentin Schneider
2022-01-07 10:46 ` Dietmar Eggemann
2022-01-07 11:49 ` John Keeping
2022-01-07 14:25 ` Dietmar Eggemann
2022-01-07 18:35 ` John Keeping
2022-01-14 18:25 ` Valentin Schneider
2022-06-27 2:02 ` andreadaoud6
2022-06-27 9:51 ` John Keeping [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=Yrl9hqqwskqVubt+@donbot \
--to=john@metanate.com \
--cc=andreadaoud6@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=valentin.schneider@arm.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