From: "Pali Rohár" <pali@kernel.org>
To: Ralph Boehme <slow@samba.org>,
Steven French <Steven.French@microsoft.com>,
Paulo Alcantara <pc@manguebit.com>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: Special files broken against Samba master
Date: Mon, 9 Dec 2024 19:39:46 +0100 [thread overview]
Message-ID: <20241209183946.yafga2vixfdx5edu@pali> (raw)
In-Reply-To: <458d3314-2010-4271-bb73-bff47e9de358@samba.org>
Hello, this patch is incomplete and still does not fix the main problem
that SMB2_OP_QUERY_WSL_EA command does not work with any Windows SMB
server except the last Windows Server version. On non-recent Windows
versions it is not possible to set both EAs and reparse point at the
same time and Windows SMB server is returning error when trying to query
EAs on file with reparse point.
Which basically means that it is not possible to query data about the
special files from Windows SMB server (except 2022 version).
More details are in the email which I wrote in September:
https://lore.kernel.org/linux-cifs/20240928140939.vjndryndfngzq7x4@pali/
I proposed similar but extended patch which skips asking for EAs based
on reparse point:
https://lore.kernel.org/linux-cifs/20240913200204.10660-1-pali@kernel.org/
But it was somehow rejected as the proper solution should be different:
https://lore.kernel.org/linux-cifs/20240917210707.4lt4obty7wlmm42j@pali/
And that is why I'm surprised that the batch below was accepted...
Are you planning to implement a proper solution? If not that I would
propose to reconsider my original idea, which will workaround also
Windows SMB server, and not only Samba server.
As I wrote in previous emails, I think that this is a serious issue as
it disallow to use any reparse points against non-recent Windows Server
systems.
On Wednesday 27 November 2024 20:23:29 Ralph Boehme wrote:
> From a57c32da874f285af266b7fbbaefb7940991d049 Mon Sep 17 00:00:00 2001
> From: Ralph Boehme <slow@samba.org>
> Date: Fri, 15 Nov 2024 13:15:50 +0100
> Subject: [PATCH 1/3] fs/smb/client: avoid querying SMB2_OP_QUERY_WSL_EA for
> SMB3 POSIX
>
> ---
> fs/smb/client/smb2inode.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/smb/client/smb2inode.c b/fs/smb/client/smb2inode.c
> index e49d0c25eb03..ab069d5285c5 100644
> --- a/fs/smb/client/smb2inode.c
> +++ b/fs/smb/client/smb2inode.c
> @@ -941,7 +941,8 @@ int smb2_query_path_info(const unsigned int xid,
> if (rc || !data->reparse_point)
> goto out;
>
> - cmds[num_cmds++] = SMB2_OP_QUERY_WSL_EA;
> + if (!tcon->posix_extensions)
> + cmds[num_cmds++] = SMB2_OP_QUERY_WSL_EA;
> /*
> * Skip SMB2_OP_GET_REPARSE if symlink already parsed in create
> * response.
> --
> 2.47.0
next prev parent reply other threads:[~2024-12-09 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 19:23 Special files broken against Samba master Ralph Boehme
2024-12-02 22:40 ` Paulo Alcantara
2024-12-03 10:02 ` Ralph Boehme
2024-12-03 19:56 ` Steve French
2024-12-03 20:25 ` Ralph Boehme
2024-12-05 0:06 ` Steve French
2024-12-06 12:11 ` Ralph Boehme
2024-12-06 14:45 ` Steve French
2024-12-09 18:39 ` Pali Rohár [this message]
2024-12-09 19:28 ` Paulo Alcantara
2024-12-09 19:34 ` Pali Rohár
2024-12-09 19:42 ` Paulo Alcantara
2024-12-09 19:54 ` Pali Rohár
2024-12-10 13:19 ` Paulo Alcantara
2025-01-01 13:39 ` 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=20241209183946.yafga2vixfdx5edu@pali \
--to=pali@kernel.org \
--cc=Steven.French@microsoft.com \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=slow@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