From: Jan Kara <jack@suse.cz>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: brauner@kernel.org, viro@zeniv.linux.org.uk, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] vfs: reorder checks in may_create_in_sticky
Date: Thu, 20 Jun 2024 14:46:33 +0200 [thread overview]
Message-ID: <20240620124633.nwknjgfvivbfmad4@quack3> (raw)
In-Reply-To: <20240620120359.151258-1-mjguzik@gmail.com>
On Thu 20-06-24 14:03:59, Mateusz Guzik wrote:
> The routine is called for all directories on file creation and weirdly
> postpones the check if the dir is sticky to begin with. Instead it first
> checks fifos and regular files (in that order), while avoidably pulling
> globals.
>
> No functional changes.
>
> Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
Yeah, putting the sticky bit check first makes sense also logically. Feel
free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/namei.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/namei.c b/fs/namei.c
> index 63d1fb06da6b..b1600060ecfb 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -1246,9 +1246,9 @@ static int may_create_in_sticky(struct mnt_idmap *idmap,
> umode_t dir_mode = nd->dir_mode;
> vfsuid_t dir_vfsuid = nd->dir_vfsuid;
>
> - if ((!sysctl_protected_fifos && S_ISFIFO(inode->i_mode)) ||
> - (!sysctl_protected_regular && S_ISREG(inode->i_mode)) ||
> - likely(!(dir_mode & S_ISVTX)) ||
> + if (likely(!(dir_mode & S_ISVTX)) ||
> + (S_ISREG(inode->i_mode) && !sysctl_protected_regular) ||
> + (S_ISFIFO(inode->i_mode) && !sysctl_protected_fifos) ||
> vfsuid_eq(i_uid_into_vfsuid(idmap, inode), dir_vfsuid) ||
> vfsuid_eq_kuid(i_uid_into_vfsuid(idmap, inode), current_fsuid()))
> return 0;
> --
> 2.43.0
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-06-20 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 12:03 Mateusz Guzik
2024-06-20 12:46 ` Jan Kara [this message]
2024-06-20 13:59 ` Christian Brauner
2024-06-21 7:45 ` Christian Brauner
2024-06-21 11:17 ` Mateusz Guzik
2024-06-21 11:25 ` Jan Kara
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=20240620124633.nwknjgfvivbfmad4@quack3 \
--to=jack@suse.cz \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--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
all inboxes | Powered by JetHome®