linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: brauner@kernel.org, jack@suse.cz, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: touch up predicts in putname()
Date: Sun, 2 Nov 2025 06:14:43 +0000	[thread overview]
Message-ID: <20251102061443.GE2441659@ZenIV> (raw)
In-Reply-To: <CAGudoHHno74hGjwu7rryrS4x2q2W8=SwMwT9Lohjr4mBbAg+LA@mail.gmail.com>

On Sat, Nov 01, 2025 at 09:19:21AM +0100, Mateusz Guzik wrote:
> On Sat, Nov 1, 2025 at 7:05 AM Al Viro <viro@zeniv.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.

See #work.filename-refcnt.  I'm not entirely happy about the API, if you
see a saner way to do it, I'd really like to hear it.  Stuff in the series:

	* get rid of getname in retry loops.  Only 9 places like that left,
massaged out of existence one by one.  (##1..9)
	* drop audit_reusename() and filename->uptr (#10)
	* get rid of mixing LOOKUP_EMPTY with the rest of the flags -
very few places do that at this point and they are not hard to take
care of (##11..15)
	* take LOOKUP_EMPTY out of LOOKUP_... space entirely - make it
GETNAME_EMPTY and have it passed only to getname_flags() (#16)
	* add GETNAME_NOAUDIT for "don't call audit_getname() there" (#17).
Helpers: getname_alien()/getname_uflags_alien() being wrappers for
that; io-uring switched to those for filename import (in ->prep()).
take_filename(): take a reference to struct filename, leaving NULL
behind, feed it to audit_getname() and return to caller.   Used by
io-uring ->issue() instances that feed an imported filename to
do_{mkdir,mknod...}() - the stuff that does actual work, done in the
thread that will do that work.
	* make filename->refcnt non-atomic; now it can be done (#19,
on top of merge from vfs-common/vfs-6.19.misc to bring your commit
in).

  reply	other threads:[~2025-11-02  6:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 13:49 [PATCH] fs: touch up predicts in putname() Mateusz Guzik
2025-10-29 15:48 ` Markus Elfring
2025-10-30 13:59 ` Jan Kara
2025-10-31 12:18 ` Christian Brauner
2025-10-31 20:17 ` Al Viro
2025-11-01  6:05   ` Al Viro
2025-11-01  8:19     ` Mateusz Guzik
2025-11-02  6:14       ` Al Viro [this message]
2025-11-02 22:42         ` Mateusz Guzik
2025-11-03  4:45           ` Al Viro
2025-11-03 16:44             ` Mateusz Guzik
2025-11-05  6:25               ` Al Viro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251102061443.GE2441659@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjguzik@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).