lkml.org 
[lkml]   [2022]   [Jan]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: linux-next: runtime warning in next-20220125
On Tue, 25 Jan 2022 16:21:46 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
>
> On Tue, 25 Jan 2022 16:05:05 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > My qemu boot test of a powerpc pseries_le_defconfig kernel produces the
> > following trace:
> >
> > ------------[ cut here ]------------
> > WARNING: CPU: 0 PID: 0 at kernel/trace/trace_events.c:417 trace_event_raw_init+0x194/0x730
> > Modules linked in:
> > CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.17.0-rc1 #2
> > NIP: c0000000002bdbb4 LR: c0000000002bdcb0 CTR: c0000000002bdb70
> >
> > I have no idea what has caused this :-( Maybe commit
> >
> > 5544d5318802 ("SUNRPC: Same as SVC_RQST_ENDPOINT, but without the xid")
>
> Actually, reverting commits
>
> 6ff851d98af8 ("SUNRPC: Improve sockaddr handling in the svc_xprt_create_error trace point")
> 5544d5318802 ("SUNRPC: Same as SVC_RQST_ENDPOINT, but without the xid")
> e2d3613db12a ("SUNRPC: Record endpoint information in trace log")
>
> makes the warning go away.
>

We added a new way to save items on the ring buffer, but did not update the
safety checks to know about them. I'll fix this shortly.

-- Steve


\
 
 \ /
  Last update: 2022-01-25 16:14    [W:0.070 / U:0.416 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site