BPF List
 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, song@kernel.org,
	haoluo@google.com, yonghong.song@linux.dev, daniel@iogearbox.net,
	kpsingh@kernel.org, sdf@google.com, jolsa@kernel.org,
	john.fastabend@gmail.com, xrivendell7@gmail.com,
	houtao1@huawei.com
Subject: Re: [PATCH bpf-next v3 0/5] bpf: Fix warnings in kvmalloc_node()
Date: Fri, 15 Dec 2023 22:00:24 +0000	[thread overview]
Message-ID: <170267762437.4416.11863868567400479013.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231215100708.2265609-1-houtao@huaweicloud.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Fri, 15 Dec 2023 18:07:03 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
> 
> Hi,
> 
> The patch set aims to fix the warnings in kvmalloc_node() when passing
> an abnormally big cnt during multiple kprobes/uprobes attachment.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/5] bpf: Limit the number of uprobes when attaching program to multiple uprobes
    https://git.kernel.org/bpf/bpf-next/c/8b2efe51ba85
  - [bpf-next,v3,2/5] bpf: Limit the number of kprobes when attaching program to multiple kprobes
    https://git.kernel.org/bpf/bpf-next/c/d6d1e6c17cab
  - [bpf-next,v3,3/5] selftests/bpf: Add test for abnormal cnt during multi-uprobe attachment
    https://git.kernel.org/bpf/bpf-next/c/0d83786f5661
  - [bpf-next,v3,4/5] selftests/bpf: Don't use libbpf_get_error() in kprobe_multi_test
    https://git.kernel.org/bpf/bpf-next/c/00cdcd2900bd
  - [bpf-next,v3,5/5] selftests/bpf: Add test for abnormal cnt during multi-kprobe attachment
    https://git.kernel.org/bpf/bpf-next/c/1467affd16b2

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



      parent reply	other threads:[~2023-12-15 22:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15 10:07 [PATCH bpf-next v3 0/5] bpf: Fix warnings in kvmalloc_node() Hou Tao
2023-12-15 10:07 ` [PATCH bpf-next v3 1/5] bpf: Limit the number of uprobes when attaching program to multiple uprobes Hou Tao
2023-12-15 10:07 ` [PATCH bpf-next v3 2/5] bpf: Limit the number of kprobes when attaching program to multiple kprobes Hou Tao
2023-12-15 10:07 ` [PATCH bpf-next v3 3/5] selftests/bpf: Add test for abnormal cnt during multi-uprobe attachment Hou Tao
2023-12-15 10:07 ` [PATCH bpf-next v3 4/5] selftests/bpf: Don't use libbpf_get_error() in kprobe_multi_test Hou Tao
2023-12-15 10:07 ` [PATCH bpf-next v3 5/5] selftests/bpf: Add test for abnormal cnt during multi-kprobe attachment Hou Tao
2023-12-15 21:15 ` [PATCH bpf-next v3 0/5] bpf: Fix warnings in kvmalloc_node() Andrii Nakryiko
2023-12-15 22:00 ` 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=170267762437.4416.11863868567400479013.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=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=martin.lau@linux.dev \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=xrivendell7@gmail.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