From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: "Ömer Mete Kaya" <omermetekaya0@gmail.com>,
ast@kernel.org, daniel@iogearbox.net
Cc: andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+fd7e415d891073b83e1f@syzkaller.appspotmail.com
Subject: Re: [PATCH bpf v2] bpf: Fix missing migration protection in __rhtab_map_lookup_and_delete_batch()
Date: Tue, 29 Sep 2026 13:08:23 +0100 [thread overview]
Message-ID: <3fff6732-025c-46e8-b3d5-320bd74a87a4@gmail.com> (raw)
In-Reply-To: <20260929081609.557899-1-omermetekaya0@gmail.com>
On 9/29/26 9:10 AM, Ömer Mete Kaya wrote:
> bpf_mem_cache_free_rcu() uses this_cpu_ptr() which requires migration
> to be disabled. All callers of rhtab_delete_elem() disable migration
> except __rhtab_map_lookup_and_delete_batch(), which calls it under
> rcu_read_lock() only.
>
> On CONFIG_PREEMPT_RCU, rcu_read_lock() does not disable preemption or
> migration, so the task can migrate between CPUs during the delete loop,
> causing this_cpu_ptr() to trigger:
>
> BUG: using smp_processor_id() in preemptible [00000000] code
>
> Fix by wrapping the delete loop in migrate_disable()/migrate_enable()
> in __rhtab_map_lookup_and_delete_batch(), matching the migration
> protection that the other callers already provide.
>
> Fixes: 818e00848227 ("bpf: Implement iteration ops for resizable hashtab")
> Reported-by: syzbot+fd7e415d891073b83e1f@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=fd7e415d891073b83e1f
> Suggested-by: Alexei Starovoitov <ast@kernel.org>
> Signed-off-by: Ömer Mete Kaya <omermetekaya0@gmail.com>
> ---
Acked-by: Mykyta Yatsenko <yatsenko@meta.com>
> Changes in v2:
> - Fix root cause in __rhtab_map_lookup_and_delete_batch() with
> migrate_disable()/migrate_enable() instead of stretching
> bpf_disable_instrumentation() in rhtab_delete_elem().
> - Fix Fixes: tag to 818e00848227.
> - Fix commit message: migration disabled, not preemption.
>
> Tested with syzkaller:
> - Before the fix: the reported warning was reproduced reliably.
> - After the fix: the warning was no longer reproducible.
>
> kernel/bpf/hashtab.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/kernel/bpf/hashtab.c b/kernel/bpf/hashtab.c
> index f744a42bb813..2bb9ac7fc73e 100644
> --- a/kernel/bpf/hashtab.c
> +++ b/kernel/bpf/hashtab.c
> @@ -3369,8 +3369,10 @@ static int __rhtab_map_lookup_and_delete_batch(struct bpf_map *map,
> }
>
> if (do_delete) {
> + migrate_disable();
> for (i = 0; i < total; i++)
> rhtab_delete_elem(rhtab, del_elems[i], NULL, 0);
> + migrate_enable();
> }
>
> rcu_read_unlock();
> --
> 2.55.0
>
>
next prev parent reply other threads:[~2026-09-29 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 8:10 [PATCH bpf v2] bpf: Fix missing migration protection in __rhtab_map_lookup_and_delete_batch() Ömer Mete Kaya
2026-09-29 12:08 ` Mykyta Yatsenko [this message]
2026-10-02 11:40 ` 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=3fff6732-025c-46e8-b3d5-320bd74a87a4@gmail.com \
--to=mykyta.yatsenko5@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=omermetekaya0@gmail.com \
--cc=song@kernel.org \
--cc=syzbot+fd7e415d891073b83e1f@syzkaller.appspotmail.com \
--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.