BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kui-Feng Lee <kuifeng@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, kernel-team@fb.com, xukuohai@huawei.com
Subject: Re: [PATCH bpf-next v8 0/5] Attach a cookie to a tracing program.
Date: Wed, 11 May 2022 01:10:13 +0000	[thread overview]
Message-ID: <165223141333.20219.2489454778876097764.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220510205923.3206889-1-kuifeng@fb.com>

Hello:

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

On Tue, 10 May 2022 13:59:18 -0700 you wrote:
> Allow users to attach a 64-bits cookie to a bpf_link of fentry, fexit,
> or fmod_ret.
> 
> This patchset includes several major changes.
> 
>  - Define struct bpf_tramp_links to replace bpf_tramp_prog.
>    struct bpf_tramp_links collects bpf_links of a trampoline
> 
> [...]

Here is the summary with links:
  - [bpf-next,v8,1/5] bpf, x86: Generate trampolines from bpf_tramp_links
    https://git.kernel.org/bpf/bpf-next/c/f7e0beaf39d3
  - [bpf-next,v8,2/5] bpf, x86: Create bpf_tramp_run_ctx on the caller thread's stack
    https://git.kernel.org/bpf/bpf-next/c/e384c7b7b46d
  - [bpf-next,v8,3/5] bpf, x86: Attach a cookie to fentry/fexit/fmod_ret/lsm.
    https://git.kernel.org/bpf/bpf-next/c/22c1d9a17b82
  - [bpf-next,v8,4/5] libbpf: Assign cookies to links in libbpf.
    https://git.kernel.org/bpf/bpf-next/c/3d5602b6d8b9
  - [bpf-next,v8,5/5] selftest/bpf: The test cses of BPF cookie for fentry/fexit/fmod_ret/lsm.
    https://git.kernel.org/bpf/bpf-next/c/f3273797de13

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



  parent reply	other threads:[~2022-05-11  1:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 20:59 [PATCH bpf-next v8 0/5] Attach a cookie to a tracing program Kui-Feng Lee
2022-05-10 20:59 ` [PATCH bpf-next v8 1/5] bpf, x86: Generate trampolines from bpf_tramp_links Kui-Feng Lee
2022-05-20 20:51   ` Martin KaFai Lau
2022-05-24 22:30     ` Andrii Nakryiko
2022-05-24 23:03       ` Martin KaFai Lau
2022-05-24 23:23         ` Andrii Nakryiko
2022-05-10 20:59 ` [PATCH bpf-next v8 2/5] bpf, x86: Create bpf_tramp_run_ctx on the caller thread's stack Kui-Feng Lee
2022-05-10 20:59 ` [PATCH bpf-next v8 3/5] bpf, x86: Attach a cookie to fentry/fexit/fmod_ret/lsm Kui-Feng Lee
2022-05-10 20:59 ` [PATCH bpf-next v8 4/5] libbpf: Assign cookies to links in libbpf Kui-Feng Lee
2022-05-10 20:59 ` [PATCH bpf-next v8 5/5] selftest/bpf: The test cses of BPF cookie for fentry/fexit/fmod_ret/lsm Kui-Feng Lee
2022-05-11  1:10 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-29 19:20 [PATCH bpf-next v8 0/5] Attach a cookie to a tracing program Kui-Feng Lee

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=165223141333.20219.2489454778876097764.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=kernel-team@fb.com \
    --cc=kuifeng@fb.com \
    --cc=xukuohai@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox