From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GIT PULL] dlm updates for 6.5
Date: Thu, 29 Jun 2023 15:02:23 -0500 [thread overview]
Message-ID: <20230629200223.GC14388@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.5
The dlm posix lock handling (for gfs2) has three notable changes:
- Local pids returned from GETLK are no longer negated. A previous
patch negating remote pids mistakenly changed local pids also.
- SETLKW operations can now be interrupted only when the process is
killed, and not from other signals. General interruption was
resulting in previously acquired locks being cleared, not just
the in-progress lock. Handling this correctly will require
extending a cancel capability to user space (a future feature.)
- If multiple threads are requesting posix locks (with SETLKW),
fix incorrect matching of results to the requests.
The dlm networking has several minor cleanups, and one notable change:
- Avoid delaying ack messages for too long (used for message reliability),
resulting in a backlog of un-acked messages. These could previously
be delayed as a result of either too many or too few other messages
being sent. Now an upper and lower threshold is used to determine
when an ack should be sent.
Thanks,
Dave
Alexander Aring (18):
fs: dlm: return positive pid value for F_GETLK
fs: dlm: fix cleanup pending ops when interrupted
fs: dlm: interrupt posix locks only when process is killed
fs: dlm: make F_SETLK use unkillable wait_event
fs: dlm: fix mismatch of plock results from userspace
fs: dlm: revert check required context while close
fs: dlm: clear pending bit when queue was empty
fs: dlm: fix missing pending to false
fs: dlm: unregister memory at the very last
fs: dlm: don't check othercon twice
fs: dlm: cleanup STOP_IO bitflag set when stop io
fs: dlm: move dlm_purge_lkb_callbacks to user module
fs: dlm: warn about messages from left nodes
fs: dlm: filter ourself midcomms calls
fs: dlm: handle lkb wait count as atomic_t
fs: dlm: handle sequence numbers as atomic
fs: dlm: add send ack threshold and append acks to msgs
fs: dlm: remove filter local comms on close
Azeem Shaikh (1):
dlm: Replace all non-returning strlcpy with strscpy
fs/dlm/ast.c | 25 ++--------
fs/dlm/ast.h | 1 -
fs/dlm/config.c | 4 +-
fs/dlm/dlm_internal.h | 2 +-
fs/dlm/lock.c | 36 +++++++--------
fs/dlm/lockspace.c | 12 -----
fs/dlm/lockspace.h | 1 -
fs/dlm/lowcomms.c | 49 +++-----------------
fs/dlm/main.c | 2 +-
fs/dlm/member.c | 37 ++++++++++++---
fs/dlm/midcomms.c | 126 ++++++++++++++++++++++----------------------------
fs/dlm/plock.c | 115 +++++++++++++++++++++++++++------------------
fs/dlm/user.c | 18 ++++++++
fs/dlm/user.h | 1 +
14 files changed, 205 insertions(+), 224 deletions(-)
next reply other threads:[~2023-06-29 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 20:02 David Teigland [this message]
2023-06-29 20:51 ` [Cluster-devel] [GIT PULL] dlm updates for 6.5 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=20230629200223.GC14388@redhat.com \
--to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).