From: Jan Kara <jack@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Jeff Layton <jlayton@kernel.org>,
Josef Bacik <josef@toxicpanda.com>,
Christoph Hellwig <hch@lst.de>,
David Howells <dhowells@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Miklos Szeredi <miklos@szeredi.hu>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/4] fsnotify: split fsnotify_perm() into two hooks
Date: Fri, 8 Dec 2023 19:33:04 +0100 [thread overview]
Message-ID: <20231208183304.iwz4fqksmutvphtd@quack3> (raw)
In-Reply-To: <20231207123825.4011620-3-amir73il@gmail.com>
On Thu 07-12-23 14:38:23, Amir Goldstein wrote:
> We would like to make changes to the fsnotify access permission hook -
> add file range arguments and add the pre modify event.
>
> In preparation for these changes, split the fsnotify_perm() hook into
> fsnotify_open_perm() and fsnotify_file_perm().
>
> This is needed for fanotify "pre content" events.
>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Looks good. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> include/linux/fsnotify.h | 34 +++++++++++++++++++---------------
> security/security.c | 4 ++--
> 2 files changed, 21 insertions(+), 17 deletions(-)
>
> diff --git a/include/linux/fsnotify.h b/include/linux/fsnotify.h
> index bcb6609b54b3..926bb4461b9e 100644
> --- a/include/linux/fsnotify.h
> +++ b/include/linux/fsnotify.h
> @@ -100,29 +100,33 @@ static inline int fsnotify_file(struct file *file, __u32 mask)
> return fsnotify_parent(path->dentry, mask, path, FSNOTIFY_EVENT_PATH);
> }
>
> -/* Simple call site for access decisions */
> -static inline int fsnotify_perm(struct file *file, int mask)
> +/*
> + * fsnotify_file_perm - permission hook before file access
> + */
> +static inline int fsnotify_file_perm(struct file *file, int perm_mask)
> {
> - int ret;
> - __u32 fsnotify_mask = 0;
> + __u32 fsnotify_mask = FS_ACCESS_PERM;
>
> - if (!(mask & (MAY_READ | MAY_OPEN)))
> + if (!(perm_mask & MAY_READ))
> return 0;
>
> - if (mask & MAY_OPEN) {
> - fsnotify_mask = FS_OPEN_PERM;
> + return fsnotify_file(file, fsnotify_mask);
> +}
>
> - if (file->f_flags & __FMODE_EXEC) {
> - ret = fsnotify_file(file, FS_OPEN_EXEC_PERM);
> +/*
> + * fsnotify_open_perm - permission hook before file open
> + */
> +static inline int fsnotify_open_perm(struct file *file)
> +{
> + int ret;
>
> - if (ret)
> - return ret;
> - }
> - } else if (mask & MAY_READ) {
> - fsnotify_mask = FS_ACCESS_PERM;
> + if (file->f_flags & __FMODE_EXEC) {
> + ret = fsnotify_file(file, FS_OPEN_EXEC_PERM);
> + if (ret)
> + return ret;
> }
>
> - return fsnotify_file(file, fsnotify_mask);
> + return fsnotify_file(file, FS_OPEN_PERM);
> }
>
> /*
> diff --git a/security/security.c b/security/security.c
> index dcb3e7014f9b..d7f3703c5905 100644
> --- a/security/security.c
> +++ b/security/security.c
> @@ -2586,7 +2586,7 @@ int security_file_permission(struct file *file, int mask)
> if (ret)
> return ret;
>
> - return fsnotify_perm(file, mask);
> + return fsnotify_file_perm(file, mask);
> }
>
> /**
> @@ -2837,7 +2837,7 @@ int security_file_open(struct file *file)
> if (ret)
> return ret;
>
> - return fsnotify_perm(file, MAY_OPEN);
> + return fsnotify_open_perm(file);
> }
>
> /**
> --
> 2.34.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2023-12-08 18:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 12:38 [PATCH 0/4] Prepare for fsnotify pre-content permission events Amir Goldstein
2023-12-07 12:38 ` [PATCH 1/4] fs: use splice_copy_file_range() inline helper Amir Goldstein
2023-12-08 17:33 ` Christian Brauner
2023-12-10 10:07 ` Amir Goldstein
2023-12-08 18:27 ` Jan Kara
2023-12-07 12:38 ` [PATCH 2/4] fsnotify: split fsnotify_perm() into two hooks Amir Goldstein
2023-12-08 18:33 ` Jan Kara [this message]
2023-12-07 12:38 ` [PATCH 3/4] fsnotify: assert that file_start_write() is not held in permission hooks Amir Goldstein
2023-12-08 18:46 ` Jan Kara
2023-12-08 21:02 ` Amir Goldstein
2023-12-11 10:30 ` Jan Kara
2023-12-11 10:57 ` Amir Goldstein
2023-12-07 12:38 ` [PATCH 4/4] fsnotify: pass access range in file " Amir Goldstein
2023-12-08 17:52 ` Christian Brauner
2023-12-08 18:53 ` Jan Kara
2023-12-08 21:34 ` Amir Goldstein
2023-12-10 13:24 ` Amir Goldstein
2023-12-11 11:49 ` Jan Kara
2023-12-11 12:00 ` Amir Goldstein
2023-12-11 14:53 ` Jan Kara
2023-12-07 21:51 ` [PATCH 0/4] Prepare for fsnotify pre-content permission events Josef Bacik
2023-12-08 7:34 ` Amir Goldstein
2023-12-15 17:00 ` Amir Goldstein
2023-12-15 20:04 ` Josef Bacik
2023-12-08 17:54 ` 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=20231208183304.iwz4fqksmutvphtd@quack3 \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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).