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.11
Date: Mon, 15 Jul 2024 11:55:12 -0500 [thread overview]
Message-ID: <ZpVUcCId-3JUmz03@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.11
Note, this set includes a patch touching drivers/md/md-cluster.c, acked
by the md-cluster developers, making use of the new DLM_LSFL_SOFTIRQ_SAFE
flag. Overall, changes include:
- New flag DLM_LSFL_SOFTIRQ_SAFE can be set by code using dlm
to indicate callbacks can be run from softirq.
- Change md-cluster to set DLM_LSFL_SOFTIRQ_SAFE.
- Clean up for previous changes, e.g. unused code and parameters.
- Remove custom pre-allocation of rsb structs which is unnecessary
with kmem caches.
- Change idr to xarray for lkb structs in use.
- Change idr to xarray for rsb structs being recovered.
- Change outdated naming related to internal rsb states.
- Fix some incorrect add/remove of rsb on scan list.
- Use rcu to free rsb structs.
Thanks,
Dave
Alexander Aring (14):
dlm: remove scand leftovers
dlm: don't kref_init rsbs created for toss list
dlm: remove unused parameter in dlm_midcomms_addr
dlm: remove ls_local_handle from struct dlm_ls
dlm: drop own rsb pre allocation mechanism
dlm: move lkb idr to xarray datastructure
dlm: move recover idr to xarray datastructure
dlm: use rcu to avoid an extra rsb struct lookup
dlm: use LSFL_FS to check for kernel lockspace
dlm: introduce DLM_LSFL_SOFTIRQ_SAFE
dlm: implement LSFL_SOFTIRQ_SAFE
md-cluster: use DLM_LSFL_SOFTIRQ for dlm_new_lockspace()
dlm: remove DLM_LSFL_SOFTIRQ from exflags
dlm: add rcu_barrier before destroy kmem cache
David Teigland (2):
dlm: change list and timer names
dlm: fix add_scan and del_scan usage
Dr. David Alan Gilbert (1):
fs: dlm: remove unused struct 'dlm_processed_nodes'
drivers/md/md-cluster.c | 2 +-
fs/dlm/ast.c | 170 +++++++++-----
fs/dlm/ast.h | 11 +-
fs/dlm/config.c | 2 +-
fs/dlm/debug_fs.c | 10 +-
fs/dlm/dlm_internal.h | 60 ++---
fs/dlm/lock.c | 568 +++++++++++++++++++++++------------------------
fs/dlm/lock.h | 7 +-
fs/dlm/lockspace.c | 131 +++++------
fs/dlm/lowcomms.c | 8 +-
fs/dlm/lowcomms.h | 2 +-
fs/dlm/member.c | 2 +-
fs/dlm/memory.c | 10 +-
fs/dlm/midcomms.c | 4 +-
fs/dlm/midcomms.h | 2 +-
fs/dlm/recover.c | 78 +++----
fs/dlm/recover.h | 2 +-
fs/dlm/recoverd.c | 14 +-
fs/dlm/user.c | 42 ++--
include/linux/dlm.h | 17 +-
include/uapi/linux/dlm.h | 2 +
21 files changed, 583 insertions(+), 561 deletions(-)
next reply other threads:[~2024-07-15 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 16:55 David Teigland [this message]
2024-07-17 20:18 ` [GIT PULL] dlm updates for 6.11 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=ZpVUcCId-3JUmz03@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