Linux filesystem development
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andreas Hindborg <a.hindborg@kernel.org>,
	Tyler Hicks <code@tyhicks.com>,
	Namjae Jeon <linkinjeon@kernel.org>,
	Andreas Gruenbacher <agruenba@redhat.com>,
	linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs: d_add() misuses in ->lookup()
Date: Sun, 14 Jun 2026 23:32:18 +0100	[thread overview]
Message-ID: <20260614223218.GQ2636677@ZenIV> (raw)
In-Reply-To: <20260606064956.2722874-1-viro@zeniv.linux.org.uk>

The following changes since commit e43ffb69e0438cddd72aaa30898b4dc446f664f8:

  Linux 7.1-rc6 (2026-05-31 15:14:24 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-d_add

for you to fetch changes up to 2555ac7a450bf11f8e461ce6cd0f62613734a796:

  gfs2: use d_splice_alias() for ->lookup() return value (2026-06-06 17:12:54 -0400)

----------------------------------------------------------------
This series converts a bunch of unidiomatic uses of d_add()
in ->lookup() instances to equivalent uses of d_splice_alias(),
which is the normal mechanism for ->lookup().

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

----------------------------------------------------------------
Al Viro (6):
      tracefs: use d_splice_alias() in ->lookup() instances
      configfs_lookup(): switch to d_splice_alias()
      ecryptfs: use d_splice_alias() for ->lookup() return value
      simple_lookup(): use d_splice_alias() for ->lookup() return value
      ntfs: use d_splice_alias() for ->lookup() return value
      gfs2: use d_splice_alias() for ->lookup() return value

 fs/configfs/dir.c        | 3 +--
 fs/ecryptfs/inode.c      | 8 +++-----
 fs/gfs2/inode.c          | 8 ++------
 fs/libfs.c               | 3 +--
 fs/ntfs/namei.c          | 3 +--
 fs/tracefs/event_inode.c | 6 ++----
 6 files changed, 10 insertions(+), 21 deletions(-)

      parent reply	other threads:[~2026-06-14 22:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-06  6:49 [PATCH 0/6] d_add() misuses in ->lookup() Al Viro
2026-06-06  6:49 ` [PATCH 1/6] tracefs: use d_splice_alias() in ->lookup() instances Al Viro
2026-06-09 22:26   ` Steven Rostedt
2026-06-06  6:49 ` [PATCH 2/6] configfs_lookup(): switch to d_splice_alias() Al Viro
2026-06-06  6:49 ` [PATCH 3/6] ecryptfs: use d_splice_alias() for ->lookup() return value Al Viro
2026-06-06  6:49 ` [PATCH 4/6] simple_lookup(): " Al Viro
2026-06-06  6:49 ` [PATCH 5/6] ntfs: " Al Viro
2026-06-06 12:26   ` Namjae Jeon
2026-06-06  6:49 ` [PATCH 6/6] gfs2: " Al Viro
2026-06-06 12:48   ` Andreas Gruenbacher
2026-06-06 12:51 ` [PATCH 0/6] d_add() misuses in ->lookup() Andreas Gruenbacher
2026-06-14 22:32 ` Al Viro [this message]

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=20260614223218.GQ2636677@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=a.hindborg@kernel.org \
    --cc=agruenba@redhat.com \
    --cc=brauner@kernel.org \
    --cc=code@tyhicks.com \
    --cc=jack@suse.cz \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    /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