BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	ihor.solodrai@pm.me, bpf@vger.kernel.org, kafai@fb.com,
	songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com,
	kpsingh@chromium.org, sdf@fomichev.me, haoluo@google.com
Subject: Re: [PATCH bpf-next 1/2] selftests/bpf: Fix uprobe consumer test
Date: Wed, 25 Sep 2024 10:00:33 +0000	[thread overview]
Message-ID: <172725843324.522662.7812055814094907335.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240924110731.2644249-1-jolsa@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Tue, 24 Sep 2024 13:07:30 +0200 you wrote:
> With newly merged code the uprobe behaviour is slightly different
> and affects uprobe consumer test.
> 
> We no longer need to check if the uprobe object is still preserved
> after removing last uretprobe, because it stays as long as there's
> pending/installed uretprobe instance.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] selftests/bpf: Fix uprobe consumer test
    https://git.kernel.org/bpf/bpf-next/c/510c654dfa3b
  - [bpf-next,2/2] selftests/bpf: Bail out quickly from failing consumer test
    https://git.kernel.org/bpf/bpf-next/c/9eac650cd120

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



      parent reply	other threads:[~2024-09-25 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24 11:07 [PATCH bpf-next 1/2] selftests/bpf: Fix uprobe consumer test Jiri Olsa
2024-09-24 11:07 ` [PATCH bpf-next 2/2] selftests/bpf: Bail out quickly from failing " Jiri Olsa
2024-09-24 17:11 ` [PATCH bpf-next 1/2] selftests/bpf: Fix uprobe " Ihor Solodrai
2024-09-25 10:00 ` 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=172725843324.522662.7812055814094907335.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=ihor.solodrai@pm.me \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kafai@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=sdf@fomichev.me \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox