From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Pull request (fixes)
Date: Thu, 03 Jan 2013 12:28:40 +0000 [thread overview]
Message-ID: <1357216120.2696.22.camel@menhir> (raw)
Hi,
Please consider pulling the following GFS2 fixes,
Steve.
---------------------------------------------------------------------------------------------------
Here are four small bug fixes for GFS2. There is no common theme here
really, just a few items that were fixed recently. The first fixes
lock name generation when the glock number is 0. The second fixes a
race allocating reservation structures and the final two fix a performance
issue by making small changes in the allocation code.
---------------------------------------------------------------------------------------------------
The following changes since commit 4a490b78cb7e0e5efa44425df72a9fedc1c36366:
Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux (2012-12-30 10:00:37 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-3.0-fixes.git master
Abhijith Das (1):
GFS2: Fix race in gfs2_rs_alloc
Bob Peterson (2):
GFS2: Stop looking for free blocks at end of rgrp
GFS2: Reset rd_last_alloc when it reaches the end of the rgrp
Nathan Straz (1):
GFS2: Initialize hex string to '0'
fs/gfs2/lock_dlm.c | 1 +
fs/gfs2/rgrp.c | 35 ++++++++++++++++++++---------------
2 files changed, 21 insertions(+), 15 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/20130103/3bdd349b/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Steven Whitehouse <swhiteho@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: GFS2: Pull request (fixes)
Date: Thu, 03 Jan 2013 12:28:40 +0000 [thread overview]
Message-ID: <1357216120.2696.22.camel@menhir> (raw)
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
Hi,
Please consider pulling the following GFS2 fixes,
Steve.
---------------------------------------------------------------------------------------------------
Here are four small bug fixes for GFS2. There is no common theme here
really, just a few items that were fixed recently. The first fixes
lock name generation when the glock number is 0. The second fixes a
race allocating reservation structures and the final two fix a performance
issue by making small changes in the allocation code.
---------------------------------------------------------------------------------------------------
The following changes since commit 4a490b78cb7e0e5efa44425df72a9fedc1c36366:
Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux (2012-12-30 10:00:37 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-3.0-fixes.git master
Abhijith Das (1):
GFS2: Fix race in gfs2_rs_alloc
Bob Peterson (2):
GFS2: Stop looking for free blocks at end of rgrp
GFS2: Reset rd_last_alloc when it reaches the end of the rgrp
Nathan Straz (1):
GFS2: Initialize hex string to '0'
fs/gfs2/lock_dlm.c | 1 +
fs/gfs2/rgrp.c | 35 ++++++++++++++++++++---------------
2 files changed, 21 insertions(+), 15 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-01-03 12:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 12:28 Steven Whitehouse [this message]
2013-01-03 12:28 ` 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-06-04 15:40 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
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=1357216120.2696.22.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.