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] generic: simple permission check on hard links
Date: Thu, 8 Sep 2016 08:45:36 +1000 [thread overview]
Message-ID: <20160907224536.GG22388@dastard> (raw)
In-Reply-To: <1473243969-12326-1-git-send-email-eguan@redhat.com>
On Wed, Sep 07, 2016 at 06:26:09PM +0800, Eryu Guan wrote:
> Overlayfs had a bug that hardlinks don't share inode, if
> chmod/chown/etc. is performed on one of the links then the inode
> belonging to the other one won't be updated. The following patch
> fixed this issue:
>
> 51f7e52 ovl: share inode for hard link
>
> This is a simple test that has nothing overlayfs specific, so make
> it a generic test.
>
> Signed-off-by: Eryu Guan <eguan@redhat.com>
Looks ok to me.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2016-09-07 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 10:26 [PATCH] generic: simple permission check on hard links Eryu Guan
2016-09-07 22:45 ` 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=20160907224536.GG22388@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).