summaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorWill Deacon <will@kernel.org>2020-05-15 14:56:05 +0100
committerWill Deacon <will@kernel.org>2020-05-18 17:47:40 +0100
commit88485be531f4aee841ddc53b56e2f6e6a338854d (patch)
tree10833e62803878f5163551402f0248494d57e3bf /security
parent711e8b0de0d63c70c825b473da01288b661a2386 (diff)
downloadlinux-stable-88485be531f4aee841ddc53b56e2f6e6a338854d.tar.gz
linux-stable-88485be531f4aee841ddc53b56e2f6e6a338854d.tar.bz2
linux-stable-88485be531f4aee841ddc53b56e2f6e6a338854d.zip
scs: Move scs_overflow_check() out of architecture code
There is nothing architecture-specific about scs_overflow_check() as it's just a trivial wrapper around scs_corrupted(). For parity with task_stack_end_corrupted(), rename scs_corrupted() to task_scs_end_corrupted() and call it from schedule_debug() when CONFIG_SCHED_STACK_END_CHECK_is enabled, which better reflects its purpose as a debug feature to catch inadvertent overflow of the SCS. Finally, remove the unused scs_overflow_check() function entirely. This has absolutely no impact on architectures that do not support SCS (currently arm64 only). Tested-by: Sami Tolvanen <samitolvanen@google.com> Reviewed-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions