lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 13 Aug 2011 22:06:17 -0400
From:	Ted Ts'o <>
To:	Christoph Hellwig <>
Cc:	Lukas Czerner <>,
	Curt Wohlgemuth <>,
	Ric Wheeler <>,
	Andreas Dilger <>,
	linux-ext4 List <>,
	Jan Kara <>, Eric Sandeen <>
Subject: Re: [PATCH v2] ext4: Deprecate data=journal mount option

On Fri, Aug 12, 2011 at 04:57:19PM -0400, Christoph Hellwig wrote:
> > and differences in error code returns for
> > xattrs) and #79 (a failure in the append-only handling which I don't
> > completely understand yet).
> This was discussed on fsdevel lately.  All filesystem but xfs inherit
> the append only bit from directories to files created inside them.
> This not only is not very useful behaviour, but also exposes a bug
> in the vfs that allows to create these new files, but fail the open
> unless using O_APPEND which is against the posix create semantics.

I agree that disabling inheritance of the APPEND_FL flag makes sense.
I propose we do this for ext2/3/4 and any other file systems which is
currently following the ext2/3/4 behavior.

Any objections?

						- Ted
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists