From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Pull request #2 (merge window)
Date: Fri, 13 Jan 2012 10:04:35 +0000 [thread overview]
Message-ID: <1326449075.2685.9.camel@menhir> (raw)
Hi,
Please consider pulling the following changes. All except one of these
patches is actually a bug fix rather than specifically merge window
material. That remaining patch applies on top of the DLM patches which
were merged in the current window,
Steve.
----------------------------------------------------------------------------
The following changes since commit e343a895a9f342f239c5e3c5ffc6c0b1707e6244:
Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost (2012-01-10 18:04:27 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-3.0-nmw.git master
Bob Peterson (1):
GFS2: Fix a use-after-free that coverity spotted
David Teigland (3):
GFS2: dlm based recovery coordination
GFS2: let spectator mount do read only recovery
GFS2: fail mount if journal recovery fails
Steven Whitehouse (1):
GFS2: Fix nlink setting on inode creation
fs/gfs2/glock.c | 2 +-
fs/gfs2/glock.h | 7 +-
fs/gfs2/incore.h | 60 +++-
fs/gfs2/inode.c | 4 +-
fs/gfs2/lock_dlm.c | 993 ++++++++++++++++++++++++++++++++++++++++++-
fs/gfs2/main.c | 10 +
fs/gfs2/ops_fstype.c | 31 +-
fs/gfs2/recovery.c | 11 +-
fs/gfs2/rgrp.c | 2 +-
fs/gfs2/sys.c | 33 +-
fs/gfs2/sys.h | 2 +
include/linux/gfs2_ondisk.h | 2 +
12 files changed, 1108 insertions(+), 49 deletions(-)
next reply other threads:[~2012-01-13 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 10:04 Steven Whitehouse [this message]
[not found] <1349891308.18959471.1523559205878.JavaMail.zimbra@redhat.com>
2018-04-12 18:53 ` [Cluster-devel] GFS2: Pull request #2 (merge window) Bob Peterson
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=1326449075.2685.9.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 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).