Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752223AbbFYUJm (ORCPT ); Thu, 25 Jun 2015 16:09:42 -0400 Received: from mo4-p05-ob.smtp.rzone.de ([81.169.146.180]:32517 "EHLO mo4-p05-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751023AbbFYUJf (ORCPT ); Thu, 25 Jun 2015 16:09:35 -0400 X-RZG-AUTH: :IWkQb0WIdvqIIwNfJfyiKBgoQwjwNKmLapmn/F6ALVwJKT3HgOJ8onvjtckvdQ== X-RZG-CLASS-ID: mo05 Message-ID: <558C5E7B.6080607@samba.org> Date: Thu, 25 Jun 2015 22:03:07 +0200 From: "Stefan (metze) Metzmacher" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Jeremy Allison , Andreas Gruenbacher CC: linux-nfs@vger.kernel.org, linux-api@vger.kernel.org, samba-technical@lists.samba.org, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [RFC v3 00/45] Richacls References: <20150523155056.GA2845@jeremy-HP> In-Reply-To: <20150523155056.GA2845@jeremy-HP> OpenPGP: id=DB6F544D32B42CDEFECD2B5B9BBD208C0E53083F Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="A5PE9kND3PJgsSitgC7xQpge8Opra1nQb" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2365 Lines: 74 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --A5PE9kND3PJgsSitgC7xQpge8Opra1nQb Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Andreas, >> here's another update of the richacl patch queue. The changes since t= he last >> posting (https://lwn.net/Articles/638242/) include: >> >> * The nfs client now allocates pages for received acls on demand like= the >> server does. It no longer caches the acl size between calls. >> >> * All possible acls consisting of only owner@, group@, and everyone@ = entries >> which are equivalent to the file mode permission bits are now recog= nized. >> This is needed because by the NFSv4 specification, the nfs server m= ust >> translate the file mode permission bits into an acl if it supports = acls at >> all. >> >> * Support for the dacl attribute over NFSv4.1 for Automatic Inheritan= ce, and >> also for the write_retention and write_retention_hold permissions. >> >> * The richacl_compute_max_masks() documentation has been improved. >> >> * Various minor bug fixes. >> >> The git version is available here: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/agruen/linux-richacl.g= it \ >> richacl-2015-04-24 >=20 > FYI. I have a mostly (needs test suite adding) working module > for Samba for Andreas's richacls code. >=20 > Using it we map incoming Windows ACLs directly to richacls > using the same mapping as we use for existing ZFS ACLs. Yes, we need to make sure the code supports everything we require, proved by working code. We should avoid the disaster with the mostly unuseable F_SETLEASE code for kernel oplocks. Thanks! metze --A5PE9kND3PJgsSitgC7xQpge8Opra1nQb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlWMXn4ACgkQm70gjA5TCD9YjwCdEItA+0iuWp+gJhJDJenkaadp 0ScAn3A2Rql/M3JwvMGuImj3O23OQ5Zt =5AB/ -----END PGP SIGNATURE----- --A5PE9kND3PJgsSitgC7xQpge8Opra1nQb-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/