IETF Logo Mail Archive

[nfsv4] Re: Our different approaches to draft POSIX ACL support in NFSv4

Rick Macklem <rick.macklem@gmail.com> Fri, 26 July 2024 03:38 UTC

Return-Path: <rick.macklem@gmail.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 DF0D3C16942C for <nfsv4@ietfa.amsl.com>; Thu, 25 Jul 2024 20:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2PM6IxQuRyLX for <nfsv4@ietfa.amsl.com>; Thu, 25 Jul 2024 20:38:57 -0700 (PDT)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75CA0C16942A for <nfsv4@ietf.org>; Thu, 25 Jul 2024 20:38:57 -0700 (PDT)
Received: by mail-pj1-x1032.google.com with SMTP id 98e67ed59e1d1-2cf11b91813so402520a91.1 for <nfsv4@ietf.org>; Thu, 25 Jul 2024 20:38:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721965136; x=1722569936; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=F2E4TVpUEbMlZ0F2bHsYuxxRmJ36xCLU//0nV6HQIq0=; b=nICsp9Gf2K0NLPZoIEQNc479FEzpHonOOlGH1WTSZ85YVz88vtFjUpYdJOO8M5O8u0 KKh0jw3ABkzIwDTiqWjLorBOFwRJBNZwlF+kpTRri77ymo9CLFS877ufnJd2QeyVQN1N q8uTOimGKOWVKR3OEGJKxQeMbrJDnj9kbDj6/Hh/cU0NEymvPdXGHxNXxa2UzdQdHpn0 z5KLnflzuRkdEuU/QRbos8z24XO3Ih7BGDL5xD5sBJwfxU2EbZkeDW1ROT7Y/s2/AneF cii/kVWkbSflvWNALqHQo8khQcvjKoBQxMqNWdMW6WN1VE/C3oZwaz/z1aNKMCXI/v7X TWaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721965136; x=1722569936; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=F2E4TVpUEbMlZ0F2bHsYuxxRmJ36xCLU//0nV6HQIq0=; b=B3YQgpQSCiCjsoyV/AH94ULPFO6fCABS8/naZwsii31waFJhlsg+/NlJJSKJQ7s6Xy M0HZMdkQMdtqqAAu4XBlJ1pvvEDcnG9cZCnGq99A7WGeXqLlHofo8VrUcsYYN/VvMvKc tmwP4H9cr5ZAMWypuKrMk81MjIpkSbJMO/BVmGS/aGqJo3eiIPTjtXXhQLZcg04R62s/ HOvj8o3K/6vefw3s5dvt78GkJRrANKo/n5rrBl8NKBXFWSRulO59fUzH9AVsFilkWO30 gKlX45JjOTf1Im5SoIy7M6tEAPtRTls93MA18UEu9Hm+BXb+KIhOpA2ywBbkATK41bEJ ZrWQ==
X-Forwarded-Encrypted: i=1; AJvYcCUdjNtVpD+/3d8aTrlHS5tN9OhK4trC2muFIX6DPL8IVTFvT4Ga0WIC76hOA5VT8m2BeR5klPpubQ9AJJ8Tdg==
X-Gm-Message-State: AOJu0Ywx/JqZ6rIEW6Qn6LRgYaDibrHXHaA3Mc0o/wVhkQ8s1HVO9PgH rRPOQL3MzxRnx34jwVoLjWh+DZz8TuVXtXfp6c48loBqiTFHuN81iOxECbqnbSUGVHVmTERJE4r CSa8ytWDKwQtPHA/EafACpw4scg==
X-Google-Smtp-Source: AGHT+IHQ8+eMB7j9F+A3hnaOnxvc13xmu7MwqswzlG3OeqLHmTe8UwZlWuJhaOY5SrqTRUFDpju2Z0azF78gNiEm9CM=
X-Received: by 2002:a17:90b:955:b0:2c9:6ad9:b75b with SMTP id 98e67ed59e1d1-2cf2393434amr4601916a91.40.1721965136261; Thu, 25 Jul 2024 20:38:56 -0700 (PDT)
MIME-Version: 1.0
References: <CADaq8jdvZ5pcFNN5zjuVHLTO30v9=2kYKzFdRxxbkTmHYZdTdA@mail.gmail.com> <CAM5tNy7Fw954gCzYHCTjRg7th_njSHhxznni48Zz4xsSXT631A@mail.gmail.com> <53DAEF45-2A4D-4066-97C2-7B09018DE99B@oracle.com> <CAM5tNy6a4ZG90i2ugXzuPqQ1zrsK9m8jLRKmv9VpnFG6m_Pqew@mail.gmail.com> <DD250FBD-A434-4294-818A-5728757CE032@oracle.com> <d1c538065728c17df66a6f9e79e55d90849fc866.camel@gmail.com> <D352FEB9-A487-4B3E-9BC8-DB2C1896F941@oracle.com> <8efc39289ecef97624622cfc431f890736b579a0.camel@hammerspace.com> <33FA1D6E-73B3-43A1-B65C-D806156E39A5@oracle.com> <cf8a48e517210512755455dd78352ae5b64f7949.camel@hammerspace.com> <449AF448-1471-47CD-B5C5-3A3A5FB9FB12@oracle.com> <2e32694382df3e70a93edcf40434a41729031e55.camel@hammerspace.com> <83c39a7b12c05b0f1a0fa6e069b08e399864277a.camel@hammerspace.com> <CADaq8jfw1FVH3dxOEJAZLrw_S5y2F6eaGkcfpha4X8BBNWgRSQ@mail.gmail.com> <6903782a95875541489844e33541114f0bf01acb.camel@hammerspace.com> <CADaq8jdFYo_DtRxS3h17dyQSFqXeoR60OjsjMM=o35HDg8ZnNg@mail.gmail.com> <855662e75c4433042fd9875c2c9c5d0244c929da.camel@hammerspace.com> <CADaq8jdZzqt-bXB4YsO=R2qpT9MNfwvSAJyBJng1qjGFTn2tbw@mail.gmail.com> <CAM5tNy5oVnyP66fzZsQXnNQcTYtpQaR59Q6io92F4LX74gPivQ@mail.gmail.com> <7FAE51A2-6E14-412F-8B0A-AC617AE4173B@oracle.com>
In-Reply-To: <7FAE51A2-6E14-412F-8B0A-AC617AE4173B@oracle.com>
From: Rick Macklem <rick.macklem@gmail.com>
Date: Thu, 25 Jul 2024 20:38:41 -0700
Message-ID: <CAM5tNy6yHfm5sn12krYtpOw4=UpyTJPCO+rq4dzi3gAggsSskg@mail.gmail.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Content-Type: multipart/alternative; boundary="000000000000433bcd061e1e40ad"
Message-ID-Hash: LR5ATYPWDNYCBCDBC7NZNE3DMBCDLVO6
X-Message-ID-Hash: LR5ATYPWDNYCBCDBC7NZNE3DMBCDLVO6
X-MailFrom: rick.macklem@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-nfsv4.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Trond Myklebust <trondmy@hammerspace.com>, Bruce Fields <bfields@fieldses.org>, "nfsv4@ietf.org" <nfsv4@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [nfsv4] Re: Our different approaches to draft POSIX ACL support in NFSv4
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/biplsKpXKOu6PUGUNhd8YCl0BCw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Owner: <mailto:nfsv4-owner@ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Subscribe: <mailto:nfsv4-join@ietf.org>
List-Unsubscribe: <mailto:nfsv4-leave@ietf.org>

On Thu, Jul 25, 2024 at 6:50 AM Chuck Lever III <chuck.lever@oracle.com>
wrote:

>
>
> > On Jul 25, 2024, at 9:44 AM, Rick Macklem <rick.macklem@gmail.com>
> wrote:
> >
> > Christoph pointed out to me that having multiple ACLs on a file is not
> > reasonable.  The draft I am writing will require a server to only support
> > one ACL model/file. (I think it needs to be a server choice and could be
> > indicated to the client by which attributes are supported for the fiile.
> > (This is related to the last point.  I'll leave the rest for others.)
>
> I agree there should be one per file, and that the server's
> local file system should determine which type of ACL it can
> support. (I don't envision a scenario where one file system
> could support multiple types of ACLs).
>
>
> > It would be nice if, somehow, the Linux folk could determine how often
> > the mapped NFSv4 ACLs are used on the Linux NFSv4 servers?
>
> As far as I am aware, NFSD does not use mapped ACLs, but I
> haven't done an in-depth look.
>
What I was referring to is when a NFSv4 client does a
Getattr or Setattr for ACL and the knfsd maps to/from
the POSIX draft ACL used on the server's file system.
(It does do this, but I understand the above was poorly
worded.)

rick

>
>
> --
> Chuck Lever
>
>
>

v2.26.15 | Report a Bug | By Email | System Status