From: Dave Chinner <david@fromorbit.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: Locking between writeback and truncate paths?
Date: Tue, 27 Apr 2010 10:05:39 +1000 [thread overview]
Message-ID: <20100427000539.GA9783@dastard> (raw)
In-Reply-To: <E1O6CFc-0006Y2-SY@closure.thunk.org>
On Sun, Apr 25, 2010 at 08:32:40PM -0400, Theodore Ts'o wrote:
> Any thoughts or suggestions would be greatly appreciated. I've looked
> at the xfs and btrfs code for some ideas, but dealing with current
> writeback and truncate is nasty, especially if there's a subsequent
> delalloc write happening in parallel with the writeback and immediately
> after the truncate. After studying the code quite extensively over the
> weekend, I'm still not entirely sure that XFS and btrfs gets this case
> right (I know ext4 currently doesn't). Of course, it's not clear
> whether users will trip against this in practice, but it's nevertheless
> still a botch, and I'm wondering if it's simpler to avoid the concurrent
> vmtruncate/writeback case entirely.
What case are you concerned that is XFS not getting right?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-04-27 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 0:32 Locking between writeback and truncate paths? Theodore Ts'o
2010-04-27 0:05 ` Dave Chinner [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=20100427000539.GA9783@dastard \
--to=david@fromorbit.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tytso@mit.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).