From: Rik van Riel <riel@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Linux kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RCU recursion? (code inspection)
Date: Fri, 01 May 2015 15:18:28 -0400 [thread overview]
Message-ID: <5543D184.4070707@redhat.com> (raw)
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.
--
All rights reversed
next reply other threads:[~2015-05-01 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 19:18 Rik van Riel [this message]
2015-05-01 19:41 ` RCU recursion? (code inspection) Paul E. McKenney
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=5543D184.4070707@redhat.com \
--to=riel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.