[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <df253016-81df-4cc9-8a8c-f92fd1cb8aea@kernel.org>
Date: Tue, 8 Apr 2025 20:18:26 +0200
From: Matthieu Baerts <matttbe@...nel.org>
To: Stanislav Fomichev <sdf@...ichev.me>, netdev@...r.kernel.org
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, paulmck@...nel.org, joel@...lfernandes.org,
steven.price@....com, akpm@...ux-foundation.org, anshuman.khandual@....com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] configs/debug: run and debug PREEMPT
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@...nel.org>
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
Powered by blists - more mailing lists