The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Charalampos Mitrodimas <charmitro@posteo.net>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>,
	David Howells <dhowells@redhat.com>,
	Eric Sandeen <sandeen@redhat.com>
Subject: Re: [PATCH v3] debugfs: fix mount options not being applied
Date: Tue, 19 Aug 2025 13:18:30 +0200	[thread overview]
Message-ID: <2025081958-scolding-spruce-696c@gregkh> (raw)
In-Reply-To: <20250819-hotel-talent-c8de78760a68@brauner>

On Tue, Aug 19, 2025 at 01:11:58PM +0200, Christian Brauner wrote:
> On Sat, 16 Aug 2025 14:14:37 +0000, 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 parsed options were never
> > applied to the superblock when it was reused. As a result, the mount
> > options were ignored when debugfs was mounted.
> > 
> > [...]
> 
> Applied to the vfs-6.18.misc branch of the vfs/vfs.git tree.
> Patches in the vfs-6.18.misc branch should appear in linux-next soon.
> 
> Please report any outstanding bugs that were missed during review in a
> new review to the original patch series allowing us to drop it.
> 
> It's encouraged to provide Acked-bys and Reviewed-bys even though the
> patch has now been applied. If possible patch trailers will be updated.
> 
> Note that commit hashes shown below are subject to change due to rebase,
> trailer updates or similar. If in doubt, please check the listed branch.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs-6.18.misc
> 
> [1/1] debugfs: fix mount options not being applied
>       https://git.kernel.org/vfs/vfs/c/8e7e265d558e

I've also included this in the driver-core -linus branch, so it should
have been in linux-next for a few days now.  I guess both versions can't
hurt :)

thanks

greg k-h

      reply	other threads:[~2025-08-19 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16 14:14 [PATCH v3] debugfs: fix mount options not being applied Charalampos Mitrodimas
2025-08-19 11:11 ` Christian Brauner
2025-08-19 11:18   ` Greg Kroah-Hartman [this message]

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=2025081958-scolding-spruce-696c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=brauner@kernel.org \
    --cc=charmitro@posteo.net \
    --cc=dakr@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sandeen@redhat.com \
    --cc=stable@vger.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