linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org,
	Andreas Gruenbacher <agruenba@redhat.com>,
	stable@vger.kernel.org, cluster-devel@redhat.com
Subject: Re: [PATCH 04/11] gfs2: Don't clear SGID when inheriting ACLs
Date: Wed, 19 Jul 2017 12:17:19 -0400 (EDT)	[thread overview]
Message-ID: <977295480.32253218.1500481039266.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170718161833.GB27293@quack2.suse.cz>

----- Original Message -----
| On Thu 22-06-17 15:31:08, Jan Kara wrote:
| > When new directory 'DIR1' is created in a directory 'DIR0' with SGID bit
| > set, DIR1 is expected to have SGID bit set (and owning group equal to
| > the owning group of 'DIR0'). However when 'DIR0' also has some default
| > ACLs that 'DIR1' inherits, setting these ACLs will result in SGID bit on
| > 'DIR1' to get cleared if user is not member of the owning group.
| > 
| > Fix the problem by moving posix_acl_update_mode() out of
| > __gfs2_set_acl() into gfs2_set_acl(). That way the function will not be
| > called when inheriting ACLs which is what we want as it prevents SGID
| > bit clearing and the mode has been properly set by posix_acl_create()
| > anyway.
| > 
| > Fixes: 073931017b49d9458aa351605b43a7e34598caef
| > CC: stable@vger.kernel.org
| > CC: cluster-devel@redhat.com
| > CC: Bob Peterson <rpeterso@redhat.com>
| > Signed-off-by: Jan Kara <jack@suse.cz>
| 
| Bob, can you please pick up this fix? Thanks!

Hi Honza,

Sorry this slipped my attention for so long.
This is now applied to the for-next branch of the linux-gfs2 tree:
https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=914cea93dd89f00b41c1d8ff93f17be47356a36a

Regards,

Bob Peterson
Red Hat File Systems

  reply	other threads:[~2017-07-19 16:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 13:31 [PATCH 0/11 v1] Fix inheritance of SGID in presence of default ACLs Jan Kara
2017-06-22 13:31 ` [PATCH 01/11] ext4: Don't clear SGID when inheriting ACLs Jan Kara
2017-06-22 15:32   ` Andreas Gruenbacher
2017-07-18 16:16   ` Jan Kara
2017-07-31  3:34     ` Theodore Ts'o
2017-06-22 13:31 ` [PATCH 02/11] ext2: " Jan Kara
2017-06-22 13:31 ` [PATCH 03/11] btrfs: " Jan Kara
2017-06-26 16:47   ` David Sterba
2017-06-22 13:31 ` [PATCH 04/11] gfs2: " Jan Kara
2017-07-18 16:18   ` Jan Kara
2017-07-19 16:17     ` Bob Peterson [this message]
2017-06-22 13:31 ` [PATCH 05/11] hfsplus: " Jan Kara
2017-06-22 13:31 ` [PATCH 06/11] jfs: " Jan Kara
2017-07-18 16:19   ` Jan Kara
2017-07-18 17:36     ` Dave Kleikamp
2017-06-22 13:31 ` [PATCH 07/11] ocfs2: Make ocfs2_set_acl() static Jan Kara
2017-06-22 13:31 ` [PATCH 08/11] ocfs2: Don't clear SGID when inheriting ACLs Jan Kara
2017-06-22 13:31 ` [PATCH 09/11] orangefs: " Jan Kara
2017-07-18 16:18   ` Jan Kara
2017-07-20 16:05     ` Mike Marshall
2017-07-20 16:27       ` Jan Kara
2017-06-22 13:31 ` [PATCH 10/11] reiserfs: " Jan Kara
2017-06-22 13:31 ` [PATCH 11/11] xfs: " Jan Kara
2017-06-26 15:52   ` Darrick J. Wong

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=977295480.32253218.1500481039266.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.com \
    --cc=agruenba@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.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;
as well as URLs for NNTP newsgroup(s).