This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "XFS development tree".
The branch, master has been updated
9681153 xfs: add lockdep annotations for the rt inodes
0d8b30a xfs: fix xfs_get_extsz_hint for a zero extent size hint
04e9945 xfs: only lock the rt bitmap inode once per allocation
from 24446fc66fdebbdd8baca0f44fd2a47ad77ba580 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 9681153b460006923bb1e9d39b05b80ec09d6b4e
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue Jan 25 09:06:21 2011 +0000
xfs: add lockdep annotations for the rt inodes
The rt bitmap and summary inodes do not participate in the normal inode
locking protocol. Instead the rt bitmap inode can be locked in any
transaction involving rt allocations, and the both of the rt inodes can
be locked at the same time. Add specific lockdep subclasses for the rt
inodes to prevent lockdep from blowing up.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Signed-off-by: Alex Elder <aelder@xxxxxxx>
commit 0d8b30ad19bf13197cbcd786e2cd5a2ecef72e68
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue Jan 25 09:06:20 2011 +0000
xfs: fix xfs_get_extsz_hint for a zero extent size hint
We can easily set the extsize flag without setting an extent size
hint, or one that evaluates to zero. Historically the di_extsize
field was only used when it was non-zero, but the commit
"Cleanup inode extent size hint extraction"
broke this. Restore the old behaviour, thus fixing xfsqa 090 with
a debug kernel.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Signed-off-by: Alex Elder <aelder@xxxxxxx>
commit 04e99455ea5bb17ea7c2e7bb0970168efb736242
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue Jan 25 09:06:19 2011 +0000
xfs: only lock the rt bitmap inode once per allocation
Currently both xfs_rtpick_extent and xfs_rtallocate_extent call
xfs_trans_iget to grab and lock the rt bitmap inode, which results in a
deadlock since the removal of the lock recursion counters in commit
"xfs: simplify inode to transaction joining"
Fix this by acquiring and locking the inode in xfs_bmap_rtalloc before
calling into xfs_rtpick_extent and xfs_rtallocate_extent.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Signed-off-by: Alex Elder <aelder@xxxxxxx>
-----------------------------------------------------------------------
Summary of changes:
fs/xfs/xfs_bmap.c | 11 +++++++++++
fs/xfs/xfs_inode.h | 23 +++++++++++++++--------
fs/xfs/xfs_rtalloc.c | 50 +++++++++++++++++++++++---------------------------
fs/xfs/xfs_rw.c | 18 +++++-------------
4 files changed, 54 insertions(+), 48 deletions(-)
hooks/post-receive
--
XFS development tree
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
