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: Sat, 1 Nov 2025 06:05:56 +0000	[thread overview]
Message-ID: <20251101060556.GA1235503@ZenIV> (raw)
In-Reply-To: <20251031201753.GD2441659@ZenIV>

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...

  reply	other threads:[~2025-11-01  6:05 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 [this message]
2025-11-01  8:19     ` Mateusz Guzik
2025-11-02  6:14       ` Al Viro
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=20251101060556.GA1235503@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).