From: Greg KH <gregkh@linuxfoundation.org>
To: Devaansh Kumar <devaanshk840@gmail.com>
Cc: sashal@kernel.org, stable@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH] bpf: Remove tracing program restriction on map types
Date: Tue, 15 Apr 2025 15:19:25 +0200 [thread overview]
Message-ID: <2025041517-semicolon-aloft-9910@gregkh> (raw)
In-Reply-To: <20250415130910.2326537-1-devaanshk840@gmail.com>
On Tue, Apr 15, 2025 at 06:39:07PM +0530, Devaansh Kumar wrote:
> [ Upstream commit 96da3f7d489d11b43e7c1af90d876b9a2492cca8 ]
>
> The hash map is now fully converted to bpf_mem_alloc. Its implementation is not
> allocating synchronously and not calling call_rcu() directly. It's now safe to
> use non-preallocated hash maps in all types of tracing programs including
> BPF_PROG_TYPE_PERF_EVENT that runs out of NMI context.
>
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Acked-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
> Acked-by: Andrii Nakryiko <andrii@kernel.org>
> Link: https://lore.kernel.org/bpf/20220902211058.60789-13-alexei.starovoitov@gmail.com
> Signed-off-by: Devaansh Kumar <devaanshk840@gmail.com>
> ---
> kernel/bpf/verifier.c | 29 -----------------------------
> 1 file changed, 29 deletions(-)
what kernel tree(s) is this for?
next prev parent reply other threads:[~2025-04-15 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 13:09 Devaansh Kumar
2025-04-15 13:19 ` Greg KH [this message]
2025-04-15 13:25 ` Devaansh Kumar
2025-04-15 15:01 ` Alexei Starovoitov
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=2025041517-semicolon-aloft-9910@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=devaanshk840@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=sashal@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
/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®