From: Neil Horman <nhorman@redhat.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
netdev@vger.kernel.org, Alexander Duyck <aduyck@mirantis.com>,
linux-kernel@vger.kernel.org
Subject: Re: netpoll rtnl_dereference() usage
Date: Fri, 25 Mar 2016 14:16:06 -0400 [thread overview]
Message-ID: <20160325181606.GA18985@hmsreliant.think-freely.org> (raw)
In-Reply-To: <20160325173032.GC29822@localhost>
On Fri, Mar 25, 2016 at 12:30:32PM -0500, Bjorn Helgaas wrote:
> Hi Neil,
>
> Since we're looking at netpoll, here's another question (or two).
> 0790bbb68f9d ("netpoll: cleanup sparse warnings") adds this:
>
> @@ -1236,7 +1236,11 @@ void __netpoll_cleanup(struct netpoll *np)
> struct netpoll_info *npinfo;
> unsigned long flags;
>
> - npinfo = np->dev->npinfo;
> + /* rtnl_dereference would be preferable here but
> + * rcu_cleanup_netpoll path can put us in here safely without
> + * holding the rtnl, so plain rcu_dereference it is
> + */
> + npinfo = rtnl_dereference(np->dev->npinfo);
> if (!npinfo)
> return;
>
> The comment seems to contradict the code: the comment says "we would
> like to use rtnl_dereference(), but we have to use rcu_dereference()."
> But the code in fact *does* use rtnl_dereference().
>
its the comment that went awry. I remember writing that patch, and I initially
thought we had to use rcu_derefence there, but I would up finding a way to keep
the rntl lock held, so rtnl_deref should be ok. I must have just forgotten to
fixup the comment.
> Also, "rcu_cleanup_netpoll" doesn't exist; maybe it's a typo for
> rcu_cleanup_netpoll_info()? I don't see the path that leads from
> rcu_cleanup_netpoll_info() to __netpoll_cleanup(), but I don't claim
> to understand the netpoll async subtleties.
>
Correct again, its the rcu callback rcu_cleanup_netpoll_info that I'm referring
to there, and the comment was written initially when rcu_cleanup_netpoll info
was called cleanup_netpoll_info and called forward into __netpoll_cleanup (in my
development patch versions). That comment should really just be re-written.
I'm happy to do so if you like
Best
Neil
> Bjorn
prev parent reply other threads:[~2016-03-25 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 17:30 netpoll rtnl_dereference() usage Bjorn Helgaas
2016-03-25 18:16 ` Neil Horman [this message]
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=20160325181606.GA18985@hmsreliant.think-freely.org \
--to=nhorman@redhat.com \
--cc=aduyck@mirantis.com \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.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