[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220125162146.13872bdb@canb.auug.org.au>
Date: Tue, 25 Jan 2022 16:21:46 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Chuck Lever <chuck.lever@...cle.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Anna Schumaker <Anna.Schumaker@...app.com>,
Trond Myklebust <trondmy@...il.com>,
NFS Mailing List <linux-nfs@...r.kernel.org>
Subject: Re: linux-next: runtime warning in next-20220125
Hi all,
On Tue, 25 Jan 2022 16:05:05 +1100 Stephen Rothwell <sfr@...b.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.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists