From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: wait for direct I/O to complete in fsync and write_inode
Date: Wed, 14 Apr 2010 09:40:15 +1000 [thread overview]
Message-ID: <20100413234015.GB2493@dastard> (raw)
In-Reply-To: <20100306132018.GA31360@infradead.org>
On Sat, Mar 06, 2010 at 08:20:18AM -0500, Christoph Hellwig wrote:
>
> We need to wait for all pending direct I/O requests before taking care of
> metadata in fsync and write_inode.
Sorry, I missed this one when scaning the list for outstanding
patches yesterday. The concept looks fine, though:
> Note that the write_inode hunk will causes conflicts when merging with
> mainline, I'm not sure how to best deal with that.
I don't think it applies to the current xfs-dev tree any more,
either. Can you rebase it?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-13 23:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 13:20 [PATCH] xfs: wait for direct I/O to complete in fsync and write_inode Christoph Hellwig
2010-04-13 14:37 ` Christoph Hellwig
2010-04-13 23:40 ` Dave Chinner [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-18 0:02 Christoph Hellwig
2010-04-20 5:25 ` Dave Chinner
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=20100413234015.GB2493@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.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