From: David Teigland <teigland@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] dlm patches for 2.6.30
Date: Tue, 24 Mar 2009 09:07:45 -0500 [thread overview]
Message-ID: <1237903672-18913-1-git-send-email-teigland@redhat.com> (raw)
Hi,
These are the pending dlm patches for the 2.6.30 merge. They have all been in
linux-next for quite a while. The notable fixes come from using the dlm with
ocfs2 and relate to handling lock cancelation and large nodeids.
Dave
fs/dlm/dir.c | 18 +++---
fs/dlm/dlm_internal.h | 2 +-
fs/dlm/lock.c | 60 ++++++++++++++--
fs/dlm/lockspace.c | 2 +-
fs/dlm/lowcomms.c | 181 ++++++++++++++++++++++++++-----------------------
fs/dlm/user.c | 24 ++++---
6 files changed, 175 insertions(+), 112 deletions(-)
Christine Caulfield (1):
dlm: replace idr with hash table for connections
David Teigland (3):
dlm: clear defunct cancel state
dlm: ignore cancel on granted lock
dlm: fix length calculation in compat code
Joe Perches (2):
dlm: use ipv6_addr_copy
dlm: comment typo fixes
Steven Whitehouse (1):
dlm: Change rwlock which is only used in write mode to a spinlock
reply other threads:[~2009-03-24 14:18 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=1237903672-18913-1-git-send-email-teigland@redhat.com \
--to=teigland@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
all inboxes | Powered by JetHome®