diff options
author | David Woodhouse <[email protected]> | 2023-05-12 23:07:43 +0200 |
---|---|---|
committer | Peter Zijlstra <[email protected]> | 2023-05-15 13:45:00 +0200 |
commit | 6d712b9b3a58018259fb40ddd498d1f7dfa1f4ec (patch) | |
tree | b4b579e063cb36a682f4f04756dc34d01fc80e95 /lib/crypto/mpi/mpi-sub-ui.c | |
parent | bc088f9a0d5bdf12bb18980739336dfcc092e55b (diff) |
cpu/hotplug: Reset task stack state in _cpu_up()
Commit dce1ca0525bf ("sched/scs: Reset task stack state in bringup_cpu()")
ensured that the shadow call stack and KASAN poisoning were removed from
a CPU's stack each time that CPU is brought up, not just once.
This is not incorrect. However, with parallel bringup the idle thread setup
will happen at a different step. As a consequence the cleanup in
bringup_cpu() would be too late.
Move the SCS/KASAN cleanup to the generic _cpu_up() function instead,
which already ensures that the new CPU's stack is available, purely to
allow for early failure. This occurs when the CPU to be brought up is
in the CPUHP_OFFLINE state, which should correctly do the cleanup any
time the CPU has been taken down to the point where such is needed.
Signed-off-by: David Woodhouse <[email protected]>
Signed-off-by: Thomas Gleixner <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Reviewed-by: Mark Rutland <[email protected]>
Tested-by: Mark Rutland <[email protected]>
Tested-by: Michael Kelley <[email protected]>
Tested-by: Oleksandr Natalenko <[email protected]>
Tested-by: Helge Deller <[email protected]> # parisc
Tested-by: Guilherme G. Piccoli <[email protected]> # Steam Deck
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'lib/crypto/mpi/mpi-sub-ui.c')
0 files changed, 0 insertions, 0 deletions