gfs2 filesystem and dlm development
 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 dlm/next 0/8] dlm: pending fixes based on v7.3-rc1
Date: Tue,  1 Sep 2026 13:47:07 -0400	[thread overview]
Message-ID: <20260901174715.3825582-1-aahringo@redhat.com> (raw)

Hi David,

this patch series contains pending fixed for dlm.

Some critical to be ensure that monitor/plock chardevs are only be
opened under administrator rights which should be as e.g. dlm_controld
is using them running as root and can conflict with additional multiple
usages. To forbid any misusage we forbid to open those devices for
normal users.

Then we switch back to rhashtables to dynamic key lengths as this might
get conflicts for DLM users who actually using different resource name
lengths in DLM.

Additional malformed packets drops to avoid kernel crashes, however we
still cannot recover from those drops but this is another problem.

Then there are missing barriers for srcu as call_srcu() uses the srcu
static structures which can end in an use after free when the module is
removed.

- Alex

Alexander Aring (1):
  dlm: fix variable key length lookup

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

Joseph Qi (1):
  dlm: fix buffer overflow from negative len in dlm_search_rsb_tree

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/config.c       | 30 ++++++++++++++++++++++++++++--
 fs/dlm/dlm_internal.h |  5 +++++
 fs/dlm/lock.c         | 18 +++++++++++++-----
 fs/dlm/lock.h         |  4 ++--
 fs/dlm/lowcomms.c     |  1 +
 fs/dlm/midcomms.c     |  1 +
 fs/dlm/plock.c        | 14 +++++++++++++-
 fs/dlm/user.c         | 23 +++++++++++++++++++++++
 8 files changed, 86 insertions(+), 10 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-09-01 17:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 17:47 Alexander Aring [this message]
2026-09-01 17:47 ` [PATCH RESEND dlm/next 1/8] dlm: gate dlm_plock device on CAP_SYS_ADMIN Alexander Aring
2026-09-01 17:47 ` [PATCH RESEND dlm/next 2/8] dlm: require CAP_SYS_ADMIN for dlm-monitor device Alexander Aring
2026-09-01 17:47 ` [PATCH RESEND dlm/next 3/8] dlm: validate userspace lock resource name length Alexander Aring
2026-09-01 17:47 ` [PATCH RESEND dlm/next 4/8] dlm: fix buffer overflow from negative len in dlm_search_rsb_tree Alexander Aring
2026-09-01 17:47 ` [PATCH RESEND dlm/next 5/8] dlm: validate lock modes in recovery messages Alexander Aring
2026-09-01 17:47 ` [PATCH RESEND dlm/next 6/8] dlm: fix NULL pointer dereference in dlm_dump_rsb_name() Alexander Aring
2026-09-01 17:47 ` [PATCH RESEND dlm/next 7/8] dlm: wait for outstanding SRCU callbacks to complete in exit paths Alexander Aring
2026-09-01 17:47 ` [PATCH RESEND dlm/next 8/8] dlm: fix variable key length lookup 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=20260901174715.3825582-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