linux-kernel - Re: [PATCH] nvmem: include bit index in cell sysfs file name

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]

Message-ID: <e9a72160-2d39-4090-8822-ca68477f429f@leemhuis.info>
Date: Fri, 9 Feb 2024 10:09:45 +0100
From: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@...mhuis.info>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
 Miquel Raynal <miquel.raynal@...tlin.com>, Arnd Bergmann <arnd@...nel.org>
Cc: Arnd Bergmann <arnd@...db.de>, regressions@...ts.linux.dev,
 Rafał Miłecki <rafal@...ecki.pl>,
 Chen-Yu Tsai <wenst@...omium.org>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>, asahi@...ts.linux.dev,
 Sven Peter <sven@...npeter.dev>, Michael Walle <michael@...le.cc>,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nvmem: include bit index in cell sysfs file name

On 22.01.24 17:55, Srinivas Kandagatla wrote:
> On Mon, 22 Jan 2024 16:34:10 +0100, Arnd Bergmann wrote:
>> Creating sysfs files for all Cells caused a boot failure for linux-6.8-rc1 on
>> Apple M1, which (in downstream dts files) has multiple nvmem cells that use the
>> same byte address. This causes the device probe to fail with
>>
>> [    0.605336] sysfs: cannot create duplicate filename '/devices/platform/soc@...000000/2922bc000.efuse/apple_efuses_nvmem0/cells/efuse@...'
>> [    0.605347] CPU: 7 PID: 1 Comm: swapper/0 Tainted: G S                 6.8.0-rc1-arnd-5+ #133
>> [    0.605355] Hardware name: Apple Mac Studio (M1 Ultra, 2022) (DT)
>> [    0.605362] Call trace:
>> [...]
> 
> Applied, thanks!
> 
> [1/1] nvmem: include bit index in cell sysfs file name
>       commit: b40fed13870045731e374e6bb48800cde0feb4e2

The problem description from Arnd to an outsider like me sounded like
this is something that should be fixed rather sooner than later in
mainline. Am I wrong with that? If not: will this be heading to Linus
soon? Just wondering, as the fix seems to be a in "for-next" branch[1]
of the nvmem repo and not in a "fixes" branch.

Or am I missing something here?

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

[1] https://git.kernel.org/pub/scm/linux/kernel/git/srini/nvmem.git
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

#regzbot poke