summaryrefslogtreecommitdiffstats
path: root/fs/read_write.c
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2020-03-23 17:01:19 +0000
committerCatalin Marinas <catalin.marinas@arm.com>2020-03-25 09:56:10 +0000
commit5d1b631c773ffbbadcbb3176a2ae0ea9d1c114c7 (patch)
treee0ced25f06a7d2d1a2507e80f2fa7760fb3c185b /fs/read_write.c
parentbf7f15c585d5b9b843e662aa78f9fc71037db968 (diff)
downloadlinux-5d1b631c773ffbbadcbb3176a2ae0ea9d1c114c7.tar.gz
linux-5d1b631c773ffbbadcbb3176a2ae0ea9d1c114c7.tar.bz2
linux-5d1b631c773ffbbadcbb3176a2ae0ea9d1c114c7.zip
arm64: bti: Document behaviour for dynamically linked binaries
For dynamically linked binaries the interpreter is responsible for setting PROT_BTI on everything except itself. The dynamic linker needs to be aware of PROT_BTI, for example in order to avoid dropping that when marking executable pages read only after doing relocations, and doing everything in userspace ensures that we don't get any issues due to divergences in behaviour between the kernel and dynamic linker within a single executable. Add a comment indicating that this is intentional to the code to help people trying to understand what's going on. Signed-off-by: Mark Brown <broonie@kernel.org> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'fs/read_write.c')
0 files changed, 0 insertions, 0 deletions