All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yafang Shao <laoar.shao@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
	john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
	haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] bpf: Fix issues caused by bpf trampoline
Date: Mon, 24 Apr 2023 21:30:18 +0000	[thread overview]
Message-ID: <168237181860.25354.10356715827184101234.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230424161104.3737-1-laoar.shao@gmail.com>

Hello:

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

On Mon, 24 Apr 2023 16:11:02 +0000 you wrote:
> The panic caused by fentry[1] drives me to write a testcase[2] to check if
> it safe to attach other kernel functions. Unsurprisingly it catches some
> issues. This patchset fixes them.
> 
> [1]. https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=c11bd046485d7bf1ca200db0e7d0bdc4bafdd395
> [2]. https://github.com/laoar/ebpf/tree/main/fentry
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] bpf: Add __rcu_read_{lock,unlock} into btf id deny list
    https://git.kernel.org/bpf/bpf-next/c/a0c109dcafb1
  - [bpf-next,2/2] fork: Rename mm_init to task_mm_init
    (no matching commit)

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



      parent reply	other threads:[~2023-04-24 21:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 16:11 [PATCH bpf-next 0/2] bpf: Fix issues caused by bpf trampoline Yafang Shao
2023-04-24 16:11 ` [PATCH bpf-next 1/2] bpf: Add __rcu_read_{lock,unlock} into btf id deny list Yafang Shao
2023-04-24 16:11 ` [PATCH bpf-next 2/2] fork: Rename mm_init to task_mm_init Yafang Shao
2023-04-24 21:13   ` Alexei Starovoitov
2023-04-27 11:34     ` Yafang Shao
2023-05-02  3:40       ` pahole issue. " Alexei Starovoitov
2023-05-09 15:35         ` Yafang Shao
2023-05-09 17:18           ` Alexei Starovoitov
2023-05-10  5:38             ` Yafang Shao
2023-05-10 13:54               ` Yonghong Song
2023-05-09 18:43         ` Alan Maguire
2023-05-09 21:21           ` Alexei Starovoitov
2023-05-10 13:08             ` Alan Maguire
2023-05-10 15:28               ` Arnaldo Carvalho de Melo
2023-04-24 21:30 ` 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=168237181860.25354.10356715827184101234.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=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=laoar.shao@gmail.com \
    --cc=sdf@google.com \
    --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.