From: Chuck Lever <chuck.lever@oracle.com>
To: Sebastian Feld <sebastian.n.feld@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: fattr4_hidden and fattr4_system r/w attributes in Linux NFSD?
Date: Mon, 28 Apr 2025 10:15:50 -0400 [thread overview]
Message-ID: <434f6474-b960-4383-8d61-0705632b4c33@oracle.com> (raw)
In-Reply-To: <CAHnbEGLHGX2rMnf=S6CasoNyc939DTe-whcsjt9WhSWG920OoA@mail.gmail.com>
Hi Sebastian -
On 4/28/25 7:06 AM, Sebastian Feld wrote:
> I've been debating with Opentext support about their Windows NFS4.0
> client about a problem that the Windows attributes HIDDEN and SYSTEM
> work with a Solaris NFSD, but not with a Linux NFSD.
>
> Their support said it's a known bug in LInux NFSD that "fattr4_hidden
> and fattr4_system, specified in RFC 3530, are broken in Linux NFSD".
RFC 7530 updates and replaces RFC 3530.
Section 5.7 lists "hidden" and "system" as RECOMMENDED attributes,
meaning that NFSv4 servers are not required to implement them.
So that tells me that both the Solaris NFS server and the Linux NFS
server are spec compliant in this regard. This is NOTABUG, but rather it
is a server implementation choice that is permitted by RFC.
It is more correct to say that the Linux NFS server does not currently
implement either of these attributes. The reason is that native Linux
file systems do not support these attributes, and I believe that neither
does the Linux VFS. So there is nowhere to store these, and no way to
access them in filesystems (such as the Linux port of NTFS) that do
implement them.
We want to have a facility that can be used by native applications
(such as Wine), Samba, and NFSD. So implementing side-car storage
for such attributes that only NFSD can see and use is not really
desirable.
> Is there a fix, or workaround?
There was recent discussion on linux-fsdevel@ about how the community
might introduce support for attributes that Windows has but POSIX does
not [1]. I'm not sure how far along that got, but there does seem to
be some interest in getting Linux native file systems (and the VFS) to
be able to store and access the attributes. Once that is available, then
it should be straightforward to add such support to NFSD.
Until then, I am not aware of a workaround.
--
Chuck Lever
[1]
https://lore.kernel.org/linux-fsdevel/20241227121508.nofy6bho66pc5ry5@pali/
next prev parent reply other threads:[~2025-04-28 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 11:06 fattr4_hidden and fattr4_system r/w attributes in Linux NFSD? Sebastian Feld
2025-04-28 14:15 ` Chuck Lever [this message]
2025-04-29 13:10 ` Sebastian Feld
2025-04-29 13:45 ` Chuck Lever
2025-06-17 7:59 ` Sebastian Feld
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=434f6474-b960-4383-8d61-0705632b4c33@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sebastian.n.feld@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