From: NeilBrown <neilb@ownmail.net>
To: Miklos Szeredi <miklos@szeredi.hu>,
Amir Goldstein <amir73il@gmail.com>, Kees Cook <kees@kernel.org>,
Joel Granados <joel.granados@kernel.org>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
Breno Leitao <leitao@debian.org>,
Andreas Hindborg <a.hindborg@kernel.org>,
Jan Harkes <jaharkes@cs.cmu.edu>, Hugh Dickins <hughd@google.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Namjae Jeon <linkinjeon@kernel.org>,
Hyunchul Lee <hyc.lee@gmail.com>,
Carlos Maiolino <cem@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>
Cc: Jeff Layton <jlayton@kernel.org>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, fuse-devel@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
linux-um@lists.infradead.org, codalist@coda.cs.cmu.edu,
coda@cs.cmu.edu, linux-mm@kvack.org, ntfs@lists.linux.dev,
linux-xfs@vger.kernel.org
Subject: [PATCH 5/7] hostfs: don't d_drop() before d_splice_alias() in hostfs_mkdir()
Date: Tue, 29 Sep 2026 13:36:05 +1000 [thread overview]
Message-ID: <20260929034158.1455429-6-neilb@ownmail.net> (raw)
In-Reply-To: <20260929034158.1455429-1-neilb@ownmail.net>
From: NeilBrown <neil@brown.name>
hostfs_mkdir() uses d_drop() and d_splice_alias() to ensure it has the
right dentry after a mkdir.
d_drop() is no longer needed here and will cause problem for future
changes to directory locking. So remove the d_drop().
Signed-off-by: NeilBrown <neil@brown.name>
---
fs/hostfs/hostfs_kern.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/hostfs/hostfs_kern.c b/fs/hostfs/hostfs_kern.c
index 7add056d47d8..f68e75981436 100644
--- a/fs/hostfs/hostfs_kern.c
+++ b/fs/hostfs/hostfs_kern.c
@@ -700,7 +700,6 @@ static struct dentry *hostfs_mkdir(struct mnt_idmap *idmap, struct inode *ino,
dentry = ERR_PTR(err);
} else {
inode = hostfs_iget(dentry->d_sb, file);
- d_drop(dentry);
dentry = d_splice_alias(inode, dentry);
}
__putname(file);
--
2.50.0.107.gf914562f5916.dirty
next prev parent reply other threads:[~2026-09-29 3:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 3:36 [PATCH 0/7] multiple-filesystems: prepare for changes to VFS locking NeilBrown
2026-09-29 3:36 ` [PATCH 1/7] VFS/xfs/ntfs: drop parent lock across d_alloc_parallel() in d_add_ci() NeilBrown
2026-09-29 3:36 ` [PATCH 2/7] shmem: use d_duplicate() NeilBrown
2026-09-29 3:36 ` [PATCH 3/7] coda: don't d_drop() early NeilBrown
2026-09-29 3:36 ` [PATCH 4/7] configfs: remove d_add() calls before configfs_attach_group() NeilBrown
2026-09-29 5:07 ` Al Viro
2026-10-01 1:32 ` NeilBrown
2026-09-29 3:36 ` NeilBrown [this message]
2026-09-29 3:36 ` [PATCH 6/7] procfs: drop parent lock for d_alloc_parallel() in iterate_shared() NeilBrown
2026-09-29 3:36 ` [PATCH 7/7] ovl: stop using lookup_one() in ovl_iterate() NeilBrown
2026-09-30 13:35 ` Amir Goldstein
2026-09-30 21:43 ` NeilBrown
2026-09-30 10:22 ` [syzbot ci] Re: multiple-filesystems: prepare for changes to VFS locking syzbot ci
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=20260929034158.1455429-6-neilb@ownmail.net \
--to=neilb@ownmail.net \
--cc=a.hindborg@kernel.org \
--cc=amir73il@gmail.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=coda@cs.cmu.edu \
--cc=codalist@coda.cs.cmu.edu \
--cc=fuse-devel@lists.linux.dev \
--cc=hughd@google.com \
--cc=hyc.lee@gmail.com \
--cc=jack@suse.cz \
--cc=jaharkes@cs.cmu.edu \
--cc=jlayton@kernel.org \
--cc=joel.granados@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kees@kernel.org \
--cc=leitao@debian.org \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-um@lists.infradead.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=neil@brown.name \
--cc=ntfs@lists.linux.dev \
--cc=richard@nod.at \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®