mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Yael Chemla <ychemla@nvidia.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Petr Pavlu <petr.pavlu@suse.com>,
	x86@kernel.org, linux-modules@vger.kernel.org,
	linux-kernel@vger.kernel.org, Gal Pressman <gal@nvidia.com>,
	Tariq Toukan <tariqt@nvidia.com>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	Thomas Gleixner <tglx@kernel.org>, Borislav Petkov <bp@alien8.de>
Subject: Re: [REGRESSION] x86: Use RCU in all users of,__module_address() slows kTLS+wrk workload on KASAN+PROVE_LOCKING+kmemleak
Date: Fri, 20 Nov 2026 12:57:45 +0100	[thread overview]
Message-ID: <20261120115745.GR2668564@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <bd2a701b-866c-4d4c-bd0b-37b4410628be@nvidia.com>

On Thu, Nov 19, 2026 at 09:54:37PM +0200, Yael Chemla wrote:
> Hi,
> 
> A kTLS stress test started failing in v6.15-rc1 on kernels built with
> KASAN and PROVE_LOCKING. It was bisected to commit 14daa3bca217 ("x86:
> Use RCU in all users of __module_address().")
> 
> The test runs wrk (1000 connections, 15s, --timeout 5s) against nginx
> serving a 1 MB file over kTLS, with 1% packet loss. It fails because too
> few requests complete: wrk reports only timeouts, no connect/read/write
> errors. With --timeout 10s it passes.
> 
> Reverting 14daa3bca217 on top of 01d5b167dc23 (modules-6.15-rc1 merge)
> or v7.4-rc2 (7475ea8b5861), with the same config, makes the test pass;
> without the revert it fails on both.
> 
> The failing config has KASAN, PROVE_LOCKING, kmemleak and UBSAN enabled.
> Building without KASAN, or without PROVE_LOCKING, also passes.
> 
> I have not looked into where the time goes.
> 
> #regzbot introduced: 14daa3bca217

Anything *SAN is not a performance target, not a regression.

      reply	other threads:[~2026-11-20 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19 19:54 Yael Chemla
2026-11-20 11:57 ` Peter Zijlstra [this message]

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=20261120115745.GR2668564@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=gal@nvidia.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=petr.pavlu@suse.com \
    --cc=regressions@lists.linux.dev \
    --cc=tariqt@nvidia.com \
    --cc=tglx@kernel.org \
    --cc=x86@kernel.org \
    --cc=ychemla@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®