linux-kernel - GFS2: Pull request (fixes)

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 19 Apr 2011 10:13:11 +0100
From:	Steven Whitehouse <swhiteho@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	cluster-devel@...hat.com, linux-kernel@...r.kernel.org
Subject: GFS2: Pull request (fixes)

Hi,

Please consider pulling the following four GFS2 fixes,

Steve.

--------------------------------------------------------------------------------------

The following changes since commit a1b49cb7e2a7961ec3aa8b64860bf480d4ec9077:

  Merge branch 'i2c-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging (2011-04-17 17:37:02 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6-fixes.git master

Benjamin Marzinski (1):
      GFS2: directly write blocks past i_size

Bob Peterson (2):
      GFS2: write_end error path fails to unlock transaction lock
      GFS2: filesystem hang caused by incorrect lock order

Steven Whitehouse (1):
      GFS2: Don't try to deallocate unlinked inodes when mounted ro

 fs/gfs2/aops.c       |    2 +-
 fs/gfs2/dir.c        |    2 +-
 fs/gfs2/file.c       |   58 +++++++++++++++++++++++++++++++++++++++++--------
 fs/gfs2/glops.c      |    4 +++
 fs/gfs2/inode.c      |   56 +++++++++++++++++++++++++++++++++++-------------
 fs/gfs2/inode.h      |    3 +-
 fs/gfs2/ops_fstype.c |    2 +-
 fs/gfs2/rgrp.c       |    4 +-
 fs/gfs2/super.c      |   14 +++++++++--
 9 files changed, 111 insertions(+), 34 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/