From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@google.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
haoluo@google.com, jolsa@kernel.org
Subject: Re: [PATCH bpf-next 1/2] selftests/bpf: Add reproducer for decl_tag in func_proto argument
Date: Thu, 24 Nov 2022 00:00:16 +0000 [thread overview]
Message-ID: <166924801670.22285.7312876485034854827.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221123035422.872531-1-sdf@google.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 22 Nov 2022 19:54:21 -0800 you wrote:
> It should trigger a WARN_ON_ONCE in btf_type_id_size.
>
> RIP: 0010:btf_type_id_size+0x8bd/0x940 kernel/bpf/btf.c:1952
> btf_func_proto_check kernel/bpf/btf.c:4506 [inline]
> btf_check_all_types kernel/bpf/btf.c:4734 [inline]
> btf_parse_type_sec+0x1175/0x1980 kernel/bpf/btf.c:4763
> btf_parse kernel/bpf/btf.c:5042 [inline]
> btf_new_fd+0x65a/0xb00 kernel/bpf/btf.c:6709
> bpf_btf_load+0x6f/0x90 kernel/bpf/syscall.c:4342
> __sys_bpf+0x50a/0x6c0 kernel/bpf/syscall.c:5034
> __do_sys_bpf kernel/bpf/syscall.c:5093 [inline]
> __se_sys_bpf kernel/bpf/syscall.c:5091 [inline]
> __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5091
> do_syscall_64+0x54/0x70 arch/x86/entry/common.c:48
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] selftests/bpf: Add reproducer for decl_tag in func_proto argument
https://git.kernel.org/bpf/bpf-next/c/8e898aaa733e
- [bpf-next,2/2] bpf: prevent decl_tag from being referenced in func_proto arg
https://git.kernel.org/bpf/bpf-next/c/f17472d45996
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:[~2022-11-24 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 3:54 [PATCH bpf-next 1/2] selftests/bpf: Add reproducer for decl_tag in func_proto argument Stanislav Fomichev
2022-11-23 3:54 ` [PATCH bpf-next 2/2] bpf: prevent decl_tag from being referenced in func_proto arg Stanislav Fomichev
2022-11-23 19:40 ` Yonghong Song
2022-11-24 0:02 ` Daniel Borkmann
2022-11-23 19:40 ` [PATCH bpf-next 1/2] selftests/bpf: Add reproducer for decl_tag in func_proto argument Yonghong Song
2022-11-24 0: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=166924801670.22285.7312876485034854827.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=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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