linux-kernel - Re: [PATCH 0/2] Backport uclamp static key to 5.4.y stable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 28 Aug 2020 12:36:49 -0400
From:   Sasha Levin <sashal@...nel.org>
To:     Qais Yousef <qais.yousef@....com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        stable@...r.kernel.org, linux-kernel@...r.kernel.org,
        "Peter Zijlstra (Intel)" <peterz@...radead.org>,
        Mel Gorman <mgorman@...e.de>,
        Dietmar Eggemann <dietmar.eggemann@....com>
Subject: Re: [PATCH 0/2] Backport uclamp static key to 5.4.y stable

On Fri, Aug 28, 2020 at 01:56:08PM +0100, Qais Yousef wrote:
>Hi Greg/Sasha
>
>The following 2 patches are backports of
>
>	46609ce22703: ("sched/uclamp: Protect uclamp fast path code with static key")
>	e65855a52b47: ("sched/uclamp: Fix a deadlock when enabling uclamp static key")
>
>into 5.4.y stable tree. The conflict was trivial and due to:
>
>	1. uclamp_rq_util_with() was renamed from util_util_with()
>	2. 2 local variables were converted to unsigned long from unsigned int.
>
>I did do compile test on aarch64 and x86_64 and both looked fine. Beside I ran
>a quick and short mmtest to verify the functionality and got the following
>results which is inline with what's expected.

I've queued it up, thanks!

-- 
Thanks,
Sasha