From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: Amir Goldstein <amir73il@gmail.com>,
Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>,
Sasha Levin <sashal@kernel.org>,
Fedor Pchelkin <pchelkin@ispras.ru>,
stable@vger.kernel.org, xfs-stable@lists.linux.dev,
Christoph Hellwig <hch@lst.de>,
Catherine Hoang <catherine.hoang@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
lvc-project@linuxtesting.org, linux-xfs@vger.kernel.org,
Leah Rumancik <leah.rumancik@gmail.com>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH 6.6 0/4] fix kernel crash for xfs/235 test
Date: Thu, 25 Jun 2026 11:34:21 -0700 [thread overview]
Message-ID: <20260625183421.GO6070@frogsfrogsfrogs> (raw)
In-Reply-To: <ajKSytW_sBFJaBTW@nidhogg.toxiclabs.cc>
On Wed, Jun 17, 2026 at 02:31:01PM +0200, Carlos Maiolino wrote:
> On Wed, Jun 17, 2026 at 11:19:25AM +0200, Amir Goldstein wrote:
> > On Tue, Jun 16, 2026 at 7:33 PM Leah Rumancik <leah.rumancik@gmail.com> wrote:
> > >
> > > I have changed teams so I no longer work on kernel and I don't believe
> > > my xfs maintenance work was backfilled ;(
> > >
> > > On Tue, Jun 16, 2026 at 7:19 AM Carlos Maiolino <cem@kernel.org> wrote:
> > > >
> > > > On Tue, Jun 16, 2026 at 09:31:41AM -0400, Hamza Mahfooz wrote:
> > > > > Cc: linux-xfs@vger.kernel.org
> > > > >
> > > > > On Tue, Jun 16, 2026 at 09:13:45AM +0200, Carlos Maiolino wrote:
> > > > > > On Mon, Jun 15, 2026 at 03:19:24PM -0400, Hamza Mahfooz wrote:
> > > > > > > Cc: Carlos Maiolino <cem@kernel.org>
> > > > > >
> > > > > > FWIW I don't maintain the stable trees I really don't have time for
> > > > > > that. Darrick/Leah have been doing a best effort case for that, but
> > > > > > again, this is mostly a best effort so we shouldn't expect them to be
> > > > > > looking/picking up every single possible patch suggested for stable.
> > > > > >
> > > > >
> > > > > Now that you mention it, the xfs-stable mailing list seems to be pretty
> > > > > much dead (i.e. the last time fixes from it were merged into stable was
> > > > > almost a year ago). I guess no one is really working on it anymore?
> > > >
> > > > IIRC Darrick started it, I personally never worked on it, but I didn't
> > > > follow the evolution there.
> >
> > I think at this point we can officially declare xfs in stable <= 6.6
> > unmaintained
> > maybe need to send patches to LTS MAINTAINERS.
> >
> > The best chance in this case to apply the requested fix to 6.6.y is that the
> > author (Darrick) approves it.
>
> Unfortunately this might be true. But let's wait for Darrick's input
> please. He's on vacations this week so will be unfair to make any
> decisions in this matter without his input.
> Also he has been still poking people to tag patches with LTS versions
> so even though he might not me dealing with the xfs-stable, he might still
> be driving work on LTS trees.
I've really only been doing QA work on 6.12/6.18 LTS. Ted Tso might
still be doing the older ones. Catherine left Oracle last year.
--D
next prev parent reply other threads:[~2026-06-25 18:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250322143418.216654-1-pchelkin@ispras.ru>
[not found] ` <aisAxyXVxf4wql2u@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
[not found] ` <20260612233110.2-1-sashal@kernel.org>
[not found] ` <ajBQPNuKCruxhkXX@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
[not found] ` <ajD3Gb-vQkGU0N6b@nidhogg.toxiclabs.cc>
2026-06-16 13:31 ` [PATCH 6.6 0/4] fix kernel crash for xfs/235 test 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 [this message]
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=20260625183421.GO6070@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=amir73il@gmail.com \
--cc=catherine.hoang@oracle.com \
--cc=cem@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hamzamahfooz@linux.microsoft.com \
--cc=hch@lst.de \
--cc=leah.rumancik@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=pchelkin@ispras.ru \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
--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