From: Amir Goldstein <amir73il@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Matthew Bobrowski <mbobrowski@mbobrowski.org>,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org
Subject: [PATCH v2 0/2] unprivileged fanotify listener
Date: Thu, 4 Mar 2021 13:29:19 +0200 [thread overview]
Message-ID: <20210304112921.3996419-1-amir73il@gmail.com> (raw)
Jan,
These patches try to implement a minimal set and least controversial
functionality that we can allow for unprivileged users as a starting
point.
The patches were tested on top of v5.12-rc1 and the fanotify_merge
patches using the unprivileged listener LTP tests written by Matthew
and another LTP tests I wrote to test the sysfs tunable limits [1].
Thanks,
Amir.
Changes since v1:
- Dropped marks per group limit in favor of max per user
- Rename sysfs files from 'listener' to 'group' terminology
- Dropped internal group flag FANOTIFY_UNPRIV
- Limit unprivileged listener to FAN_REPORT_FID family
- Report event->pid depending on reader capabilities
[1] https://github.com/amir73il/ltp/commits/fanotify_unpriv
Amir Goldstein (2):
fanotify: configurable limits via sysfs
fanotify: support limited functionality for unprivileged users
fs/notify/fanotify/fanotify.c | 16 ++-
fs/notify/fanotify/fanotify_user.c | 152 ++++++++++++++++++++++++-----
fs/notify/fdinfo.c | 3 +-
fs/notify/group.c | 1 -
fs/notify/mark.c | 4 -
include/linux/fanotify.h | 36 ++++++-
include/linux/fsnotify_backend.h | 6 +-
include/linux/sched/user.h | 3 -
include/linux/user_namespace.h | 4 +
kernel/sysctl.c | 12 ++-
kernel/ucount.c | 4 +
11 files changed, 194 insertions(+), 47 deletions(-)
--
2.30.0
next reply other threads:[~2021-03-04 11:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 11:29 Amir Goldstein [this message]
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
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=20210304112921.3996419-1-amir73il@gmail.com \
--to=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;
as well as URLs for NNTP newsgroup(s).