From nobody Sat Jul 12 00:50:39 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 4bf94P20Sgz614xf for ; Sat, 12 Jul 2025 00:51:01 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bf94N246Pz3cCn; Sat, 12 Jul 2025 00:51:00 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=eBFXSwIb; spf=pass (mx1.freebsd.org: domain of rick.macklem@gmail.com designates 2a00:1450:4864:20::632 as permitted sender) smtp.mailfrom=rick.macklem@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-ae0df6f5758so466058466b.0; Fri, 11 Jul 2025 17:51:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1752281453; x=1752886253; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=RmAPuY11DRHEGWf2fbvjK/+eZei7sVP5tmORsEmLlks=; b=eBFXSwIbTK5i5ImbHgMhBlvq6vS9gjAPXfSRBXlrVgXIzVl4xsSR7iDqBTWGthYuhj xw1KnMZGEALT5BX6j5HSP3t2+uMTWNd5y7nAWqDFsFz5De/CObzPK3y+W5T3v6wAInA+ H2QpjNzsQYIlGAOzWekBsJ1+SLuJjV5HM3krl9XL7WocVJskqgqCMA/DCfY789wrftuo k3503W8AZJiOwulL/nAHj4HqAdzKfdCfGcSAnGnn2UNL8BXMKcoAfqyNnhQuhd6ZAvMI 9nGdyUSVTlt0WJQCaR2+aml86EQmPr4Q6WW7PSrLv8VosnVYfzmht88HD0z2+n7QfqFY eV8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752281453; x=1752886253; h=content-transfer-encoding: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=RmAPuY11DRHEGWf2fbvjK/+eZei7sVP5tmORsEmLlks=; b=dVmFyRsF+TMdF5faZqt3hoyo0zYEq4mQeY3XeTqsDpjPZ4K5z9iwnlxkjcZ4LBx4q5 EyIr4A+w2cC2srZ7V3JCztO++gEkWBJEV7YQL8H5RcxyXklPo96gBCBb2+0nr0AbimuA 7vFju3i3j11sRIBEvCWx71Uu2TF7axN9Rh1MHkZ3GyCFAddopoJsQYNO3azCkGuAfgIN w3FvbJG8OIIRxPBDyTICMBbEeJ7udUP5aynnD2HacKd2c6mLzE8gMoMKLK+zsjfiGg/L kDKXCQEn5vuOHQhg0xUIPvlkfcKiGXp/hwOmdCC9NsuPCmjmXFrFPPQ/7vsATCq/0jy/ GSTA== X-Forwarded-Encrypted: i=1; AJvYcCVplLGAyxC0m7W/XduNbD9jjXJDAaA042q4T0xnDz/7n4mVmBdiy8qKIR/5teeTb6f1Vjg=@freebsd.org X-Gm-Message-State: AOJu0YzJ+pLquyQiw4CN7LgP1yPj3o//HQyDDB9/SO8z5YG64H2FsSRg /JC5aeKQtfz0BCOIIFMQVZekp8X8ID5n89xU5K62aN9YKM9ChDAHUFj/lX0XcPQeQkAsEhFZn8/ W0lNcRyreWIfJc0vJ4PpXx3ufVbYULf75 X-Gm-Gg: ASbGncv06bZDEqYiIeKKIpTXTV+20o/sz+VTsxy+LA1Qu9J6aoI26xGGK7xs7vATJdi Wf6KREEoCPOG9WUqJoYoiZ8qxhtJcBH33YSq3MLeY+w3rasDbMDdaY31wF0oufDNb/FJvsOTHtJ X60aljCvsIUCGRLzdu298/HRf0lJBdDw+u3lWk0o4UY59ZCOdu6Oy1hdJ4lNMWjqXROiyRrtCvo 7RDBR9bZJ1E/Aqm0YJ6j+6pdlga+QToXRdSpuk= X-Google-Smtp-Source: AGHT+IF9WpdnOcwXaBIjbqU5Y0VsKUgjElKT8j/lUMOHIBnviIrcDxbmKHHOgUvP1kb3SNS+EwNA/AcP5GjHbdIqlgk= X-Received: by 2002:a17:907:c897:b0:ade:40cb:2515 with SMTP id a640c23a62f3a-ae6fc40132bmr581823366b.59.1752281452522; Fri, 11 Jul 2025 17:50:52 -0700 (PDT) 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 References: In-Reply-To: From: Rick Macklem Date: Fri, 11 Jul 2025 17:50:39 -0700 X-Gm-Features: Ac12FXz64uf2HNkQomqmOdWiQnsU6PGCkl9qBx6KvZL12V6AouuKumLUYscANfk Message-ID: Subject: Re: RFC: Documenting weird case w.r.t. Solaris style extended attr (ZFS) To: Konstantin Belousov Cc: FreeBSD CURRENT , Alexander Motin Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-2.32 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.989]; NEURAL_HAM_SHORT(-0.88)[-0.876]; NEURAL_SPAM_LONG(0.54)[0.545]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; TO_DN_ALL(0.00)[]; TAGGED_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; ARC_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::632:from]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4bf94N246Pz3cCn X-Spamd-Bar: -- On Thu, Jul 10, 2025 at 10:55=E2=80=AFAM Konstantin Belousov wrote: > > On Thu, Jul 10, 2025 at 06:59:35AM -0700, Rick Macklem wrote: > > I've done a series of commits to main to add support for > > Solaris style extended attributes (which I called named attributes, > > which is the NFSv4 term for them). > > > > ZFS is currently the only local file system that will support them > > and only if the ZFS property "xattr" is set to "dir". > > > > If "zfs set xattr=3Ddir " is done before any user namespace > > extended attributes are created for files via extattr(2), I think > > everything makes sense. > > --> There is one set of extended attributes that are visible through > > both extattr(2) and named_attribute(7). > > > > However, if extattr(2) is used to create user namespace extended > > attributes when "xattr=3Dsa" and then "xattr" is set to "dir", these > > extended attributes are only visible to extattr(2) and not > > named_attribute(7). > > --> I will note that you can use tar(1) to copy the files and then the > > extended attributes become visible to named_attribute(7). > > I do not see any way to avoid this, but it should at least be documente= d. > > > > So, where do you think I should document this? > > - I could put it in named_attribute(7) as an additional case where > > the two extended attribute system call mechanisms cannot be > > used. (I was hesitant, since this is ZFS specific). > > Does this sound ok, or is there somewhere better to put it? > > (zfsprops(7) is another possibility, since it already documents > > "sa" and "dir" values for the "xattr" property.) > > I do not see why not put it to named_attribute(7) page. We do not have a > ban on adding important fs-specific notes in the generic documentation. > More, I think it is a proper place to document the details instead of > spreading them into corners. > > BTW, would you consider adding named attrs support to tmpfs? > I believe it is useful for tmpfs to be on par with the union of > all features of our local filesystems. I'll take a look at tmpfs someday. Probably not in time for 15.0. Thanks for the comments, rick >