From: Andrew Morton <akpm@osdl.org>
To: Chris Mason <mason@suse.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: deadlocks caused by ext3/reiser dirty_inode calls during do_mmap_pgoff
Date: Tue, 22 Jun 2004 11:57:48 -0700 [thread overview]
Message-ID: <20040622115748.396badfe.akpm@osdl.org> (raw)
In-Reply-To: <1087913598.1512.264.camel@watt.suse.com>
Chris Mason <mason@suse.com> wrote:
>
> Hmmm, reiserfs_file_write does fault_in_pages_readable after the
> transaction is started.
That nests down_read(mmap_sem) inside transaction start, vastly increasing
the deadlock probability.
> I can at least make the window smaller for now
> by moving that before the transaction is started.
Much smaller.
We need to decide what the ranking is and stick with it. I think that's
"transaction start nests inside mmap_sem", agree?
next prev parent reply other threads:[~2004-06-22 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 16:59 deadlocks caused by ext3/reiser dirty_inode calls during do_mmap_pgoff Chris Mason
2004-06-22 0:13 ` Andrew Morton
2004-06-22 14:13 ` Chris Mason
2004-06-22 18:57 ` Andrew Morton [this message]
2004-06-22 20:32 ` Chris Mason
2004-06-22 14:43 ` Chris Mason
2004-06-22 19:05 ` Andrew Morton
2004-06-22 20:41 ` Chris Mason
2004-06-25 17:59 ` 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=20040622115748.396badfe.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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