Date: Sat, 3 Sep 2011 11:10:19 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: mdf@FreeBSD.org Cc: svn-src-projects@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r225351 - projects/ino64/sys/ufs/ufs Message-ID: <alpine.BSF.2.00.1109031107100.34583@fledge.watson.org> In-Reply-To: <CAMBSHm-%2BC9t2Vnwh5z=c8Tg9VEQHGv0pGoK2t%2Bp6w4G=d4MNqA@mail.gmail.com> References: <201109021852.p82IqH1M011851@svn.freebsd.org> <CAMBSHm-%2BC9t2Vnwh5z=c8Tg9VEQHGv0pGoK2t%2Bp6w4G=d4MNqA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2 Sep 2011, mdf@FreeBSD.org wrote: > Is anyone using UFS_EXTATTR_AUTOSTART? I think the code is now correct for > the endpoint of the returned dirent's, but it would be nice to have a review > and/or someone test the code. Good question. UFS_EXTATTR_AUTOSTART was the precursor to UFS2 extended attributes (which integrated EAs more tightly into the file sytem design), so is relevant only on UFS1. Anyone using ACLs, MAC, etc, on UFS1 will be using at least options UFS_EXTATTR. This code is pretty easy to test -- create a UFS1 file system, and use extattrctl to configure storage: mkdir -p /.attribute/system cd /.attribute/system extattrctl initattr -p / 388 posix1e.acl_access extattrctl initattr -p / 388 posix1e.acl_default Then unmount, set the "acls" flag with tunefs, and remount. If ACLs work, then the attributes were properly configured when the file system was mounted. I imagine it's not seeing a lot of use with widespread deployment of UFS2, but when we have broken it in the past, we have received bug reports. Robert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1109031107100.34583>