[nfsv4] Constructing a NFSv4 ACL from POSIX mode bits

"Haynes, Tom" <thomas@netapp.com> Tue, 24 July 2012 19:33 UTC

Return-Path: <thomas@netapp.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21C6611E8087 for <nfsv4@ietfa.amsl.com>; Tue, 24 Jul 2012 12:33:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eEXxWA6P+txM for <nfsv4@ietfa.amsl.com>; Tue, 24 Jul 2012 12:33:53 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 566D321F8554 for <nfsv4@ietf.org>; Tue, 24 Jul 2012 12:33:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,647,1336374000"; d="scan'208";a="668284130"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 24 Jul 2012 12:33:53 -0700
Received: from loghyr.hq.netapp.com (loghyr.hq.netapp.com [10.34.16.47]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q6OJXqf9010387; Tue, 24 Jul 2012 12:33:52 -0700 (PDT)
Received: from loghyr.hq.netapp.com (localhost.localdomain [127.0.0.1]) by loghyr.hq.netapp.com (8.14.5/8.14.5) with ESMTP id q6OJXqZ0004981; Tue, 24 Jul 2012 12:33:52 -0700
Received: (from thomas@localhost) by loghyr.hq.netapp.com (8.14.5/8.14.5/Submit) id q6OJXnTi004980; Tue, 24 Jul 2012 12:33:49 -0700
Date: Tue, 24 Jul 2012 12:33:49 -0700
From: "Haynes, Tom" <thomas@netapp.com>
To: bfields@fieldses.org, linux-nfs@vger.kernel.org, nfsv4@ietf.org
Message-ID: <20120724193348.GA4977@netapp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: [nfsv4] Constructing a NFSv4 ACL from POSIX mode bits
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 19:33:54 -0000

Bruce,

In looking at http://tools.ietf.org/html/draft-ietf-nfsv4-acl-mapping-05, it
states that when mapping the write bit, only for the owner do we set
ACE4_WRITE_ACL.

Back in version 00, it is open as to whether we can also set it for the
group and other if they have the write bit set.

I looked back at the NFSv4 WG aliases and I see some discussion from Lisa
on how Solaris only ever sets it for the owner due to POSIX restrictions
via chmod(). So, now I know how another server does it.

What does the Linux server do in this case?

Thanks,
Tom

-- 
thomas@netapp.com, ex-cfb