public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, cluster-devel@redhat.com
Subject: [GIT PULL] dlm updates for 6.4
Date: Tue, 25 Apr 2023 10:39:51 -0500	[thread overview]
Message-ID: <20230425153951.GB28392@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.4

Change summary:

Remove some unused features (related to lock timeouts) that have been
previously scheduled for removal.

Fix a bug where the pending callback flag would be incorrectly cleared,
which could potentially result in missing a completion callback.

Use an unbound workqueue for dlm socket handling so that socket
operations can be processed with less delay.

Fix possible lockspace join connection errors with large clusters (e.g.
over 16 nodes) caused by a small socket backlog setting.

Use atomic bit ops for internal flags to help avoid mistakes copying
flag values from messages.

Fix recently introduced bug where memory for lvb data could be
unnecessarily allocated for a lock.

Thanks,
Dave


Alexander Aring (11):
      fs: dlm: fix DLM_IFL_CB_PENDING gets overwritten
      fs: dlm: add unbound flag to dlm_io workqueue
      fs: dlm: remove deprecated code parts
      fs: dlm: rename stub to local message flag
      fs: dlm: remove DLM_IFL_LOCAL_MS flag
      fs: dlm: store lkb distributed flags into own value
      fs: dlm: change dflags to use atomic bits
      fs: dlm: move internal flags to atomic ops
      fs: dlm: rsb hash table flag value to atomic ops
      fs: dlm: switch lkb_sbflags to atomic ops
      fs: dlm: stop unnecessarily filling zero ms_extra bytes

Edwin Török (1):
      DLM: increase socket backlog to avoid hangs with 16 nodes


 fs/dlm/Kconfig                    |   9 -
 fs/dlm/Makefile                   |   1 -
 fs/dlm/ast.c                      |  11 +-
 fs/dlm/config.c                   |  21 --
 fs/dlm/config.h                   |   3 -
 fs/dlm/debug_fs.c                 |   8 +-
 fs/dlm/dlm_internal.h             | 154 +++++++----
 fs/dlm/lock.c                     | 533 ++++++++++++--------------------------
 fs/dlm/lock.h                     |  17 --
 fs/dlm/lockspace.c                |  29 +--
 fs/dlm/lowcomms.c                 |   6 +-
 fs/dlm/main.c                     |   9 +-
 fs/dlm/memory.c                   |   2 +-
 fs/dlm/netlink.c                  | 139 ----------
 fs/dlm/rcom.c                     |   2 +-
 fs/dlm/recover.c                  |   2 +-
 fs/dlm/recoverd.c                 |   2 -
 fs/dlm/user.c                     |  34 +--
 include/linux/dlm.h               |   3 -
 include/trace/events/dlm.h        |  12 +-
 include/uapi/linux/dlm.h          |   1 +
 include/uapi/linux/dlm_netlink.h  |  60 -----
 include/uapi/linux/dlmconstants.h |   5 +-
 23 files changed, 299 insertions(+), 764 deletions(-)
 delete mode 100644 fs/dlm/netlink.c
 delete mode 100644 include/uapi/linux/dlm_netlink.h


             reply	other threads:[~2023-04-25 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 15:39 David Teigland [this message]
2023-04-26 17:06 ` [GIT PULL] dlm updates for 6.4 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=20230425153951.GB28392@redhat.com \
    --to=teigland@redhat.com \
    --cc=cluster-devel@redhat.com \
    --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