public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Chris Mason <chris.mason@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs failing fsx-linux
Date: Wed, 9 Sep 2009 15:34:35 +0200	[thread overview]
Message-ID: <20090909133435.GC6034@wotan.suse.de> (raw)
In-Reply-To: <20090909131349.GB4522@think>

On Wed, Sep 09, 2009 at 09:13:49AM -0400, Chris Mason wrote:
> On Tue, Aug 18, 2009 at 07:26:41PM +0200, Nick Piggin wrote:
> > Hi Chris,
> > 
> > Don't know if this is a known issue, but I have btrfs (after my previous
> > inode_tree fixup patch) failing fsx-linux in Linus's current git tree.
> > 
> > This makes it a bit hard for me to test my btrfs truncate conversion patch
> > unfortunately, though it does seem pretty stable so I will probably just
> > send it out anyway.
> > 
> > Anyway, just a head's up. Oh, the way I reproduce is to create btrfs
> > on 1GB rd, run 4 instances of fsx-linux on different files in the root
> > directory, and run `while true ; do sync ; echo 3 > /proc/sys/vm/drop_caches;
> > done` at the same time.
> 
> Just an update, I think I've tracked this down.  Our fixup code for when
> set_page_dirty was called without page_mkwrite wasn't catching every
> case.  I'm hitting other problems because I'm testing on my new
> performance code, but hopefully this will all be nailed down soon.

Which cases do set_page_dirty happen without page_mkwrite? For fsx-linux
I hope there shouldn't be any... but one issue with btrfs's page_mkwrite
is that it still unlocks the page before page_mkwrite returns so if it
is anything like other filesystems, the page might get written out
between the page_mkwrite and the page fault's subsequent set_page_dirty.

So if that race is hitting, it might appear like set_page_dirty is
being called without a page_mkwrite.


  reply	other threads:[~2009-09-09 13:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18 17:26 btrfs failing fsx-linux Nick Piggin
2009-08-18 17:59 ` Josef Bacik
2009-08-19  8:50   ` Nick Piggin
2009-09-02 17:14   ` Nick Piggin
2009-09-02 17:29     ` Josef Bacik
2009-09-02 19:07     ` Chris Mason
2009-09-03  7:10       ` Nick Piggin
2009-09-09 13:13 ` Chris Mason
2009-09-09 13:34   ` Nick Piggin [this message]
2009-09-09 13:37     ` Chris Mason
2009-09-09 13:43       ` Nick Piggin
2009-09-09 13:47         ` Chris Mason
2009-09-11 19:36 ` Chris Mason

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=20090909133435.GC6034@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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