BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Quentin Monnet <qmo@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
	yonghong.song@linux.dev, john.fastabend@gmail.com,
	kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
	jolsa@kernel.org, rostedt@goodmis.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] bpftool: Search for tracefs at /sys/kernel/tracing first
Date: Mon, 15 Sep 2025 17:20:06 +0000	[thread overview]
Message-ID: <175795680625.66377.14189607108181766320.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250915134209.36568-1-qmo@kernel.org>

Hello:

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

On Mon, 15 Sep 2025 14:42:09 +0100 you wrote:
> With "bpftool prog tracelog", bpftool prints messages from the trace
> pipe. To do so, it first needs to find the tracefs mount point to open
> the pipe. Bpftool looks at a few "default" locations, including
> /sys/kernel/debug/tracing and /sys/kernel/tracing.
> 
> Some of these locations, namely /tracing and /trace, are not standard.
> They are in the list because some users used to hardcode the tracing
> directory to short names; but we have no compelling reason to look at
> these locations. If we fail to find the tracefs at the default
> locations, we have an additional step to find it by parsing /proc/mounts
> anyway, so it's safe to remove these entries from the list of default
> locations to check.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2] bpftool: Search for tracefs at /sys/kernel/tracing first
    https://git.kernel.org/bpf/bpf-next/c/32d376610bdf

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



      parent reply	other threads:[~2025-09-15 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 13:42 [PATCH bpf-next v2] bpftool: Search for tracefs at /sys/kernel/tracing first Quentin Monnet
2025-09-15 13:53 ` Daniel Borkmann
2025-09-15 17:20 ` 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=175795680625.66377.14189607108181766320.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=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=qmo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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