public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev,
	alexei.starovoitov@gmail.com, andrii@kernel.org,
	eddyz87@gmail.com, song@kernel.org, haoluo@google.com,
	yonghong.song@linux.dev, daniel@iogearbox.net,
	kpsingh@kernel.org, sdf@fomichev.me, jolsa@kernel.org,
	john.fastabend@gmail.com, laoar.shao@gmail.com,
	houtao1@huawei.com, xukuohai@huawei.com
Subject: Re: [PATCH bpf v4 0/5] Fixes for bits iterator
Date: Wed, 30 Oct 2024 19:20:34 +0000	[thread overview]
Message-ID: <173031603400.1439165.2937332424790644908.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241030100516.3633640-1-houtao@huaweicloud.com>

Hello:

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

On Wed, 30 Oct 2024 18:05:11 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
> 
> Hi,
> 
> The patch set fixes several issues in bits iterator. Patch #1 fixes the
> kmemleak problem of bits iterator. Patch #2~#3 fix the overflow problem
> of nr_bits. Patch #4 fixes the potential stack corruption when bits
> iterator is used on 32-bit host. Patch #5 adds more test cases for bits
> iterator.
> 
> [...]

Here is the summary with links:
  - [bpf,v4,1/5] bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()
    https://git.kernel.org/bpf/bpf/c/101ccfbabf47
  - [bpf,v4,2/5] bpf: Add bpf_mem_alloc_check_size() helper
    https://git.kernel.org/bpf/bpf/c/62a898b07b83
  - [bpf,v4,3/5] bpf: Check the validity of nr_words in bpf_iter_bits_new()
    https://git.kernel.org/bpf/bpf/c/393397fbdcad
  - [bpf,v4,4/5] bpf: Use __u64 to save the bits in bits iterator
    https://git.kernel.org/bpf/bpf/c/e13393836750
  - [bpf,v4,5/5] selftests/bpf: Add three test cases for bits_iter
    https://git.kernel.org/bpf/bpf/c/ebafc1e535db

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



      parent reply	other threads:[~2024-10-30 19:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30 10:05 [PATCH bpf v4 0/5] Fixes for bits iterator Hou Tao
2024-10-30 10:05 ` [PATCH bpf v4 1/5] bpf: Free dynamically allocated bits in bpf_iter_bits_destroy() Hou Tao
2024-10-30 10:05 ` [PATCH bpf v4 2/5] bpf: Add bpf_mem_alloc_check_size() helper Hou Tao
2024-10-30 10:05 ` [PATCH bpf v4 3/5] bpf: Check the validity of nr_words in bpf_iter_bits_new() Hou Tao
2024-10-30 10:05 ` [PATCH bpf v4 4/5] bpf: Use __u64 to save the bits in bits iterator Hou Tao
2024-10-30 10:05 ` [PATCH bpf v4 5/5] selftests/bpf: Add three test cases for bits_iter Hou Tao
2024-10-30 19:20 ` 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=173031603400.1439165.2937332424790644908.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=houtao1@huawei.com \
    --cc=houtao@huaweicloud.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=laoar.shao@gmail.com \
    --cc=martin.lau@linux.dev \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=xukuohai@huawei.com \
    --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