mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Charalampos Mitrodimas <charmitro@posteo.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>,
	Christian Brauner <brauner@kernel.org>,
	David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] debugfs: fix mount options not being applied
Date: Mon, 4 Aug 2025 12:22:23 -0500	[thread overview]
Message-ID: <a1b3f555-acfe-4fd1-8aa4-b97f456fd6f4@redhat.com> (raw)
In-Reply-To: <20250804-debugfs-mount-opts-v1-1-bc05947a80b5@posteo.net>

On 8/4/25 9:30 AM, Charalampos Mitrodimas wrote:
> Mount options (uid, gid, mode) are silently ignored when debugfs is
> mounted. This is a regression introduced during the conversion to the
> new mount API.
> 
> When the mount API conversion was done, the line that sets
> sb->s_fs_info to the parsed options was removed. This causes
> debugfs_apply_options() to operate on a NULL pointer.
> 
> As an example, with the bug the "mode" mount option is ignored:
> 
>   $ mount -o mode=0666 -t debugfs debugfs /tmp/debugfs_test
>   $ mount | grep debugfs_test
>   debugfs on /tmp/debugfs_test type debugfs (rw,relatime)
>   $ ls -ld /tmp/debugfs_test
>   drwx------ 25 root root 0 Aug  4 14:16 /tmp/debugfs_test

Argh. So, this looks a lot like the issue that got fixed for tracefs in:

e4d32142d1de tracing: Fix tracefs mount options

Let me look at this; tracefs & debugfs are quite similar, so perhaps
keeping the fix consistent would make sense as well but I'll dig
into it a bit more.

Thanks,
-Eric


  parent reply	other threads:[~2025-08-04 17:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 14:30 Charalampos Mitrodimas
2025-08-04 16:48 ` Greg Kroah-Hartman
2025-08-04 17:22 ` Eric Sandeen [this message]
2025-08-05 17:03   ` Eric Sandeen
2025-08-05 17:22     ` Charalampos Mitrodimas
2025-08-06 16:33       ` Eric Sandeen
2025-08-08 14:13         ` Christian Brauner
2025-08-13 22:02           ` Eric Sandeen
2025-08-13 23:49             ` Charalampos Mitrodimas
2025-08-14  9:05     ` Aleksa Sarai
2025-08-14 13:47       ` Aleksa Sarai
2025-08-14 16:46       ` Eric Sandeen
2025-08-15  0:31         ` Aleksa Sarai

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=a1b3f555-acfe-4fd1-8aa4-b97f456fd6f4@redhat.com \
    --to=sandeen@redhat.com \
    --cc=brauner@kernel.org \
    --cc=charmitro@posteo.net \
    --cc=dakr@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.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

all inboxes | Powered by JetHome®