From nobody Fri Apr 04 16:06:03 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4ZTk4417pSz5s0m6 for ; Fri, 04 Apr 2025 16:06:12 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (prime256v1) client-digest SHA256) (Client CN "mail.oetec.com", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ZTk431x2nz4NqD for ; Fri, 04 Apr 2025 16:06:11 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=VreFBclg; dmarc=pass (policy=quarantine) header.from=blastwave.org; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org Received: from [172.16.35.3] (pool-99-253-118-250.cpe.net.cable.rogers.com [99.253.118.250]) (authenticated bits=0) by mail.oetec.com (8.17.1/8.17.1) with ESMTPSA id 534G63Zs003938 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Fri, 4 Apr 2025 12:06:05 -0400 (EDT) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1743782765; bh=TeOvobjwogE9x9+mAJ5zhNbPn1cFOIQmSflH/Pe9Py4=; h=Date:Subject:To:References:From:In-Reply-To; b=VreFBclglSsQVb1zXoVf+MX6GbHo5uRmstSl+G/4BLMs0GQP2HKPAndn4FqtGO6Kf NyMxLmrzKZOQz2mDUPtjGUj8wZh/EDB1HCQaBWik3BFih0mB/Yylsvnc7T7eoklb9l fFedkFsN36cd31EEAW2bjxk9IOw88dQsQmxEf488OxSnf8ygTbhqfvHyX/t+Rf5819 0j3BamQVkQwdRq2jXsP9O7GMfebf72CpWmNXzZR3gjo50IUZBUqkDtXBkfTrU0l0Ma E96ovE9g7ube0tG3gDxSJ9rxSeW9tYYEUSxyK3p4ESgDzsaGXTc5J1S0WphEPB1h6B asPDBB6eHMkFQ== Message-ID: <613d4907-6837-4cdb-abc5-86e53a6cce14@blastwave.org> Date: Fri, 4 Apr 2025 12:06:03 -0400 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Heads Up: commit 2ec2ba7e232d just hit main Content-Language: en-CA To: freebsd-current@freebsd.org References: From: Dennis Clarke Organization: GENUNIX In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 534G63Zs003938 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Spamd-Result: default: False [-4.40 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.93)[-0.932]; NEURAL_HAM_MEDIUM(-0.77)[-0.771]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; R_SPF_ALLOW(-0.20)[+mx:c]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+] X-Rspamd-Queue-Id: 4ZTk431x2nz4NqD X-Spamd-Bar: ---- On 4/4/25 10:25, Rick Macklem wrote: > On Fri, Apr 4, 2025 at 6:37 AM Rick Macklem wrote: >> >> On Fri, Apr 4, 2025 at 1:48 AM Dennis Clarke wrote: >>> . . . >>> well ooops .... what was the idea here again ?? >> Well, this has nothing to do with my recent commit. >> Thus.... ooops. >> ZFS has always supported NFSv4 ACLs (and not POSIX draft ACLs) >> on FreeBSD. (I actually am planning on a ZFS patch to add POSIX >> draft ACL support, but I haven't even started to work on it. I do have >> an IETF draft that adds POSIX draft ACL support to NFSv4.2.) >> >> If you look at the setfacl man page, it shows you how to set NFSv4 >> ACLs. > Oh, and to clarify it, ACLs are stored as "system" extended attributes, > which this new syscall/KAPI does not access and, in general, anything > else can be stored in extended attributes as well. > So no easy way for a user/sysadmin to see what the big "Heads Up" did. Dennis