[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221029024444.gonna.633-kees@kernel.org>
Date: Fri, 28 Oct 2022 19:54:29 -0700
From: Kees Cook <keescook@...omium.org>
To: Alexei Starovoitov <ast@...nel.org>
Cc: Kees Cook <keescook@...omium.org>,
Daniel Borkmann <daniel@...earbox.net>,
John Fastabend <john.fastabend@...il.com>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>,
Song Liu <song@...nel.org>, Yonghong Song <yhs@...com>,
KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...gle.com>,
Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
linux-kernel@...r.kernel.org, bpf@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: [PATCH bpf-next v2 0/3] bpf/verifier: Use kmalloc_size_roundup() to match ksize() usage
v2:
- split up patch into logical changes
- simplify copy_array, which can use ksize() directly
v1: https://lore.kernel.org/all/20221018090550.never.834-kees@kernel.org/
Hi,
Here's the next version of removing the BPF verifier's dependency on the
side-effects of ksize(), so we can remove the special handling needed
for KASAN, UBSAN_BOUNDS, nor FORTIFY_SOURCE in ksize().
Thanks,
-Kees
Kees Cook (3):
bpf/verifier: Fix potential memory leak in array reallocation
bpf/verifier: Use kmalloc_size_roundup() to match ksize() usage
bpf/verifier: Take advantage of full allocation sizes
kernel/bpf/verifier.c | 44 ++++++++++++++++++++++++++++---------------
1 file changed, 29 insertions(+), 15 deletions(-)
--
2.34.1
Powered by blists - more mailing lists