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 7.4
Date: Mon, 19 Oct 2026 15:16:48 -0500 [thread overview]
Message-ID: <atZ6sKjlr3SxThCU@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-7.4
This set contains several fixes for bugs found by static analysis,
fuzzing and code review. They mostly involve invalid input, e.g. from
userspace, configfs or remote nodes, and are unlikely to be seen in
normal usage.
Thanks,
Dave
Alexander Aring (1):
dlm: fix variable key length lookup
Dan Carpenter (1):
dlm: clean up a type in waiters_read()
Danila Chernetsov (2):
dlm: validate lock modes in recovery messages
dlm: fix NULL pointer dereference in dlm_dump_rsb_name()
Haofeng Li (2):
dlm: gate dlm_plock device on CAP_SYS_ADMIN
dlm: require CAP_SYS_ADMIN for dlm-monitor device
Hemanth Selam (1):
dlm: fix typos in comments
Joseph Qi (1):
dlm: fix buffer overflow from negative len in dlm_search_rsb_tree
Qing Ming (1):
dlm: validate node weights before building member array
Samuel Moelius (1):
dlm: validate userspace lock resource name length
Zqiang (1):
dlm: wait for outstanding SRCU callbacks to complete in exit paths
fs/dlm/ast.c | 2 +-
fs/dlm/config.c | 39 ++++++++++++++++++++++++++++++++++++---
fs/dlm/debug_fs.c | 3 ++-
fs/dlm/dlm_internal.h | 5 +++++
fs/dlm/lock.c | 20 ++++++++++++++------
fs/dlm/lock.h | 4 ++--
fs/dlm/lowcomms.c | 1 +
fs/dlm/member.c | 17 +++++++++++------
fs/dlm/midcomms.c | 1 +
fs/dlm/plock.c | 14 +++++++++++++-
fs/dlm/user.c | 23 +++++++++++++++++++++++
11 files changed, 109 insertions(+), 20 deletions(-)
reply other threads:[~2026-10-19 20:16 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=atZ6sKjlr3SxThCU@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
all inboxes | Powered by JetHome®