From nobody Thu Jul 10 13:59:35 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 4bdGgZ5D6Yz615Y9 for ; Thu, 10 Jul 2025 13:59:54 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 4bdGgZ0d2Qz412w; Thu, 10 Jul 2025 13:59:54 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b="ieUtpzT/"; spf=pass (mx1.freebsd.org: domain of rick.macklem@gmail.com designates 2a00:1450:4864:20::534 as permitted sender) smtp.mailfrom=rick.macklem@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-60bf5a08729so1776546a12.0; Thu, 10 Jul 2025 06:59:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1752155988; x=1752760788; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=RcI6jVrLEd9TRHUaXiCH+/6w6nlo6VBPu3PJlnweJq8=; b=ieUtpzT/+SCsXv7bT7RPWeJanCQynaddvTVBhDoil4IXSsgHI81MeQbamUA1ahgmKr sCmT5YnmI+4nXTEq5lfjB1JzbiH2h/er7ty0MrSH8Q4MBrn1itr55TNoiorFv3tbm3Jl yQGnKhOa7HIo45phL/1tlID6ZJJZzwQo6om7RlHRU3JiSqzu9DkD916pBFOputFEB8ga UMeNUuNFJu+ZlSoqmFBw6MbFLn9gOmAunbdlKmzEy1a1kDG7qLpQ7XNNnADZl5dJI584 T0pd1KKWw8zyAK+l3LZ7LRgs7UyWD0QRyB4hSVO2tnig/QJ26CuCkrxGM0akEgtUoH8q zqfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752155988; x=1752760788; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=RcI6jVrLEd9TRHUaXiCH+/6w6nlo6VBPu3PJlnweJq8=; b=YaKB+UdsOcBfj5L/qt0nIMPhn0Shk+EKnL8YJTPpvjN7xWMaZIloE7flRltvYhc3l3 na52RaxLulR30kTy8Vwv02i72SickWMkxzChyxnDJuCdJUbUDN2lzuv0glTZIVYCpXMD oDHUNZQ8gs5X1z8kl6xw9zKJcbbOgwwIsQbo2WqPYisShLhmJkQiKAz0i4xGIkbZ9tR2 Ws5Qvxlhe1kC3Nd1HdI/7UPki2vktu+Gwz2iScHZkN+e0R8WDsX44KPmgcSQHATrrkqL cpWanntTyJ3v6VwIz0BF5LEKLAOqAWDIQqFyYx/bg1sLbdFdRbq3N488izLuQbXLPeYx Nx/g== X-Forwarded-Encrypted: i=1; AJvYcCUVTDNy3vgbQzvxsCFyzX8Gt/szbSqKvJnNcHzrtCOseTGCE6qMz8Kuo/49YYD7kHLc+mTx@freebsd.org, AJvYcCX957hsYGDDfEOAKBJfOmQNX/8tHLlZU+fvxVsp7v2Cmppc6Qpurj26ORgse81QenheRmE=@freebsd.org X-Gm-Message-State: AOJu0YzQzLCmCfFofG0MRqe9pTNAChFVcIHOnwSnAsJd6eqayJT/AO70 BbL1f7FjSPz7dwIn2BVeSIdPBYIKj2crsIWUmHfzVdeY+aNje2AkLohvv3n1+BXLf8klvEuu0y1 DDS34keySl/hsojLGxth3aLstPwbOYVfK X-Gm-Gg: ASbGncu/Wzgrr6XdzyrVbqTHP3rGeXdyGu1BUIf7p/offwnbVK0hJiMX/N/y3l0jpKj L9ehgQiZcMcKNzYHzd2FrjRDM4YAHyiuWEzai4PeCnhiJF33lEZSMf4dWMkkF/sAeHq1LT26CHy PlsdLFZsIwe2X9FvcaS9/zQG/htSzzqwzCIdeQmpCd4qOu6nQg1jVkPvv7V3eYeMqk4TMlTNL6m X8= X-Google-Smtp-Source: AGHT+IG6NIlkXpv95GuUBBfx8R1kL1gQXf2yEAVpxq6GGqBMetDfDf4gtG+U30MAtua8ka/XS5S8bXzZplS1nZTvz8g= X-Received: by 2002:a05:6402:4404:b0:608:f493:871c with SMTP id 4fb4d7f45d1cf-611c8495fe3mr2632220a12.14.1752155987338; Thu, 10 Jul 2025 06:59:47 -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 From: Rick Macklem Date: Thu, 10 Jul 2025 06:59:35 -0700 X-Gm-Features: Ac12FXzCxjG-9vajLTVlCnF-CCufDmDcbTi2E38aXrlXn-6RwT4mt3tksMZqQdk Message-ID: Subject: RFC: Documenting weird case w.r.t. Solaris style extended attr (ZFS) To: FreeBSD CURRENT , Alexander Motin , Konstantin Belousov Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [0.52 / 15.00]; NEURAL_SPAM_LONG(1.00)[0.999]; NEURAL_SPAM_MEDIUM(1.00)[0.999]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.48)[-0.480]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TAGGED_FROM(0.00)[]; TO_DN_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROMTLD(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::534: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)[]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4bdGgZ0d2Qz412w X-Spamd-Bar: / 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=dir " 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=sa" 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 documented. 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.) Thanks in advance for any comments, rick