From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-kernel@vger.kernel.org
Cc: linux-arch@vger.kernel.org
Subject: de-reference of rcu pointers (sparse warnings)
Date: Tue, 05 Nov 2019 08:13:13 +0000 [thread overview]
Message-ID: <d0e13f6d93323acd3df7a6b92a56ab13@codethink.co.uk> (raw)
There are a few places in the kenrnel which directly de-reference
pointers marked as "noderef" such sa rcu or percpu. In the case
of rcu, one example is:
kernel/fork.c:2146:32: warning: incorrect type in assignment (different
address spaces)
kernel/fork.c:2146:32: expected struct task_struct [noderef] <asn:4>
*real_parent
kernel/fork.c:2146:32: got struct task_struct *task
this looks fairly non-trivial to fix given there's a mix of __rcu and
non-__rcu
attributed variables.
Does anyone have an idea how to go about fixing these, if possible?
--
Ben
reply other threads:[~2019-11-05 8:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d0e13f6d93323acd3df7a6b92a56ab13@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®