BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Leon Hwang <leon.hwang@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, toke@redhat.com, martin.lau@kernel.org,
	yonghong.song@linux.dev, puranjay@kernel.org,
	xukuohai@huaweicloud.com, eddyz87@gmail.com, iii@linux.ibm.com,
	kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next v8 0/2] bpf: Fix tailcall infinite loop caused by freplace
Date: Tue, 15 Oct 2024 18:40:29 +0000	[thread overview]
Message-ID: <172901762951.1255819.18163538713043138202.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241015150207.70264-1-leon.hwang@linux.dev>

Hello:

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

On Tue, 15 Oct 2024 23:02:05 +0800 you wrote:
> Previously, I addressed a tailcall infinite loop issue related to
> trampolines[0].
> 
> In this patchset, I resolve a similar issue where a tailcall infinite loop
> can occur due to the combination of tailcalls and freplace programs. The
> fix prevents adding extended programs to the prog_array map and blocks the
> extension of a tail callee program with freplace.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v8,1/2] bpf: Prevent tailcall infinite loop caused by freplace
    https://git.kernel.org/bpf/bpf-next/c/d24c6a9d3a9f
  - [bpf-next,v8,2/2] selftests/bpf: Add test to verify tailcall and freplace restrictions
    https://git.kernel.org/bpf/bpf-next/c/5a2ac3844d47

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-15 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 15:02 [PATCH bpf-next v8 0/2] bpf: Fix tailcall infinite loop caused by freplace Leon Hwang
2024-10-15 15:02 ` [PATCH bpf-next v8 1/2] bpf: Prevent " Leon Hwang
2024-10-15 15:02 ` [PATCH bpf-next v8 2/2] selftests/bpf: Add test to verify tailcall and freplace restrictions Leon Hwang
2024-10-15 18:40 ` 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=172901762951.1255819.18163538713043138202.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=iii@linux.ibm.com \
    --cc=kernel-patches-bot@fb.com \
    --cc=leon.hwang@linux.dev \
    --cc=martin.lau@kernel.org \
    --cc=puranjay@kernel.org \
    --cc=toke@redhat.com \
    --cc=xukuohai@huaweicloud.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