From: Joel Becker <jlbec@evilplan.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] ocfs2 and configfs fixes for 2.6.39-rc
Date: Wed, 18 May 2011 14:07:19 -0700 [thread overview]
Message-ID: <20110518210719.GE5898@noexit.corp.google.com> (raw)
Linus et al,
Here are the last ocfs2 and configfs fixes for 2.6.39-rc.
These include a configfs crash and a compatibility regression in the
ocfs2 internal DLM.
Please pull.
The following changes since commit 446cc6345d3de6571bdd0840f48aca441488a28d:
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs (2011-05-12 18:00:09 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlbec/ocfs2.git fixes
Joel Becker (2):
configfs: Don't try to d_delete() negative dentries.
configfs: Fix race between configfs_readdir() and configfs_d_iput()
Marcus Meissner (1):
ocfs2: Initialize data_ac (might be used uninitialized)
Sunil Mushran (5):
ocfs2/dlm: Use negotiated o2dlm protocol version
ocfs2/cluster: Increase the live threshold for global heartbeat
ocfs2/cluster: Heartbeat mismatch message improved
ocfs2: Skip mount recovery for hard-ro mounts
ocfs2/dlm: Target node death during resource migration leads to thread spin
Tristan Ye (1):
ocfs2: skip existing hole when removing the last extent_rec in punching-hole codes.
fs/configfs/dir.c | 39 ++++++++++++++++++++++-----
fs/ocfs2/cluster/heartbeat.c | 61 +++++++++++++++++++++++++++++------------
fs/ocfs2/dir.c | 2 +-
fs/ocfs2/dlm/dlmdomain.c | 3 +-
fs/ocfs2/dlm/dlmmaster.c | 3 ++
fs/ocfs2/file.c | 12 ++++++++
fs/ocfs2/journal.c | 3 ++
7 files changed, 96 insertions(+), 27 deletions(-)
reply other threads:[~2011-05-18 21:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110518210719.GE5898@noexit.corp.google.com \
--to=jlbec@evilplan.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=torvalds@linux-foundation.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