From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Cc: Brian Foster <bfoster@redhat.com>
Subject: [RFC PATCH v2 3/3] xfs: fix xfsaild hang due to lost wake ups
Date: Mon, 21 May 2012 14:49:29 -0400 [thread overview]
Message-ID: <1337626169-21730-4-git-send-email-bfoster@redhat.com> (raw)
In-Reply-To: <1337626169-21730-1-git-send-email-bfoster@redhat.com>
Running xfstests 273 in a loop reproduces an XFS lockup due to
xfsaild entering idle mode indefinitely. The following
high-level sequence of events leads to the hang:
- xfsaild is running with a cached target lsn
- xfs_ail_push() is invoked, updates ailp->xa_target_lsn and
invokes wake_up_process(). wake_up_process() returns 0
because xfsaild is already running.
- xfsaild enters idle mode having met its current target.
Once in the described state, xfs_ail_push() is invoked many
more times with the already set threshold_lsn, but these calls
do not lead to wake_up_process() calls because no further
invocations result in moving the threshold_lsn forward. Add a
flag to xfs_ail to capture whether an issued wake actually
succeeds. If not, continue issuing wakes until we know one has
been successful for the current target.
Signed-off-by: Brian Foster <bfoster@redhat.com>
---
fs/xfs/xfs_trans_ail.c | 4 ++--
fs/xfs/xfs_trans_priv.h | 1 +
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/xfs/xfs_trans_ail.c b/fs/xfs/xfs_trans_ail.c
index 8bc8aa2..e886785 100644
--- a/fs/xfs/xfs_trans_ail.c
+++ b/fs/xfs/xfs_trans_ail.c
@@ -583,7 +583,7 @@ xfs_ail_push(
lip = xfs_ail_min(ailp);
if (!lip || XFS_FORCED_SHUTDOWN(ailp->xa_mount) ||
- XFS_LSN_CMP(threshold_lsn, ailp->xa_target) <= 0)
+ ((XFS_LSN_CMP(threshold_lsn, ailp->xa_target) <= 0) && !ailp->xa_pending_wake))
return;
/*
@@ -594,7 +594,7 @@ xfs_ail_push(
xfs_trans_ail_copy_lsn(ailp, &ailp->xa_target, &threshold_lsn);
smp_wmb();
- wake_up_process(ailp->xa_task);
+ ailp->xa_pending_wake = !wake_up_process(ailp->xa_task);
}
/*
diff --git a/fs/xfs/xfs_trans_priv.h b/fs/xfs/xfs_trans_priv.h
index 8ab2ced..62bb4a9 100644
--- a/fs/xfs/xfs_trans_priv.h
+++ b/fs/xfs/xfs_trans_priv.h
@@ -71,6 +71,7 @@ struct xfs_ail {
spinlock_t xa_lock;
xfs_lsn_t xa_last_pushed_lsn;
int xa_log_flush;
+ int xa_pending_wake;
};
/*
--
1.7.7.6
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-05-21 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 18:49 [RFC PATCH v2 0/3] xfs: fix xfsaild races and re-enable idle mode Brian Foster
2012-05-21 18:49 ` [RFC PATCH v2 1/3] xfs: re-enable xfsaild " Brian Foster
2012-05-21 18:49 ` [RFC PATCH v2 2/3] xfs: fix xfsaild hang due to premature idle Brian Foster
2012-05-21 21:19 ` Mark Tinguely
2012-05-22 0:31 ` Brian Foster
2012-05-22 13:10 ` Mark Tinguely
2012-05-21 18:49 ` Brian Foster [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=1337626169-21730-4-git-send-email-bfoster@redhat.com \
--to=bfoster@redhat.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