Re: [PATCH] bpf: Always use maximal size for copy_array()

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 23 Dec 2022 10:28:44 -0800 you wrote:
> Instead of counting on prior allocations to have sized allocations to
> the next kmalloc bucket size, always perform a krealloc that is at least
> ksize(dst) in size (which is a no-op), so the size can be correctly
> tracked by all the various allocation size trackers (KASAN,
> __alloc_size, etc).
> 
> Reported-by: Hyunwoo Kim <v4bel@theori.io>
> Link: https://lore.kernel.org/bpf/20221223094551.GA1439509@ubuntu
> Fixes: ceb35b666d42 ("bpf/verifier: Use kmalloc_size_roundup() to match ksize() usage")
> Cc: Alexei Starovoitov <ast@kernel.org>
> Cc: Daniel Borkmann <daniel@iogearbox.net>
> Cc: John Fastabend <john.fastabend@gmail.com>
> Cc: Andrii Nakryiko <andrii@kernel.org>
> Cc: Martin KaFai Lau <martin.lau@linux.dev>
> Cc: Song Liu <song@kernel.org>
> Cc: Yonghong Song <yhs@fb.com>
> Cc: KP Singh <kpsingh@kernel.org>
> Cc: Stanislav Fomichev <sdf@google.com>
> Cc: Hao Luo <haoluo@google.com>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: bpf@vger.kernel.org
> Signed-off-by: Kees Cook <keescook@chromium.org>
> 
> [...]

Here is the summary with links:
  - bpf: Always use maximal size for copy_array()
    https://git.kernel.org/bpf/bpf/c/45435d8da71f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html