From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: GFS2: Pre-pull patch posting (fixes)
Date: Tue, 25 May 2010 09:21:26 +0100 [thread overview]
Message-ID: <1274775689-4689-1-git-send-email-swhiteho@redhat.com> (raw)
Hi,
These are three important, but relatively small, bug fixes for GFS2.
The first prevents a kernel BUG triggering in a relatively unlikely
(but possible) scenario when a log flush caused by glock demotion
races with a log flush from some other initiator (e.g. fsync).
The second and third patches add extra conditions to two areas
of code. This makes their behaviour match ext3 in those cases,
Steve.
next reply other threads:[~2010-05-25 8:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 8:21 Steven Whitehouse [this message]
2010-05-25 8:21 ` [PATCH 1/3] GFS2: Rework reclaiming unlinked dinodes Steven Whitehouse
2010-05-25 8:21 ` [PATCH 2/3] GFS2: Don't "get" xattrs for ACLs when ACLs are turned off Steven Whitehouse
2010-05-25 8:21 ` [PATCH 3/3] GFS2: Fix permissions checking for setflags ioctl() Steven Whitehouse
2010-05-25 9:21 ` [Cluster-devel] [PATCH 1/3] GFS2: Rework reclaiming unlinked dinodes Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2014-09-15 9:32 GFS2: Pre-pull patch posting (fixes) Steven Whitehouse
2014-07-18 10:37 Steven Whitehouse
2014-01-02 12:28 Steven Whitehouse
2013-11-22 10:35 Steven Whitehouse
2013-08-19 8:48 Steven Whitehouse
2013-06-04 13:40 Steven Whitehouse
2013-05-24 13:37 Steven Whitehouse
2012-11-07 10:15 Steven Whitehouse
2012-09-13 9:42 Steven Whitehouse
2012-04-11 8:56 Steven Whitehouse
2012-02-28 11:11 Steven Whitehouse
2011-07-14 8:21 Steven Whitehouse
2011-05-23 12:39 Steven Whitehouse
2011-04-19 8:40 Steven Whitehouse
2010-07-15 13:57 Steven Whitehouse
2010-02-04 9:46 Steven Whitehouse
2010-01-11 9:11 Steven Whitehouse
2009-07-30 13:45 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=1274775689-4689-1-git-send-email-swhiteho@redhat.com \
--to=swhiteho@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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).