From: Theodore Ts'o <tytso@mit.edu>
To: Jayashree Mohan <jayashree2912@gmail.com>
Cc: linux-ext4@vger.kernel.org,
Vijaychidambaram Velayudhan Pillai <vijay@cs.utexas.edu>
Subject: Re: Incorrect block count during stat of a file if fallocate follows a buffered write.
Date: Tue, 2 Jan 2018 13:52:40 -0500 [thread overview]
Message-ID: <20180102185240.GC2367@thunk.org> (raw)
In-Reply-To: <CA+EzBbAbdJAU4v_Wb5c1kkgWA=fU0HLz_XmV9Y4NUit1HUiGeQ@mail.gmail.com>
On Tue, Jan 02, 2018 at 11:39:22AM -0600, Jayashree Mohan wrote:
> I wasn't sure if you missed this mail in your inbox. So I wanted to
> send a gentle reminder about the same.
Ack, I have seen it. I've just hadn't gotten to it yet, but it is
definitely on my queue!
- Ted
prev parent reply other threads:[~2018-01-02 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-26 22:07 Incorrect block count during stat of a file if fallocate follows a buffered write Jayashree Mohan
2018-01-02 17:39 ` Jayashree Mohan
2018-01-02 18:52 ` 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=20180102185240.GC2367@thunk.org \
--to=tytso@mit.edu \
--cc=jayashree2912@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=vijay@cs.utexas.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 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).