From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Pre-pull patch posting
Date: Thu, 3 Jan 2013 11:50:06 +0000 [thread overview]
Message-ID: <1357213810-3739-1-git-send-email-swhiteho@redhat.com> (raw)
Hi,
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,
Steve.
next reply other threads:[~2013-01-03 11:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 11:50 Steven Whitehouse [this message]
2013-01-03 11:50 ` [Cluster-devel] [PATCH 1/4] GFS2: Initialize hex string to '0' Steven Whitehouse
2013-01-03 11:50 ` [Cluster-devel] [PATCH 2/4] GFS2: Fix race in gfs2_rs_alloc Steven Whitehouse
2013-01-03 11:50 ` [Cluster-devel] [PATCH 3/4] GFS2: Stop looking for free blocks at end of rgrp Steven Whitehouse
2013-01-03 11:50 ` [Cluster-devel] [PATCH 4/4] GFS2: Reset rd_last_alloc when it reaches the end of the rgrp Steven Whitehouse
-- strict thread matches above, loose matches on Subject: below --
2015-02-10 10:36 [Cluster-devel] GFS2: Pre-pull patch posting Steven Whitehouse
2013-04-05 9:57 Steven Whitehouse
2010-10-18 14:15 Steven Whitehouse
2010-08-02 9:27 Steven Whitehouse
2010-05-17 12:40 Steven Whitehouse
2010-03-11 17:21 Steven Whitehouse
2010-03-01 15:08 Steven Whitehouse
2009-09-10 11:27 Steven Whitehouse
2009-06-10 8:30 Steven Whitehouse
2009-03-18 12:23 [Cluster-devel] [GFS2] " swhiteho
2008-12-17 11:29 [Cluster-devel] GFS2: " swhiteho
2008-09-26 12:00 Steven Whitehouse
2008-07-11 10:11 [Cluster-devel] [GFS2] " swhiteho
2008-04-17 8:37 swhiteho
2008-01-21 9:21 swhiteho
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=1357213810-3739-1-git-send-email-swhiteho@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).