From: Jiri Olsa <olsajiri@gmail.com>
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, Martin KaFai Lau <martin.lau@linux.dev>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>, Song Liu <song@kernel.org>,
Hao Luo <haoluo@google.com>,
Yonghong Song <yonghong.song@linux.dev>,
Daniel Borkmann <daniel@iogearbox.net>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>,
John Fastabend <john.fastabend@gmail.com>,
xingwei lee <xrivendell7@gmail.com>,
houtao1@huawei.com
Subject: Re: [PATCH bpf-next v2 0/4] bpf: Fix warnings in kvmalloc_node()
Date: Wed, 13 Dec 2023 15:42:54 +0100 [thread overview]
Message-ID: <ZXnC7iCNL4K9J_9R@krava> (raw)
In-Reply-To: <20231213112531.3775079-1-houtao@huaweicloud.com>
On Wed, Dec 13, 2023 at 07:25:27PM +0800, Hou Tao 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.
>
> Patch #1 and #2 fix the warning by limiting the maximal number of
> uprobes/kprobes. Patch #3 and #4 add tests to ensure these warnings are
> fixed.
>
> Please see individual patches for more details. Comments are always
> welcome.
>
> Change Log:
> v2:
> * limit the number of uprobes/kprobes instead of suppressing the
> out-of-memory warning message (Alexei)
> * provide a faked non-zero offsets to simplify the multiple uprobe
> test (Jiri)
>
> v1: https://lore.kernel.org/bpf/20231211112843.4147157-1-houtao@huaweicloud.com/
>
> Hou Tao (4):
> bpf: Limit the number of uprobes when attaching program to multiple
> uprobes
> bpf: Limit the number of kprobes when attaching program to multiple
> kprobes
> selftests/bpf: Add test for abnormal cnt during multi-uprobe
> attachment
> selftests/bpf: Add test for abnormal cnt during multi-kprobe
> attachment
>
> kernel/trace/bpf_trace.c | 7 ++--
> .../bpf/prog_tests/kprobe_multi_test.c | 14 ++++++++
> .../bpf/prog_tests/uprobe_multi_test.c | 33 ++++++++++++++++++-
> 3 files changed, 51 insertions(+), 3 deletions(-)
with one minor comment, for the patchset
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
>
> --
> 2.29.2
>
prev parent reply other threads:[~2023-12-13 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 11:25 [PATCH bpf-next v2 0/4] bpf: Fix warnings in kvmalloc_node() Hou Tao
2023-12-13 11:25 ` [PATCH bpf-next v2 1/4] bpf: Limit the number of uprobes when attaching program to multiple uprobes Hou Tao
2023-12-13 11:25 ` [PATCH bpf-next v2 2/4] bpf: Limit the number of kprobes when attaching program to multiple kprobes Hou Tao
2023-12-13 23:32 ` Andrii Nakryiko
2023-12-14 1:00 ` Hou Tao
2023-12-13 11:25 ` [PATCH bpf-next v2 3/4] selftests/bpf: Add test for abnormal cnt during multi-uprobe attachment Hou Tao
2023-12-13 14:43 ` Jiri Olsa
2023-12-14 1:02 ` Hou Tao
2023-12-13 11:25 ` [PATCH bpf-next v2 4/4] selftests/bpf: Add test for abnormal cnt during multi-kprobe attachment Hou Tao
2023-12-13 23:33 ` Andrii Nakryiko
2023-12-14 1:44 ` Hou Tao
2023-12-14 4:26 ` Andrii Nakryiko
2023-12-13 14:42 ` Jiri Olsa [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=ZXnC7iCNL4K9J_9R@krava \
--to=olsajiri@gmail.com \
--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=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 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.