From: Denis Kulikov <dar1knessx@gmail.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Tom Talpey <tom@talpey.com>,
ChenXiaoSong <chenxiaosong@chenxiaosong.com>,
Steve French <stfrench@microsoft.com>,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
Denis Kulikov <dar1knessx@gmail.com>
Subject: [PATCH] ksmbd: use the resolved share path for the share root
Date: Mon, 26 Oct 2026 15:55:41 +0300 [thread overview]
Message-ID: <20261026125541.87507-1-dar1knessx@gmail.com> (raw)
If the share path is a mount point and crossmnt is not set (crossmnt = no,
or ksmbd-tools that predate the option), the share root looks empty to
clients: QUERY_DIRECTORY on it returns only "." and "..". Files created
in the root go to the mounted filesystem, but a directory query cannot
find them afterwards, so e.g. "rm" of a file that was just uploaded
fails with STATUS_NO_SUCH_FILE.
An empty name refers to the share root. For it, ksmbd_vfs_path_lookup()
looks up share_conf->path again starting from its parent, and the mount
on the last component is not followed, which gives the directory covered
by the mount. All other names are looked up relative to
share_conf->vfs_path, which was resolved through the mount when the
share was set up.
share_conf->vfs_path already refers to the share root, so return a
reference to it instead of looking the path up again.
Fixes: 74d7970febf7 ("ksmbd: fix racy issue from using ->d_parent and ->d_name")
Signed-off-by: Denis Kulikov <dar1knessx@gmail.com>
---
Tested on x86_64 hardware running v7.3 with this change applied to the
ksmbd module: share on a loop-mounted ext4, crossmnt = no, smbclient.
Without the patch the root lists only "." and ".."; with it all files
are listed and put/ls/rm work. Also tested on current mainline in QEMU.
fs/smb/server/vfs.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/fs/smb/server/vfs.c b/fs/smb/server/vfs.c
index 4ee72eda9bc0..1f2bc76f0d09 100644
--- a/fs/smb/server/vfs.c
+++ b/fs/smb/server/vfs.c
@@ -66,12 +66,13 @@ static int ksmbd_vfs_path_lookup(struct ksmbd_share_config *share_conf,
if (for_remove)
return -EINVAL;
- pathname = share_conf->path;
- root_share_path = NULL;
- } else {
- flags |= LOOKUP_BENEATH;
+ *path = share_conf->vfs_path;
+ path_get(path);
+ return 0;
}
+ flags |= LOOKUP_BENEATH;
+
CLASS(filename_kernel, filename)(pathname);
scoped_with_init_fs()
err = vfs_path_parent_lookup(filename, flags, path, &last,
--
2.56.0
next reply other threads:[~2026-10-26 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 12:55 Denis Kulikov [this message]
2026-10-27 9:28 ` Namjae Jeon
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=20261026125541.87507-1-dar1knessx@gmail.com \
--to=dar1knessx@gmail.com \
--cc=chenxiaosong@chenxiaosong.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=stfrench@microsoft.com \
--cc=tom@talpey.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
all inboxes | Powered by JetHome®