mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
	gfs2@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] gfs2 changes for 7.3
Date: Mon, 17 Aug 2026 13:26:46 +0200	[thread overview]
Message-ID: <20260817112647.1203264-1-agruenba@redhat.com> (raw)

Dear Linus,

please consider pulling the following gfs2 changes for 7.3.

Thanks,
Andreas


The following changes since commit a13c140cc289c0b7b3770bce5b3ad42ab35074aa:

  Linux 7.2-rc3 (2026-07-12 14:16:39 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-for-7.3

for you to fetch changes up to 657e5af4fe0b9696a6c7232da1727a9f37eaa04d:

  gfs2: harden gfs2_glock_hold (2026-08-12 20:22:51 +0200)

----------------------------------------------------------------
gfs2 changes

- Don't cache unreferenced glocks: when a glock is no longer referenced (for
  example, because the inode it protects is evicted), it is now released as
  soon as possible instead of leaving it around until memory pressure or an
  unmount forces it out.  For some workloads, this saves a lot of memory and
  speeds up unmounts significantly.

- Harden gfs2_glock_hold() by making sure the caller holds a reference and
  fix a related race in checking for the liveliness of glocks between
  gdlm_bast() and gfs2_glock_cb().

----------------------------------------------------------------
Andreas Gruenbacher (5):
      gfs2: Enable automatic glock hash table shrinking
      gfs2: Don't cache unreferenced glocks
      gfs2: Skip dlm unlocks earlier
      gfs2: Remove the glock lru list and shrinker
      gfs2: harden gfs2_glock_hold

 fs/gfs2/glock.c      | 231 ++++++---------------------------------------------
 fs/gfs2/glock.h      |   2 +-
 fs/gfs2/incore.h     |   7 +-
 fs/gfs2/lock_dlm.c   |   5 +-
 fs/gfs2/main.c       |   1 -
 fs/gfs2/ops_fstype.c |   5 +-
 fs/gfs2/super.c      |   2 +-
 fs/gfs2/sys.c        |   2 -
 fs/gfs2/trace_gfs2.h |   1 -
 9 files changed, 35 insertions(+), 221 deletions(-)


             reply	other threads:[~2026-08-17 11:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 11:26 Andreas Gruenbacher [this message]
2026-08-17 16:19 ` Andreas Gruenbacher
2026-08-18  3:57 ` 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=20260817112647.1203264-1-agruenba@redhat.com \
    --to=agruenba@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

all inboxes | Powered by JetHome®