mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hou Tao <houtao@huaweicloud.com>
To: "Byeonguk Jeong" <jungbu2855@gmail.com>,
	"Toke Høiland-Jørgensen" <toke@kernel.org>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Yonghong Song" <yonghong.song@linux.dev>
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v2 bpf 2/2] selftests/bpf: Add test for trie_get_next_key()
Date: Tue, 29 Oct 2024 09:33:02 +0800	[thread overview]
Message-ID: <b91763b5-9c02-525d-db8a-ff0da5cbdb69@huaweicloud.com> (raw)
In-Reply-To: <Zxx4ep78tsbeWPVM@localhost.localdomain>



On 10/26/2024 1:04 PM, Byeonguk Jeong wrote:
> Add a test for out-of-bounds write in trie_get_next_key() when a full
> path from root to leaf exists and bpf_map_get_next_key() is called
> with the leaf node. It may crashes the kernel on failure, so please
> run in a VM.
>
> Signed-off-by: Byeonguk Jeong <jungbu2855@gmail.com>
> ---
> v1 -> v2:
>   - Fixed a build error.
>   - Removed unnecessary comments about crash-on-failure warning.
>   - Fix a variable to be initialized before using it.
> ---

Acked-by: Hou Tao <houtao1@huawei.com>


  reply	other threads:[~2024-10-29  1:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26  5:02 [PATCH v2 bpf 1/2] bpf: Fix out-of-bounds write in trie_get_next_key() Byeonguk Jeong
2024-10-26  5:04 ` [PATCH v2 bpf 2/2] selftests/bpf: Add test for trie_get_next_key() Byeonguk Jeong
2024-10-29  1:33   ` Hou Tao [this message]
2024-10-29  1:32 ` [PATCH v2 bpf 1/2] bpf: Fix out-of-bounds write in trie_get_next_key() Hou Tao
2024-10-29 20:50 ` patchwork-bot+netdevbpf

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=b91763b5-9c02-525d-db8a-ff0da5cbdb69@huaweicloud.com \
    --to=houtao@huaweicloud.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jungbu2855@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toke@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 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®