From: Steven Rostedt <rostedt@goodmis.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: runtime warning after merge of the cel-fixes tree
Date: Thu, 7 Apr 2022 10:54:46 -0400 [thread overview]
Message-ID: <20220407105446.186114c3@gandalf.local.home> (raw)
In-Reply-To: <F83867B8-2737-4850-83A6-13B95973A0BB@oracle.com>
On Thu, 7 Apr 2022 13:48:54 +0000
Chuck Lever III <chuck.lever@oracle.com> wrote:
> > event svc_defer_recv has unsafe dereference of argument 1
> > print_fmt: "addr=%pISpc dr=%p xid=0x%08x", (struct sockaddr *)__get_dynamic_array(addr), REC->dr, REC->xid
> > event svc_defer_queue has unsafe dereference of argument 1
> > print_fmt: "addr=%pISpc dr=%p xid=0x%08x", (struct sockaddr *)__get_dynamic_array(addr), REC->dr, REC->xid
> > event svc_defer_drop has unsafe dereference of argument 1
> > print_fmt: "addr=%pISpc dr=%p xid=0x%08x", (struct sockaddr *)__get_dynamic_array(addr), REC->dr, REC->xid
> > NR_IRQS: 512, nr_irqs: 512, preallocated irqs: 16
> > rcu: srcu_init: Setting srcu_struct sizes based on contention.
> >
> > Introduced by commit
> >
> > e2e917f8677d ("SUNRPC: Fix the svc_deferred_event trace class")
> >
> > At least reverting that commit makes the warning go away.
> >
> > I have left that commit reverted for today.
>
> Thank you, Stephen. The NFS community has already discussed a
> fix for this issue. I'll push it out as soon as I can.
Hmm, I know we added code to handle "__get_sockaddr()" but I guess this
should also be fine for "__get_dynamic_array()" as well.
I could write a patch to cover those too.
-- Steve
next prev parent reply other threads:[~2022-04-07 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 4:45 linux-next: runtime warning after merge of the cel-fixes tree Stephen Rothwell
2022-04-07 13:48 ` Chuck Lever III
2022-04-07 14:54 ` Steven Rostedt [this message]
2022-04-07 15:13 ` Steven Rostedt
2022-04-07 15:35 ` Chuck Lever III
2022-04-07 15:42 ` Steven Rostedt
2022-04-07 15:50 ` Steven Rostedt
2022-04-07 16:05 ` Steven Rostedt
2022-04-07 16:04 ` 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=20220407105446.186114c3@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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