linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Karel Zak <kzak@redhat.com>,
	Christian Brauner <brauner@kernel.org>,
	linux-fsdevel@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 0/4] Add the ability to query mount options in statmount
Date: Mon, 11 Nov 2024 10:28:05 -0500	[thread overview]
Message-ID: <20241111152805.GA675696@perftesting> (raw)
In-Reply-To: <CAJfpegs=JseHWx1H-3iOmkfav2k0rdFzr03eoVsdiW3rT_2MZg@mail.gmail.com>

On Mon, Nov 11, 2024 at 02:12:16PM +0100, Miklos Szeredi wrote:
> On Wed, 26 Jun 2024 at 14:23, Miklos Szeredi <miklos@szeredi.hu> wrote:
> >
> > On Tue, 25 Jun 2024 at 16:18, Josef Bacik <josef@toxicpanda.com> wrote:
> >
> > > But that means getting the buffer, and going back through it and replacing every
> > > ',' with a '\0', because I'm sure as hell not going and changing all of our
> > > ->show_options() callbacks to not put in a ','.
> > >
> > > Is this the direction we want to go?
> >
> > IMO yes.  Having a clean interface is much more important than doing
> > slightly less processing on the kernel side (which would likely be
> > done anyway on the user side).
> 
> So I went for an extended leave, and this interface was merged in the
> meantime with much to be desired.
> 
> The options are presented just the same as in /proc/self/mountinfo
> (just the standard options left out).  And that has all the same
> problems:
> 
>  - options can't contain commas (this causes much headache for
> overlayfs which has filenames in its options)
> 
>  - to allow the result to be consumed by fsconfig() for example
> options need to be unescaped
> 
>  - mnt_opts is confusing, since these are *not* mount options, these
> are super block options.
> 
> This patchset was apparently hurried through without much thought and
> review, and what review I did provide was ignored.  So I'm
> frustrated, but not sure what if anything can be done at this point,
> since the interface went live in the last release and changing it
> would probably break things...

My apologies Miklos, I value your opinion and your feedback.  Sending my mind
back to when we were discussing this I think it just got lost in the other
patchsets I was working on, and then it got merged so it was "ok that's done,
next thing."  That's my bad, I'll be more careful in the future.  Thanks,

Josef

  parent reply	other threads:[~2024-11-11 15:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24 19:40 [PATCH 0/4] Add the ability to query mount options in statmount Josef Bacik
2024-06-24 19:40 ` [PATCH 1/4] fs: rename show_mnt_opts -> show_vfsmnt_opts Josef Bacik
2024-06-24 19:40 ` [PATCH 2/4] fs: add a helper to show all the options for a mount Josef Bacik
2024-06-25 14:16   ` Christian Brauner
2024-06-26  7:47     ` Karel Zak
2024-06-24 19:40 ` [PATCH 3/4] fs: export mount options via statmount() Josef Bacik
2024-06-24 19:40 ` [PATCH 4/4] sefltests: extend the statmount test for mount options Josef Bacik
2024-06-24 19:53 ` [PATCH 0/4] Add the ability to query mount options in statmount Jeff Layton
2024-06-25 10:42 ` Christian Brauner
2024-06-25 13:00   ` Josef Bacik
2024-06-25 13:04     ` Miklos Szeredi
2024-06-25 13:35       ` Christian Brauner
2024-06-25 13:52         ` Karel Zak
2024-06-25 13:55           ` Christian Brauner
2024-06-25 14:17           ` Josef Bacik
2024-06-26  7:34             ` Karel Zak
2024-06-26 12:23             ` Miklos Szeredi
2024-11-11 13:12               ` Miklos Szeredi
2024-11-11 13:29                 ` Christian Brauner
2024-11-11 13:47                   ` Miklos Szeredi
2024-11-11 15:28                 ` Josef Bacik [this message]
2024-11-11 16:02                   ` Miklos Szeredi
2024-11-12  8:54                     ` Karel Zak
2024-06-26 12:03 ` (subset) " Christian Brauner

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=20241111152805.GA675696@perftesting \
    --to=josef@toxicpanda.com \
    --cc=brauner@kernel.org \
    --cc=kernel-team@fb.com \
    --cc=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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;
as well as URLs for NNTP newsgroup(s).