public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] dlm updates for 2.6.28
Date: Fri, 10 Oct 2008 12:52:49 -0500	[thread overview]
Message-ID: <20081010175249.GF4284@redhat.com> (raw)

Linus,

Please pull dlm updates for 2.6.28 from:

 git://git.kernel.org/pub/scm/linux/kernel/git/teigland/dlm.git for-linus

They have all been in linux-next for a long time.  There are two minor
enhancements in addition to the fixes.  The first allows a lockspace to be
created and used from both kernel and userspace threads at once.  This is to
support ocfs2 tools using the dlm along with the fs.  The second copies an
idea from ocfs2.  It allows the dlm to detect when the necessary userspace
control daemon fails, and to stop locking activity in response.

Thanks,
Dave


Andrew Morton (1):
      dlm: choose better identifiers

David Teigland (5):
      dlm: allow multiple lockspace creates
      dlm: detect available userspace daemon
      dlm: fix locking of lockspace list in dlm_scand
      dlm: fix address compare
      dlm: remove bkl


 fs/dlm/config.c             |   77 ++++++++++++++-------
 fs/dlm/dlm_internal.h       |    7 ++-
 fs/dlm/lockspace.c          |  158 ++++++++++++++++++++++++++++++++-----------
 fs/dlm/lockspace.h          |    1 +
 fs/dlm/user.c               |  124 +++++++++++++++++++++++++--------
 fs/dlm/user.h               |    4 +-
 fs/gfs2/locking/dlm/mount.c |    3 +-
 include/linux/dlm.h         |    5 +-
 include/linux/dlm_device.h  |    2 +-
 9 files changed, 281 insertions(+), 100 deletions(-)


                 reply	other threads:[~2008-10-10 18:06 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=20081010175249.GF4284@redhat.com \
    --to=teigland@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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