[Cluster-devel] GFS2: Pull request (fixes)

Steven Whitehouse <[email protected]>
Newsgroups com.redhat.cluster-devel,org.kernel.vger.linux-kernel
Message-ID <1352285889.2729.12.camel@menhir>
Hi,

Please consider pulling the following GFS2 fixes,

Steve.

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

Here are a number of GFS2 bug fixes. There are three from Andy Price
which fix various issues spotted by automated code analysis. There are two
from Lukas Czerner fixing my mistaken assumptions as to how FITRIM
should work. Finally Ben Marzinski has fixed a bug relating to mmap and
atime and also a bug relating to a locking issue in the transaction code.


The following changes since commit ddffeb8c4d0331609ef2581d84de4d763607bd37:

  Linux 3.7-rc1 (2012-10-14 14:41:04 -0700)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-3.0-fixes.git master

Andrew Price (3):
      GFS2: Fix an unchecked error from gfs2_rs_alloc
      GFS2: Fix possible null pointer deref in gfs2_rs_alloc
      GFS2: Clean up some unused assignments

Benjamin Marzinski (2):
      GFS2: Don't call file_accessed() with a shared glock
      GFS2: Test bufdata with buffer locked and gfs2_log_lock held

Lukas Czerner (2):
      GFS2: Require user to provide argument for FITRIM
      GFS2: Fix FITRIM argument handling

 fs/gfs2/file.c  |   14 +++++---------
 fs/gfs2/lops.c  |   16 ++--------------
 fs/gfs2/quota.c |    7 +++++--
 fs/gfs2/rgrp.c  |   33 +++++++++++++++++++++------------
 fs/gfs2/super.c |    3 ++-
 fs/gfs2/trans.c |    8 ++++++++
 6 files changed, 43 insertions(+), 38 deletions(-)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20121107/9b78f3e0/attachment.sig>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.