From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Libo Chen <libo.chen@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: runtime warning after merge of the mm-unstable tree
Date: Tue, 22 Apr 2025 20:57:40 +1000 [thread overview]
Message-ID: <20250422205740.02c4893a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 3222 bytes --]
Hi all,
After merging the mm-unstable tree, today's linux-next build
(powerpcmpseries_le_defconfig) produced this warning:
[ 0.000000][ T0] ------------[ cut here ]------------
[ 0.000000][ T0] WARNING: CPU: 0 PID: 0 at kernel/trace/trace_events.c:596 trace_event_raw_init+0x1b0/0x6d0
[ 0.000000][ T0] Modules linked in:
[ 0.000000][ T0] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.15.0-rc3-05418-g16441530e08c #1 VOLUNTARY
[ 0.000000][ T0] Hardware name: IBM pSeries (emulated by qemu) POWER10 (architected) 0x801200 0xf000006 of:SLOF,HEAD pSeries
[ 0.000000][ T0] NIP: c0000000003efd30 LR: c0000000003f0140 CTR: 0000000000000000
[ 0.000000][ T0] REGS: c0000000028f7940 TRAP: 0700 Not tainted (6.15.0-rc3-05418-g16441530e08c)
[ 0.000000][ T0] MSR: 8000000002021033 <SF,VEC,ME,IR,DR,RI,LE> CR: 44000288 XER: 00000000
[ 0.000000][ T0] CFAR: c0000000003f0144 IRQMASK: 3
[ 0.000000][ T0] GPR00: c0000000003f0140 c0000000028f7be0 c000000001811100 0000000000000000
[ 0.000000][ T0] GPR04: 000000000000005b c000000001617716 0000000000000006 c0000000003efc7c
[ 0.000000][ T0] GPR08: c0000000014dd6a8 ffffffffffffffff 000000000000005b 0000000000000000
[ 0.000000][ T0] GPR12: c0000000003efb80 c000000002aa8000 0000000000000000 00000000019e40b8
[ 0.000000][ T0] GPR16: 000000007e68eef8 0000000000000001 0000000002d500d0 00000000019e3f38
[ 0.000000][ T0] GPR20: 0000000000000093 c000000002654c03 0000000000000000 0000000000000093
[ 0.000000][ T0] GPR24: 0000000000000005 0000000000000000 0000000000000000 0000000000000020
[ 0.000000][ T0] GPR28: 0000000000000000 c000000002656c68 c000000002654b70 00000000000000bb
[ 0.000000][ T0] NIP [c0000000003efd30] trace_event_raw_init+0x1b0/0x6d0
[ 0.000000][ T0] LR [c0000000003f0140] trace_event_raw_init+0x5c0/0x6d0
[ 0.000000][ T0] Call Trace:
[ 0.000000][ T0] [c0000000028f7be0] [c0000000003f0140] trace_event_raw_init+0x5c0/0x6d0 (unreliable)
[ 0.000000][ T0] [c0000000028f7ca0] [c0000000003f2768] event_init+0x68/0x100
[ 0.000000][ T0] [c0000000028f7d10] [c00000000203e62c] trace_event_init+0xfc/0x4ac
[ 0.000000][ T0] [c0000000028f7e00] [c00000000203d4e0] trace_init+0x6c/0x680
[ 0.000000][ T0] [c0000000028f7f30] [c0000000020042f8] start_kernel+0x664/0x964
[ 0.000000][ T0] [c0000000028f7fe0] [c00000000000e99c] start_here_common+0x1c/0x20
[ 0.000000][ T0] Code: 72d60001 7c8407b4 7c7e1a14 41820430 4bfffca9 2c230000 41820010 3920fffe 7929c010 7f7b4838 2c3b0000 41820064 <0fe00000> 73690001 3be00001 40820014
[ 0.000000][ T0] ---[ end trace 0000000000000000 ]---
[ 0.000000][ T0] event sched_skip_cpuset_numa has unsafe dereference of argument 6
[ 0.000000][ T0] print_fmt: "comm=%s pid=%d tgid=%d ngid=%d mem_nodes_allowed=%*pbl", REC->comm, REC->pid, REC->tgid, REC->ngid, __nodemask_pr_numnodes(REC->mem_allowed_ptr), __nodemask_pr_bits(REC->mem_allowed_ptr)
Introduced by commit
516be5b3418e ("sched/numa: add tracepoint that tracks the skipping of numa balancing due to cpuset memory pinning")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-04-22 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 10:57 Stephen Rothwell [this message]
2025-04-22 18:05 ` linux-next: runtime warning after merge of the mm-unstable tree Libo Chen
2025-04-22 23:16 ` Stephen Rothwell
2025-04-22 23:28 ` Steven Rostedt
2025-04-23 6:12 ` Venkat Rao Bagalkote
2025-04-23 14:29 ` Steven Rostedt
2025-04-24 0:04 ` Libo Chen
2025-04-23 5:19 ` Aithal, Srikanth
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=20250422205740.02c4893a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=libo.chen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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