linux-kernel - Re: [PATCH v2] driver core: Fix userspace expectations of uevent

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: <42dfef93-eb8a-458b-b76b-b7de9077d0af@leemhuis.info>
Date: Mon, 28 Oct 2024 10:08:49 +0100
From: Thorsten Leemhuis <regressions@...mhuis.info>
To: Dan Williams <dan.j.williams@...el.com>, gregkh@...uxfoundation.org
Cc: rafael.j.wysocki@...el.com, tj@...nel.org, linux-kernel@...r.kernel.org,
 regressions@...ts.linux.dev
Subject: Re: [PATCH v2] driver core: Fix userspace expectations of
 uevent_show() as a probe barrier

On 08.10.24 02:26, Dan Williams wrote:
> Dan Williams wrote:
>> Changes since v1 [1]:
>> - Move the new "locked" infrastructure to private header files to make
>>   it clear it is not approved for general usage (Greg)
> 
> Greg, per the 0day report and further testing I am missing something
> subtle in using kernfs open files to pin device objects. So hold off on
> this for now until I can get that root caused. If someone else can spot
> what I missed feel free to chime in, but otherwise I will circle back.
> 
> If I don't get back to this before -rc6 I think the theoretical deadlock
> that would be re-introduced by a revert of 15fffc6a5624 would be
> preferable to this reported regression. I am not aware of any reports of
> that deadlock triggering in practice.
Was there any progress? If not: given that Linus prefers to have things
fixed by -rc6 I wonder if now would be a good time to get the revert on
track for a merge later this week.

Ciao, Thorsten

#regzbot poke