firmware: arm_sdei: Document the motivation behind these set_fs() calls
authorJames Morse <james.morse@arm.com>
Tue, 19 May 2020 18:21:08 +0000 (19:21 +0100)
committerWill Deacon <will@kernel.org>
Wed, 20 May 2020 08:36:01 +0000 (09:36 +0100)
commit472de63b0b8383565e103f809f5df37d1c4390ab
treed2bc2eb495a0b2e8a8bde740987a2a7104c0d9d4
parent82b2077afccd2a46ce15a43a50f2bfbf1b295de5
firmware: arm_sdei: Document the motivation behind these set_fs() calls

The SDEI handler save/restores the addr_limit using set_fs(). It isn't
very clear why. The reason is to mirror the arch code's entry assembly.
The arch code does this because perf may access user-space, and
inheriting the addr_limit may be a problem.

Add a comment explaining why this is here.

Suggested-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: James Morse <james.morse@arm.com>
Link: https://bugs.chromium.org/p/project-zero/issues/detail?id=822
Link: https://lore.kernel.org/r/20200519182108.13693-4-james.morse@arm.com
Signed-off-by: Will Deacon <will@kernel.org>
drivers/firmware/arm_sdei.c