From: Siddh Raman Pant <siddh.raman.pant@oracle.com>
To: "Darrick J . Wong" <djwong@kernel.org>,
linux-xfs@vger.kernel.org, stable@vger.kernel.org
Cc: Dave Chinner <dchinner@redhat.com>,
linux-kernel@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Mark Tinguely <mark.tinguely@oracle.com>
Subject: [PATCH RESEND 6.12 v2 0/6] Backport of XFS umount hang fixes
Date: Tue, 13 Oct 2026 15:07:23 +0530 [thread overview]
Message-ID: <cover.1791883280.git.siddh.raman.pant@oracle.com> (raw)
Backport of this series:
https://lore.kernel.org/all/20250625224957.1436116-1-david@fromorbit.com/
I have added information in commit message upon conflict resolutions.
v2: Address Sasha's comments to v1 in the below mail:
https://lore.kernel.org/stable/2026-10-01-1-daily-reply-0012-re-xfs-umount-hang-backports@kernel.org/
xfstests_xfs testing results:
Generic:
Ran: 001 to 771 (672 tests; gaps)
Failures before changes:
Count: 4
IDs: 633, 696, 697, 753
Failures after changes:
Count: 4
IDs: 633, 696, 697, 753
No new success or failure after changes.
XFS:
Ran: 001 to 789 (311 tests; gaps)
Failures before changes:
Count: 2
IDs: 300, 556
Failures after changes:
Count: 2
IDs: 300, 556
No new success or failure after changes.
Thanks,
Siddh
Dave Chinner (6):
xfs: xfs_ifree_cluster vs xfs_iflush_shutdown_abort deadlock
xfs: catch stale AGF/AGF metadata
xfs: avoid dquot buffer pin deadlock
xfs: rearrange code in xfs_buf_item.c
xfs: factor out stale buffer item completion
xfs: fix unmount hang with unflushable inodes stuck in the AIL
fs/xfs/libxfs/xfs_alloc.c | 41 ++++-
fs/xfs/libxfs/xfs_ialloc.c | 31 +++-
fs/xfs/xfs_buf.c | 55 -------
fs/xfs/xfs_buf.h | 1 -
fs/xfs/xfs_buf_item.c | 297 ++++++++++++++++++++++---------------
fs/xfs/xfs_buf_item.h | 3 +-
fs/xfs/xfs_dquot.c | 4 +-
fs/xfs/xfs_icache.c | 8 +
fs/xfs/xfs_inode.c | 2 +-
fs/xfs/xfs_qm.c | 87 +++--------
fs/xfs/xfs_trace.h | 1 -
11 files changed, 270 insertions(+), 260 deletions(-)
--
2.53.0
next reply other threads:[~2026-10-13 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 9:37 Siddh Raman Pant [this message]
2026-10-13 9:37 ` [PATCH RESEND 6.12 v2 1/6] xfs: xfs_ifree_cluster vs xfs_iflush_shutdown_abort deadlock Siddh Raman Pant
2026-10-13 9:37 ` [PATCH RESEND 6.12 v2 2/6] xfs: catch stale AGF/AGF metadata Siddh Raman Pant
2026-10-13 9:37 ` [PATCH RESEND 6.12 v2 3/6] xfs: avoid dquot buffer pin deadlock Siddh Raman Pant
2026-10-13 9:37 ` [PATCH RESEND 6.12 v2 4/6] xfs: rearrange code in xfs_buf_item.c Siddh Raman Pant
2026-10-13 9:37 ` [PATCH RESEND 6.12 v2 5/6] xfs: factor out stale buffer item completion Siddh Raman Pant
2026-10-13 9:37 ` [PATCH RESEND 6.12 v2 6/6] xfs: fix unmount hang with unflushable inodes stuck in the AIL Siddh Raman Pant
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=cover.1791883280.git.siddh.raman.pant@oracle.com \
--to=siddh.raman.pant@oracle.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mark.tinguely@oracle.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.