[GIT PULL] XFS updates (#2) for 3.10-rc1

From: Ben Myers
Date: Thu May 09 2013 - 15:23:48 EST


Hi Linus,

Please pull these three stragglers for 3.10-rc1. CONFIG_XFS_WARN will be
helpful in environments which are having trouble, and where full
CONFIG_XFS_DEBUG isn't appropriate. There are two fixes for issues with
extended attribtues seen with xfsdump.

Thanks,
Ben

The following changes since commit cab09a81fbefcb21db5213a84461d421946f6eb8:

xfs: fix da node magic number mismatches (2013-05-01 14:48:30 -0500)

are available in the git repository at:

git://oss.sgi.com/xfs/xfs tags/for-linus-v3.10-rc1-2

for you to fetch changes up to 7dfbcbefad4b24d9822d04dbd7b5dd5c3fd45076:

xfs: fallback to vmalloc for large buffers in xfs_compat_attrlist_by_handle (2013-05-07 19:00:10 -0500)

----------------------------------------------------------------
xfs: update (#2) for v3.10-rc1

* add CONFIG_XFS_WARN, a step between zero debugging and CONFIG_XFS_DEBUG.
* fix attrmulti and attrlist to fall back to vmalloc when kmalloc fails.

----------------------------------------------------------------
Dave Chinner (1):
xfs: introduce CONFIG_XFS_WARN

Eric Sandeen (2):
xfs: fallback to vmalloc for large buffers in xfs_attrlist_by_handle
xfs: fallback to vmalloc for large buffers in xfs_compat_attrlist_by_handle

fs/xfs/Kconfig | 13 +++++++++++++
fs/xfs/mrlock.h | 12 ++++++------
fs/xfs/xfs.h | 5 +++++
fs/xfs/xfs_alloc_btree.c | 4 ++--
fs/xfs/xfs_bmap_btree.c | 4 ++--
fs/xfs/xfs_btree.h | 2 +-
fs/xfs/xfs_dir2_node.c | 4 ++--
fs/xfs/xfs_ialloc_btree.c | 4 ++--
fs/xfs/xfs_inode.c | 2 +-
fs/xfs/xfs_ioctl.c | 14 ++++++++++----
fs/xfs/xfs_ioctl32.c | 14 ++++++++++----
fs/xfs/xfs_linux.h | 24 ++++++++++++++++++------
fs/xfs/xfs_message.c | 8 ++++++++
fs/xfs/xfs_message.h | 1 +
fs/xfs/xfs_trans.h | 4 ++--
15 files changed, 83 insertions(+), 32 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/