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
Subject: [GIT PULL] dlm updates for 5.20
Date: Mon, 11 Jul 2022 08:36:44 -0500	[thread overview]
Message-ID: <20220711133644.GA27727@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-5.20

Changes in this set of commits:

. Delay the cleanup of interrupted posix lock requests until the
  user space result arrives. Previously, the immediate cleanup
  would lead to extraneous warnings when the result arrived.

. Tracepoint improvements, e.g. adding the lock resource name.

. Delay the completion of lockspace creation until one full recove
  cycle has completed. This allows more error cases to be returned
  the caller.

. Remove warnings from the locking layer about delayed network rep
  The recently added midcomms warnings are much more useful.

. Begin the process of deprecating two unused lock-timeout-related
  features. These features now require enabling via a Kconfig opti
  and enabling them triggers deprecation warnings. We expect to
  remove the code in v5.22.

Thanks,
Dave

Alexander Aring (19):
      fs: dlm: plock use list_first_entry
      fs: dlm: add pid to debug log
      fs: dlm: change plock interrupted message to debug again
      fs: dlm: use dlm_plock_info for do_unlock_close
      fs: dlm: change posix lock sigint handling
      fs: dlm: change ast and bast trace order
      fs: dlm: remove additional dereference of lksb
      fs: dlm: add resource name to tracepoints
      fs: dlm: update comments about recovery and membership handling
      fs: dlm: call dlm_lsop_recover_prep once
      fs: dlm: make new_lockspace() wait until recovery completes
      fs: dlm: handle recovery result outside of ls_recover
      fs: dlm: add comment about lkb IFL flags
      fs: dlm: fix grammar in lowcomms output
      fs: dlm: remove waiter warnings
      fs: dlm: remove timeout from dlm_user_adopt_orphan
      fs: dlm: add deprecation Kconfig and warnings for timeouts
      fs: dlm: don't use deprecated timeout features by default
      fs: dlm: move kref_put assert for lkb structs


 fs/dlm/Kconfig             |   9 +++
 fs/dlm/Makefile            |   2 +-
 fs/dlm/ast.c               |   4 +-
 fs/dlm/config.c            |  21 ++++---
 fs/dlm/config.h            |   3 +-
 fs/dlm/dlm_internal.h      |  32 ++++++++--
 fs/dlm/lock.c              | 143 ++++++++++++++++++---------------------------
 fs/dlm/lock.h              |  17 +++++-
 fs/dlm/lockspace.c         |  31 +++++++---
 fs/dlm/lowcomms.c          |   4 +-
 fs/dlm/member.c            |  30 +++++-----
 fs/dlm/plock.c             |  51 +++++++++++-----
 fs/dlm/recoverd.c          |  35 +++++++++--
 fs/dlm/user.c              |  21 ++++++-
 include/trace/events/dlm.h | 118 ++++++++++++++++++++++++++++++-------
 15 files changed, 351 insertions(+), 170 deletions(-)


                 reply	other threads:[~2022-07-11 13:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220711133644.GA27727@redhat.com \
    --to=teigland@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