From: David Teigland <teigland@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, gfs2@lists.linux.dev
Subject: [GIT PULL] dlm updates for 6.18
Date: Mon, 29 Sep 2025 09:41:07 -0500 [thread overview]
Message-ID: <aNqag0RIXLcG5BH3@redhat.com> (raw)
Hi Linus,
Please pull dlm updates from tag:
git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git dlm-6.18
This set of patches add a dlm_release_lockspace() flag to request that
node-failure recovery be performed for the node leaving the lockspace.
The implementation of this flag requires coordination with userland
clustering components. It's been requested for use by GFS2.
Thanks,
Dave
Alexander Aring (9):
dlm: check for defined force value in dlm_lockspace_release
dlm: use defines for force values in dlm_release_lockspace
dlm: add new RELEASE_RECOVER uevent attribute for release_lockspace
dlm: add new configfs entry release_recover for lockspace members
dlm: add new flag DLM_RELEASE_RECOVER for dlm_lockspace_release
dlm: handle invalid lockspace member remove
dlm: move to rinfo for all middle conversion cases
dlm: handle release_option as unsigned
dlm: check for undefined release_option values
drivers/md/md-cluster.c | 4 ++--
fs/dlm/config.c | 64 +++++++++++++++++++++++++++++++++++++++++++++++--
fs/dlm/config.h | 2 ++
fs/dlm/lock.c | 2 +-
fs/dlm/lockspace.c | 46 +++++++++++++++++++----------------
fs/dlm/member.c | 27 ++++++++++++++++-----
fs/dlm/recover.c | 2 +-
fs/dlm/user.c | 6 ++---
fs/gfs2/lock_dlm.c | 4 ++--
fs/ocfs2/stack_user.c | 2 +-
include/linux/dlm.h | 33 ++++++++++++++++++++++++-
11 files changed, 153 insertions(+), 39 deletions(-)
next reply other threads:[~2025-09-29 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 14:41 David Teigland [this message]
2025-09-29 23:22 ` [GIT PULL] dlm updates for 6.18 pr-tracker-bot
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=aNqag0RIXLcG5BH3@redhat.com \
--to=teigland@redhat.com \
--cc=gfs2@lists.linux.dev \
--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