From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH v3 0/2] fix spinlock recursion on xa_lock in xfs_buf_item_push
Date: Fri, 8 Feb 2013 09:51:05 -0500 [thread overview]
Message-ID: <1360335067-59999-1-git-send-email-bfoster@redhat.com> (raw)
Hi all,
Here is v3 of the spinlock recursion fix, based on Dave's comments here:
http://oss.sgi.com/archives/xfs/2013-02/msg00106.html
Note that I'm testing and posting this for review in parallel, given that v2
had seen several hours of testing with the log force bypassed in aild context.
This implementation removes the trylock log force entirely, so continued testing
will determine whether any regressions crop up and I'll post an update after a
few days.
Brian
v3:
- Patches reordered and revised to:
1.) Add the race detection in xfs_buf_item_push().
2.) Remove the log force from xfs_buf_trylock() entirely to fix the recursion
and rely on xfsaild to issue the log force.
v2:
- Patch 2 is reworked to detect the potential race and defer the log force to
xfsaild by returning XFS_ITEM_PINNED.
Brian Foster (2):
xfs: recheck buffer pinned status after push trylock failure
xfs: remove log force from xfs_buf_trylock()
fs/xfs/xfs_buf.c | 2 --
fs/xfs/xfs_buf_item.c | 9 ++++++++-
2 files changed, 8 insertions(+), 3 deletions(-)
--
1.7.7.6
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-02-08 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 14:51 Brian Foster [this message]
2013-02-08 14:51 ` [PATCH v3 1/2] xfs: recheck buffer pinned status after push trylock failure Brian Foster
2013-02-10 23:24 ` Dave Chinner
2013-02-08 14:51 ` [PATCH v3 2/2] xfs: remove log force from xfs_buf_trylock() Brian Foster
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=1360335067-59999-1-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