* [PATCH v3 bpf] bpf: Fix a data-race around bpf_jit_limit.
@ 2022-08-23 21:58 Kuniyuki Iwashima
2022-08-23 22:30 ` patchwork-bot+netdevbpf
0 siblings, 1 reply; 2+ messages in thread
From: Kuniyuki Iwashima @ 2022-08-23 21:58 UTC (permalink / raw)
To: Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko
Cc: Kuniyuki Iwashima, Kuniyuki Iwashima, bpf, netdev
While reading bpf_jit_limit, it can be changed concurrently via sysctl,
WRITE_ONCE() in __do_proc_doulongvec_minmax(). The size of bpf_jit_limit
is long, so we need to add a paired READ_ONCE() to avoid load-tearing.
Fixes: ede95a63b5e8 ("bpf: add bpf_jit_limit knob to restrict unpriv allocations")
Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com>
---
v3:
* Update changelog to clarify paired WRITE_ONCE() and motivation
as load-tearing.
v2: https://lore.kernel.org/netdev/20220823181247.90349-1-kuniyu@amazon.com/
* Drop other 3 patches (No change for this patch)
v1: https://lore.kernel.org/bpf/20220818042339.82992-1-kuniyu@amazon.com/
---
kernel/bpf/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/bpf/core.c b/kernel/bpf/core.c
index c1e10d088dbb..3d9eb3ae334c 100644
--- a/kernel/bpf/core.c
+++ b/kernel/bpf/core.c
@@ -971,7 +971,7 @@ pure_initcall(bpf_jit_charge_init);
int bpf_jit_charge_modmem(u32 size)
{
- if (atomic_long_add_return(size, &bpf_jit_current) > bpf_jit_limit) {
+ if (atomic_long_add_return(size, &bpf_jit_current) > READ_ONCE(bpf_jit_limit)) {
if (!bpf_capable()) {
atomic_long_sub(size, &bpf_jit_current);
return -EPERM;
--
2.30.2
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH v3 bpf] bpf: Fix a data-race around bpf_jit_limit.
2022-08-23 21:58 [PATCH v3 bpf] bpf: Fix a data-race around bpf_jit_limit Kuniyuki Iwashima
@ 2022-08-23 22:30 ` patchwork-bot+netdevbpf
0 siblings, 0 replies; 2+ messages in thread
From: patchwork-bot+netdevbpf @ 2022-08-23 22:30 UTC (permalink / raw)
To: Kuniyuki Iwashima; +Cc: ast, daniel, andrii, kuni1840, bpf, netdev
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 23 Aug 2022 14:58:04 -0700 you wrote:
> While reading bpf_jit_limit, it can be changed concurrently via sysctl,
> WRITE_ONCE() in __do_proc_doulongvec_minmax(). The size of bpf_jit_limit
> is long, so we need to add a paired READ_ONCE() to avoid load-tearing.
>
> Fixes: ede95a63b5e8 ("bpf: add bpf_jit_limit knob to restrict unpriv allocations")
> Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com>
>
> [...]
Here is the summary with links:
- [v3,bpf] bpf: Fix a data-race around bpf_jit_limit.
https://git.kernel.org/bpf/bpf/c/0947ae112108
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-08-23 22:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-08-23 21:58 [PATCH v3 bpf] bpf: Fix a data-race around bpf_jit_limit Kuniyuki Iwashima
2022-08-23 22:30 ` patchwork-bot+netdevbpf
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).