vfs: reorder checks in may_create_in_sticky

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>
Link: https://lore.kernel.org/r/20240620120359.151258-1-mjguzik@gmail.com
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Christian Brauner <brauner@kernel.org>
This commit is contained in:
Mateusz Guzik 2024-06-20 14:03:59 +02:00 committed by Christian Brauner
parent 26a2ed1079
commit 5e362bd5ee
No known key found for this signature in database
GPG Key ID: 91C61BC06578DCA2

View File

@ -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;