From: Christoph Hellwig <hch@infradead.org>
To: Josef Bacik <josef@redhat.com>
Cc: Liu Bo <liubo2009@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: only inherit btrfs specific flags when creating files
Date: Wed, 28 Sep 2011 10:45:03 -0400 [thread overview]
Message-ID: <20110928144502.GA4018@infradead.org> (raw)
In-Reply-To: <4E831261.9010100@redhat.com>
On Wed, Sep 28, 2011 at 08:26:09AM -0400, Josef Bacik wrote:
> >
> > It shows EXT[3,4]_APPEND_FL should be inherited from their parent, is this the standard?
> >
>
> I have no idea actually, it was just failing on xfstest 79 and when I
> took out the inheritance thing it passed so I took the test to be the
> standard, maybe we should open this up to a wider audience. Thanks,
We had a little discussion on this when Stefan Behrens made this
test generic, and the conclusion was that the other filesystems should
adopt the xfs behaviour.
prev parent reply other threads:[~2011-09-28 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 15:02 [PATCH] Btrfs: only inherit btrfs specific flags when creating files Josef Bacik
2011-09-28 0:59 ` Liu Bo
2011-09-28 12:26 ` Josef Bacik
2011-09-28 14:45 ` Christoph Hellwig [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=20110928144502.GA4018@infradead.org \
--to=hch@infradead.org \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.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 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).