All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
	syzbot+958967f249155967d42a@syzkaller.appspotmail.com
Subject: Re: [PATCH bpf-next v2 1/2] bpf: Silence a warning in btf_type_id_size()
Date: Tue, 30 May 2023 22:40:20 +0000	[thread overview]
Message-ID: <168548642000.11166.404309143613379286.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230530205029.264910-1-yhs@fb.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Tue, 30 May 2023 13:50:29 -0700 you wrote:
> syzbot reported a warning in [1] with the following stacktrace:
>   WARNING: CPU: 0 PID: 5005 at kernel/bpf/btf.c:1988 btf_type_id_size+0x2d9/0x9d0 kernel/bpf/btf.c:1988
>   ...
>   RIP: 0010:btf_type_id_size+0x2d9/0x9d0 kernel/bpf/btf.c:1988
>   ...
>   Call Trace:
>    <TASK>
>    map_check_btf kernel/bpf/syscall.c:1024 [inline]
>    map_create+0x1157/0x1860 kernel/bpf/syscall.c:1198
>    __sys_bpf+0x127f/0x5420 kernel/bpf/syscall.c:5040
>    __do_sys_bpf kernel/bpf/syscall.c:5162 [inline]
>    __se_sys_bpf kernel/bpf/syscall.c:5160 [inline]
>    __x64_sys_bpf+0x79/0xc0 kernel/bpf/syscall.c:5160
>    do_syscall_x64 arch/x86/entry/common.c:50 [inline]
>    do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
>    entry_SYSCALL_64_after_hwframe+0x63/0xcd
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/2] bpf: Silence a warning in btf_type_id_size()
    https://git.kernel.org/bpf/bpf-next/c/e6c2f594ed96
  - [bpf-next,v2,2/2] selftests/bpf: Add a test where map key_type_id with decl_tag type
    https://git.kernel.org/bpf/bpf-next/c/e38096d95f4d

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



      parent reply	other threads:[~2023-05-30 22:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 20:50 [PATCH bpf-next v2 1/2] bpf: Silence a warning in btf_type_id_size() Yonghong Song
2023-05-30 20:50 ` [PATCH bpf-next v2 2/2] selftests/bpf: Add a test where map key_type_id with decl_tag type Yonghong Song
2023-05-30 22: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=168548642000.11166.404309143613379286.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=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    --cc=syzbot+958967f249155967d42a@syzkaller.appspotmail.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 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.