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 6.17
Date: Mon, 28 Jul 2025 16:38:35 +0200	[thread overview]
Message-ID: <20250728143837.137302-1-agruenba@redhat.com> (raw)

Dear Linus,

please consider pulling the following gfs2 changes for 6.17.

Thanks,
Andreas

The following changes since commit d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af:

  Linux 6.16-rc4 (2025-06-29 13:09:04 -0700)

are available in the Git repository at:

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

for you to fetch changes up to deb016c1669002e48c431d6fd32ea1c20ef41756:

  gfs2: No more self recovery (2025-07-16 23:30:32 +0200)

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

- Prevent cluster nodes from trying to recover their own filesystems
  during a withdraw.

- Add two missing migrate_folio aops and an additional exhash directory
  consistency check (both triggered by syzbot bug reports).

- Sanitize how dlm results are processed and clean up a few quirks in
  the glock code.

- Minor stuff: Get rid of the GIF_ALLOC_FAILED flag; use SECTOR_SIZE and
  SECTOR_SHIFT.

----------------------------------------------------------------
Andreas Gruenbacher (7):
      gfs2: Use SECTOR_SIZE and SECTOR_SHIFT
      gfs2: Remove GIF_ALLOC_FAILED flag
      gfs2: Minor do_xmote cancelation fix
      gfs2: sanitize the gdlm_ast -> finish_xmote interface
      gfs2: simplify finish_xmote
      gfs2: a minor finish_xmote cleanup
      gfs2: No more self recovery

Andrew Price (2):
      gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops
      gfs2: Validate i_depth for exhash directories

 fs/gfs2/dir.c        |  6 ++----
 fs/gfs2/glock.c      | 43 +++++++++++++++++++++----------------------
 fs/gfs2/glock.h      | 10 ++++++++++
 fs/gfs2/glops.c      |  6 ++++++
 fs/gfs2/incore.h     |  1 -
 fs/gfs2/inode.c      |  7 ++-----
 fs/gfs2/inode.h      |  6 +++---
 fs/gfs2/lock_dlm.c   |  9 ++++++---
 fs/gfs2/meta_io.c    | 10 +++++-----
 fs/gfs2/ops_fstype.c | 12 ++++++------
 fs/gfs2/super.c      |  6 ++----
 fs/gfs2/util.c       | 31 +++++++++++--------------------
 12 files changed, 74 insertions(+), 73 deletions(-)


             reply	other threads:[~2025-07-28 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 14:38 Andreas Gruenbacher [this message]
2025-07-28 23:41 ` 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=20250728143837.137302-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®