rcu: Make FQS more aggressive in complaining about offline CPUs (666ca290) · Commits · 戴 / test

The RCU grace-period kthread's force-quiescent state (FQS) loop should never see an offline CPU that has not yet reported a quiescent state. After all, the offline CPU should have reported a quiescent state during the CPU-offline process, or, failing that, by rcu_gp_init() if it ran concurrently with either the CPU going offline or the last task on a leaf rcu_node structure exiting its RCU read-side critical section while all CPUs corresponding to that structure are offline. The FQS loop should therefore complain if it does see an offline CPU that has not yet reported a quiescent state. And it does, but only once the grace period has been in force for a full second. This commit therefore makes this warning more aggressive, so that it will trigger as soon as the condition makes its appearance. Light testing with TREE03 and hotplug shows no warnings. This commit also converts the warning to WARN_ON_ONCE() in order to stave off possible log spam. Signed-off-by:

Joel Fernandes (Google) <joel@joelfernandes.org> Signed-off-by:

Paul E. McKenney <paulmck@kernel.org>

kernel/rcu/tree.c

+19 −4

Original line number	Diff line number	Diff line
		@@ -1214,13 +1214,28 @@ static int rcu_implicit_dynticks_qs(struct rcu_data *rdp)
		return 1;
		}

		/* If waiting too long on an offline CPU, complain. */
		if (!(rdp->grpmask & rcu_rnp_online_cpus(rnp)) &&
		time_after(jiffies, rcu_state.gp_start + HZ)) {
		/*
		* Complain if a CPU that is considered to be offline from RCU's
		* perspective has not yet reported a quiescent state. After all,
		* the offline CPU should have reported a quiescent state during
		* the CPU-offline process, or, failing that, by rcu_gp_init()
		* if it ran concurrently with either the CPU going offline or the
		* last task on a leaf rcu_node structure exiting its RCU read-side
		* critical section while all CPUs corresponding to that structure
		* are offline. This added warning detects bugs in any of these
		* code paths.
		*
		* The rcu_node structure's ->lock is held here, which excludes
		* the relevant portions the CPU-hotplug code, the grace-period
		* initialization code, and the rcu_read_unlock() code paths.
		*
		* For more detail, please refer to the "Hotplug CPU" section
		* of RCU's Requirements documentation.
		*/
		if (WARN_ON_ONCE(!(rdp->grpmask & rcu_rnp_online_cpus(rnp)))) {
		bool onl;
		struct rcu_node *rnp1;

		WARN_ON(1); /* Offline CPUs are supposed to report QS! */
		pr_info("%s: grp: %d-%d level: %d ->gp_seq %ld ->completedqs %ld\n",
		__func__, rnp->grplo, rnp->grphi, rnp->level,
		(long)rnp->gp_seq, (long)rnp->completedqs);

Admin message