From: Christian Brauner <brauner@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.cz>,
Amir Goldstein <amir73il@gmail.com>, Karel Zak <kzak@redhat.com>,
Lennart Poettering <lennart@poettering.net>,
Ian Kent <raven@themaw.net>, Al Viro <viro@zeniv.linux.org.uk>,
linux-security-module@vger.kernel.org,
Paul Moore <paul@paul-moore.com>
Subject: Re: [PATCH v4 4/4] vfs: add notifications for mount attribute change
Date: Sat, 25 Jan 2025 10:22:24 +0100 [thread overview]
Message-ID: <20250125-gesessen-gerutscht-0a0468193303@brauner> (raw)
In-Reply-To: <CAJfpegvK9Q_uE-O8HkzzjeNh7nZ_sO89=OCyw_SZCudfXbB2JQ@mail.gmail.com>
On Fri, Jan 24, 2025 at 04:49:28PM +0100, Miklos Szeredi wrote:
> On Fri, 24 Jan 2025 at 16:38, Christian Brauner <brauner@kernel.org> wrote:
> >
> > On Thu, Jan 23, 2025 at 08:41:07PM +0100, Miklos Szeredi wrote:
> > > Notify when mount flags, propagation or idmap changes.
> > >
> > > Just like attach and detach, no details are given in the notification, only
> > > the mount ID.
> > >
> > > Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
> > > ---
> >
> > I think this is a good next step but I would first go with the minimal
> > functionality of notifying about mount topology changes for v6.15.
>
> I can totally relate to that. I added the fourth patch more as a
> "let's see if this can also fit into the current framework".
>
> > Btw, if we notify in do_remount() on the mount that triggered
> > superblock reconfiguration then we also need to trigger in
> > vfs_cmd_reconfigure() aka fsconfig(FSCONFIG_CMD_RECONFIGURE) but the
> > mount that was used to change superblock options is only available in
> > fspick() currently. That would need to be handled.
>
> No, if we'd want to watch changes on super blocks, then we'd need to
> iterate all the mounts of the superblock and notify each.
Ah, I remember that old remount had unclear semantics where mount
specific and superblock specific options are interleaved. So we would
need to notify from do_remount() on mount specific changes. Right, then
this change is correct and I agree about the superblock part.
prev parent reply other threads:[~2025-01-25 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 19:41 [PATCH v4 0/4] mount notification Miklos Szeredi
2025-01-23 19:41 ` [PATCH v4 1/4] fsnotify: add mount notification infrastructure Miklos Szeredi
2025-01-23 19:41 ` [PATCH v4 2/4] fanotify: notify on mount attach and detach Miklos Szeredi
2025-01-24 19:38 ` Paul Moore
2025-01-25 1:09 ` Russell Coker
2025-01-28 12:42 ` Miklos Szeredi
2025-01-28 13:37 ` Miklos Szeredi
2025-01-28 18:11 ` Daniel Burgener
2025-01-23 19:41 ` [PATCH v4 3/4] vfs: add notifications for " Miklos Szeredi
2025-01-23 19:41 ` [PATCH v4 4/4] vfs: add notifications for mount attribute change Miklos Szeredi
2025-01-24 9:09 ` Amir Goldstein
2025-01-24 15:38 ` Christian Brauner
2025-01-24 15:49 ` Miklos Szeredi
2025-01-25 9:22 ` Christian Brauner [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=20250125-gesessen-gerutscht-0a0468193303@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=kzak@redhat.com \
--cc=lennart@poettering.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
--cc=paul@paul-moore.com \
--cc=raven@themaw.net \
--cc=viro@zeniv.linux.org.uk \
/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).