[GIT PULL] gfs2 changes for 7.3

Andreas Gruenbacher <[email protected]>
Newsgroups dev.linux.lists.gfs2,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
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(-)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.