From: Paulo Alcantara <pc@manguebit.com>
To: "Pali Rohár" <pali@kernel.org>, "Ralph Boehme" <slow@samba.org>,
"Steven French" <Steven.French@microsoft.com>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: Special files broken against Samba master
Date: Mon, 09 Dec 2024 16:28:08 -0300 [thread overview]
Message-ID: <1098e751d1109d8730254ada7648ae4d@manguebit.com> (raw)
In-Reply-To: <20241209183946.yafga2vixfdx5edu@pali>
Pali Rohár <pali@kernel.org> writes:
> 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.
No, Ralph's patch has nothing to do with your problem. SMB3.1.1 POSIX
will support NFS reparse points with no EAs, so makes sense skipping
SMB2_OP_QUERY_WSL_EA altogether for posix case.
> 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/
Yes, that patch looks incorrect and untested. Can you tell me how is
@data->reparse.tag supposed to be set, for non-readdir case, if the
compound request wasn't sent yet? Have you tried to stat(2) those files
with your patch?
> But it was somehow rejected as the proper solution should be different:
> https://lore.kernel.org/linux-cifs/20240917210707.4lt4obty7wlmm42j@pali/
Yes. Have you sent a patch with the proposed solution yet?
next prev parent reply other threads:[~2024-12-09 19:34 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
2024-12-09 19:28 ` Paulo Alcantara [this message]
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=1098e751d1109d8730254ada7648ae4d@manguebit.com \
--to=pc@manguebit.com \
--cc=Steven.French@microsoft.com \
--cc=linux-cifs@vger.kernel.org \
--cc=pali@kernel.org \
--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