From: Chuck Lever <chuck.lever@oracle.com>
To: Lionel Cons <lionelcons1972@gmail.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>,
CIFS <linux-cifs@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: NFSv4 server sets/gets FATTR4_HIDDEN, FATTR4_SYSTEM, FATTR4_ARCHIVE attributes from Linux "user.DOSATTRIB"?
Date: Wed, 5 Nov 2025 09:53:03 -0500 [thread overview]
Message-ID: <21813208-da86-427b-9e6b-4ecb066e6763@oracle.com> (raw)
In-Reply-To: <CAPJSo4Wa4EGCTQhfK7O9S9O7rmkb5aQHg85_R19FJHqCGi1Usg@mail.gmail.com>
On 11/5/25 9:47 AM, Lionel Cons wrote:
> Is it feasibe that the Linux NFSv4 server sets/gets FATTR4_HIDDEN,
> FATTR4_SYSTEM, FATTR4_ARCHIVE attributes from Linux "user.DOSATTRIB"
> XATTR used by SMB/CIFS?
>
> This is for MacOS, MacOS X and Windows client support.
Of course NFSD can access that attribute. The question is: is that the
agreed-upon standard storage location that everyone else uses for those
settings? (I don't know the answer, so copying linux-cifs@ and
linux-fsdevel@ )
--
Chuck Lever
parent reply other threads:[~2025-11-05 14:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAPJSo4Wa4EGCTQhfK7O9S9O7rmkb5aQHg85_R19FJHqCGi1Usg@mail.gmail.com>]
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=21813208-da86-427b-9e6b-4ecb066e6763@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lionelcons1972@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).