From: Seth Forshee <sforshee@kernel.org>
To: Stephen Dolan <sdolan@janestreet.com>
Cc: Dave Hansen <dave.hansen@intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Eric Hagberg <ehagberg@janestreet.com>,
Nick Barnes <nbarnes@janestreet.com>
Subject: Re: x86/mm: Finishing off the fix for a should_flush_tlb race
Date: Wed, 18 Feb 2026 13:43:25 -0600 [thread overview]
Message-ID: <aZYWXe739XUJrBld@do-x1carbon> (raw)
In-Reply-To: <CAHDw0oG7kfmUyRLSzmh9gGNgLyot39uRn-98_dafdveYzVmBAg@mail.gmail.com>
On Tue, Feb 17, 2026 at 05:21:19PM +0000, Stephen Dolan wrote:
> On Tue, 17 Feb 2026 at 15:20, Seth Forshee <sforshee@kernel.org> wrote:
> > > I wanted to check on the status of the stable patches, since I see the
> > > upstream fix went into 6.18 but there's still no fix in the 6.12 stable
> > > tree. We've been seeing segfaults during a test case with 6.12, and
> > > after bisecting we found that reverting both "x86/mm: Eliminate window
> > > where TLB flushes may be inadvertently skipped" and "x86/mm/tlb: Only
> > > trim the mm_cpumask once a second" seems to get rid of the segfaults.
> > > I'll try to get some testing with the proposed stable patch today.
>
> Hmm, ok. I posted the patch to stable@vger.kernel.org a while ago but
> it looks like it never got merged. Does this patch fix the issue for
> you?
>
> https://lore.kernel.org/stable/CAHDw0oE0334gEJ=ga1PAnZ3Av8+tFkKF-MJCF7Jj3i6pBVJvFQ@mail.gmail.com/
Without the patch we've seen a segfault within a couple of hours of
running our test case, often within 30 minutes. We ran for 18 hours
with the patch applied without any crashes, so it looks like it fixes
our crash.
Thanks,
Seth
next prev parent reply other threads:[~2026-02-18 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 14:01 x86/mm: Finishing off the fix for a should_flush_tlb race Stephen Dolan
2025-10-10 20:45 ` Dave Hansen
2026-02-17 15:12 ` Seth Forshee
2026-02-17 15:20 ` Seth Forshee
2026-02-17 17:21 ` Stephen Dolan
2026-02-18 19:43 ` Seth Forshee [this message]
2026-02-24 9:38 ` Stephen Dolan
2026-03-10 17:22 ` Greg Thelen
2026-03-12 21:06 ` Dave Hansen
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=aZYWXe739XUJrBld@do-x1carbon \
--to=sforshee@kernel.org \
--cc=dave.hansen@intel.com \
--cc=ehagberg@janestreet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=nbarnes@janestreet.com \
--cc=peterz@infradead.org \
--cc=sdolan@janestreet.com \
/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.