All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: neil@brown.name
Cc: Christian Brauner <brauner@kernel.org>,
	Amir Goldstein <amir73il@gmail.com>,
	Jeff Layton <jlayton@kernel.org>, Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 6/7] VFS: introduce simple_end_creating() and simple_failed_creating()
Date: Tue, 9 Sep 2025 09:20:41 +0100	[thread overview]
Message-ID: <20250909082041.GN31600@ZenIV> (raw)
In-Reply-To: <20250909044637.705116-7-neilb@ownmail.net>

On Tue, Sep 09, 2025 at 02:43:20PM +1000, NeilBrown wrote:
> From: NeilBrown <neil@brown.name>
> 
> These are partners of simple_start_creating().
> On failure we don't keep a reference.  On success we do.
> 
> We now Use these where simple_start_creating() is used, in debugfs,
> tracefs, and rpcpipefs.

NAK, for the same reason as with the next commit.

  reply	other threads:[~2025-09-09  8:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09  4:43 [PATCH v2 0/8] VFS: more prep for change to directory locking NeilBrown
2025-09-09  4:43 ` [PATCH v2 1/7] VFS/ovl: add lookup_one_positive_killable() NeilBrown
2025-09-11 20:05   ` Al Viro
2025-09-11 23:02     ` NeilBrown
2025-09-09  4:43 ` [PATCH v2 2/7] VFS: discard err2 in filename_create() NeilBrown
2025-09-09 11:24   ` Jeff Layton
2025-09-09  4:43 ` [PATCH v2 3/7] VFS: unify old_mnt_idmap and new_mnt_idmap in renamedata NeilBrown
2025-09-09  4:43 ` [PATCH v2 4/7] VFS/audit: introduce kern_path_parent() for audit NeilBrown
2025-09-09  4:43 ` [PATCH v2 5/7] VFS: rename kern_path_locked() and related functions NeilBrown
2025-09-09 14:07   ` Amir Goldstein
2025-09-10  2:49     ` NeilBrown
2025-09-09  4:43 ` [PATCH v2 6/7] VFS: introduce simple_end_creating() and simple_failed_creating() NeilBrown
2025-09-09  8:20   ` Al Viro [this message]
2025-09-09  4:43 ` [PATCH v2 7/7] Use simple_start_creating() in various places NeilBrown
2025-09-09  8:19   ` Al Viro
2025-09-10  3:01     ` NeilBrown
2025-09-10  4:12       ` Al Viro
2025-09-10  4:16         ` Al Viro
2025-09-10  7:37           ` Al Viro
2025-09-10 11:04             ` Jeff Layton
2025-09-10 11:30               ` NeilBrown
2025-09-10 11:54                 ` Jeff Layton
2025-09-10 18:28                   ` Al Viro
2025-09-10 12:34             ` Jeff Layton
2025-09-10 23:13           ` NeilBrown

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=20250909082041.GN31600@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=neil@brown.name \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.