mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: cliff white <cliffw@osdl.org>, Badari Pulavarty <pbadari@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 2.6.12-rc2 + rc3: reaim with ext3 - system stalls.
Date: Tue, 3 May 2005 16:43:25 +0200	[thread overview]
Message-ID: <20050503144325.GF4501@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20050421152345.6b87aeae@es175>

  Hello,

> Started seeing some odd behaviour with recent kernels, haven't been able to
> run it down, could use some suggestions/help.
> 
> Running re-aim7 with 2.6.12-rc2 and rc3, if I use xfs, jfs, or
> reiserfs things work just fine.
> 
> With ext3, the  test stalls, such that:
> CPU is 50% idle, 50% waiting IO (top)
> vmstat shows one process blocked wio
  I've looked through your dumps and I spotted where is the problem -
it's our well known and beloved lock inversion between PageLock and
transaction start (giving CC to Badari who's the author of the patch
that introduced it AFAIK).
  The correct order is: first get PageLock and *then* start transaction.
But in ext3_writeback_writepages() first ext3_journal_start() is called
and then __mpage_writepages is called that tries to do LockPage and
deadlock is there. Badari, could you please fix that (sadly I think that
would not be easy)? Maybe we should back out those changes until it gets
fixed...

								Honza


  reply	other threads:[~2005-05-03 14:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 22:23 cliff white
2005-05-03 14:43 ` Jan Kara [this message]
2005-05-03 15:01   ` Badari Pulavarty
2005-05-03 15:32     ` cliff white
2005-05-04 16:02     ` Cliff White
2005-05-05 17:57       ` Badari Pulavarty
2005-05-06 10:14         ` Jan Kara
2005-05-06 15:06           ` Badari Pulavarty
2005-05-09  9:25             ` 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=20050503144325.GF4501@atrey.karlin.mff.cuni.cz \
    --to=jack@suse.cz \
    --cc=akpm@osdl.org \
    --cc=cliffw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.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

all inboxes | Powered by JetHome®