linux-kernel - Re: Regression caused by "eeprom: at24: Probe for DDR3 thermal sensor in the SPD case" - "sysfs: cannot create duplicate filename"

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: <55445bee-03c6-4725-8b1d-5f656018a8af@ans.pl>
Date: Tue, 23 Jul 2024 07:12:13 -0700
From: Krzysztof Olędzki <ole@....pl>
To: Heiner Kallweit <hkallweit1@...il.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Bartosz Golaszewski <brgl@...ev.pl>
Cc: stable@...r.kernel.org, linux-i2c@...r.kernel.org,
        linux-hwmon@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Regression caused by "eeprom: at24: Probe for DDR3 thermal sensor
 in the SPD case" - "sysfs: cannot create duplicate filename"

On 06.07.2024 at 18:42, Krzysztof Olędzki wrote:
> On 02.07.2024 at 13:25, Heiner Kallweit wrote:
>> On 23.06.2024 20:47, Krzysztof Olędzki wrote:
>>> Hi,
>>>
>>> After upgrading kernel to Linux 6.6.34 on one of my systems, I noticed "sysfs: cannot create duplicate filename" and i2c registration errors in dmesg, please see below.
>>>
>>> This seems to be related to https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.6.y&id=4d5ace787273cb159bfdcf1c523df957938b3e42 - reverting the change fixes the problem.
> 
> <CUT>
> 
>>
>> Could you please test whether the attached two experimental patches fix the issue for you?
>> They serialize client device instantiation per I2C adapter, and include the client device
>> name in the check whether a bus address is busy.
> 
> Sadly, they crash the kernel.
> 
> I will get serial console attached there next week, so will be able to capture the full crash.
> For now, I was able to obtain a photo. I'm very sorry for the quality, just wanted to provide
> something for now.

Sorry it took me so long - my attempts to coordinate setting up serial console
were not successful, so it had to wait for me to go there in person...

I have attached complete dmesg, summary:

[   10.905953] rtmutex deadlock detected
[   10.909959] WARNING: CPU: 5 PID: 83 at kernel/locking/rtmutex.c:1642 __rt_mutex_slowlock_locked.constprop.0+0x10f/0x1a5
[   10.920961] CPU: 5 PID: 83 Comm: kworker/u16:3 Not tainted 6.6.34-o5 #1
[   10.929970] Hardware name: Dell Inc. PowerEdge T110 II/0PM2CW, BIOS 2.10.0 05/24/2018
[   10.938954] Workqueue: events_unbound async_run_entry_fn


[   11.336954] BUG: scheduling while atomic: kworker/u16:3/83/0x00000002
[   11.342953] Preemption disabled at:
[   11.342953] [<0000000000000000>] 0x0
[   11.350953] CPU: 5 PID: 83 Comm: kworker/u16:3 Tainted: G        W          6.6.34-o5 #1
[   11.361954] Hardware name: Dell Inc. PowerEdge T110 II/0PM2CW, BIOS 2.10.0 05/24/2018
[   11.369953] Workqueue: events_unbound async_run_entry_fn



Krzysztof

View attachment "at24-lock.txt" of type "text/plain" (70677 bytes)