BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: luyun <luyun_611@163.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
	song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
	emil@etsalapatis.com, ihor.solodrai@linux.dev, yatsenko@meta.com,
	bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v7 0/4] bpf: Fix task work scheduling races
Date: Fri, 16 Oct 2026 00:50:13 +0000	[thread overview]
Message-ID: <179211181351.4179746.9574390540438023653.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261012061915.231254-1-luyun_611@163.com>

Hello:

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

On Mon, 12 Oct 2026 14:19:11 +0800 you wrote:
> From: Yun Lu <luyun@kylinos.cn>
> 
> This series fixes two races in the bpf_task_work scheduling kfuncs and
> adds a regression test for each.  Each fix is followed by its test.
> 
> Patch 1 captures the task pointer before publishing the callback, which
> can clear ctx->task before the scheduling handler attempts cancellation.
> The existing RCU read-side section keeps the captured task alive because
> bpf_task_release() is put_task_struct_rcu_user().
> 
> [...]

Here is the summary with links:
  - [bpf-next,v7,1/4] bpf: Fix NULL task dereference in task work cancellation
    https://git.kernel.org/bpf/bpf-next/c/c961f7b41a10
  - [bpf-next,v7,2/4] selftests/bpf: Add task work cancellation race test
    https://git.kernel.org/bpf/bpf-next/c/6674dcb2785d
  - [bpf-next,v7,3/4] bpf: Prevent task work context reuse while irq_work is busy
    https://git.kernel.org/bpf/bpf-next/c/a36d9afe8d92
  - [bpf-next,v7,4/4] selftests/bpf: Add task work BUSY window test
    https://git.kernel.org/bpf/bpf-next/c/33b2c64f073c

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-10-16  0:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12  6:19 [PATCH bpf-next v7 0/4] bpf: Fix task work scheduling races Yun Lu
2026-10-12  6:19 ` [PATCH bpf-next v7 1/4] bpf: Fix NULL task dereference in task work cancellation Yun Lu
2026-10-12  6:19 ` [PATCH bpf-next v7 2/4] selftests/bpf: Add task work cancellation race test Yun Lu
2026-10-12  6:19 ` [PATCH bpf-next v7 3/4] bpf: Prevent task work context reuse while irq_work is busy Yun Lu
2026-10-12  6:34   ` sashiko-bot
2026-10-13  6:17     ` luyun
2026-10-12  6:19 ` [PATCH bpf-next v7 4/4] selftests/bpf: Add task work BUSY window test Yun Lu
2026-10-16  0:50 ` 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=179211181351.4179746.9574390540438023653.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=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jolsa@kernel.org \
    --cc=luyun_611@163.com \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=song@kernel.org \
    --cc=yatsenko@meta.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