From: Eric Sandeen <sandeen@redhat.com>
To: linux-fsdevel@vger.kernel.org,
lsf-pc <lsf-pc@lists.linux-foundation.org>
Subject: [LSF/MM/BPF TOPIC] finishing up mount API conversions; consistency & logging
Date: Mon, 15 Apr 2024 10:59:25 -0500 [thread overview]
Message-ID: <12d50bb6-7238-466b-8b67-c4ae42586818@redhat.com> (raw)
In case this is of interest to anyone I'll propose it.
The "new" mount API was merged about 5 years ago, but not all filesystems
were converted, so we still have the legacy helpers in place. There has been
a slow trickle of conversions, with a renewed interest in completing this
task.
The remaining conversions are of varying complexity (bcachefs might
be "fun!") but other questions remain around how userspace expects to use
the informational messages the API provides, what types of messages those
should be, and whether those messages should also go to the kernel dmesg.
Last I checked, userspace is not yet doing anything with those messages,
so any inconsistencies probably aren't yet apparent.
There's also the remaining task of getting the man pages completed.
There were also some recent questions and suggestions about how to handle
unknown mount options, see Miklos' FSOPEN_REJECT_UNKNOWN suggestion. [1]
I'm not sure if this warrants a full session, as it's actually quite
an old topic. If nothing else, a BOF for those interested might be
worthwhile.
Thanks,
-Eric
[1] https://lore.kernel.org/linux-fsdevel/CAJfpeguCKgMPBbD_ESD+Voxq5ChS9nGQFdYrA4+YWBz17yFADA@mail.gmail.com/
next reply other threads:[~2024-04-15 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 15:59 Eric Sandeen [this message]
2024-05-08 10:32 ` [LSF/MM/BPF TOPIC] finishing up mount API conversions; consistency & logging Amir Goldstein
2024-05-08 11:42 ` Christian Brauner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12d50bb6-7238-466b-8b67-c4ae42586818@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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.
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 NNTP newsgroup(s).