From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/3] xfs: fixes for 3.12-rc2
Date: Tue, 17 Sep 2013 11:44:28 +1000 [thread overview]
Message-ID: <1379382271-29907-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
Three patches for 3.12-rc2. The first has been posted previously,
and prevents an assert failure during a shutdown while zeroing space
with an uncached buffer.
The second patch is to fix a regression introduced in the 3.12 merge
by commit 46f9d2e ("xfs: aborted buf items can be in the AIL").
The third is fixing a thinko made a long time ago when adding RCU
freeing to the struct xfs_inode, but has only been exposed by the
recent merge of the per-node LRUs and shrinkers allowing concurrent
reclaim and lookup races to be hit easily. The RCU traversals of the
inode radix trees take the lock on the inode to determine if it is
being freed or not, and so that can race with freeing of the inode.
Hence we can't assert that the lock is not held when freeing the
inode.
These all fix regressions triggered by xfstests....
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-09-17 1:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 1:44 Dave Chinner [this message]
2013-09-17 1:44 ` [PATCH 1/3] xfs: don't try to mark uncached buffers stale on error Dave Chinner
2013-09-17 1:44 ` [PATCH 2/3] xfs: lock the AIL before removing the buffer item Dave Chinner
2013-09-17 1:44 ` [PATCH 3/3] xfs: asserting lock not held during freeing not valid Dave Chinner
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=1379382271-29907-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.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