From: Christoph Hellwig <hch@infradead.org>
To: Filipe David Manana <fdmanana@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
linuxpatches@star.c10r.facebook.com
Subject: Re: [PATCH] Btrfs: implement inode_operations callback tmpfile
Date: Wed, 16 Apr 2014 04:27:00 -0700 [thread overview]
Message-ID: <20140416112700.GA1187@infradead.org> (raw)
In-Reply-To: <CAL3q7H5zO8nVrXRcdMwAa-6MDG_RFxUdWHpMV7MrY03Bvet3+A@mail.gmail.com>
On Wed, Apr 16, 2014 at 12:25:07PM +0100, Filipe David Manana wrote:
> Interesting Christoph.
> I was following the ext4 implementation initially.
>
> So it seems the question is still open, and none of the following
> alternatives is decided yet (unless I missed something in the thread
> at fsdevel):
>
> 1) inherit acl from directory passed to the tmpfile handler;
> 2) inherit acl at link time from directory we're linking to;
> 3) don't inherit acls
>
> Thanks for the heads up.
I'll make sure we'll have a testcase in xfstests to cover whatever
behavior we decide on to make sure all filesystems behave the same way.
next prev parent reply other threads:[~2014-04-16 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 22:53 [PATCH] Btrfs: implement inode_operations callback tmpfile Filipe David Borba Manana
2014-04-04 13:59 ` David Sterba
2014-04-04 14:12 ` Chris Mason
2014-04-04 14:16 ` Filipe David Manana
2014-04-16 9:00 ` Chandan Rajendra
2014-04-16 10:36 ` Filipe David Manana
2014-04-16 11:09 ` Christoph Hellwig
2014-04-16 11:25 ` Filipe David Manana
2014-04-16 11:27 ` Christoph Hellwig [this message]
2014-04-27 19:40 ` [PATCH v2] " Filipe David Borba Manana
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=20140416112700.GA1187@infradead.org \
--to=hch@infradead.org \
--cc=chandan@linux.vnet.ibm.com \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linuxpatches@star.c10r.facebook.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.