From: patchwork-bot+netdevbpf@kernel.org
To: Andrea Righi <arighi@nvidia.com>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
andrii.nakryiko@gmail.com
Subject: Re: [PATCH v2] bpf: Fix bpf_get_smp_processor_id() on !CONFIG_SMP
Date: Wed, 18 Dec 2024 00:20:30 +0000 [thread overview]
Message-ID: <173448123077.1129094.278515116622545492.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241217195813.622568-1-arighi@nvidia.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 17 Dec 2024 20:58:13 +0100 you wrote:
> On x86-64 calling bpf_get_smp_processor_id() in a kernel with CONFIG_SMP
> disabled can trigger the following bug, as pcpu_hot is unavailable:
>
> [ 8.471774] BUG: unable to handle page fault for address: 00000000936a290c
> [ 8.471849] #PF: supervisor read access in kernel mode
> [ 8.471881] #PF: error_code(0x0000) - not-present page
>
> [...]
Here is the summary with links:
- [v2] bpf: Fix bpf_get_smp_processor_id() on !CONFIG_SMP
https://git.kernel.org/bpf/bpf/c/23579010cf0a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-12-18 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 19:58 [PATCH v2] bpf: Fix bpf_get_smp_processor_id() on !CONFIG_SMP Andrea Righi
2024-12-18 0:20 ` patchwork-bot+netdevbpf [this message]
2024-12-18 12:22 ` Daniel Borkmann
-- strict thread matches above, loose matches on Subject: below --
2024-12-16 21:00 Andrea Righi
2024-12-17 18:38 ` Andrii Nakryiko
2024-12-17 19:53 ` Andrea Righi
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=173448123077.1129094.278515116622545492.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=arighi@nvidia.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.