[GIT PULL] nilfs2 fixes for 2.6.30-rc6

[Ryusuke Konishi]

Hi Linus,

please pull nilfs2 bug-fixes from

 git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git for-linus

The following changes since commit 091bf7624d1c90cec9e578a18529f615213ff847
 Linus Torvalds (1):
      Linux 2.6.30-rc5

Ryusuke Konishi (6):
      nilfs2: fix possible recovery failure due to block creation without writer
      nilfs2: fix circular locking dependency of writer mutex
      nilfs2: ensure to clear dirty state when deleting metadata file block
      nilfs2: fix possible circular locking for get information ioctls
      nilfs2: fix lock order reversal in nilfs_clean_segments ioctl
      nilfs2: check size of array structured data exchanged via ioctls

 fs/nilfs2/ioctl.c    |  281 ++++++++++++++++++++++++++------------------------
 fs/nilfs2/mdt.c      |   15 ++--
 fs/nilfs2/nilfs.h    |    3 +-
 fs/nilfs2/page.c     |    3 +-
 fs/nilfs2/recovery.c |    6 +-
 fs/nilfs2/segment.c  |    5 +-
 fs/nilfs2/segment.h  |    3 +-
 7 files changed, 167 insertions(+), 149 deletions(-)
-

The "nilfs2: check size of array structured data exchanged via ioctls"
adds missing sanity checks to ioctls.  These checks are needed to
prevent memory access overrun in kernel code due to incorrect
argument data.

The "nilfs2: ensure to clear dirty state when deleting metadata file
block" fixes user-reported GC failures.

The "nilfs2: fix possible recovery failure due to block creation
without writer" fixes recovery failure on mount which can happen in a
boundary condition.

The "nilfs2: fix circular locking dependency of writer mutex",
    "nilfs2: fix possible circular locking for get information ioctls", and
    "nilfs2: fix lock order reversal in nilfs_clean_segments ioctl"
fix circular locking problems and lock order reversal the lockdep
check has detected.

Thanks,
Ryusuke Konishi
--
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/