summaryrefslogtreecommitdiff
path: root/mm/memtest.c
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2024-07-30 01:16:04 -0400
committerAndrii Nakryiko <andrii@kernel.org>2024-08-13 15:58:17 -0700
commit55f325958ccc41eaea43eb4546d4dc77c1b5ef8a (patch)
tree3a67490e9e4a0ce16ffc6c7c92d36cb5c87c834a /mm/memtest.c
parent535ead44ffd08479212e31729a7118bd4e9ac699 (diff)
downloadlinux-55f325958ccc41eaea43eb4546d4dc77c1b5ef8a.tar.gz
linux-55f325958ccc41eaea43eb4546d4dc77c1b5ef8a.tar.bz2
linux-55f325958ccc41eaea43eb4546d4dc77c1b5ef8a.zip
bpf: switch maps to CLASS(fd, ...)
Calling conventions for __bpf_map_get() would be more convenient if it left fpdut() on failure to callers. Makes for simpler logics in the callers. Among other things, the proof of memory safety no longer has to rely upon file->private_data never being ERR_PTR(...) for bpffs files. Original calling conventions made it impossible for the caller to tell whether __bpf_map_get() has returned ERR_PTR(-EINVAL) because it has found the file not be a bpf map one (in which case it would've done fdput()) or because it found that ERR_PTR(-EINVAL) in file->private_data of a bpf map file (in which case fdput() would _not_ have been done). Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Reviewed-by: Christian Brauner <brauner@kernel.org> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Diffstat (limited to 'mm/memtest.c')
0 files changed, 0 insertions, 0 deletions