All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.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: Wed, 5 Jun 2024 17:33:26 +0200	[thread overview]
Message-ID: <20240605-miterleben-empfunden-ee9efeded6d3@brauner> (raw)
In-Reply-To: <934aaad0-4c41-43d4-9ba2-bd15513b9527@redhat.com>

On Mon, Jun 03, 2024 at 10:13:43AM -0500, Eric Sandeen wrote:
> On 6/3/24 9:33 AM, Christian Brauner wrote:
> > On Mon, Jun 03, 2024 at 09:17:10AM -0500, Eric Sandeen wrote:
> >> On 6/3/24 8:31 AM, Christian Brauner wrote:
> >>> On Mon, Jun 03, 2024 at 09:24:50AM +0200, Wolfram Sang wrote:
> >>>>
> >>>>>>> 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>
> >>>>>
> >>>>> Thanks, applied. Should be fixed by end of the week.
> >>>>
> >>>> It is in -next but not in rc2. rc3 then?
> >>>
> >>> Yes, it wasn't ready when I sent the fixes for -rc2 as I just put it in
> >>> that day.
> >>>
> >>
> >> See my other reply, are you sure we should make this change? From a
> >> "keep the old behavior" POV maybe so, but this looks to me like a
> >> bug in busybox, passing fstab hint "options" like "auto" as actual mount
> >> options being the root cause of the problem. debugfs isn't uniquely
> >> affected by this behavior.
> >>
> >> I'm not dead set against the change, just wanted to point this out.
> > 
> > Hm, it seems I forgot your other mail, sorry.
> 
> No worries!
> 
> > So the issue is that we're breaking existing userspace and it doesn't
> > seem like a situation where we can just ignore broken userspace. If
> > busybox has been doing that for a long time we might just have to
> > accommodate their brokenness. Thoughts?
> 
> Yep, I can totally see that POV.
> 
> It's just that surely every other strict-parsing filesystem is also
> broken in this same way, so coding around the busybox bug only in debugfs
> seems a little strange. (Surely we won't change every filesystem to accept
> unknown options just for busybox's benefit.)
> 
> IOWS: why do we accomodate busybox brokenness only for debugfs, given that
> "auto" can be used in fstab for any filesystem?

I suspect that not that most filesystems aren't mounted from fstab which
is why we've never saw reports.

  reply	other threads:[~2024-06-05 15:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22  8:38 [PATCH] debugfs: ignore auto and noauto options if given Wolfram Sang
2024-05-24 13:55 ` Christian Brauner
2024-05-27 10:06   ` Wolfram Sang
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 [this message]
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=20240605-miterleben-empfunden-ee9efeded6d3@brauner \
    --to=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 \
    --cc=wsa+renesas@sang-engineering.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.