[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167831648986.1965482.3536353696063382395.b4-ty@chromium.org>
Date: Wed, 8 Mar 2023 15:01:32 -0800
From: Kees Cook <keescook@...omium.org>
To: jstultz@...gle.com, linux-kernel@...r.kernel.org
Cc: Kees Cook <keescook@...omium.org>, gpiccoli@...lia.com,
chunhui.li@...iatek.com, wvw@...gle.com, midaschieh@...gle.com,
anton@...msg.org, Tony Luck <tony.luck@...el.com>,
rostedt@...dmis.org, kernel-team@...roid.com
Subject: Re: [PATCH v3] pstore: Revert pmsg_lock back to a normal mutex
On Wed, 8 Mar 2023 20:40:43 +0000, John Stultz wrote:
> This reverts commit 76d62f24db07f22ccf9bc18ca793c27d4ebef721.
>
> So while priority inversion on the pmsg_lock is an occasional
> problem that an rt_mutex would help with, in uses where logging
> is writing to pmsg heavily from multiple threads, the pmsg_lock
> can be heavily contended.
>
> [...]
Applied to for-next/pstore, thanks!
[1/1] pstore: Revert pmsg_lock back to a normal mutex
https://git.kernel.org/kees/c/5239a89b06d6
--
Kees Cook
Powered by blists - more mailing lists