From: Theodore Ts'o <tytso@mit.edu>
To: Niu Yawei <yawei.niu@gmail.com>
Cc: adityakali@google.com, linux-ext4@vger.kernel.org,
yawei.niu@intel.com, andreas.dilger@intel.com
Subject: Re: [PATCH] tune2fs: update i_size in ext2fs_file_write()
Date: Tue, 8 Oct 2013 11:45:32 -0400 [thread overview]
Message-ID: <20131008154532.GC17896@thunk.org> (raw)
In-Reply-To: <52537C42.9010808@gmail.com>
On Tue, Oct 08, 2013 at 11:30:10AM +0800, Niu Yawei wrote:
> ext2fs_file_write() needs to update i_size on successful write,
> otherwise, ext2fs_file_read() in same open/close cycle will not
> be able to read the just written data.
>
> This bug result in the the problem of quotacheck triggered on
> 'tune2fs -O quota' failed to write back multiple users/groups
> accounting information.
>
> Signed-off-by: Niu Yawei <yawei.niu@intel.com>
Applied, thanks.
- Ted
prev parent reply other threads:[~2013-10-08 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 14:21 [PATCH] tune2fs: update i_size in ext2fs_file_write() Niu Yawei
2013-10-08 3:30 ` Niu Yawei
2013-10-08 15:45 ` Theodore Ts'o [this message]
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=20131008154532.GC17896@thunk.org \
--to=tytso@mit.edu \
--cc=adityakali@google.com \
--cc=andreas.dilger@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=yawei.niu@gmail.com \
--cc=yawei.niu@intel.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).