From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, 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, matttbe@kernel.org,
anshuman.khandual@arm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] configs/debug: run and debug PREEMPT
Date: Thu, 10 Apr 2025 01:00:35 +0000 [thread overview]
Message-ID: <174424683541.3096919.18023331757196166323.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250402172305.1775226-1-sdf@fomichev.me>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Apr 2025 10:23:05 -0700 you 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.
>
> 0: https://lore.kernel.org/netdev/20250314120048.12569-2-justin.iurman@uliege.be/
> 1: https://lore.kernel.org/netdev/20250402094458.006ba2a7@kernel.org/T/#mbf72641e9d7d274daee9003ef5edf6833201f1bc
>
> [...]
Here is the summary with links:
- [net-next] configs/debug: run and debug PREEMPT
https://git.kernel.org/netdev/net-next/c/311920774c40
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-04-10 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 17:23 [PATCH net-next] configs/debug: run and debug PREEMPT Stanislav Fomichev
2025-04-04 9:32 ` Simon Horman
2025-04-08 18:18 ` Matthieu Baerts
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 [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=174424683541.3096919.18023331757196166323.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@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=matttbe@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;
as well as URLs for NNTP newsgroup(s).