Date: Tue, 8 Apr 2025 22:39:00 +0200 From: Dan Shelton <dan.f.shelton@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: FreeBSD NFSv4.1 nfsd, named attribute support (OPENATTR)? Message-ID: <CAAvCNcCHS=F1jMs53ouiqkaAV_bpht9kvp2PEYofntDrMf2UOA@mail.gmail.com> In-Reply-To: <CAM5tNy5z_eNy9eSk=tpfrtWBirUqJhf29K2=%2BfV-XeRqibLOpg@mail.gmail.com> References: <CALXu0Ufwu_tsZW7mgLLGySbB_XMVOChwEyK1Z%2Br3rpYiXiyXGg@mail.gmail.com> <CAM5tNy5HLEGZc=EMuD%2BQFhFRZg5SwmN6P5KvwMFPO5%2B3Cckh3g@mail.gmail.com> <CAPJSo4Uzhapmpk5zovhycMKXS-egZ3xsC_eFUQWdEUdtKYaMNQ@mail.gmail.com> <CAPJSo4WLs5e0PJY1iO3wHe8L61AgAu5fQbNjmBYhx_-7topOcg@mail.gmail.com> <CAM5tNy4tHt9WFjwj0Zc_pQ4c4DLgr=0UDzcj2vzUjMfTsOH_LA@mail.gmail.com> <CAM5tNy5z_eNy9eSk=tpfrtWBirUqJhf29K2=%2BfV-XeRqibLOpg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Sat, 8 Mar 2025 at 16:43, Rick Macklem <rick.macklem@gmail.com> wrote: > > On Sun, Mar 2, 2025 at 3:48 PM Rick Macklem <rick.macklem@gmail.com> wrote: > > > > On Tue, Feb 18, 2025 at 4:14 PM Lionel Cons <lionelcons1972@gmail.com> wrote: > > > > > > On Mon, 20 Jan 2025 at 13:15, Lionel Cons <lionelcons1972@gmail.com> wrote: > > > > > > > > On Sun, 12 Jan 2025 at 16:50, Rick Macklem <rick.macklem@gmail.com> wrote: > > > > > > > > > > On Sun, Jan 12, 2025 at 2:09 AM Cedric Blancher > > > > > <cedric.blancher@gmail.com> wrote: > > > > > > > > > > > > Good morning! > > > > > > > > > > > > Does FreeBSD NFSv4.1 nfsd support named attributes (e.g. OPENATTR), > > > > > > per https://datatracker.ietf.org/doc/html/rfc5661#section-5.3 > > > > > > > > > > > > ZFS and Solaris UFS support named attributes (via O_XATTR), does > > > > > > FreeBSD do it too? > > > > > No. fork files/resource forks (or whatever you choose to call them) > > > > > have been discussed multiple times. > > > > > > > > > > If I recall correctly, one showstopper was fixing the archive tools. > > > > > There was also the generic argument that Linux doesn't support them. > > > > > Then there was the issue of what VFS/VOP changes were required. > > > > > (The FreeBSD VFS carries vnode locks across VOP calls and is at > > > > > what I would call a lower level than Solaris.) > > > > > --> Which all comes down to who will do the work? > > > > > > > > > > If I recall correctly, there was a time when a group associated with > > > > > CERN needed them to transition away from Solaris. > > > > > > > > That was my team, and there is still the need to do it. What keeps us > > > > FRUSTRATED is the lack of progress. Well, and "no", we cannot do it > > > > ourselves, this is well beyond the expertise my team has. > > > > > > Does anyone have any suggestions on how to proceed? > > The patch found here does the very basics for ZFS (no NFSv4 code yet). > > https://people.freebsd.org/~rmacklem/xattr.patch > I am updating this patch regularly. What is missing are mostly the > "don't do this to named attributes" checks for other syscalls. I'll be > adding those soon. I have done nothing for userland. I am hoping > others might step in to help with that. > --> I do need opinions w.r.t. what else is needed (if anything) syscall wise. > If you want to see this proceed, please test/look at the patches. > > There is now also a patch for the NFSv4 client/server to use the above. > https://people.freebsd.org/~rmacklem/nfs-xattr.patch. Where does the patch define O_NAMEDATTR or O_XATTR? Dan -- Dan Shelton - Cluster Specialist Win/Lin/Bsdhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAvCNcCHS=F1jMs53ouiqkaAV_bpht9kvp2PEYofntDrMf2UOA>