All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Pull request (fixes)
Date: Tue, 04 Jun 2013 16:40:41 +0100	[thread overview]
Message-ID: <1370360441.2705.10.camel@menhir> (raw)

Hi,

Please consider pulling the following fixes for GFS2,

Steve.

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

There are four patches this time. The first fixes a problem where the
wrong descriptor type was being written into the log for journaled data
blocks. The second fixes a race relating to the deallocation of allocator
data. The third provides a fallback if kmalloc is unable to satisfy a
request to allocate a directory hash table. The fourth fixes the iopen
glock caching so that inodes are deleted in a more timely manner after
rmdir/unlink.

-----------------------------------------------------------------------------
The following changes since commit aa4f608478acb7ed69dfcff4f3c404100b78ac49:

  Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k (2013-06-03 18:09:42 +0900)

are available in the git repository at:

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

Bob Peterson (4):
      GFS2: Set log descriptor type for jdata blocks
      GFS2: Increase i_writecount during gfs2_setattr_size
      GFS2: Fall back to vmalloc if kmalloc fails for dir hash tables
      GFS2: Don't cache iopen glocks

 fs/gfs2/bmap.c  |   17 +++++++++++++----
 fs/gfs2/dir.c   |   43 +++++++++++++++++++++++++++++++++----------
 fs/gfs2/file.c  |   19 +++++++++++++------
 fs/gfs2/inode.c |    1 +
 fs/gfs2/lops.c  |    4 +++-
 fs/gfs2/rgrp.c  |    4 +++-
 fs/gfs2/super.c |    6 +++++-
 7 files changed, 71 insertions(+), 23 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/20130604/6d1cc8f2/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Steven Whitehouse <swhiteho@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, cluster-devel@redhat.com
Subject: GFS2: Pull request (fixes)
Date: Tue, 04 Jun 2013 16:40:41 +0100	[thread overview]
Message-ID: <1370360441.2705.10.camel@menhir> (raw)

[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]

Hi,

Please consider pulling the following fixes for GFS2,

Steve.

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

There are four patches this time. The first fixes a problem where the
wrong descriptor type was being written into the log for journaled data
blocks. The second fixes a race relating to the deallocation of allocator
data. The third provides a fallback if kmalloc is unable to satisfy a
request to allocate a directory hash table. The fourth fixes the iopen
glock caching so that inodes are deleted in a more timely manner after
rmdir/unlink.

-----------------------------------------------------------------------------
The following changes since commit aa4f608478acb7ed69dfcff4f3c404100b78ac49:

  Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k (2013-06-03 18:09:42 +0900)

are available in the git repository at:

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

Bob Peterson (4):
      GFS2: Set log descriptor type for jdata blocks
      GFS2: Increase i_writecount during gfs2_setattr_size
      GFS2: Fall back to vmalloc if kmalloc fails for dir hash tables
      GFS2: Don't cache iopen glocks

 fs/gfs2/bmap.c  |   17 +++++++++++++----
 fs/gfs2/dir.c   |   43 +++++++++++++++++++++++++++++++++----------
 fs/gfs2/file.c  |   19 +++++++++++++------
 fs/gfs2/inode.c |    1 +
 fs/gfs2/lops.c  |    4 +++-
 fs/gfs2/rgrp.c  |    4 +++-
 fs/gfs2/super.c |    6 +++++-
 7 files changed, 71 insertions(+), 23 deletions(-)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-06-04 15:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04 15:40 Steven Whitehouse [this message]
2013-06-04 15:40 ` GFS2: Pull request (fixes) Steven Whitehouse
  -- strict thread matches above, loose matches on Subject: below --
2014-09-16 10:11 [Cluster-devel] " Steven Whitehouse
2014-07-18 11:21 Steven Whitehouse
2014-01-02 12:41 Steven Whitehouse
2013-11-22 10:39 Steven Whitehouse
2013-08-19  9:26 Steven Whitehouse
2013-08-19 16:33 ` Linus Torvalds
2013-08-19  9:24 Steven Whitehouse
2013-05-24 14:05 Steven Whitehouse
2013-04-05 10:34 Steven Whitehouse
2013-04-05 16:27 ` David Teigland
2013-04-05 16:51   ` Steven Whitehouse
2013-04-05 16:53   ` Linus Torvalds
2013-04-05 17:52     ` Steven Whitehouse
2013-01-28 10:31 Steven Whitehouse
2013-01-03 12:28 Steven Whitehouse
2012-11-07 10:58 Steven Whitehouse
2012-09-13 13:42 Steven Whitehouse
2012-04-11 10:21 Steven Whitehouse
2012-04-11 10:18 Steven Whitehouse
2012-02-28 11:49 Steven Whitehouse
2011-07-27 10:00 Steven Whitehouse
2011-07-14 15:16 Steven Whitehouse
2011-05-23 14:05 Steven Whitehouse
2011-04-19  9:13 Steven Whitehouse
2011-01-19 10:50 Steven Whitehouse
2010-11-29 13:42 Steven Whitehouse
2010-11-15 15:41 Steven Whitehouse
2010-09-17 13:59 Steven Whitehouse
2010-07-15 14:35 Steven Whitehouse
2010-05-25  8:51 Steven Whitehouse
2010-03-11 17:41 Steven Whitehouse
2010-02-12 11:37 Steven Whitehouse
2010-02-04 10:06 Steven Whitehouse
2010-02-02 10:07 [Cluster-devel] [GFS2] " Steven Whitehouse
2010-01-11 14:24 [Cluster-devel] GFS2: " Steven Whitehouse
2009-08-14 13:01 Steven Whitehouse
2009-07-30 13:45 [Cluster-devel] GFS2: Pre-pull patch posting (fixes) Steven Whitehouse
2009-07-30 13:02 ` [Cluster-devel] GFS2: Pull request (fixes) Steven Whitehouse
2009-04-23 13:13 Steven Whitehouse
2009-01-07 10:21 Steven Whitehouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1370360441.2705.10.camel@menhir \
    --to=swhiteho@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.