Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Chandan Babu R <chandan.babu@oracle.com>
To: gregkh@linuxfoundation.org
Cc: sashal@kernel.org, mcgrof@kernel.org, linux-xfs@vger.kernel.org,
	stable@vger.kernel.org, djwong@kernel.org,
	chandan.babu@oracle.com, amir73il@gmail.com,
	leah.rumancik@gmail.com
Subject: [PATCH 5.4 11/17] xfs: fix up non-directory creation in SGID directories
Date: Wed, 12 Apr 2023 09:56:18 +0530	[thread overview]
Message-ID: <20230412042624.600511-12-chandan.babu@oracle.com> (raw)
In-Reply-To: <20230412042624.600511-1-chandan.babu@oracle.com>

From: Christoph Hellwig <hch@lst.de>

commit 01ea173e103edd5ec41acec65b9261b87e123fc2 upstream.

XFS always inherits the SGID bit if it is set on the parent inode, while
the generic inode_init_owner does not do this in a few cases where it can
create a possible security problem, see commit 0fa3ecd87848
("Fix up non-directory creation in SGID directories") for details.

Switch XFS to use the generic helper for the normal path to fix this,
just keeping the simple field inheritance open coded for the case of the
non-sgid case with the bsdgrpid mount option.

Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Reported-by: Christian Brauner <christian.brauner@ubuntu.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Acked-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Chandan Babu R <chandan.babu@oracle.com>
Acked-by: Darrick J. Wong <djwong@kernel.org>
---
 fs/xfs/xfs_inode.c | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
index 6bc565c186ca..568a9332efd2 100644
--- a/fs/xfs/xfs_inode.c
+++ b/fs/xfs/xfs_inode.c
@@ -750,6 +750,7 @@ xfs_ialloc(
 	xfs_buf_t	**ialloc_context,
 	xfs_inode_t	**ipp)
 {
+	struct inode	*dir = pip ? VFS_I(pip) : NULL;
 	struct xfs_mount *mp = tp->t_mountp;
 	xfs_ino_t	ino;
 	xfs_inode_t	*ip;
@@ -795,18 +796,17 @@ xfs_ialloc(
 		return error;
 	ASSERT(ip != NULL);
 	inode = VFS_I(ip);
-	inode->i_mode = mode;
 	set_nlink(inode, nlink);
-	inode->i_uid = current_fsuid();
 	inode->i_rdev = rdev;
 	ip->i_d.di_projid = prid;
 
-	if (pip && XFS_INHERIT_GID(pip)) {
-		inode->i_gid = VFS_I(pip)->i_gid;
-		if ((VFS_I(pip)->i_mode & S_ISGID) && S_ISDIR(mode))
-			inode->i_mode |= S_ISGID;
+	if (dir && !(dir->i_mode & S_ISGID) &&
+	    (mp->m_flags & XFS_MOUNT_GRPID)) {
+		inode->i_uid = current_fsuid();
+		inode->i_gid = dir->i_gid;
+		inode->i_mode = mode;
 	} else {
-		inode->i_gid = current_fsgid();
+		inode_init_owner(inode, dir, mode);
 	}
 
 	/*
-- 
2.39.1


  parent reply	other threads:[~2023-04-12  4:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12  4:26 [PATCH 5.4 00/17] xfs stable candidate patches for 5.4.y (from v5.11 & v5.12) Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 01/17] xfs: show the proper user quota options Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 02/17] xfs: merge the projid fields in struct xfs_icdinode Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 03/17] xfs: ensure that the inode uid/gid match values match the icdinode ones Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 04/17] xfs: remove the icdinode di_uid/di_gid members Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 05/17] xfs: remove the kuid/kgid conversion wrappers Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 06/17] xfs: add a new xfs_sb_version_has_v3inode helper Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 07/17] xfs: only check the superblock version for dinode size calculation Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 08/17] xfs: simplify di_flags2 inheritance in xfs_ialloc Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 09/17] xfs: simplify a check in xfs_ioctl_setattr_check_cowextsize Chandan Babu R
2023-04-12  4:29   ` kernel test robot
2023-04-12  4:36     ` Chandan Babu R
2023-04-12  4:47       ` Philip Li
2023-04-12  4:50         ` Chandan Babu R
2023-04-12  5:08   ` [PATCH 5.4 V2] " Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 10/17] xfs: remove the di_version field from struct icdinode Chandan Babu R
2023-04-12  4:26 ` Chandan Babu R [this message]
2023-04-12  4:26 ` [PATCH 5.4 12/17] xfs: set inode size after creating symlink Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 13/17] xfs: report corruption only as a regular error Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 14/17] xfs: shut down the filesystem if we screw up quota reservation Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 15/17] xfs: consider shutdown in bmapbt cursor delete assert Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 16/17] xfs: don't reuse busy extents on extent trim Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 17/17] xfs: force log and push AIL to clear pinned inodes when aborting mount Chandan Babu R
2023-04-18  9:49 ` [PATCH 5.4 00/17] xfs stable candidate patches for 5.4.y (from v5.11 & v5.12) Greg KH
2023-04-18 10:53   ` Greg KH
2023-04-18 12:39     ` Chandan Babu R

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=20230412042624.600511-12-chandan.babu@oracle.com \
    --to=chandan.babu@oracle.com \
    --cc=amir73il@gmail.com \
    --cc=djwong@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=leah.rumancik@gmail.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.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