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: <67047c516045d_964fe294b1@dwillia2-xfh.jf.intel.com.notmuch>
Date: Mon, 7 Oct 2024 17:26:57 -0700
From: Dan Williams <dan.j.williams@...el.com>
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

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.