[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230908162254.999499-1-bigeasy@linutronix.de>
Date: Fri, 8 Sep 2023 18:22:47 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Peter Zijlstra <peterz@...radead.org>, linux-kernel@...r.kernel.org
Cc: bigeasy@...utronix.de, tglx@...utronix.de, boqun.feng@...il.com,
bristot@...hat.com, bsegall@...gle.com, dietmar.eggemann@....com,
jstultz@...gle.com, juri.lelli@...hat.com, longman@...hat.com,
mgorman@...e.de, mingo@...hat.com, rostedt@...dmis.org,
swood@...hat.com, vincent.guittot@...aro.org, vschneid@...hat.com,
will@...nel.org
Subject: [PATCH v3 0/7] locking/rtmutex: Avoid PI state recursion through sched_submit_work()
Hi!
this is the third iteration of the patch series that PeterZ sent.
PeterZ v1: https://lore.kernel.org/all/20230815110121.117752409@infradead.org/
My v2: https://lore.kernel.org/all/20230825181033.504534-1-bigeasy@linutronix.de/
It contains a range-diff what changed, in brief:
- + include linux/sched/rt.h to get compiled
- rt_mutex_pre_schedule()/post() for rwbase_write_lock().
Now the v3:
- Sultan Alsawaf reported a deadlock in write_lock(). A brown paper back
later, I replaced rt_mutex_pre_schedule()/post() with
rwbase_pre_schedule() in rwbase_write_lock().
- The reported futex splat in v2 has been addressed with a trylock. This
is 7/7.
Sebastian
Powered by blists - more mailing lists