diff options
author | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2015-07-31 08:28:35 -0700 |
---|---|---|
committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2015-10-06 11:09:41 -0700 |
commit | ee968ac61d5a3440b931375d81113e0eedfcb249 (patch) | |
tree | ac6f4bc6727b19506941412b6d09c5fe44ca8b3d /init | |
parent | bb73c52bad3666997ed2ec83c0c80c3f8ef55008 (diff) | |
download | kernel_replicant_linux-ee968ac61d5a3440b931375d81113e0eedfcb249.tar.gz kernel_replicant_linux-ee968ac61d5a3440b931375d81113e0eedfcb249.tar.bz2 kernel_replicant_linux-ee968ac61d5a3440b931375d81113e0eedfcb249.zip |
rcu: Eliminate panic when silly boot-time fanout specified
This commit loosens rcutree.rcu_fanout_leaf range checks
and replaces a panic() with a fallback to compile-time values.
This fallback is accompanied by a WARN_ON(), and both occur when the
rcutree.rcu_fanout_leaf value is too small to accommodate the number of
CPUs. For example, given the current four-level limit for the rcu_node
tree, a system with more than 16 CPUs built with CONFIG_FANOUT=2 must
have rcutree.rcu_fanout_leaf larger than 2.
Reported-by: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions