linux-kernel - [PATCH 0/8] dlm and gfs2 patches for 3.5

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:	Mon, 21 May 2012 16:18:32 -0500
From:	David Teigland <teigland@...hat.com>
To:	linux-kernel@...r.kernel.org
Subject: [PATCH 0/8] dlm and gfs2 patches for 3.5


These are dlm and gfs2 patches from -next for 3.5.  The one large patch
fixes various problems with the "nodir" mode, in which the dlm operates
without a resource directory (a long neglected feature).  Other patches
are all minor fixes and improvements.

Dan Carpenter (1):
      dlm: NULL dereference on failure in kmem_cache_create()

David Teigland (7):
      dlm: prevent connections during shutdown
      dlm: fix waiter recovery
      dlm: limit rcom debug messages
      dlm: avoid unnecessary search in search_rsb
      dlm: improve error and debug messages
      dlm: fixes for nodir mode
      gfs2: fix recovery during unmount

 fs/dlm/ast.c          |    3 +-
 fs/dlm/dlm_internal.h |   16 +-
 fs/dlm/lock.c         |  541 +++++++++++++++++++++++++++++++++----------------
 fs/dlm/lock.h         |    7 +-
 fs/dlm/lockspace.c    |   20 ++
 fs/dlm/lowcomms.c     |   28 ++-
 fs/dlm/memory.c       |    8 +-
 fs/dlm/rcom.c         |   61 +++---
 fs/dlm/recover.c      |   73 ++++---
 fs/dlm/recoverd.c     |   15 +-
 fs/dlm/requestqueue.c |   43 ++--
 fs/gfs2/incore.h      |    1 -
 fs/gfs2/lock_dlm.c    |    2 -
 fs/gfs2/ops_fstype.c  |    7 +-
 fs/gfs2/sys.c         |   10 +-
 include/linux/dlm.h   |    1 -
 16 files changed, 538 insertions(+), 298 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/