From nobody Sat Mar 9 05:07:07 2024 X-Original-To: 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 4Ts9yM2wQBz5CsVW for ; Sat, 9 Mar 2024 05:07:23 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ts9yL5BPrz4r3D for ; Sat, 9 Mar 2024 05:07:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20230601.gappssmtp.com header.s=20230601 header.b=aXzOGqdv; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2a00:1450:4864:20::634) smtp.mailfrom=wlosh@bsdimp.com Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-a36126ee41eso378599066b.2 for ; Fri, 08 Mar 2024 21:07:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1709960839; x=1710565639; darn=freebsd.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=UXGRtcXOmabz1QlClhmq5rwxDH+LWuCL1GkT9+Ss0bs=; b=aXzOGqdvTC5vl/CsheZBnt2a+0cEzGQv3UdQjwxFA1DvAu17n4pR6gU5vJQE2sD2mb V9+GJntc8oHiA7oXcq7OmYvs1/vss2P0GYQ7/1jK3E5OZLl0I2lRiP0OiC5AChO6OZmL HCk9gi1GkO+OjeGeLSLuAqxKHoGTk5Y0cqrVtb/JJZ1VM/92NKYJ63YYhrM3rl/NFpdS oYmVMZ7niH95uvTIIcy46mX36iOOsqIvBKTLJBa97xiWNlHU3uILDZHzHy1NlX1s4GWQ MwLHsA6b6Jbr+X1aaI/EjYrO4TRkhZOR7yRJ/CEDppCkN6w7gXdpGga6TzRe2Z3vhyGY 6Bbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709960839; x=1710565639; 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=UXGRtcXOmabz1QlClhmq5rwxDH+LWuCL1GkT9+Ss0bs=; b=asVdoFixMzgGoxRcMyvfQ327B+73/OviutT9EHWjClM8c10KadiLKywJ6Le4v0A4xH hupsKaHHfHbTzeLVHESsQacZkNdjaMV+C0B3EIMZvbQ0Fnk80E4Ki5w7+QYrTmZ1ec6C QSxb3H0TAvjj7oDI1EDnrrqLgJ7B5FB47K74M7OEMHT8Lnj8AHEmj+VGmdi9V//lDjTy YQDF6HrFUIpt7cIr049aI2KRC1mLCkx16aiuLmslCE1MbW921wykToQN2YLRkJIncOhy iewCNhOnpbAD16Pmb88sGpEw+cNPxPKXkt6DI/SyslqD1ILFMBvQx9WbEL7XLRK6MsnK j5RQ== X-Gm-Message-State: AOJu0YzNThaLF+WzpE5zFiVYOlkrcx0kIPLaLshQ1SytA0FapDn5aGB+ iBfxyFApFvK0glaY97OIcSuxNTJ/i9sNmGsVouk4RUPmlQoMEkwEUnQ1SRSQLgmDf4/iUlHJ1+U UxbFV8P4aY5N17SCfPdw5P2O6/uHcmgi765b4bw== X-Google-Smtp-Source: AGHT+IF/gbMF1zKwy1RCvIJIjCw/nS0SNMYdi2dt29EzWimom5kBhyuyM5KnSi1WMmPjhkGPSZGv2WxWzgkjlXcaQWI= X-Received: by 2002:a17:907:8b8b:b0:a3e:7cf7:2fb7 with SMTP id tb11-20020a1709078b8b00b00a3e7cf72fb7mr412327ejc.33.1709960839165; Fri, 08 Mar 2024 21:07:19 -0800 (PST) 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: <09bb45dea82d96c11f34cc48dda540dc@Leidinger.net> <202403072005.427K58KX014923@donotpassgo.dyslexicfish.net> In-Reply-To: <202403072005.427K58KX014923@donotpassgo.dyslexicfish.net> From: Warner Losh Date: Fri, 8 Mar 2024 22:07:07 -0700 Message-ID: Subject: Re: Reason why "nocache" option is not displayed in "mount"? To: Jamie Landeg-Jones Cc: current@freebsd.org, Alexander@leidinger.net Content-Type: multipart/alternative; boundary="000000000000661900061333488d" X-Spamd-Bar: - X-Spamd-Result: default: False [-2.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_DN_SOME(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::634:from]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCPT_COUNT_THREE(0.00)[3]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[bsdimp.com]; R_SPF_NA(0.00)[no SPF record]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4Ts9yL5BPrz4r3D --000000000000661900061333488d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Mar 7, 2024 at 1:05=E2=80=AFPM Jamie Landeg-Jones wrote: > Alexander Leidinger wrote: > > > Hi, > > > > what is the reason why "nocache" is not displayed in the output of > > "mount" for nullfs options? > > Good catch. I also notice that "hidden" is not shown either. > > I guess that as for some time, "nocache" was a "secret" option, no-one > update "mount" to display it? > So a couple of things to know. First, there's a list of known options. These are converted to a bitmask. This is then decoded and reported by mount. The other strings are passed to the filesystem directly. They decode it and do things, but they don't export them (that I can find). I believe that's why they aren't reported with 'mount'. There's a couple of other options in /etc/fstab that are pseudo options too. Warner --000000000000661900061333488d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Mar 7, 2024 at 1:05=E2=80=AFP= M Jamie Landeg-Jones <jamie@catflap= .org> wrote:
Alexander Leidinger <Alexander@Leidinger.net> wrote:

> Hi,
>
> what is the reason why "nocache" is not displayed in the out= put of
> "mount" for nullfs options?

Good catch. I also notice that "hidden" is not shown either.

I guess that as for some time, "nocache" was a "secret"= option, no-one
update "mount" to display it?

So a couple of things to know.

First, there's= a list of known options. These are converted to a bitmask. This is then de= coded and reported by mount. The other strings are passed to the filesystem= directly. They decode it and do things, but they don't export them (th= at I can find). I believe that's why they aren't reported with '= ;mount'. There's a couple of other options in /etc/fstab that are p= seudo options too.

Warner
--000000000000661900061333488d--