[GIT PULL] XFS update for 2.6.38-rc3

From: Alex Elder
Date: Mon Jan 31 2011 - 11:42:42 EST

Linus, please accept the following updates for XFS, for 2.6.38-rc3
(if it's not too late) or 2.6.38-rc4.

They are all fixes for bugs that have some pretty undesirable
consequences. They address:
- One spot in which a hang can occur due to neglecting to drop a
- A bug which in some cases a bogus block number can be recorded in
a block map btree, resulting in a subsequent BUG_ON().
- Two memory leaks
- Three places in which extent sizes are allowed to exceed various
size limits
- One place where code depends on behavior that is not well-defined
by the C standard
- One problem in handling transaction commit errors

Thank you.


The following changes since commit 70d1f365568e0cdbc9f4ab92428e1830fdb09ab0:

Merge branch 'for-linus' of git://git.infradead.org/ubi-2.6 (2011-01-31 13:04:51 +1000)

are available in the git repository at:

git://oss.sgi.com/xfs/xfs for-linus

Dave Chinner (8):
xfs: fix log ticket leak on forced shutdown.
xfs: fix efi item leak on forced shutdown
xfs: speculative delayed allocation uses rounddown_power_of_2 badly
xfs: limit extent length for allocation to AG size
xfs: prevent extsize alignment from exceeding maximum extent size
xfs: limit extsize to size of AGs and/or MAXEXTLEN
xfs: handle CIl transaction commit failures correctly
xfs: fix dquot shaker deadlock

bpm@xxxxxxx (1):
xfs: xfs_bmap_add_extent_delay_real should init br_startblock

fs/xfs/linux-2.6/xfs_ioctl.c | 20 ++++++++++++-
fs/xfs/quota/xfs_qm.c | 46 ++++++++++++++-----------------
fs/xfs/xfs_alloc.h | 16 +++++++++++
fs/xfs/xfs_bmap.c | 61 +++++++++++++++++++++++++++++++-----------
fs/xfs/xfs_buf_item.c | 12 +++++---
fs/xfs/xfs_extfree_item.c | 3 +-
fs/xfs/xfs_iomap.c | 7 ++++-
fs/xfs/xfs_log.h | 2 +-
fs/xfs/xfs_log_cil.c | 15 ++++------
fs/xfs/xfs_trans.c | 41 ++++++++++++++++++++-------
10 files changed, 152 insertions(+), 71 deletions(-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/