From: patchwork-bot+netdevbpf@kernel.org
To: Lorenz Bauer <lmb@isovalent.com>
Cc: leitao@debian.org, 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, shakeel.butt@linux.dev,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf] btf: fix virt_to_phys warning on arm64 when mmapping vmlinux
Date: Thu, 17 Jul 2025 19:50:06 +0000 [thread overview]
Message-ID: <175278180651.2055348.12385131153368330090.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250717-vmlinux-mmap-pa-symbol-v1-1-970be6681158@isovalent.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 17 Jul 2025 17:49:49 +0100 you wrote:
> Breno Leitao reports that arm64 emits the following warning:
>
> [ 58.896157] virt_to_phys used for non-linear address: 000000009fea9737
> (__start_BTF+0x0/0x685530)
> [ 23.988669] WARNING: CPU: 25 PID: 1442 at arch/arm64/mm/physaddr.c:15
> __virt_to_phys (arch/arm64/mm/physaddr.c:?)
>
> [...]
Here is the summary with links:
- [bpf] btf: fix virt_to_phys warning on arm64 when mmapping vmlinux
https://git.kernel.org/bpf/bpf/c/2e2713ae1a05
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:[~2025-07-17 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 16:49 [PATCH bpf] btf: fix virt_to_phys warning on arm64 when mmapping vmlinux Lorenz Bauer
2025-07-17 19:50 ` 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=175278180651.2055348.12385131153368330090.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=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@isovalent.com \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=shakeel.butt@linux.dev \
--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