aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/task-analyzer.py
diff options
context:
space:
mode:
authorEric Sandeen <[email protected]>2024-07-02 17:22:41 -0500
committerChristian Brauner <[email protected]>2024-07-03 16:55:11 +0200
commit525bd65aa759ec320af1dc06e114ed69733e9e23 (patch)
tree5d0e8538661766a6f0be52feea968eef7490135c /tools/perf/scripts/python/task-analyzer.py
parentd02f0bb332d52c0330a1ef11cf98b7ec6448b99b (diff)
fuse: verify {g,u}id mount options correctly
As was done in 0200679fc795 ("tmpfs: verify {g,u}id mount options correctly") we need to validate that the requested uid and/or gid is representable in the filesystem's idmapping. Cribbing from the above commit log, The contract for {g,u}id mount options and {g,u}id values in general set from userspace has always been that they are translated according to the caller's idmapping. In so far, fuse has been doing the correct thing. But since fuse is mountable in unprivileged contexts it is also necessary to verify that the resulting {k,g}uid is representable in the namespace of the superblock. Fixes: c30da2e981a7 ("fuse: convert to use the new mount API") Cc: [email protected] # 5.4+ Signed-off-by: Eric Sandeen <[email protected]> Link: https://lore.kernel.org/r/[email protected] Reviewed-by: Christian Brauner <[email protected]> Reviewed-by: Josef Bacik <[email protected]> Signed-off-by: Christian Brauner <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions