aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/lists.py
diff options
context:
space:
mode:
authorMark Rutland <mark.rutland@arm.com>2023-08-21 17:35:26 +0100
committerThomas Gleixner <tglx@linutronix.de>2023-08-23 10:32:39 +0200
commit1dfe3a5a7cefbe2162cecb759f3933baea22c393 (patch)
treef78b2a7b553e2feb8ebe183ac97413f4e7b3c6a5 /scripts/gdb/linux/lists.py
parent6eaae198076080886b9e7d57f4ae06fa782f90ef (diff)
entry: Remove empty addr_limit_user_check()
Back when set_fs() was a generic API for altering the address limit, addr_limit_user_check() was a safety measure to prevent userspace being able to issue syscalls with an unbound limit. With the the removal of set_fs() as a generic API, the last user of addr_limit_user_check() was removed in commit: b5a5a01d8e9a44ec ("arm64: uaccess: remove addr_limit_user_check()") ... as since that commit, no architecture defines TIF_FSCHECK, and hence addr_limit_user_check() always expands to nothing. Remove addr_limit_user_check(), updating the comment in exit_to_user_mode_prepare() to no longer refer to it. At the same time, the comment is reworded to be a little more generic so as to cover kmap_assert_nomap() in addition to lockdep_sys_exit(). No functional change. Signed-off-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Link: https://lore.kernel.org/r/20230821163526.2319443-1-mark.rutland@arm.com
Diffstat (limited to 'scripts/gdb/linux/lists.py')
0 files changed, 0 insertions, 0 deletions