From: Steve French <smfrench@gmail.com>
To: Ralph Boehme <slow@samba.org>
Cc: samba-technical <samba-technical@lists.samba.org>,
"Volker.Lendecke@sernet.de" <Volker.Lendecke@sernet.de>,
Jeremy Allison <jra@samba.org>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: query fs info level 0x100
Date: Mon, 29 Apr 2024 11:13:37 -0500 [thread overview]
Message-ID: <CAH2r5muhcnf6iYaB25k+wZC50b5pNV+enrK=Ye_-9t2NCVdCJQ@mail.gmail.com> (raw)
In-Reply-To: <72ec968a-ac67-415f-8478-d1b9017c0326@samba.org>
On Mon, Apr 29, 2024 at 12:31 AM Ralph Boehme <slow@samba.org> wrote:
>
> On 4/29/24 1:27 AM, Steve French wrote:
> > Trying some xfstests to current Samba (master branch, Samba 4.21),
> > they fail because query fs info (level 0x100) is returning
> > STATUS_INVALID_INFO_CLASS) - this works to ksmbd and I thought it used
> > to work to Samba. I do see the SMB3.1.1 opens with the POSIX open
> > context works - but the query fs info failing causes xfstests to fail.
> >
> > Is that missing rom current mainline Samba?
>
> have you enabled SMB3 UNIX Extensions?
>
> smb3 unix extensions = yes
Yes - it is set to yes in the smb.conf for both the global section and
the per share section
I also see that POSIX extensions in:
1) the server returns posix negotiation context in the SMB3.1.1
negotiate protocol response
2) the server returns the level 100 (FILE_POSIX_INFO) query info responses
But the (current Samba) server fails the level 100 (level 0x64 in hex)
FS_POSIX_INFO with "STATUS_INVALID_ERROR_CLASS"
which causes all xfstests to break since they can't verify the mount
(e.g. with "stat -f").
Nothing related to this on the client has changed, and ksmbd has
always supported this so works fine there.
--
Thanks,
Steve
next prev parent reply other threads:[~2024-04-29 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 23:27 query fs info level 0x100 Steve French
2024-04-29 5:31 ` Ralph Boehme
2024-04-29 16:13 ` Steve French [this message]
2024-04-29 16:37 ` Stefan Metzmacher
2024-04-29 16:44 ` Ralph Boehme
2024-04-29 17:11 ` Jeremy Allison
2024-04-30 3:30 ` Steve French
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='CAH2r5muhcnf6iYaB25k+wZC50b5pNV+enrK=Ye_-9t2NCVdCJQ@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=Volker.Lendecke@sernet.de \
--cc=jra@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=samba-technical@lists.samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.