From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/2 v3] ocfs2: Flush drive's caches on fdatasync
Date: Wed, 11 Aug 2010 17:32:42 -0700 [thread overview]
Message-ID: <20100812003241.GE8985@mail.oracle.com> (raw)
In-Reply-To: <1281033166-12485-2-git-send-email-jack@suse.cz>
On Thu, Aug 05, 2010 at 08:32:45PM +0200, Jan Kara wrote:
> When 'barrier' mount option is specified, we have to issue a cache flush
> during fdatasync(2). We have to do this even if inode doesn't have
> I_DIRTY_DATASYNC set because we still have to get written *data* to disk so
> that they are not lost in case of crash.
>
> Acked-by: Tao Ma <tao.ma@oracle.com>
> Signed-off-by: Jan Kara <jack@suse.cz>
This patch is now in the merge-window branch of ocfs2.git
Joel
--
Life's Little Instruction Book #335
"Every so often, push your luck."
Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-08-12 0:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 18:32 [Ocfs2-devel] [PATCH 0/2 v3] OCFS2 bugfix in fdatasync and a cleanup Jan Kara
2010-08-05 18:32 ` [Ocfs2-devel] [PATCH 1/2 v3] ocfs2: Flush drive's caches on fdatasync Jan Kara
2010-08-12 0:32 ` Joel Becker [this message]
2010-08-05 18:32 ` [Ocfs2-devel] [PATCH 2/2 v3] ocfs2: Remove ocfs2_sync_inode() Jan Kara
2010-08-08 19:47 ` Mark Fasheh
2010-08-12 0:32 ` Joel Becker
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=20100812003241.GE8985@mail.oracle.com \
--to=joel.becker@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.