From: Matthieu Baerts <matttbe@kernel.org>
To: Stanislav Fomichev <sdf@fomichev.me>, netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, paulmck@kernel.org, joel@joelfernandes.org,
steven.price@arm.com, akpm@linux-foundation.org,
anshuman.khandual@arm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] configs/debug: run and debug PREEMPT
Date: Tue, 8 Apr 2025 20:18:26 +0200 [thread overview]
Message-ID: <df253016-81df-4cc9-8a8c-f92fd1cb8aea@kernel.org> (raw)
In-Reply-To: <20250402172305.1775226-1-sdf@fomichev.me>
Hi Stanislav,
On 02/04/2025 19:23, Stanislav Fomichev wrote:
> Recent change [0] resulted in a "BUG: using __this_cpu_read() in
> preemptible" splat [1]. PREEMPT kernels have additional requirements
> on what can and can not run with/without preemption enabled.
> Expose those constrains in the debug kernels.
Good idea to suggest this to find more bugs!
I did some quick tests on my side with our CI, and the MPTCP selftests
seem to take a bit more time, but without impacting the results.
Hopefully, there will be no impact in slower/busy environments :)
Acked-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-04-08 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 17:23 Stanislav Fomichev
2025-04-04 9:32 ` Simon Horman
2025-04-08 18:18 ` Matthieu Baerts [this message]
2025-04-08 19:03 ` Jakub Kicinski
2025-04-09 11:58 ` Matthieu Baerts
2025-04-09 15:55 ` Jakub Kicinski
2025-04-10 1:00 ` patchwork-bot+netdevbpf
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=df253016-81df-4cc9-8a8c-f92fd1cb8aea@kernel.org \
--to=matttbe@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joel@joelfernandes.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=sdf@fomichev.me \
--cc=steven.price@arm.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®