From: patchwork-bot+netdevbpf@kernel.org
To: Nicholas Velten <nicholasfvelten@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, 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+1ea4f564bf6f1f3d1dc4@syzkaller.appspotmail.com
Subject: Re: [PATCH bpf-next v2] bpf: Annotate data races on bpf_lru_node type
Date: Tue, 20 Oct 2026 00:30:06 +0000 [thread overview]
Message-ID: <179245620614.3402121.11443505330541884495.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261019-fix-lru-node-type-kcsan-v2-1-c10a410b3565@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 19 Oct 2026 14:38:20 -0300 you wrote:
> From: Nicholas Velten <nicholasfvelten@gmail.com>
>
> KCSAN reports a data race on bpf_lru_node::type between the LRU list
> rotation and the free path of the common LRU:
>
> BUG: KCSAN: data-race in __bpf_lru_list_rotate / bpf_lru_push_free
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf: Annotate data races on bpf_lru_node type
https://git.kernel.org/bpf/bpf-next/c/f25f6319e248
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-10-20 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 17:38 Nicholas Velten via B4 Relay
2026-10-20 0:30 ` 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=179245620614.3402121.11443505330541884495.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=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=nicholasfvelten@gmail.com \
--cc=song@kernel.org \
--cc=syzbot+1ea4f564bf6f1f3d1dc4@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
all inboxes | Powered by JetHome®