From: "Aurélien Aptel" <aaptel@suse.com>
To: L Walsh <cifs@tlinx.org>, linux-cifs <linux-cifs@vger.kernel.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Regression -- linux 5.5.3: can no longer mount with unix extentions using cifs 2.1 (Win10-only client additions)
Date: Mon, 24 Feb 2020 12:05:11 +0100 [thread overview]
Message-ID: <87blpo5jq0.fsf@suse.com> (raw)
In-Reply-To: <5E51DAEA.8090702@tlinx.org>
Hi,
L Walsh <cifs@tlinx.org> writes:
> Unix extensions worked long before SMB3.x. It seems there is ongoing work
> to disable SMB2.1 support and replace it with only latest SMB from MS
> compatible with Win10.
* UNIX extension are smb1 only and are only implemented by the Samba
server (not windows).
* POSIX extensions are for smb2+ and are still experimental.
The fact that serverino gets disabled looks like a bug. As Steve said,
the problem seems to be related to ACL.
You should open a bug and provide dmesg and network capture as
documented here:
https://wiki.samba.org/index.php/Bug_Reporting#cifs.ko
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)
prev parent reply other threads:[~2020-02-24 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 1:52 Regression -- linux 5.5.3: can no longer mount with unix extentions using cifs 2.1 (Win10-only client additions) L Walsh
[not found] ` <CAH2r5mtNgEi1noHAY0v_LmnwFOOZ1LsQ20zwTwWNk4uL5HY3EA@mail.gmail.com>
2020-02-24 1:59 ` L Walsh
2020-02-24 6:05 ` Steve French
2020-02-24 11:05 ` Aurélien Aptel [this message]
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=87blpo5jq0.fsf@suse.com \
--to=aaptel@suse.com \
--cc=cifs@tlinx.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@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 NNTP newsgroup(s).