From: Eduard Zingerman <eddyz87@gmail.com>
To: Qianfeng Rong <rongqianfeng@vivo.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
Hao Luo <haoluo@google.com>, Jiri Olsa <jolsa@kernel.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bpf: replace kvfree with kfree for kzalloc memory
Date: Mon, 11 Aug 2025 09:47:41 -0700 [thread overview]
Message-ID: <5cdd264d324de1b78f4fc3768cc20a3ee79336d1.camel@gmail.com> (raw)
In-Reply-To: <d106b3c7-6afb-4e55-b2cc-0354f5db4bde@vivo.com>
On Mon, 2025-08-11 at 21:15 +0800, Qianfeng Rong wrote:
> Hi all,
>
> Sorry, please ignore this patch, because I found that there are still a
> lot of mixed uses of kfree and kvfree in kernel/bpf/verifier.c. Best
> regards, Qianfeng
Using kvfree() in this position was sloppy on my side,
thank you for noticing this.
next prev parent reply other threads:[~2025-08-11 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 12:39 [PATCH] bpf: replace kvfree with kfree for kzalloc memory Qianfeng Rong
2025-08-11 13:15 ` Qianfeng Rong
2025-08-11 16:47 ` Eduard Zingerman [this message]
2025-08-11 13:25 ` Markus Elfring
2025-08-11 16:46 ` Eduard Zingerman
2025-08-12 23:00 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2025-08-26 7:39 [PATCH] bpf: Replace " Feng Yang
2025-08-26 11:43 ` Daniel Borkmann
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=5cdd264d324de1b78f4fc3768cc20a3ee79336d1.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=rongqianfeng@vivo.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.