From: David Teigland <teigland@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: gfs2@lists.linux.dev
Subject: [GIT PULL] dlm updates for 7.2
Date: Mon, 15 Jun 2026 11:43:41 -0500 [thread overview]
Message-ID: <ajArvSdW8Js7l72b@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.2
There are four fixes/cleanups in this series; none are likely to be issues
in real usage:
- improve debugfs error exit path
- fix sequence number ordering in an artificial test case
- fix usercopy_abort for lvb data
- use hlist_for_each_entry_srcu for srcu lists
Thanks,
Dave
Alexander Aring (2):
dlm: fix add msg handle in send_queue ordered
dlm: init per node debugfs before add to node hash
Li RongQing (1):
dlm: use hlist_for_each_entry_srcu for SRCU protected lists
Ziyi Guo (1):
dlm: add usercopy whitelist to dlm_cb cache
fs/dlm/lowcomms.c | 12 ++++++++----
fs/dlm/memory.c | 4 +++-
fs/dlm/midcomms.c | 21 +++++++++++++--------
3 files changed, 24 insertions(+), 13 deletions(-)
next reply other threads:[~2026-06-15 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 16:43 David Teigland [this message]
2026-06-16 7:08 ` [GIT PULL] dlm updates for 7.2 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=ajArvSdW8Js7l72b@redhat.com \
--to=teigland@redhat.com \
--cc=gfs2@lists.linux.dev \
--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