linux-kernel - Re: [PATCH] fs: touch up predicts in putname()

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: <20251101060556.GA1235503@ZenIV>
Date: Sat, 1 Nov 2025 06:05:56 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: Mateusz Guzik <mjguzik@...il.com>
Cc: brauner@...nel.org, jack@...e.cz, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] fs: touch up predicts in putname()

On Fri, Oct 31, 2025 at 08:17:53PM +0000, Al Viro wrote:

> 0) get rid of audit_reusename() and aname->uptr (I have that series,
> massaging it for posting at the moment).  Basically, don't have
> getname et.al. called in retry loops - there are few places doing
> that, and they are not hard to fix.

See #work.filename-uptr; I'll post individual patches tomorrow morning,
hopefully along with getname_alien()/take_filename() followups, including
the removal of atomic (still not settled on the calling conventions for
getname_alien()).

> I'll post the ->uptr removal series tonight or tomorrow; figuring out the right
> calling conventions for getname_alien() is the main obstacle for (1--3) ATM...