From: Josef Bacik <josef@redhat.com>
To: Liu Bo <liubo2009@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: only inherit btrfs specific flags when creating files
Date: Wed, 28 Sep 2011 08:26:09 -0400 [thread overview]
Message-ID: <4E831261.9010100@redhat.com> (raw)
In-Reply-To: <4E82717D.6080008@cn.fujitsu.com>
On 09/27/2011 08:59 PM, Liu Bo wrote:
> On 09/27/2011 11:02 PM, Josef Bacik wrote:
>> Xfstests 79 was failing because we were inheriting the S_APPEND flag when we
>> weren't supposed to. There isn't any specific documentation on this so I'm
>> taking the test as the standard of how things work, and having S_APPEND set on a
>> directory doesn't mean that S_APPEND gets inherited by its children according to
>> this test. So only inherit btrfs specific things. This will let us set
>> compress/nocompress on specific directories and everything in the directories
>> will inherit this flag, same with nodatacow. With this patch test 79 passes.
>> Thanks,
>>
>
> I've checked ext3&4, they have such comments:
>
> /* Flags that should be inherited by new inodes from their parent. */
> #define EXT3_FL_INHERITED (EXT3_SECRM_FL | EXT3_UNRM_FL | EXT3_COMPR_FL |\
> EXT3_SYNC_FL | EXT3_IMMUTABLE_FL | EXT3_APPEND_FL |\
> EXT3_NODUMP_FL | EXT3_NOATIME_FL | EXT3_COMPRBLK_FL|\
> EXT3_NOCOMPR_FL | EXT3_JOURNAL_DATA_FL |\
> EXT3_NOTAIL_FL | EXT3_DIRSYNC_FL)
>
> 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,
Josef
next prev parent reply other threads:[~2011-09-28 12:26 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 [this message]
2011-09-28 14:45 ` Christoph Hellwig
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=4E831261.9010100@redhat.com \
--to=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).