From: Shyam Prasad N <nspmangalore@gmail.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
CIFS <linux-cifs@vger.kernel.org>,
linux-nfs@vger.kernel.org
Subject: "Intent" of VFS lookups
Date: Thu, 23 Apr 2026 22:31:37 +0530 [thread overview]
Message-ID: <CANT5p=oV8kcE6hXPoUVQAYGaiz+2OERoSRLAS6X+q9KJ_8w8YQ@mail.gmail.com> (raw)
Hi all,
Wanted to understand if this is a problem for other filesystems or if
it is specific to SMB protocol?
SMB2+ protocol mandate that open call specifies if the file being
opened is a directory or not (regular file).
This means that during the VFS lookup callback, fs/smb/client needs to
first try open as one type, check the return status and then possibly
do the open as the other type.
From SMB client POV, it would have been good to know from VFS lookup
callback if the current dentry is intended to be a leaf or not. This
would enable the SMB client to decide which type of open to make
first.
Or if there is a clever hack that I'm missing here, I'm open to ideas.
--
Regards,
Shyam
next reply other threads:[~2026-04-23 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 17:01 Shyam Prasad N [this message]
2026-04-23 17:43 ` "Intent" of VFS lookups Ralph Boehme
2026-04-24 13:20 ` Shyam Prasad N
2026-04-24 13:41 ` Tom Talpey
2026-04-28 16:12 ` Shyam Prasad N
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='CANT5p=oV8kcE6hXPoUVQAYGaiz+2OERoSRLAS6X+q9KJ_8w8YQ@mail.gmail.com' \
--to=nspmangalore@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).