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]
Message-Id: <87302cfa-c3ec-4d60-b870-a86acf0f6f8b@app.fastmail.com>
Date: Fri, 09 Feb 2024 11:20:21 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Linux regressions mailing list" <regressions@...ts.linux.dev>,
 "Srinivas Kandagatla" <srinivas.kandagatla@...aro.org>,
 "Miquel Raynal" <miquel.raynal@...tlin.com>,
 "Arnd Bergmann" <arnd@...nel.org>
Cc: 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 Fri, Feb 9, 2024, at 10:09, Linux regression tracking (Thorsten Leemhuis) wrote:
> 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.

Yes, this that this needs to be fixed before v6.8 is
out. I assumed it had gone upstream already.

If anyone is still unsure about the ABI, we could also revert
the original commit 0088cbc19276 ("nvmem: core: Expose cells
through sysfs") for v6.8 and try again for v6.9 with the
fixed ABI, but I think we already had an agreement on the
changes that I sent.

     Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ