From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Rik van Riel <riel@redhat.com>
Cc: Linux kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RCU recursion? (code inspection)
Date: Fri, 1 May 2015 12:41:02 -0700 [thread overview]
Message-ID: <20150501194102.GH5381@linux.vnet.ibm.com> (raw)
In-Reply-To: <5543D184.4070707@redhat.com>
On Fri, May 01, 2015 at 03:18:28PM -0400, Rik van Riel wrote:
> Hi Paul,
>
> While looking at synchronize_rcu(), I noticed that
> synchronize_rcu_expedited() calls synchronize_sched_expedited(),
> which can call synchronize_sched() when it is worried about
> the counter wrapping, which can call synchronize_sched_expedited()
>
> The code is sufficiently convoluted that I am unsure whether this
> recursion can actually happen in practice, but I also did not spot
> anything that would stop it.
Hmmm... Sounds like I should take a look!
Thanx, Paul
next prev parent reply other threads:[~2015-05-01 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 19:18 RCU recursion? (code inspection) Rik van Riel
2015-05-01 19:41 ` Paul E. McKenney [this message]
2015-05-01 20:10 ` Paul E. McKenney
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=20150501194102.GH5381@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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