public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Anna Schumaker <Anna.Schumaker@Netapp.com>,
	Trond Myklebust <trondmy@gmail.com>,
	NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: linux-next: runtime warning in next-20220125
Date: Tue, 25 Jan 2022 16:21:46 +1100	[thread overview]
Message-ID: <20220125162146.13872bdb@canb.auug.org.au> (raw)
In-Reply-To: <20220125160505.068dbb52@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

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.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-01-25  6:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25  5:05 linux-next: runtime warning in next-20220125 Stephen Rothwell
2022-01-25  5:21 ` Stephen Rothwell [this message]
2022-01-25 15:01   ` Steven Rostedt
2022-01-25 15:36     ` Steven Rostedt
2022-01-25 15:38       ` Chuck Lever III
2022-01-25 15:46         ` Steven Rostedt
2022-01-25 15:49           ` Chuck Lever III

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=20220125162146.13872bdb@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Anna.Schumaker@Netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=trondmy@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox