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.12
Date: Tue, 17 Sep 2024 12:05:50 -0500 [thread overview]
Message-ID: <Zum2QP7hS1mDzqBT@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.12
Summary:
- Remove some unnecesary hold/unhold rsb refcounting
in cases where an existing refcount is known to exist.
- Remove some unnecessary checking for zero nodeids, which
should never exist, and add some warning if they do.
- Make the slow freeing of structs in release_lockspace()
async, run from a workqueue.
- Prior rcu freeing allows some further struct lookups to
run without a lock.
- Use blocking kernel_connect on sockets to avoid EINPROGRESS.
Thanks,
Dave
Alexander Aring (11):
dlm: cleanup memory allocation helpers
dlm: remove unnecessary refcounts
dlm: never return invalid nodeid by dlm_our_nodeid()
dlm: warn about invalid nodeid comparsions
dlm: drop kobject release callback handling
dlm: async freeing of lockspace resources
dlm: use RSB_HASHED to avoid lookup twice
dlm: move dlm_search_rsb_tree() out of lock
dlm: move lkb xarray lookup out of lock
dlm: do synchronized socket connect call
dlm: add missing -ENOMEM if alloc_workqueue() fails
fs/dlm/config.c | 2 +-
fs/dlm/dlm_internal.h | 5 ++
fs/dlm/lock.c | 134 +++++++++++++++++++++++++++-----------------------
fs/dlm/lock.h | 2 +
fs/dlm/lockspace.c | 97 ++++++++++++++++++------------------
fs/dlm/lowcomms.c | 36 +-------------
fs/dlm/main.c | 12 +++++
fs/dlm/member.c | 2 +
fs/dlm/memory.c | 28 +++++------
fs/dlm/memory.h | 4 +-
fs/dlm/recover.c | 9 ++--
11 files changed, 164 insertions(+), 167 deletions(-)
next reply other threads:[~2024-09-17 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 17:05 David Teigland [this message]
2024-09-19 5:20 ` [GIT PULL] dlm updates for 6.12 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=Zum2QP7hS1mDzqBT@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.