diff options
author | Kumar Kartikeya Dwivedi <memxor@gmail.com> | 2023-01-21 05:52:35 +0530 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2023-01-20 17:55:03 -0800 |
commit | f5b625e5f8bbc6be8bb568a64d7906b091bc7cb0 (patch) | |
tree | 6af62721a84101baf519d0ec2127a25759a4c068 /mm | |
parent | 379d4ba831cfa895d0cc61d88cd0e1402f35818c (diff) |
bpf: Combine dynptr_get_spi and is_spi_bounds_valid
Currently, a check on spi resides in dynptr_get_spi, while others
checking its validity for being within the allocated stack slots happens
in is_spi_bounds_valid. Almost always barring a couple of cases (where
being beyond allocated stack slots is not an error as stack slots need
to be populated), both are used together to make checks. Hence, subsume
the is_spi_bounds_valid check in dynptr_get_spi, and return -ERANGE to
specially distinguish the case where spi is valid but not within
allocated slots in the stack state.
The is_spi_bounds_valid function is still kept around as it is a generic
helper that will be useful for other objects on stack similar to dynptr
in the future.
Suggested-by: Joanne Koong <joannelkoong@gmail.com>
Acked-by: Joanne Koong <joannelkoong@gmail.com>
Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Link: https://lore.kernel.org/r/20230121002241.2113993-7-memxor@gmail.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions