From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/9] rcu: Panic if RCU tree can not accommodate all CPUs
Date: Sat, 7 Mar 2015 13:52:23 -0800 [thread overview]
Message-ID: <20150307215223.GQ5236@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150307184821.GA15033@agordeev.usersys.redhat.com>
On Sat, Mar 07, 2015 at 06:48:21PM +0000, Alexander Gordeev wrote:
> On Sat, Mar 07, 2015 at 09:42:34AM -0800, Paul E. McKenney wrote:
> > On Sat, Mar 07, 2015 at 06:03:36PM +0100, Alexander Gordeev wrote:
> > > Currently a condition when RCU tree is unable to accommodate
> > > the configured number of CPUs is not permitted and causes
> > > a fall back to compile-time values. However, the code has no
> > > means to exceed the RCU tree capacity neither at compile-time
> > > nor in run-time. Therefore, if the condition is met in run-
> > > time then it indicates a serios problem elsewhere and should
> > > be handled with a panic.
> > >
> > > Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > Signed-off-by: Alexander Gordeev <agordeev@redhat.com>
> >
> > The place to put a check like this is in the code that calculates
> > nr_cpu_ids. And at least some (perhaps all) are set up so that nr_cpu_ids
> > cannot exceed NR_CPUS, which would render this check redundant.
>
> The emphasis here the existing check (... n > rcu_capacity[MAX_RCU_LVLS])
> (below as [1]) should not cause the fall back to compiled-time values.
> It either must panic or, as you say - redundant.
You are right, I responded too early on a Saturday. The point of the
check below is indeed to verify that RCU's calculations are correct.
So do the testing with CONFIG_RCU_FANOUT and CONFIG_RCU_FANOUT_LEAF both
equal to five, and rebase to the rcu/next branch of:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
And I will give them a spin.
Thanx, Paul
> > So I have to say "no" to this one.
> >
> > Thanx, Paul
> >
> > > ---
> > > kernel/rcu/tree.c | 15 +++++++++------
> > > 1 file changed, 9 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> > > index 48d640c..7588c7f 100644
> > > --- a/kernel/rcu/tree.c
> > > +++ b/kernel/rcu/tree.c
> > > @@ -3889,16 +3889,19 @@ static void __init rcu_init_geometry(void)
> > > rcu_capacity[i] = rcu_capacity[i - 1] * CONFIG_RCU_FANOUT;
> > >
> > > /*
> > > + * The tree must be able to accommodate the configured number of CPUs.
> > > + * If this limit is exceeded than we have a serious problem elsewhere.
> > > + *
> > > * The boot-time rcu_fanout_leaf parameter is only permitted
> > > * to increase the leaf-level fanout, not decrease it. Of course,
> > > * the leaf-level fanout cannot exceed the number of bits in
> > > - * the rcu_node masks. Finally, the tree must be able to accommodate
> > > - * the configured number of CPUs. Complain and fall back to the
> > > - * compile-time values if these limits are exceeded.
> > > + * the rcu_node masks. Complain and fall back to the compile-
> > > + * time values if these limits are exceeded.
> > > */
> > > - if (rcu_fanout_leaf < CONFIG_RCU_FANOUT_LEAF ||
> > > - rcu_fanout_leaf > sizeof(unsigned long) * 8 ||
> > > - n > rcu_capacity[MAX_RCU_LVLS]) {
>
> [1]
>
> > > + if (n > rcu_capacity[MAX_RCU_LVLS])
> > > + panic("rcu_init_geometry: rcu_capacity[] is too small");
> > > + else if (rcu_fanout_leaf < CONFIG_RCU_FANOUT_LEAF ||
> > > + rcu_fanout_leaf > sizeof(unsigned long) * 8) {
> > > WARN_ON(1);
> > > return;
> > > }
> > > --
> > > 1.8.3.1
> > >
> >
>
> --
> Regards,
> Alexander Gordeev
> agordeev@redhat.com
>
next prev parent reply other threads:[~2015-03-07 21:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 17:03 [PATCH 0/9] rcu: Cleanup RCU tree initialization Alexander Gordeev
2015-03-07 17:03 ` [PATCH 1/9] rcu: Panic if RCU tree can not accommodate all CPUs Alexander Gordeev
2015-03-07 17:42 ` Paul E. McKenney
2015-03-07 18:48 ` Alexander Gordeev
2015-03-07 21:52 ` Paul E. McKenney [this message]
2015-03-07 17:03 ` [PATCH 2/9] rcu: Remove superfluous local variable in rcu_init_geometry() Alexander Gordeev
2015-03-07 18:03 ` Paul E. McKenney
2015-03-07 17:03 ` [PATCH 3/9] rcu: Cleanup rcu_init_geometry() code and arithmetics Alexander Gordeev
2015-03-07 18:08 ` Paul E. McKenney
2015-03-07 18:59 ` Alexander Gordeev
2015-03-07 21:47 ` Paul E. McKenney
2015-03-07 17:03 ` [PATCH 4/9] rcu: Simplify rcu_init_geometry() capacity arithmetics Alexander Gordeev
2015-03-07 17:03 ` [PATCH 5/9] rcu: Limit rcu_state::levelcnt[] to RCU_NUM_LVLS items Alexander Gordeev
2015-03-07 17:03 ` [PATCH 6/9] rcu: Limit rcu_capacity[] size " Alexander Gordeev
2015-03-07 17:03 ` [PATCH 7/9] rcu: Remove unnecessary fields from rcu_state structure Alexander Gordeev
2015-03-07 17:03 ` [PATCH 8/9] rcu: Limit count of static data to the number of RCU levels Alexander Gordeev
2015-03-07 17:03 ` [PATCH 9/9] rcu: Simplify arithmetic to calculate number of RCU nodes Alexander Gordeev
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=20150307215223.GQ5236@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=agordeev@redhat.com \
--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 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.