From: "Theodore Tso" <tytso@mit.edu>
To: Michael Bommarito <michael.bommarito@gmail.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Please consider 83f99de1b7c0 ("ext2: fix race between setxattr and write back") for 5.10.y, 5.15.y, and 6.1.y
Date: Fri, 10 Jul 2026 07:28:28 -0400 [thread overview]
Message-ID: <alDWUmORy7fTnorX@mit.edu> (raw)
In-Reply-To: <20260710023142.3748810-1-michael.bommarito@gmail.com>
On Thu, Jul 09, 2026 at 10:31:42PM -0500, Michael Bommarito wrote:
> Fresh stable check (2026-07-08):
> - 5.10.y: 738ac465e4e9
> fix shape: absent; upstream diff: needs-adjustment
> - 5.15.y: c86c4726e7f0
> fix shape: absent; upstream diff: needs-adjustment
> - 6.1.y: 090666d3cc90
> fix shape: absent; upstream diff: needs-adjustment
> - 6.6.y and newer checked longterms already have the fixed shape
And this is why the patches have not been backported. It requires
work, and an AI generated request doesn't change the reality that
*someone* has to do that work,
I invite you to figure out a way to figure out an AI mediated tool
that can attempt the backport, and then run the moral equivalent of
"gce-xfstests -c ext4.all -g auto" to verify that the backport doesn't
result in any regressions. (Some previous attempts to backport to
older LTS kernels have resulted in the kernels crashing as a result.)
Otherwise, I recommend that most users consider switching to a newer
LTS kernel, or if they can't to pay $$$ to an enterprise Linux
distribution that pays engineers to do that hard work.
- Ted
next prev parent reply other threads:[~2026-07-10 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 2:31 Please consider 83f99de1b7c0 ("ext2: fix race between setxattr and write back") for 5.10.y, 5.15.y, and 6.1.y Michael Bommarito
2026-07-10 11:28 ` Theodore Tso [this message]
2026-07-11 20:09 ` Michael Bommarito
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=alDWUmORy7fTnorX@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.bommarito@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox