mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
	eddyz87@gmail.com, memxor@gmail.com, tj@kernel.org,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCH bpf v3 0/2] bpf: Fix tracing of kfuncs with implicit args
Date: Thu, 16 Jul 2026 23:20:09 +0000	[thread overview]
Message-ID: <178424400940.1454328.16219271761426595594.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260713235223.1639022-1-ihor.solodrai@linux.dev>

Hello:

This series was applied to bpf/bpf.git (master)
by Eduard Zingerman <eddyz87@gmail.com>:

On Mon, 13 Jul 2026 16:52:21 -0700 you wrote:
> Tejun reported an issue where a BPF program tracing a kfunc with
> KF_IMPLICIT_ARGS can crash the kernel [1]. This is caused by a bug in
> bpf_check_attach_target(): the btf_func_model for such a kfunc is
> computed from a wrong BTF prototype. For more details see the commit
> message of patch #1.
> 
> The second patch adds a selftest that can catch this situation.
> 
> [...]

Here is the summary with links:
  - [bpf,v3,1/2] bpf: Fix tracing of kfuncs with implicit args
    https://git.kernel.org/bpf/bpf/c/3917b1012ee2
  - [bpf,v3,2/2] selftests/bpf: Cover tracing implicit kfunc args
    https://git.kernel.org/bpf/bpf/c/0af15f3057a6

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



      parent reply	other threads:[~2026-07-16 23:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 23:52 Ihor Solodrai
2026-07-13 23:52 ` [PATCH bpf v3 1/2] " Ihor Solodrai
2026-07-13 23:52 ` [PATCH bpf v3 2/2] selftests/bpf: Cover tracing implicit kfunc args Ihor Solodrai
2026-07-16 23: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=178424400940.1454328.16219271761426595594.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=memxor@gmail.com \
    --cc=tj@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
Powered by JetHome