From: Jan Kara <jack@suse.cz>
To: Gu Zheng <guzheng1@huawei.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk, jack@suse.cz
Subject: Re: [PATCH] tmpfs: clear S_ISGID when setting posix ACLs
Date: Fri, 6 Jan 2017 11:10:25 +0100 [thread overview]
Message-ID: <20170106101025.GA3533@quack2.suse.cz> (raw)
In-Reply-To: <1483690375-40718-1-git-send-email-guzheng1@huawei.com>
On Fri 06-01-17 16:12:55, Gu Zheng wrote:
> This change was missed the tmpfs modification in In CVE-2016-7097
> commit 073931017b49d9458aa351605b43a7e34598caef
> posix_acl: Clear SGID bit when setting file permissions.
> It can test by xfstest generic/375, which failed to clear
> setgid bit in the following test case on tmpfs:
>
> touch $testfile
> chown 100:100 $testfile
> chmod 2755 $testfile
> _runas -u 100 -g 101 -- setfacl -m u::rwx,g::rwx,o::rwx $testfile
>
> Signed-off-by: Gu Zheng <guzheng1@huawei.com>
Ah, good catch. One comment below:
> diff --git a/fs/posix_acl.c b/fs/posix_acl.c
> index 5955220..d014dff 100644
> --- a/fs/posix_acl.c
> +++ b/fs/posix_acl.c
> @@ -922,11 +922,10 @@ int simple_set_acl(struct inode *inode, struct posix_acl *acl, int type)
> int error;
>
> if (type == ACL_TYPE_ACCESS) {
> - error = posix_acl_equiv_mode(acl, &inode->i_mode);
> - if (error < 0)
> - return 0;
> - if (error == 0)
> - acl = NULL;
> + error = posix_acl_update_mode(inode,
> + &inode->i_mode, &acl);
> + if (error > 0)
> + return error;
Uh, why this error > 0 check? AFAIU it should be:
if (error < 0)
return 0;
As it used to be before...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2017-01-06 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 8:12 [PATCH] tmpfs: clear S_ISGID when setting posix ACLs Gu Zheng
2017-01-06 10:10 ` Jan Kara [this message]
2017-01-09 1:26 ` Gu Zheng
-- strict thread matches above, loose matches on Subject: below --
2017-01-09 1:34 Gu Zheng
2017-01-10 8:03 ` Jan Kara
2017-01-10 8:12 ` Al Viro
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=20170106101025.GA3533@quack2.suse.cz \
--to=jack@suse.cz \
--cc=guzheng1@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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