From: "Marc Aurèle La France" <tsi@tuyoix.net>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Christian Brauner <brauner@kernel.org>,
David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] debugfs show actual source in /proc/mounts
Date: Sun, 18 Aug 2024 19:29:00 -0600 (Mountain Daylight Time) [thread overview]
Message-ID: <alpine.WNT.2.20.2408181925400.3116@CLUIJ> (raw)
In-Reply-To: <0798a2cf-b43b-4c17-94a0-142314d80f5b@redhat.com>
On Tue, 2024-Aug-13, Eric Sandeen wrote:
> On 8/13/24 4:54 AM, Greg Kroah-Hartman wrote:
>> On Sat, Aug 10, 2024 at 01:25:27PM -0600, Marc Aurèle La France wrote:
>>> After its conversion to the new mount API, debugfs displays "none" in
>>> /proc/mounts instead of the actual source. Fix this by recognising its
>>> "source" mount option.
>>> Signed-off-by: Marc Aurèle La France <tsi@tuyoix.net>
>>> Fixes: a20971c18752 ("vfs: Convert debugfs to use the new mount API")
>>> Cc: stable@vger.kernel.org # 6.10.x: 9f111059e725: fs_parse: add uid & gid option option parsing helpers
>>> Cc: stable@vger.kernel.org # 6.10.x: 49abee5991e1: debugfs: Convert to new uid/gid option parsing helpers
>> As this came from a fs tree, I'll let the vfs maintainer take it if they
>> think it is ok as I know nothing about the fs_parse stuff at the moment,
>> sorry.
> Hm, I guess this is OK, though it seems a little unexpected for debugfs
> to have to parse the trivial internal "source" option.
> This actually worked OK until
> 0c07c273a5fe debugfs: continue to ignore unknown mount options
> but after that commit, debugfs claims to parse "source" successfully even
> though it has not. So really, it Fixes: that commit, not the original
> conversion.
> I'm not sure of a better approach offhand, but maybe a comment about why
> Opt_source exists in debugfs would help future readers?
Meaning what? I'd say you're in a better position to explain why debugfs
shouldn't follow other fs's in this regard.
Marc.
next prev parent reply other threads:[~2024-08-19 1:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 19:25 [PATCH] debugfs show actual source in /proc/mounts Marc Aurèle La France
2024-08-13 9:54 ` Greg Kroah-Hartman
2024-08-13 19:18 ` Eric Sandeen
2024-08-14 4:50 ` Greg Kroah-Hartman
2024-08-14 15:20 ` Eric Sandeen
2024-08-14 15:26 ` Greg Kroah-Hartman
2024-08-19 1:29 ` Marc Aurèle La France [this message]
2024-08-30 3:44 ` Marc Aurèle La France
2024-08-30 13:38 ` Eric Sandeen
2024-08-31 3:51 ` Marc Aurèle La France
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=alpine.WNT.2.20.2408181925400.3116@CLUIJ \
--to=tsi@tuyoix.net \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sandeen@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.