linux-kernel - Re: [PATCH v3 02/10] perf/alibaba_uncore_drw: Avoid placing cpumask on the stack

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 for Android: free password hash cracker in your pocket

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

Date: Mon, 8 Apr 2024 08:28:29 +0800
From: Shuai Xue <xueshuai@...ux.alibaba.com>
To: Dawei Li <dawei.li@...ngroup.cn>, will@...nel.org, mark.rutland@....com,
 yury.norov@...il.com, linux@...musvillemoes.dk
Cc: renyu.zj@...ux.alibaba.com, yangyicong@...ilicon.com,
 jonathan.cameron@...wei.com, andersson@...nel.org, konrad.dybcio@...aro.org,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v3 02/10] perf/alibaba_uncore_drw: Avoid placing cpumask
 on the stack



On 2024/4/3 23:59, Dawei Li wrote:
> In general it's preferable to avoid placing cpumasks on the stack, as
> for large values of NR_CPUS these can consume significant amounts of
> stack space and make stack overflows more likely.
> 
> Use cpumask_any_and_but() to avoid the need for a temporary cpumask on
> the stack.
> 
> Suggested-by: Mark Rutland <mark.rutland@....com>
> Reviewed-by: Mark Rutland <mark.rutland@....com>
> Signed-off-by: Dawei Li <dawei.li@...ngroup.cn>
> ---

Reviewed-by: Shuai Xue <xueshuai@...ux.alibaba.com>