From: Peter Watkins <treestem@gmail.com>
To: xfs@oss.sgi.com
Cc: Peter Watkins <treestem@gmail.com>
Subject: [PATCH] xfs: Fix inode buffer deadlock during memory reclaim
Date: Tue, 17 May 2011 10:39:35 -0400 [thread overview]
Message-ID: <1305643175-8673-1-git-send-email-treestem@gmail.com> (raw)
During reclaim under clear_inode, one thread holds the iprune_mutex while
trying to get an inode buffer lock. The other thread has the inode buffer
lock while trying to get the iprune_mutex lock.
Avoid reclaim recursing into the file system by using KM_NOFS in
xfs_trans_alloc.
Signed-off-by: Peter Watkins <treestem@gmail.com>
---
fs/xfs/xfs_trans.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/xfs/xfs_trans.c b/fs/xfs/xfs_trans.c
index 7692279..f26f6d8 100644
--- a/fs/xfs/xfs_trans.c
+++ b/fs/xfs/xfs_trans.c
@@ -578,7 +578,7 @@ xfs_trans_alloc(
uint type)
{
xfs_wait_for_freeze(mp, SB_FREEZE_TRANS);
- return _xfs_trans_alloc(mp, type, KM_SLEEP);
+ return _xfs_trans_alloc(mp, type, KM_SLEEP|KM_NOFS);
}
xfs_trans_t *
--
1.7.0.4
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2011-05-17 14:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1305643175-8673-1-git-send-email-treestem@gmail.com \
--to=treestem@gmail.com \
--cc=xfs@oss.sgi.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