linux-kernel - [GIT PULL] XFS update for 3.2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <20111207230819.37403426DA7@whiskey.americas.sgi.com>
Date:	Wed,  7 Dec 2011 17:08:19 -0600 (CST)
From:	bpm@....com (Ben Myers)
To:	torvalds@...ux-foundation.org
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	xfs@....sgi.com
Subject: [GIT PULL] XFS update for 3.2

Hi Linus,

Please pull the following fixes for XFS for 3.2.

a99ebf4 fixes an overflow when converting allocation length to extent length,

c29f7d4 fixes export of 64 bit inode numbers on 32 bit kernels, and

9f9c19e fixes a log hang due to a race when granting log space.  It was
debugged and tested thoroughly by Chandra Seetharaman <sekharan@...ibm.com>.

Thanks,
	Ben

The following changes since commit 77a7300abad7fe01891b400e88d746f97307ee5a:
  Anton Vorontsov (1):
        of/irq: Get rid of NO_IRQ usage

are available in the git repository at:

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

Christoph Hellwig (2):
      xfs: fix nfs export of 64-bit inodes numbers on 32-bit kernels
      xfs: fix the logspace waiting algorithm

Dave Chinner (1):
      xfs: fix allocation length overflow in xfs_bmapi_write()

 fs/xfs/xfs_bmap.c   |   20 +++-
 fs/xfs/xfs_export.c |    8 +-
 fs/xfs/xfs_log.c    |  348 +++++++++++++++++++++++++--------------------------
 fs/xfs/xfs_trace.h  |   12 +--
 4 files changed, 200 insertions(+), 188 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/