From: Ted Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
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 13:19:49 -0500 [thread overview]
Message-ID: <20111222181949.GE5041@thunk.org> (raw)
In-Reply-To: <4EF371AC.6000001@redhat.com>
On Thu, Dec 22, 2011 at 12:06:36PM -0600, Eric Sandeen wrote:
> 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?
Yes, it's there. It hit upstream as of v3.2-rc1. Commit id 1cd9f097
- Ted
next prev parent reply other threads:[~2011-12-22 18:19 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
2011-12-22 18:19 ` Ted Ts'o [this message]
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=20111222181949.GE5041@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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).