public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jordan Rome <jordalgo@meta.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next] bpf: add crosstask check to __bpf_get_stack
Date: Fri, 10 Nov 2023 19:10:25 +0000	[thread overview]
Message-ID: <169964342509.26701.16290991235531133661.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231108112334.3433136-1-jordalgo@meta.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Wed, 8 Nov 2023 03:23:34 -0800 you wrote:
> Currently get_perf_callchain only supports user stack walking for
> the current task. Passing the correct *crosstask* param will return
> 0 frames if the task passed to __bpf_get_stack isn't the current
> one instead of a single incorrect frame/address. This change
> passes the correct *crosstask* param but also does a preemptive
> check in __bpf_get_stack if the task is current and returns
> -EOPNOTSUPP if it is not.
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next] bpf: add crosstask check to __bpf_get_stack
    https://git.kernel.org/bpf/bpf-next/c/b8e3a87a627b

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



      reply	other threads:[~2023-11-10 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 11:23 [PATCH v2 bpf-next] bpf: add crosstask check to __bpf_get_stack Jordan Rome
2023-11-10 19: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=169964342509.26701.16290991235531133661.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=jordalgo@meta.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@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