From: "Adrian Garcia Casado" <adriangarciacasado42@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/slub: Revert "mm: Aggressive slab merging heuristics"
Date: Fri, 10 Apr 2026 16:14:28 -0700 (PDT) [thread overview]
Message-ID: <69d98454.5d0a0220.2786dd.98a9@mx.google.com> (raw)
On Fri, 10 Apr 2026 18:45:22 -0700, Linus Torvalds wrote:
> The so-called "AI optimizations" for SLUB merging are completely broken.
> They ignore hardware cache-line alignment requirements on x86_64, leading
> to silent memory corruption and eventual kernel panics under heavy load.
I can confirm this revert saves the system from the SLUB corruption introduced by the AI-generated patch.
Applied cleanly on top of v7.0-rc7. Compiled and running on Fedora (x86_64).
I have stress-tested the memory allocator with heavy gaming workloads (Euro Truck Simulator 2 via Wine 11 / fsync) which previously triggered the out-of-bounds writes and stuttering.
The system is now rock solid. No kernel panics, no memory corruption, and frametimes are perfectly stable. The Antigravity slop is gone.
Ready for the final 7.0 release tomorrow.
Tested-by: Adrian Garcia Casado <adriangarciacasado42@gmail.com>
reply other threads:[~2026-04-10 23:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=69d98454.5d0a0220.2786dd.98a9@mx.google.com \
--to=adriangarciacasado42@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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