linux-kernel - [GIT PULL] dlm updates for 2.6.40

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Tue, 24 May 2011 15:53:56 -0400
From:	David Teigland <teigland@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: [GIT PULL] dlm updates for 2.6.40

Linus,

Please pull dlm updates for 2.6.40 from:

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

The most useful patch makes posix lock operations (from gfs2/ocfs2)
interruptible using the helpful wait_event_killable.  This is followed by
a new timer that can be set to warn when locks have been waiting for a
reply message for a configured time.  People debugging lost dlm messages
have been asking for this.
Thanks,
Dave

David Teigland (3):
      dlm: delayed reply message warning
      dlm: remove shared message stub for recovery
      dlm: make plock operation killable

Matt Fleming (1):
      dlm: Remove superfluous call to recalc_sigpending()

 fs/dlm/config.c           |    9 ++-
 fs/dlm/config.h           |    1 +
 fs/dlm/dlm_internal.h     |    3 +
 fs/dlm/lock.c             |  182 +++++++++++++++++++++++++++++++++++----------
 fs/dlm/lock.h             |    1 +
 fs/dlm/lockspace.c        |    6 +-
 fs/dlm/plock.c            |   65 +++++++++++++++-
 fs/dlm/user.c             |    1 -
 include/linux/dlm_plock.h |    6 +-
 9 files changed, 223 insertions(+), 51 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/