public inbox for gfs2@lists.linux.dev
 help / color / mirror / Atom feed
From: Alexander Aring <aahringo@redhat.com>
To: teigland@redhat.com
Cc: aahringo@redhat.com, gfs2@lists.linux.dev
Subject: [PATCH RESEND v7.1-rc1 0/4] dlm: pending DLM patches
Date: Mon, 27 Apr 2026 11:59:31 -0400	[thread overview]
Message-ID: <20260427155935.2415989-1-aahringo@redhat.com> (raw)

Hi David,

here are the pending DLM patches for dlm/next.

- using srcu list iterations to be aligned with lockdep
- fixing an issue with hardened kernel and lvb bytearray
  in dlm_callback that is copied to user address space
- fixing an issue with concurrent DLM requests and the
  midcomms sendqueue is out of order that ends in ref
  counting issues
- cleanup midcomms node creation by moving debugfs
  assignment before adding it to the node hash to
  avoid issues that debugfs is not initialiazed if
  concurrent users iterate over the hash.

- Alex

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(-)

-- 
2.43.0


             reply	other threads:[~2026-04-27 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 15:59 Alexander Aring [this message]
2026-04-27 15:59 ` [PATCH RESEND v7.1-rc1 1/4] dlm: use hlist_for_each_entry_srcu for SRCU protected lists Alexander Aring
2026-04-27 15:59 ` [PATCH RESEND v7.1-rc1 2/4] dlm: add usercopy whitelist to dlm_cb cache Alexander Aring
2026-04-27 15:59 ` [PATCH RESEND v7.1-rc1 3/4] dlm: fix add msg handle in send_queue ordered Alexander Aring
2026-04-27 15:59 ` [PATCH RESEND v7.1-rc1 4/4] dlm: init per node debugfs before add to node hash Alexander Aring

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=20260427155935.2415989-1-aahringo@redhat.com \
    --to=aahringo@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --cc=teigland@redhat.com \
    /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