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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2024101356-gauntlet-sludge-7b76@gregkh>
Date: Sun, 13 Oct 2024 17:00:15 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Dan Williams <dan.j.williams@...el.com>
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 Mon, Oct 07, 2024 at 05:26:57PM -0700, 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.

Ok, I'll drop this for now and wait for a follow-on patch to come for
whatever you decide.

thanks,

greg k-h