From: "Pali Rohár" <pali@kernel.org>
To: Steve French <sfrench@samba.org>, Paulo Alcantara <pc@manguebit.com>
Cc: linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: Fix getting reparse points from server without WSL support
Date: Tue, 17 Sep 2024 22:06:00 +0200 [thread overview]
Message-ID: <20240917200600.6smfxhrppkyjuyku@pali> (raw)
In-Reply-To: <20240913201041.cwueaflcxhewnvwj@pali>
And seems that SMB2_OP_QUERY_WSL_EA is useful not only for reparse
points, but also for any regular file or directory as it can contain
UNIX mode and UID/GID ownership.
On Friday 13 September 2024 22:10:41 Pali Rohár wrote:
> Paulo, please look at this patch as it is related to WSL attributes
> which you introduced in the mentioned commit. I think that the proper
> fix should be to change SMB2_OP_QUERY_WSL_EA code to not trigger that
> -EOPNOTSUPP error which is delivered to userspace. I just checked that
> this my patch works fine for Native NTFS symlinks and NFS-style reparse
> point special files.
>
> On Friday 13 September 2024 22:02:04 Pali Rohár wrote:
> > If SMB server does not support WSL EAs then for SMB2_OP_QUERY_WSL_EA
> > request it returns STATUS_EAS_NOT_SUPPORTED. Function smb2_compound_op()
> > translates STATUS_EAS_NOT_SUPPORTED to -EOPNOTSUPP which cause failure
> > during calling lstat() syscall from userspace on any reparse point,
> > including Native SMB symlink (which does not use any EAs). This issue
> > happen for example when trying to resolve Native NTFS symlink from SMB
> > server on Windows 8.
> >
> > Avoid this problem by calling SMB2_OP_QUERY_WSL_EA only when detected
> > reparse point is of WSL type. Note that this is not solve this problem
> > fully as WSL reparse points can be created also on other SMB server
> > which do not support Extended Attributes at all.
> >
> > Fixes: ea41367b2a60 ("smb: client: introduce SMB2_OP_QUERY_WSL_EA")
> > Signed-off-by: Pali Rohár <pali@kernel.org>
> > ---
> > fs/smb/client/smb2inode.c | 15 ++++++++++++++-
> > 1 file changed, 14 insertions(+), 1 deletion(-)
> >
> > diff --git a/fs/smb/client/smb2inode.c b/fs/smb/client/smb2inode.c
> > index 11a1c53c64e0..d65471aa55e6 100644
> > --- a/fs/smb/client/smb2inode.c
> > +++ b/fs/smb/client/smb2inode.c
> > @@ -941,7 +941,20 @@ int smb2_query_path_info(const unsigned int xid,
> > if (rc || !data->reparse_point)
> > goto out;
> >
> > - cmds[num_cmds++] = SMB2_OP_QUERY_WSL_EA;
> > + /*
> > + * Skip SMB2_OP_QUERY_WSL_EA if reparse point is not WSL.
> > + * The server file system does not have to support Extended
> > + * Attributes and in this case returns STATUS_EAS_NOT_SUPPORTED
> > + * which smb2_compound_op() translate to -EOPNOTSUPP. This will
> > + * present failure during reading of non-WSL special files.
> > + */
> > + if (data->reparse.tag == IO_REPARSE_TAG_LX_SYMLINK ||
> > + data->reparse.tag == IO_REPARSE_TAG_AF_UNIX ||
> > + data->reparse.tag == IO_REPARSE_TAG_LX_FIFO ||
> > + data->reparse.tag == IO_REPARSE_TAG_LX_CHR ||
> > + data->reparse.tag == IO_REPARSE_TAG_LX_BLK)
> > + cmds[num_cmds++] = SMB2_OP_QUERY_WSL_EA;
> > +
> > /*
> > * Skip SMB2_OP_GET_REPARSE if symlink already parsed in create
> > * response.
> > --
> > 2.20.1
> >
next prev parent reply other threads:[~2024-09-17 20:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 20:02 Pali Rohár
2024-09-13 20:10 ` Pali Rohár
2024-09-17 20:06 ` Pali Rohár [this message]
2024-09-17 20:23 ` Jeremy Allison
2024-09-17 20:29 ` Pali Rohár
2024-09-17 20:31 ` Jeremy Allison
2024-09-17 20:34 ` Pali Rohár
2024-09-17 20:44 ` Jeremy Allison
2024-09-17 20:44 ` ronnie sahlberg
2024-09-17 20:46 ` Jeremy Allison
2024-09-17 20:59 ` Pali Rohár
2024-09-17 21:19 ` Steve French
2025-08-11 10:52 ` Do not use UID and GID from EAs Pali Rohár
2025-08-29 13:01 ` Pali Rohár
2024-09-17 21:04 ` [PATCH] cifs: Fix getting reparse points from server without WSL support Paulo Alcantara
2024-09-17 21:07 ` Pali Rohár
2024-09-17 21:17 ` Paulo Alcantara
2024-09-23 18:10 ` Pali Rohár
2024-10-06 10:08 ` Pali Rohár
2024-09-17 21:14 ` Steve French
2024-09-28 14:09 ` Pali Rohár
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=20240917200600.6smfxhrppkyjuyku@pali \
--to=pali@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=sfrench@samba.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
all inboxes | Powered by JetHome®