linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org, linux-unionfs@vger.kernel.org
Subject: Re: [PATCH] overlay: sgid inheritance over whiteout
Date: Thu, 1 Sep 2016 12:41:33 +1000	[thread overview]
Message-ID: <20160901024133.GD30056@dastard> (raw)
In-Reply-To: <1472112972-11919-1-git-send-email-eguan@redhat.com>

On Thu, Aug 25, 2016 at 04:16:12PM +0800, Eryu Guan wrote:
> Newly created files and dirs should inherit sgit bit from parent
> dir, no matter the new files & dirs are created over whiteout or
> not.
> 
> Signed-off-by: Eryu Guan <eguan@redhat.com>

Looks reasonable. The overlay use of SCRATCH_DEV gets me every time,
though. :P

Reviewed-by: Dave Chinner <dchinner@redhat.com>

-- 
Dave Chinner
david@fromorbit.com

      parent reply	other threads:[~2016-09-01  2:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25  8:16 [PATCH] overlay: sgid inheritance over whiteout Eryu Guan
2016-08-31  9:45 ` Eryu Guan
2016-09-01  2:41 ` Dave Chinner [this message]

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=20160901024133.GD30056@dastard \
    --to=david@fromorbit.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-unionfs@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).