From: Sasha Levin <sashal@kernel.org>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: Sasha Levin <sashal@kernel.org>,
Leah Rumancik <leah.rumancik@gmail.com>,
stable@vger.kernel.org, xfs-stable@lists.linux.dev,
"Darrick J. Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Catherine Hoang <catherine.hoang@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
lvc-project@linuxtesting.org,
Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>
Subject: Re: [PATCH 6.6 0/4] fix kernel crash for xfs/235 test
Date: Fri, 12 Jun 2026 20:20:34 -0400 [thread overview]
Message-ID: <20260612233110.2-1-sashal@kernel.org> (raw)
In-Reply-To: <aisAxyXVxf4wql2u@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Wed, Jun 11, 2026 at 02:39:03PM -0400, Hamza Mahfooz wrote:
> Any idea what happened to this series? It resolves an issue that I've
> hit in a production environment FWIW.
>
> Series is:
>
> Tested-by: Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>
Thanks for the nudge, and thanks Fedor for putting the backport together.
We generally don't take XFS backports without a maintainer signing off on them,
so right now we're waiting for one to do so :)
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-06-13 0:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 14:34 [PATCH 6.6 0/4] fix kernel crash for xfs/235 test Fedor Pchelkin
2025-03-22 14:34 ` [PATCH 6.6 1/4] xfs: recreate work items when recovering intent items Fedor Pchelkin
2025-03-22 14:34 ` [PATCH 6.6 2/4] xfs: dump the recovered xattri log item if corruption happens Fedor Pchelkin
2025-03-22 14:34 ` [PATCH 6.6 3/4] xfs: use xfs_defer_finish_one to finish recovered work items Fedor Pchelkin
2025-03-22 14:34 ` [PATCH 6.6 4/4] xfs: move ->iop_recover to xfs_defer_op_type Fedor Pchelkin
2026-06-11 18:39 ` [PATCH 6.6 0/4] fix kernel crash for xfs/235 test Hamza Mahfooz
2026-06-13 0:20 ` Sasha Levin [this message]
2026-06-15 19:19 ` Hamza Mahfooz
2026-06-16 7:13 ` Carlos Maiolino
2026-06-16 13:31 ` Hamza Mahfooz
2026-06-16 14:19 ` Carlos Maiolino
2026-06-16 17:26 ` Leah Rumancik
2026-06-17 9:19 ` Amir Goldstein
2026-06-17 12:31 ` Carlos Maiolino
2026-06-25 18:34 ` Darrick J. Wong
2026-06-30 23:39 ` Hamza Mahfooz
2026-07-01 16:33 ` Darrick J. Wong
2026-07-03 4:06 ` Sasha Levin
2026-07-03 13:46 ` Amir Goldstein
2026-07-08 0:34 ` Hamza Mahfooz
2026-07-08 16:18 ` Sasha Levin
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=20260612233110.2-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=catherine.hoang@oracle.com \
--cc=djwong@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hamzamahfooz@linux.microsoft.com \
--cc=hch@lst.de \
--cc=leah.rumancik@gmail.com \
--cc=lvc-project@linuxtesting.org \
--cc=pchelkin@ispras.ru \
--cc=stable@vger.kernel.org \
--cc=xfs-stable@lists.linux.dev \
/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