From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Eric Sandeen <sandeen@redhat.com>,
linux-renesas-soc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] debugfs: ignore auto and noauto options if given
Date: Mon, 27 May 2024 12:06:18 +0200 [thread overview]
Message-ID: <20240527100618.np2wqiw5mz7as3vk@ninjato> (raw)
In-Reply-To: <20240524-glasfaser-gerede-fdff887f8ae2@brauner>
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
Hi Christian,
> Afaict, the "auto" option has either never existent or it was removed before
> the new mount api conversion time ago for debugfs.
Frankly, I have no idea why I put this 'auto' in my fstab ages ago. But
it seems, I am not the only one[1].
[1] https://www.ibm.com/docs/en/linux-on-systems?topic=assumptions-debugfs
> diff --git a/fs/debugfs/inode.c b/fs/debugfs/inode.c
> index dc51df0b118d..713b6f76e75d 100644
> --- a/fs/debugfs/inode.c
> +++ b/fs/debugfs/inode.c
> @@ -107,8 +107,16 @@ static int debugfs_parse_param(struct fs_context *fc, struct fs_parameter *param
> int opt;
>
> opt = fs_parse(fc, debugfs_param_specs, param, &result);
> - if (opt < 0)
> + if (opt < 0) {
> + /*
> + * We might like to report bad mount options here; but
> + * traditionally debugfs has ignored all mount options
> + */
> + if (opt == -ENOPARAM)
> + return 0;
> +
> return opt;
> + }
>
> switch (opt) {
> case Opt_uid:
>
>
> Does that fix it for you?
Yes, it does, thank you.
Reported-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-05-27 10:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 8:38 Wolfram Sang
2024-05-24 13:55 ` Christian Brauner
2024-05-27 10:06 ` Wolfram Sang [this message]
2024-05-27 10:23 ` Geert Uytterhoeven
2024-05-27 12:19 ` Christian Brauner
2024-06-03 7:24 ` Wolfram Sang
2024-06-03 13:31 ` Christian Brauner
2024-06-03 14:17 ` Eric Sandeen
2024-06-03 14:33 ` Christian Brauner
2024-06-03 15:13 ` Eric Sandeen
2024-06-05 15:33 ` Christian Brauner
2024-06-03 19:52 ` Wolfram Sang
2024-05-29 20:43 ` Eric Sandeen
2024-05-29 22:05 ` Wolfram Sang
2024-05-29 22:33 ` Eric Sandeen
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=20240527100618.np2wqiw5mz7as3vk@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®