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.6
Date: Thu, 31 Aug 2023 09:21:53 -0500 [thread overview]
Message-ID: <20230831142152.GA28483@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.6
Changes include:
- Allow blocking posix lock requests to be interrupted while waiting.
This requires a cancel request to be sent to the userspace daemon
where posix lock requests are processed across the cluster.
- Fix a posix lock patch from the previous cycle in which lock requests
from different file systems could be mixed up.
- Fix some long standing problems with nfs posix lock cancelation.
- Add a new debugfs file for printing queued callbacks.
- Stop modifying buffers that have been used to receive a message.
- Misc cleanups and some refactoring.
Thanks,
Dave
Alexander Aring (17):
fs: dlm: remove twice newline
fs: dlm: allow to F_SETLKW getting interrupted
fs: dlm: fix F_CANCELLK to cancel pending request
fs: dlm: add missing spin_unlock
fs: dlm: remove unused processed_nodes
fs: dlm: debugfs for queued callbacks
fs: dlm: check on plock ops when exit dlm
fs: dlm: add plock dev tracepoints
fs: dlm: remove clear_members_cb
fs: dlm: cleanup lock order
fs: dlm: get recovery sequence number as parameter
fs: dlm: drop rxbuf manipulation in dlm_copy_master_names
fs: dlm: drop rxbuf manipulation in dlm_recover_master_copy
fs: dlm: constify receive buffer
fs: dlm: create midcomms nodes when configure
fs: dlm: don't use RCOM_NAMES for version detection
dlm: fix plock lookup when using multiple lockspaces
fs/dlm/config.c | 2 +-
fs/dlm/debug_fs.c | 101 +++++++++++++-
fs/dlm/dir.c | 14 +-
fs/dlm/dir.h | 6 +-
fs/dlm/dlm_internal.h | 1 +
fs/dlm/lock.c | 120 ++++++++--------
fs/dlm/lock.h | 16 ++-
fs/dlm/lowcomms.c | 1 -
fs/dlm/member.c | 15 +-
fs/dlm/member.h | 2 +-
fs/dlm/midcomms.c | 304 ++++++++++++++++-------------------------
fs/dlm/midcomms.h | 1 +
fs/dlm/plock.c | 176 +++++++++++++++++++-----
fs/dlm/rcom.c | 102 ++++++++------
fs/dlm/rcom.h | 15 +-
fs/dlm/recover.c | 60 ++++----
fs/dlm/recover.h | 14 +-
fs/dlm/recoverd.c | 16 +--
fs/dlm/requestqueue.c | 3 +-
fs/dlm/requestqueue.h | 3 +-
fs/gfs2/file.c | 9 +-
fs/ocfs2/stack_user.c | 13 +-
include/linux/dlm_plock.h | 2 +
include/trace/events/dlm.h | 51 +++++++
include/uapi/linux/dlm_plock.h | 1 +
25 files changed, 628 insertions(+), 420 deletions(-)
next reply other threads:[~2023-08-31 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 14:21 David Teigland [this message]
2023-08-31 22:42 ` [GIT PULL] dlm updates for 6.6 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=20230831142152.GA28483@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;
as well as URLs for NNTP newsgroup(s).