From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
Networking <netdev@vger.kernel.org>
Cc: Yonghong Song <yonghong.song@linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: boot warning from the bpf-next tree
Date: Wed, 13 Sep 2023 13:34:36 +1000 [thread overview]
Message-ID: <20230913133436.0eeec4cb@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 3301 bytes --]
Hi all,
Today's linux-next boot tests (powerpc pseries_le_defconfig) produced
this warning:
------------[ cut here ]------------
bpf_mem_cache[0]: unexpected object size 16, expect 96
WARNING: CPU: 0 PID: 1 at kernel/bpf/memalloc.c:500 bpf_mem_alloc_init+0x410/0x440
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.6.0-rc1-04964-g2e08ed1d459f #1
Hardware name: IBM pSeries (emulated by qemu) POWER8 (raw) 0x4d0200 0xf000004 of:SLOF,HEAD pSeries
NIP: c0000000003c0890 LR: c0000000003c088c CTR: 0000000000000000
REGS: c000000004783890 TRAP: 0700 Not tainted (6.6.0-rc1-04964-g2e08ed1d459f)
MSR: 8000000002029033 <SF,VEC,EE,ME,IR,DR,RI,LE> CR: 24000280 XER: 00000000
CFAR: c00000000014cfa0 IRQMASK: 0
GPR00: c0000000003c088c c000000004783b30 c000000001578c00 0000000000000036
GPR04: 0000000000000000 c000000002667e18 0000000000000001 0000000000000000
GPR08: c000000002667ce0 0000000000000001 0000000000000000 0000000044000280
GPR12: 0000000000000000 c000000002b00000 c000000000011188 0000000000000060
GPR16: c0000000011f9a30 c000000002920f68 c0000000021fac40 c0000000021fac40
GPR20: c000000002a3ed88 c000000002921560 c0000000014867f0 c00000000291ccd8
GPR24: 0000000000000000 0000000000000000 0000000000000000 0000000000000010
GPR28: c0000000011f9a30 0000000000000000 000000000000000b c00000007fc9ac40
NIP [c0000000003c0890] bpf_mem_alloc_init+0x410/0x440
LR [c0000000003c088c] bpf_mem_alloc_init+0x40c/0x440
Call Trace:
[c000000004783b30] [c0000000003c088c] bpf_mem_alloc_init+0x40c/0x440 (unreliable)
[c000000004783c20] [c00000000203d0c0] bpf_global_ma_init+0x5c/0x9c
[c000000004783c50] [c000000000010bc0] do_one_initcall+0x80/0x300
[c000000004783d20] [c000000002004978] kernel_init_freeable+0x30c/0x3b4
[c000000004783df0] [c0000000000111b0] kernel_init+0x30/0x1a0
[c000000004783e50] [c00000000000debc] ret_from_kernel_user_thread+0x14/0x1c
--- interrupt: 0 at 0x0
NIP: 0000000000000000 LR: 0000000000000000 CTR: 0000000000000000
REGS: c000000004783e80 TRAP: 0000 Not tainted (6.6.0-rc1-04964-g2e08ed1d459f)
MSR: 0000000000000000 <> CR: 00000000 XER: 00000000
CFAR: 0000000000000000 IRQMASK: 0
GPR00: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR04: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR12: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR24: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR28: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
NIP [0000000000000000] 0x0
LR [0000000000000000] 0x0
--- interrupt: 0
Code: 3b000000 4bfffcbc 78650020 3c62ffe7 39200001 3d420130 7cc607b4 7ba40020 386382f0 992a1e24 4bd8c631 60000000 <0fe00000> 4bffff40 ea410080 3860fff4
---[ end trace 0000000000000000 ]---
Presumably related to commit
41a5db8d8161 ("bpf: Add support for non-fix-size percpu mem allocation")
(or other commist in that series) from the bpf-next tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-09-13 3:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 3:34 Stephen Rothwell [this message]
2023-09-13 4:59 ` linux-next: boot warning from the bpf-next tree Stephen Rothwell
2023-09-13 7:56 ` Hou Tao
2023-09-13 22:19 ` Stephen Rothwell
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=20230913133436.0eeec4cb@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.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