From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, kafai@fb.com, yhs@fb.com,
andrii@kernel.org, daniel@iogearbox.net
Subject: Re: [PATCH bpf v3 0/3] Don't reinit map value in prealloc_lru_pop
Date: Wed, 10 Aug 2022 02:00:14 +0000 [thread overview]
Message-ID: <166009681487.29831.12016451715348052623.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220809213033.24147-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 9 Aug 2022 23:30:30 +0200 you wrote:
> Fix for a bug in prealloc_lru_pop spotted while reading the code, then a test +
> example that checks whether it is fixed.
>
> Changelog:
> ----------
> v2 -> v3:
> v2: https://lore.kernel.org/bpf/20220809140615.21231-1-memxor@gmail.com
>
> [...]
Here is the summary with links:
- [bpf,v3,1/3] bpf: Allow calling bpf_prog_test kfuncs in tracing programs
https://git.kernel.org/bpf/bpf/c/1f0752628e76
- [bpf,v3,2/3] bpf: Don't reinit map value in prealloc_lru_pop
https://git.kernel.org/bpf/bpf/c/275c30bcee66
- [bpf,v3,3/3] selftests/bpf: Add test for prealloc_lru_pop bug
https://git.kernel.org/bpf/bpf/c/de7b9927105b
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:[~2022-08-10 2:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 21:30 [PATCH bpf v3 0/3] Don't reinit map value in prealloc_lru_pop Kumar Kartikeya Dwivedi
2022-08-09 21:30 ` [PATCH bpf v3 1/3] bpf: Allow calling bpf_prog_test kfuncs in tracing programs Kumar Kartikeya Dwivedi
2022-08-09 21:30 ` [PATCH bpf v3 2/3] bpf: Don't reinit map value in prealloc_lru_pop Kumar Kartikeya Dwivedi
2022-08-09 22:29 ` Martin KaFai Lau
2022-08-10 0:49 ` Alexei Starovoitov
2022-08-10 0:51 ` Kumar Kartikeya Dwivedi
2022-08-10 0:58 ` Alexei Starovoitov
2022-08-09 21:30 ` [PATCH bpf v3 3/3] selftests/bpf: Add test for prealloc_lru_pop bug Kumar Kartikeya Dwivedi
2022-08-10 2:00 ` 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=166009681487.29831.12016451715348052623.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=kafai@fb.com \
--cc=memxor@gmail.com \
--cc=yhs@fb.com \
/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