torture: Break affinity of kthreads last running on outgoing CPU
The advent of commit 06249738a41a ("workqueue: Manually break affinity
on hotplug") means that the scheduler no longer silently breaks affinity
for kthreads pinned to the outgoing CPU. This can happen for many of
rcutorture's kthreads due to shuffling, which periodically affinities
these ktheads away from a randomly chosen CPU. This usually works fine
because these kthreads are allowed to run on any other CPU and because
shuffling is a no-op any time there is but one online CPU.
However, consider the following sequence of events:
1. CPUs 0 and 1 are initially online.
2. The torture_shuffle_tasks() function affinities all the tasks
away from CPU 0.
3. CPU 1 goes offline.
4. All the tasks are now affinitied to an offline CPU, triggering
the warning added by the commit noted above.
This commit therefore adds a new torture_shuffle_tasks_offline() function
that is invoked from torture_offline() prior to offlining a CPU. This new
function scans the list of shuffled kthreads and for any thread that
last ran (or is set to run) on the outgoing CPU, sets its affinity to
all online CPUs. Thus there will never be a kthread that is affinitied
only to the outgoing CPU.
Of course, if the sysadm manually applies affinity to any of these
kthreads, all bets are off. However, such a sysadm must be fast because
the torture_shuffle_tasks_offline() function is invoked immediately before
offlining the outgoing CPU. Therefore, let it be known that with great
speed and great power comes great responsibility.
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
1 file changed
