linux-kernel - Re: [PATCH v3] ARM64: Dynamically allocate cpumasks and increase supported CPUs to 512

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] [thread-next>] [day] [month] [year] [list]

Date: Wed, 13 Mar 2024 09:39:21 -0700 (PDT)
From: "Christoph Lameter (Ampere)" <cl@...ux.com>
To: Marek Szyprowski <m.szyprowski@...sung.com>
cc: Sudeep Holla <sudeep.holla@....com>, 
    Catalin Marinas <catalin.marinas@....com>, 
    Mark Rutland <mark.rutland@....com>, 
    "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>, 
    "Rafael J. Wysocki" <rafael@...nel.org>, Viresh Kumar <vireshk@...nel.org>, 
    Will Deacon <will@...nel.org>, Jonathan.Cameron@...wei.com, 
    Matteo.Carlini@....com, Valentin.Schneider@....com, 
    akpm@...ux-foundation.org, anshuman.khandual@....com, 
    Eric Mackay <eric.mackay@...cle.com>, dave.kleikamp@...cle.com, 
    linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
    linux-mm@...ck.org, linux@...linux.org.uk, robin.murphy@....com, 
    vanshikonda@...amperecomputing.com, yang@...amperecomputing.com, 
    Nishanth Menon <nm@...com>, Stephen Boyd <sboyd@...nel.org>
Subject: Re: [PATCH v3] ARM64: Dynamically allocate cpumasks and increase
 supported CPUs to 512

On Wed, 13 Mar 2024, Marek Szyprowski wrote:

>> I did try to trigger this on FVP by adding OPPs + some hacks to add dummy
>> clock provider to successfully probe this driver. I couldn't hit the issue
>> reported 🙁. It could be that with the hardware clock/regulator drivers, it
>> take a different path in OPP core.
>
> I can fully reproduce this issue on Khadas VIM3 and Odroid-N2 boards.
> Both Meson A311D SoC based.

Hmm... Would it trigger on Orangepi5plus? With some effort I can get that 
board up at home.

Could you reboot with some memory diagnostics so that we are sure that 
nothing gets corrupted?

F.e. specify a command line parameter "slub_debug" to enable redzoning. 
That way we may see potential memory corruption.