From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 3/4] gfs2: Use generic handlers of O_SYNC AIO DIO
Date: Mon, 13 Feb 2012 09:42:18 +0000 [thread overview]
Message-ID: <1329126138.2702.4.camel@menhir> (raw)
In-Reply-To: <1328889842-23231-4-git-send-email-jack@suse.cz>
Hi,
Acked-by: Steven Whitehouse <swhiteho@redhat.com>
That looks ok to me,
Steve.
On Fri, 2012-02-10 at 17:04 +0100, Jan Kara wrote:
> Use generic handlers to queue fsync() when AIO DIO is completed for O_SYNC
> file.
>
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> fs/gfs2/aops.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/gfs2/aops.c b/fs/gfs2/aops.c
> index 501e5cb..9c381ff 100644
> --- a/fs/gfs2/aops.c
> +++ b/fs/gfs2/aops.c
> @@ -1034,7 +1034,7 @@ static ssize_t gfs2_direct_IO(int rw, struct kiocb *iocb,
>
> rv = __blockdev_direct_IO(rw, iocb, inode, inode->i_sb->s_bdev, iov,
> offset, nr_segs, gfs2_get_block_direct,
> - NULL, NULL, 0);
> + NULL, NULL, DIO_SYNC_WRITES);
> out:
> gfs2_glock_dq_m(1, &gh);
> gfs2_holder_uninit(&gh);
next prev parent reply other threads:[~2012-02-13 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 16:03 [Cluster-devel] [PATCH 0/4] Generic O_SYNC AIO DIO handling Jan Kara
2012-02-10 16:03 ` [Cluster-devel] [PATCH 1/4] vfs: Handle O_SYNC AIO DIO in generic code properly Jan Kara
2012-02-10 16:04 ` [Cluster-devel] [PATCH 2/4] ocfs2: Use generic handlers of O_SYNC AIO DIO Jan Kara
2012-02-10 16:04 ` [Cluster-devel] [PATCH 3/4] gfs2: " Jan Kara
2012-02-13 9:42 ` Steven Whitehouse [this message]
2012-02-10 16:04 ` [Cluster-devel] [PATCH 4/4] btrfs: " Jan Kara
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=1329126138.2702.4.camel@menhir \
--to=swhiteho@redhat.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).