All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext2,ext3,ext4: don't inherit APPEND_FL or IMMUTABLE_FL for new inodes
Date: Thu, 22 Dec 2011 12:06:36 -0600	[thread overview]
Message-ID: <4EF371AC.6000001@redhat.com> (raw)
In-Reply-To: <1313288886-32689-1-git-send-email-tytso@mit.edu>

On 8/13/11 9:28 PM, Theodore Ts'o wrote:
> This doesn't make much sense, and it exposes a bug in the kernel where
> attempts to create a new file in an append-only directory using
> O_CREAT will fail (but still leave a zero-length file).  This was
> discovered when xfstests #79 was generalized so it could run on all
> file systems.

Curious about the status of this one; I think it makes sense to me, but
I don't think it ever made it upstream?  I'd be willing to give it a:

Reviewed-by: Eric Sandeen <sandeen@redhat.com>

Are there concerns about it or did it just slip through the cracks?


> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
> ---
>  fs/ext4/ext4.h          |    3 +--
>  include/linux/ext2_fs.h |    4 ++--
>  include/linux/ext3_fs.h |    4 ++--
>  3 files changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index e717dfd..be593d5 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -357,8 +357,7 @@ struct flex_groups {
>  
>  /* Flags that should be inherited by new inodes from their parent. */
>  #define EXT4_FL_INHERITED (EXT4_SECRM_FL | EXT4_UNRM_FL | EXT4_COMPR_FL |\
> -			   EXT4_SYNC_FL | EXT4_IMMUTABLE_FL | EXT4_APPEND_FL |\
> -			   EXT4_NODUMP_FL | EXT4_NOATIME_FL |\
> +			   EXT4_SYNC_FL | EXT4_NODUMP_FL | EXT4_NOATIME_FL |\
>  			   EXT4_NOCOMPR_FL | EXT4_JOURNAL_DATA_FL |\
>  			   EXT4_NOTAIL_FL | EXT4_DIRSYNC_FL)
>  
> diff --git a/include/linux/ext2_fs.h b/include/linux/ext2_fs.h
> index 53792bf..ce1b719 100644
> --- a/include/linux/ext2_fs.h
> +++ b/include/linux/ext2_fs.h
> @@ -197,8 +197,8 @@ struct ext2_group_desc
>  
>  /* Flags that should be inherited by new inodes from their parent. */
>  #define EXT2_FL_INHERITED (EXT2_SECRM_FL | EXT2_UNRM_FL | EXT2_COMPR_FL |\
> -			   EXT2_SYNC_FL | EXT2_IMMUTABLE_FL | EXT2_APPEND_FL |\
> -			   EXT2_NODUMP_FL | EXT2_NOATIME_FL | EXT2_COMPRBLK_FL|\
> +			   EXT2_SYNC_FL | EXT2_NODUMP_FL |\
> +			   EXT2_NOATIME_FL | EXT2_COMPRBLK_FL |\
>  			   EXT2_NOCOMP_FL | EXT2_JOURNAL_DATA_FL |\
>  			   EXT2_NOTAIL_FL | EXT2_DIRSYNC_FL)
>  
> diff --git a/include/linux/ext3_fs.h b/include/linux/ext3_fs.h
> index 67a803a..0244611 100644
> --- a/include/linux/ext3_fs.h
> +++ b/include/linux/ext3_fs.h
> @@ -180,8 +180,8 @@ struct ext3_group_desc
>  
>  /* 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_SYNC_FL | EXT3_NODUMP_FL |\
> +			   EXT3_NOATIME_FL | EXT3_COMPRBLK_FL |\
>  			   EXT3_NOCOMPR_FL | EXT3_JOURNAL_DATA_FL |\
>  			   EXT3_NOTAIL_FL | EXT3_DIRSYNC_FL)
>  


  reply	other threads:[~2011-12-22 18:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 11:26 [PATCH v2] ext4: Deprecate data=journal mount option Lukas Czerner
2011-06-29  4:49 ` Bruce Guenter
2011-06-29 11:49   ` Lukas Czerner
2011-08-11 15:01 ` Lukas Czerner
2011-08-11 21:08   ` Andreas Dilger
2011-08-12  8:16     ` Lukas Czerner
2011-08-12  8:25       ` Ric Wheeler
2011-08-12 15:45         ` Curt Wohlgemuth
2011-08-12 16:08           ` Lukas Czerner
2011-08-12 18:13             ` Ted Ts'o
2011-08-12 20:57               ` Christoph Hellwig
2011-08-14  2:06                 ` Ted Ts'o
2011-08-14  2:28                   ` [PATCH] ext2,ext3,ext4: don't inherit APPEND_FL or IMMUTABLE_FL for new inodes Theodore Ts'o
2011-12-22 18:06                     ` Eric Sandeen [this message]
2011-12-22 18:19                       ` Ted Ts'o
2011-12-22 18:23                         ` Eric Sandeen
2011-08-15 11:19                   ` [PATCH v2] ext4: Deprecate data=journal mount option Jan Kara

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=4EF371AC.6000001@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.