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: <CAGudoHHno74hGjwu7rryrS4x2q2W8=SwMwT9Lohjr4mBbAg+LA@mail.gmail.com>
Date: Sat, 1 Nov 2025 09:19:21 +0100
From: Mateusz Guzik <mjguzik@...il.com>
To: Al Viro <viro@...iv.linux.org.uk>
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 Sat, Nov 1, 2025 at 7:05 AM Al Viro <viro@...iv.linux.org.uk> wrote:
>
> 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()).
>

Ok, in that case I think it will be most expedient if my patch gets
dropped and you just fold the updated predicts into your patchset
somewhere. I don't need any credit.