From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
songliubraving@fb.com, yhs@fb.com, qmo@kernel.org,
chen.dylane@linux.dev, info@starlabs.sg, contact@arnaud-lcm.com
Subject: Re: [PATCHv4 bpf-next 00/12] bpf: Disable preemption in stack map code
Date: Wed, 05 Aug 2026 18:40:21 +0000 [thread overview]
Message-ID: <178595522164.482099.4352769835591488217.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260805092843.516315-1-jolsa@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 5 Aug 2026 11:28:31 +0200 you wrote:
> hi,
> we need to disable preemption for get_perf_callchain and keep it disabled
> as long as we are accessing its returned trace entries buffer.
>
> This patchset refactors both bpf_get_stack and bpf_get_stackid helpers as
> suggested by Andrii [1] before applying the actual preemption fix.
>
> [...]
Here is the summary with links:
- [PATCHv4,bpf-next,01/12] bpf: Factor stackid_init function from __bpf_get_stackid
https://git.kernel.org/bpf/bpf-next/c/15b837759a97
- [PATCHv4,bpf-next,02/12] bpf: Factor stackid_fastpath function from __bpf_get_stackid
https://git.kernel.org/bpf/bpf-next/c/0ca56befcffe
- [PATCHv4,bpf-next,03/12] bpf: Factor stackid_new_bucket from __bpf_get_stackid
https://git.kernel.org/bpf/bpf-next/c/bb4e6f4e1b68
- [PATCHv4,bpf-next,04/12] bpf: Use stack id functions instead of __bpf_get_stackid
https://git.kernel.org/bpf/bpf-next/c/09b3fd6caa0b
- [PATCHv4,bpf-next,05/12] bpf: Disable preemption in bpf_get_stackid
https://git.kernel.org/bpf/bpf-next/c/15f1bd857466
- [PATCHv4,bpf-next,06/12] bpf: Factor callchain_store function from __bpf_get_stack
https://git.kernel.org/bpf/bpf-next/c/cbb99938e793
- [PATCHv4,bpf-next,07/12] bpf: Factor callchain_finalize function from __bpf_get_stack
https://git.kernel.org/bpf/bpf-next/c/014fbe5902dc
- [PATCHv4,bpf-next,08/12] bpf: Remove trace_in argument from __bpf_get_stack
(no matching commit)
- [PATCHv4,bpf-next,09/12] bpf: Clear buf on error in __bpf_get_task_stack
https://git.kernel.org/bpf/bpf-next/c/f5d242825ca4
- [PATCHv4,bpf-next,10/12] bpf: Disable preemption in __bpf_get_stack
(no matching commit)
- [PATCHv4,bpf-next,11/12] bpf: Avoid changing callchain in bpf_get_stack_pe
(no matching commit)
- [PATCHv4,bpf-next,12/12] bpf: Avoid changing callchain in bpf_get_stackid_pe
https://git.kernel.org/bpf/bpf-next/c/a74594607a0b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-05 18:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 9:28 [PATCHv4 bpf-next 00/12] bpf: Disable preemption in stack map code Jiri Olsa
2026-08-05 9:28 ` [PATCHv4 bpf-next 01/12] bpf: Factor stackid_init function from __bpf_get_stackid Jiri Olsa
2026-08-05 9:40 ` sashiko-bot
2026-08-05 9:28 ` [PATCHv4 bpf-next 02/12] bpf: Factor stackid_fastpath " Jiri Olsa
2026-08-05 9:28 ` [PATCHv4 bpf-next 03/12] bpf: Factor stackid_new_bucket " Jiri Olsa
2026-08-05 9:28 ` [PATCHv4 bpf-next 04/12] bpf: Use stack id functions instead of __bpf_get_stackid Jiri Olsa
2026-08-05 9:28 ` [PATCHv4 bpf-next 05/12] bpf: Disable preemption in bpf_get_stackid Jiri Olsa
2026-08-05 9:28 ` [PATCHv4 bpf-next 06/12] bpf: Factor callchain_store function from __bpf_get_stack Jiri Olsa
2026-08-05 9:28 ` [PATCHv4 bpf-next 07/12] bpf: Factor callchain_finalize " Jiri Olsa
2026-08-05 9:28 ` [PATCHv4 bpf-next 08/12] bpf: Remove trace_in argument " Jiri Olsa
2026-08-05 9:28 ` [PATCHv4 bpf-next 09/12] bpf: Clear buf on error in __bpf_get_task_stack Jiri Olsa
2026-08-05 9:28 ` [PATCHv4 bpf-next 10/12] bpf: Disable preemption in __bpf_get_stack Jiri Olsa
2026-08-05 18:34 ` Andrii Nakryiko
2026-08-05 20:29 ` Jiri Olsa
2026-08-05 9:28 ` [PATCHv4 bpf-next 11/12] bpf: Avoid changing callchain in bpf_get_stack_pe Jiri Olsa
2026-08-05 9:28 ` [PATCHv4 bpf-next 12/12] bpf: Avoid changing callchain in bpf_get_stackid_pe Jiri Olsa
2026-08-05 18:36 ` [PATCHv4 bpf-next 00/12] bpf: Disable preemption in stack map code Andrii Nakryiko
2026-08-05 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=178595522164.482099.4352769835591488217.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=chen.dylane@linux.dev \
--cc=contact@arnaud-lcm.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=info@starlabs.sg \
--cc=jolsa@kernel.org \
--cc=martin.lau@linux.dev \
--cc=qmo@kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.