lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3k4l5lgfa.fsf@linux.vnet.ibm.com>
Date:	Tue, 26 Oct 2010 10:05:37 +0530
From:	"Aneesh Kumar K. V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	"J. Bruce Fields" <bfields@...i.umich.edu>
Cc:	sfrench@...ibm.com, ffilz@...ibm.com, agruen@...e.de,
	adilger@....com, sandeen@...hat.com, tytso@....edu,
	jlayton@...hat.com, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, Jeremy Allison <jra@...ba.org>
Subject: Re: [PATCH -V4 00/11]  New ACL format for better NFSv4 acl interoperability

On Mon, 25 Oct 2010 15:09:02 -0400, "J. Bruce Fields" <bfields@...i.umich.edu> wrote:
> On Tue, Oct 12, 2010 at 11:35:07AM -0400, J. Bruce Fields wrote:
> > On Tue, Oct 12, 2010 at 12:47:38PM +0530, Aneesh Kumar K. V wrote:
> > > What we need in the first step is to get VFS changes reviewed.Once we
> > > agree on the VFS changes done, then we can start looking at the changes
> > > upto NFS richacl nfs support. When get that merged then we can start
> > > having discussion on how local file system maintainers want to migrate
> > > the existing file system with posixacl to richacl.
> > 
> > OK.  So, personally: I'm resigned to the idea that we want support for
> > this ACL model.  The vfs changes look OK to me (and wouldn't be changed
> > by any comments I'd have on the more richacl-specific patches to
> > follow).  So that's an ACK from me on the first set of these patches,
> > assuming it's OK with people to merge these things one step at a time.
> 
> Is there any progress on this?
> 

The next step would be to get Al Viro or Christoph to look at the
proposed VFS changes and get an ACK on them. Meanwhile i can rebase
the full series to the latest linux kernel. 

Apart from that is there any specific changes you would like to see
as a part of richacl patch series. Would you like to see the full
patchset posted to the list or should we go in steps as mentioned above
?

-aneesh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ