From: Chris Mason <chris.mason@oracle.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
linux-mm <linux-mm@kvack.org>, ext4 <linux-ext4@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
npiggin@suse.de
Subject: Re: pagefault in generic_file_buffered_write() causing deadlock
Date: Wed, 15 Nov 2006 15:39:52 -0500 [thread overview]
Message-ID: <20061115203929.GE2392@think.oraclecorp.com> (raw)
In-Reply-To: <20061115112957.e38539e9.akpm@osdl.org>
On Wed, Nov 15, 2006 at 11:29:57AM -0800, Andrew Morton wrote:
> Oh well. If it's a deadlock (this is not clear from your description) then
> please gather backtraces of all affected tasks.
>
> There is an ab/ba deadlock with journal_start() and lock_page(), iirc.
> Chris and I had a look at that a while back and collapsed in exhaustion -
> it isn't pretty.
This should be the page fault/journal lock inversion stuff Nick was
working on. His patchset had a pretty good description of the problems,
Badari can also dig through the novell/ltc bugzillas for vmmstress.
Should be LTC9358.
Hopefully Nick's patches will address all of this. sles9 had a partial
solution for the mmap deadlock, I think it was to dirty the inode at a
later time. For some reason, I thought this workload was passing in
later kernels...
-chris
prev parent reply other threads:[~2006-11-15 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 15:57 pagefault in generic_file_buffered_write() causing deadlock Badari Pulavarty
2006-11-15 17:00 ` Andrew Morton
2006-11-15 18:16 ` Badari Pulavarty
2006-11-15 18:20 ` Badari Pulavarty
2006-11-15 19:29 ` Andrew Morton
2006-11-15 20:39 ` Chris Mason [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=20061115203929.GE2392@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=akpm@osdl.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).