From: patchwork-bot+netdevbpf@kernel.org
To: Quanye Yang <quanyeyang@proton.me>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
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, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+44044637ef892e79ca2b@syzkaller.appspotmail.com,
ihor.solodrai@linux.dev
Subject: Re: [PATCH v3] bpf: Annotate bpf_obj_memcpy with data_race
Date: Sun, 23 Aug 2026 19:40:05 +0000 [thread overview]
Message-ID: <178751400564.2127284.2628420937760907856.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260822-bpf-kcsan-obj-memcpy-v3-1-4227b2edd8b4@proton.me>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Sat, 22 Aug 2026 14:55:33 +0800 you wrote:
> From: Quanye Yang <quanyeyang@proton.me>
>
> syzbot reported KCSAN write-write races when two tasks concurrently
> update the same map value. Both accesses reach the ordinary memcpy()
> paths in bpf_obj_memcpy() through copy_map_value().
>
> Unlocked in-place updates of published map values are intentionally not
> serialized and may produce torn values. Callers requiring consistency
> must provide synchronization appropriate for the map type.
> bpf_long_memcpy() already annotates the same behavior for long-aligned
> copies.
>
> [...]
Here is the summary with links:
- [v3] bpf: Annotate bpf_obj_memcpy with data_race
https://git.kernel.org/bpf/bpf-next/c/5e289c5a4a52
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:[~2026-08-23 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 6:55 [PATCH v3] bpf: Annotate bpf_obj_memcpy with data_race Quanye Yang via B4 Relay
2026-08-23 19:40 ` 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=178751400564.2127284.2628420937760907856.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=quanyeyang@proton.me \
--cc=song@kernel.org \
--cc=syzbot+44044637ef892e79ca2b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox