From: Christian Brauner <christian.brauner@ubuntu.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
Matthew Bobrowski <mbobrowski@mbobrowski.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] unprivileged fanotify listener
Date: Wed, 24 Mar 2021 15:32:30 +0100 [thread overview]
Message-ID: <20210324143230.y36hga35xvpdb3ct@wittgenstein> (raw)
In-Reply-To: <CAOQ4uxhFU=H8db35JMhfR+A5qDkmohQ01AWH995xeBAKuuPhzA@mail.gmail.com>
On Wed, Mar 24, 2021 at 03:57:12PM +0200, Amir Goldstein wrote:
> > > Now tested FAN_MARK_FILESYSTEM watch on tmpfs mounted
> > > inside userns and works fine, with two wrinkles I needed to iron:
> > >
> > > 1. FAN_REPORT_FID not supported on tmpfs because tmpfs has
> > > zero f_fsid (easy to fix)
> > > 2. open_by_handle_at() is not userns aware (can relax for
> > > FS_USERNS_MOUNT fs)
> > >
> > > Pushed these two fixes to branch fanotify_userns.
> >
> > Pushed another fix to mnt refcount bug in WIP and another commit to
> > add the last piece that could make fanotify usable for systemd-homed
> > setup - a filesystem watch filtered by mnt_userns (not tested yet).
> >
>
> Now I used mount-idmapped (from xfstest) to test that last piece.
> Found a minor bug and pushed a fix.
>
> It is working as expected, that is filtering only the events generated via
> the idmapped mount. However, because the listener I tested is capable in
> the mapped userns and not in the sb userns, the listener cannot
> open_ny_handle_at(), so the result is not as useful as one might hope.
This is another dumb question probably but in general, are you saying
that someone watching a mount or directory and does _not_ want file
descriptors from fanotify to be returned has no other way of getting to
the path they want to open other than by using open_by_handle_at()?
>
> I guess we will also need to make open_by_handle_at() idmapped aware
> and use a variant of vfs_dentry_acceptable() that validates that the opened
> path is legitimately accessible via the idmapped mount.
So as a first step, I think there's a legitimate case to be made for
open_by_handle_at() to be made useable inside user namespaces. That's a
change worth to be made independent of fanotify. For example, nowadays
cgroups have a 64 bit identifier that can be used with open_by_handle_at
to map a cgrp id to a path and back:
https://lkml.org/lkml/2020/12/2/1126
Right now this can't be used in user namespaces because of this
restriction but it is genuinely useful to have this feature available
since cgroups are FS_USERNS_MOUNT and that identifier <-> path mapping
is very convenient.
Without looking at the code I'm not super sure how name_to_handle_at()
and open_by_handle_at() behave in the face of mount namespaces so that
would need looking into to. But it would be a genuinely useful change, I
think.
>
> I think I will leave this complexity to you should you think the userns filtered
> watch is something worth the effort.
Fair enough!
Thanks!
Christian
next prev parent reply other threads:[~2021-03-24 14:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 11:29 [PATCH v2 0/2] unprivileged fanotify listener Amir Goldstein
2021-03-04 11:29 ` [PATCH v2 1/2] fanotify: configurable limits via sysfs Amir Goldstein
2021-03-04 11:29 ` [PATCH v2 2/2] fanotify: support limited functionality for unprivileged users Amir Goldstein
2021-03-16 15:55 ` [PATCH v2 0/2] unprivileged fanotify listener Jan Kara
2021-03-17 11:01 ` Amir Goldstein
2021-03-17 11:42 ` Jan Kara
2021-03-17 12:19 ` Amir Goldstein
2021-03-17 17:45 ` Christian Brauner
2021-03-17 19:14 ` Amir Goldstein
2021-03-18 14:31 ` Christian Brauner
2021-03-18 16:48 ` Amir Goldstein
2021-03-19 13:40 ` Christian Brauner
2021-03-19 14:21 ` Amir Goldstein
2021-03-20 12:57 ` Amir Goldstein
2021-03-22 12:44 ` Amir Goldstein
2021-03-22 16:28 ` Christian Brauner
2021-03-22 17:22 ` Amir Goldstein
2021-03-24 13:57 ` Amir Goldstein
2021-03-24 14:32 ` Christian Brauner [this message]
2021-03-24 15:05 ` Amir Goldstein
2021-03-24 16:28 ` Christian Brauner
2021-03-24 17:07 ` Amir Goldstein
2021-03-25 11:12 ` Christian Brauner
2021-03-25 15:31 ` Amir Goldstein
2021-03-28 14:58 ` Amir Goldstein
2021-03-18 15:44 ` Jan Kara
2021-03-18 17:07 ` Amir Goldstein
2021-03-18 18:40 ` Christian Brauner
2021-03-22 18:38 ` Amir Goldstein
2021-03-24 11:48 ` Jan Kara
2021-03-24 15:50 ` Amir Goldstein
2021-03-25 13:49 ` Jan Kara
2021-03-25 15:05 ` Amir Goldstein
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=20210324143230.y36hga35xvpdb3ct@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mbobrowski@mbobrowski.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