diff options
author | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2013-10-16 08:39:10 -0700 |
---|---|---|
committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2013-12-09 15:12:38 -0800 |
commit | 04f34650ca5e8445aae0ab3e0ff6704f141150a8 (patch) | |
tree | b16d8e405b078520af0c72177045864b31788ff7 /COPYING | |
parent | f6f7ee9af7554e4d167ccd0ffe7cb8da0aa954f9 (diff) | |
download | linux-04f34650ca5e8445aae0ab3e0ff6704f141150a8.tar.gz linux-04f34650ca5e8445aae0ab3e0ff6704f141150a8.tar.bz2 linux-04f34650ca5e8445aae0ab3e0ff6704f141150a8.zip |
rcu: Fix CONFIG_RCU_FANOUT_EXACT for odd fanout/leaf values
Each element of the rcu_state structure's ->levelspread[] array
is intended to contain the per-level fanout, where the zero-th
element corresponds to the root of the rcu_node tree, and the last
element corresponds to the leaves. In the CONFIG_RCU_FANOUT_EXACT
case, this means that the last element should be filled in
from CONFIG_RCU_FANOUT_LEAF (or from the rcu_fanout_leaf boot
parameter, if provided) and that the remaining elements should
be filled in from CONFIG_RCU_FANOUT. Unfortunately, the current
code in rcu_init_levelspread() takes the opposite approach, placing
CONFIG_RCU_FANOUT_LEAF in the zero-th element and CONFIG_RCU_FANOUT in
the remaining elements.
For typical power-of-two values, this generates odd but functional
rcu_node trees. However, other values, for example CONFIG_RCU_FANOUT=3
and CONFIG_RCU_FANOUT_LEAF=2, generate trees that can leave some CPUs
out of the grace-period computation, resulting in too-short grace periods
and therefore a broken RCU implementation.
This commit therefore fixes rcu_init_levelspread() to set the last
->levelspread[] array element from CONFIG_RCU_FANOUT_LEAF and the
remaining elements from CONFIG_RCU_FANOUT, thus generating the
intended rcu_node trees.
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions