From: patchwork-bot+netdevbpf@kernel.org
To: chenyuan <chenyuan_fl@163.com>
Cc: bpf@vger.kernel.org, chenyuan@kylinos.cn, qmo@kernel.org,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
emil@etsalapatis.com, ihor.solodrai@linux.dev, kuba@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpftool: Fix inverted tracefs validation when scanning /proc/mounts
Date: Fri, 16 Oct 2026 13:40:11 +0000 [thread overview]
Message-ID: <179215801179.300760.9186201876116142523.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016015057.127061-1-chenyuan_fl@163.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 16 Oct 2026 09:50:57 +0800 you wrote:
> From: Yuan Chen <chenyuan@kylinos.cn>
>
> The /proc/mounts fallback in get_tracefs_pipe() accepts only
> non-tracefs mount points, so a tracefs mounted outside the default
> locations is ignored: bpftool prog tracelog then mounts a second
> tracefs, or exits silently with --nomount. Negate the condition.
>
> [...]
Here is the summary with links:
- [bpf-next] bpftool: Fix inverted tracefs validation when scanning /proc/mounts
https://git.kernel.org/bpf/bpf-next/c/21c755efaab1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-16 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 1:50 [PATCH bpf-next] bpftool: Fix inverted tracefs validation when scanning /proc/mounts chenyuan_fl
2026-10-16 13:40 ` 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=179215801179.300760.9186201876116142523.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=chenyuan@kylinos.cn \
--cc=chenyuan_fl@163.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=qmo@kernel.org \
--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 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.