From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] Remove filesize checks for sync I/O journal commit
Date: Wed, 05 Nov 2014 09:26:28 -0600 [thread overview]
Message-ID: <545A41A4.90002@suse.de> (raw)
In-Reply-To: <20141104144533.a05c6dd5d3db3b5274d4e36c@linux-foundation.org>
On 11/04/2014 04:45 PM, Andrew Morton wrote:
> On Tue, 4 Nov 2014 09:52:22 -0600 Goldwyn Rodrigues <rgoldwyn@suse.de> wrote:
>
>> Filesize is not a good indication that the file needs to be synced.
>> An example where this breaks is:
>> 1. Open the file in O_SYNC|O_RDWR
>> 2. Read a small portion of the file (say 64 bytes)
>> 3. Lseek to starting of the file
>> 4. Write 64 bytes
>>
>> If the node crashes, it is not written out to disk because this
>> was not committed in the journal and the other node which reads
>> the file after recovery reads stale data (even if the write on
>> the other node was successful)
>>
>> ...
>>
>> --- a/fs/ocfs2/file.c
>> +++ b/fs/ocfs2/file.c
>> @@ -2381,9 +2381,7 @@ out_dio:
>> if (ret < 0)
>> written = ret;
>>
>> - if (!ret && ((old_size != i_size_read(inode)) ||
>> - (old_clusters != OCFS2_I(inode)->ip_clusters) ||
>> - has_refcount)) {
>> + if (!ret) {
>> ret = jbd2_journal_force_commit(osb->journal->j_journal);
>> if (ret < 0)
>> written = ret;
>
> Can we have a signed-off-by for this, please?
>
Oops. Missed that.
Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.de>
--
Goldwyn
next prev parent reply other threads:[~2014-11-05 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 15:52 [Ocfs2-devel] [PATCH] Remove filesize checks for sync I/O journal commit Goldwyn Rodrigues
2014-11-04 22:45 ` Andrew Morton
2014-11-05 15:26 ` Goldwyn Rodrigues [this message]
2014-11-05 21:18 ` Mark Fasheh
2014-12-03 8:20 ` Xue jiufei
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=545A41A4.90002@suse.de \
--to=rgoldwyn@suse.de \
--cc=ocfs2-devel@oss.oracle.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