From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 51425@debbugs.gnu.org, jonathan.brielmaier@web.de
Subject: bug#51425: file-system: validate flags
Date: Fri, 29 Oct 2021 20:45:28 -0400 [thread overview]
Message-ID: <87fssj8hnb.fsf@gmail.com> (raw)
In-Reply-To: <87lf2bipgp.fsf@nckx> (Tobias Geerinckx-Rice's message of "Fri, 29 Oct 2021 21:41:15 +0200")
Hello Tobias,
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> [FTR, I'm the one who encouraged Jonathan to file a bug. Mount flags
> seem ideally suited to build-time validation.]
>
> Maxim,
>
> Maxim Cournoyer 写道：
>> each file system may have their own flags
>
> Really? Huh. Interesting. How does that work? Where would these
> file-system specific flags be #defined?
Or maybe I'm confusing with file system options; I can't find the past
discussion that I had on mind; but options are file driver specific,
while flags are file system independent. So yes, flags are a good
candidate for validation!
Another thing that is tricky about options is that some of them are only
really understood by the 'mount' command line utility, not the 'mount'
system call such as used in our init RAM disk (both are thrown together
in 'man 8 mount' without an easy way to discern them apart, IIRC).
> Ludo', I'll take a look at ‘sanitize’; thanks!
Neat, thank you Tobias!
Maxim
next prev parent reply other threads:[~2021-10-30 0:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 22:24 bug#51425: file-system: validate flags Jonathan Brielmaier
2021-10-28 1:31 ` Maxim Cournoyer
2021-10-29 19:41 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-10-30 0:45 ` Maxim Cournoyer [this message]
2021-10-30 0:48 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-10-31 2:31 ` Maxim Cournoyer
2021-10-29 19:13 ` Ludovic Courtès
2021-11-07 22:16 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fssj8hnb.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=51425@debbugs.gnu.org \
--cc=jonathan.brielmaier@web.de \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).