From: Ted Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v2] ext3: Convert ext3 to new truncate calling convention
Date: Wed, 25 May 2011 17:41:10 -0400 [thread overview]
Message-ID: <20110525214110.GB9520@thunk.org> (raw)
In-Reply-To: <1306320216-19368-1-git-send-email-jack@suse.cz>
On Wed, May 25, 2011 at 12:43:36PM +0200, Jan Kara wrote:
> Mostly trivial conversion. We fix a bug that IS_IMMUTABLE and IS_APPEND
> files could not be truncated during failed writes as we change the code.
> In fact we remove the test altogether because do_sys_[f]truncate() and
> may_open() do necessary checks anyway.
>
> Signed-off-by: Jan Kara <jack@suse.cz>
Thanks, added to the ext4 tree.
- Ted
next prev parent reply other threads:[~2011-05-25 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 10:43 [PATCH v2] ext3: Convert ext3 to new truncate calling convention Jan Kara
2011-05-25 11:48 ` Christoph Hellwig
2011-05-26 14:23 ` Jan Kara
2011-05-27 7:16 ` Christoph Hellwig
2011-05-25 21:41 ` Ted Ts'o [this message]
2011-05-25 21:42 ` Ted Ts'o
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=20110525214110.GB9520@thunk.org \
--to=tytso@mit.edu \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
/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).