public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, martin.lau@kernel.org, eddyz87@gmail.com,
	paulmck@kernel.org, rostedt@goodmis.org, kkd@meta.com,
	kernel-team@meta.com
Subject: Re: [PATCH bpf v4 0/1] Fix bpf_link grace period wait for tracepoints
Date: Tue, 31 Mar 2026 23:10:07 +0000	[thread overview]
Message-ID: <177499860704.2983413.11566673938472181354.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260331211021.1632902-1-memxor@gmail.com>

Hello:

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

On Tue, 31 Mar 2026 23:10:19 +0200 you wrote:
> A recent change to non-faultable tracepoints switched from
> preempt-disabled critical sections to SRCU-fast, which breaks
> assumptions in the bpf_link_free() path. Use call_srcu() to fix the
> breakage.
> 
> Changelog:
> 
> [...]

Here is the summary with links:
  - [bpf,v4,1/1] bpf: Fix grace period wait for tracepoint bpf_link
    https://git.kernel.org/bpf/bpf/c/c76fef7dcd93

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-03-31 23:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 21:10 [PATCH bpf v4 0/1] Fix bpf_link grace period wait for tracepoints Kumar Kartikeya Dwivedi
2026-03-31 21:10 ` [PATCH bpf v4 1/1] bpf: Fix grace period wait for tracepoint bpf_link Kumar Kartikeya Dwivedi
2026-03-31 21:23   ` Steven Rostedt
2026-03-31 23:10 ` 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=177499860704.2983413.11566673938472181354.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=kernel-team@meta.com \
    --cc=kkd@meta.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=rostedt@goodmis.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