From nobody Thu Jul 03 08:57:15 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 4bXrHk6rS8z60Pkt for ; Thu, 03 Jul 2025 08:57:22 +0000 (UTC) (envelope-from olce@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bXrHk4P1rz3LQR for ; Thu, 03 Jul 2025 08:57:22 +0000 (UTC) (envelope-from olce@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1751533042; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4yoAYPb+n8i6NlzKxqg2XzSeItqZiJ7aLoHe31D7guM=; b=dnR+zfy2bzhnchzYKQU8MpNK9LeM8csrLqL/mxmHN2jS/WjQ4LEdOusltNyQe0SzyKT5S9 13Sow13ukBLWrcyJw6mPK5DaoeWgrYXH2LYQLA3vn2JGy1tfPZrBlWxr5eAN7776A7Aw0S 3GVRtYH3tQTJdINHbiiy02jwWQfYJyAalBxAnGLd1CGfqd90ojNUD9D/bAzSkP78jNMT8s l+1rv6nZBYkmRGENO/O6Zto3oOKSM15Q5sKF2qW+Te9en9mWk0QEnKXjRkUSdkX8t8Il35 sFfqCT07Gt1UZxqltFDFiaZaPGbiG31hqIJkISsvLfSXat72R4uxiu7Nj+zQWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1751533042; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4yoAYPb+n8i6NlzKxqg2XzSeItqZiJ7aLoHe31D7guM=; b=MfLJPlKPAFT4H3znwe8x6lS6NIHwFfNvPXR6FOyUEJGDpc+xj75HecVKPgkNM3YP6rxhkB misnw7JQQX8jgmGmIp0Q8GfpublWFWuh/ETXJoNGp2broyo60dv2dAO29O+WerG0tEEBqk axsW25bk/m7LC0Z2elMPVwL3YZmw0fwh3jvryv+TlTZY5yDpPBqAcztKTWwnPJ/swcllQ2 fNjplXPaDsht672fgB/FkT+5xyt2TAPSSaDsdi4DLRi3koM+nRi5Bm6M3EDaHVY6UfyWq4 3RRzaJ2Q46IDx0tPD3yE13hvrJkkmpY1EZnywgI433qgP86nxfCSb1iHgllk8g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1751533042; a=rsa-sha256; cv=none; b=liizNuIIpFaGn6M4k6eddWrDj2u9XduE+NibEZIfoc07DC//KZ8tyWDw532NnNPCk76f2A kiubHmilzmHSlWl9cLdTHJz6jVwtWa/sl2dof3hlN0akt8WBKdnb70DTbPiblBPpF87BZf pq2t6ttBC6CJBWvx934ToFMFBEWnsuOufDbZ+dDeI4hvgURVgHMuMZWuzc34mUFeZSAVpf eudTtBpkjnjFlqgTPPipB4WCo9h5jsSRzoW8/V0yqtZ6j4nRu8mGoagGQV729X3vYpa4oP MKP+OE0Hg1Zec1bPgGKbpSglWhPaS/rXbR/pbjeqX8Sk+ThfOJof8v0HUjsPbA== Received: from ravel.localnet (aclermont-ferrand-653-1-222-123.w90-14.abo.wanadoo.fr [90.14.66.123]) (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 did not present a certificate) (Authenticated sender: olce/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4bXrHk2Trzz1B3r for ; Thu, 03 Jul 2025 08:57:22 +0000 (UTC) (envelope-from olce@freebsd.org) From: Olivier Certner To: freebsd-current@freebsd.org Subject: Re: RFC: checking file systems support UF_HIDDEN, UF_SYSTEM Date: Thu, 03 Jul 2025 10:57:15 +0200 Message-ID: <4214798.O2WMGSuNBG@ravel> In-Reply-To: References: 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 Content-Type: multipart/signed; boundary="nextPart4126058.p4y8TspHLy"; micalg="pgp-sha384"; protocol="application/pgp-signature" --nextPart4126058.p4y8TspHLy Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Olivier Certner To: freebsd-current@freebsd.org Subject: Re: RFC: checking file systems support UF_HIDDEN, UF_SYSTEM Date: Thu, 03 Jul 2025 10:57:15 +0200 Message-ID: <4214798.O2WMGSuNBG@ravel> In-Reply-To: MIME-Version: 1.0 > I suggest adding more _PC_XXX constants and use VOP_PATHCONF() to get the > property of the specific mount point. You might query it on the root > vnode and cache it somewhere. Also this information would become > available to userspace due to pathconf(2). That works and is probably the path of least resistance. An alternative would be to export this information through statfs()/statvfs(), as probably no (sane) filesystem would support these file attributes only in some directories (in other words, this information is per-mount). However, to stay backwards-compatible, that would mean either defining new MNT_* flags or using some spares in 'struct statfs', and translating these into a new report flag for statvfs(). Regards. -- Olivier Certner --nextPart4126058.p4y8TspHLy Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCQAdFiEEmNCxHjkosai0LYIujKEwQJceJicFAmhmResACgkQjKEwQJce JielpRAAmHHK59YzIGc6BpV9avCV/ZHVrgkU0mQZ6w9MmOTNU++8reuXgx4x7z5j XUS1zDRpAQUJ9UId2lzmOSwJO8oY4radjO+kCN5uDut7iLDS9ixQa7fekkS+tGaR 9muPIEc27qaoSA4XXJ/tsQXUN6Pn9f8raDRveaMB+2Px9PuaIN08KoF+NlQxEm1a wWhonTxQ/n82+akV9U3E9QpgZmCuTPIoFXM2kd98pH2OCBIBrshX200qpNMraaa0 8L1WhEq1KEYUDzE2iSR8SD8ysGMFoUElI+Ria9fOhIWOv5Gfp1Oa5T2rI9Xxy8C4 WGeJmtzqTU7fI5ErczyY26q3uruG9Udcgt8KtKq4+AncB3lpTNXrxODFvslmX8jC 3/euKeSjWGHDZsIlLG51+skpWwBig3UZQIM8Pw++BD/lxYFWDERMmIFzri3iE27m ZqRz1Q+gwGbRhp23/KuTNcSBRslMX8Afthu8HtkkMFqunh0GpvyUNG6n5Xn+2cHS QDTH5RZttAYmwIpQg+SGADl46apCe9+Fjv3JANRqb9zveD0JD16tYHd/viUPm7vg yKUTIHpBnrH2pnHN7uKo/P+1rSTbkwOl7Jw4RNCFgrz3fxeygv9GOG4wtgLyPb5T phUN6pkeqLnk6jJwAma3jtCzva056SHkMNI8gsxlR/qFNEp3MBQ= =8iWp -----END PGP SIGNATURE----- --nextPart4126058.p4y8TspHLy--