diff options
| author | Kumar Kartikeya Dwivedi <memxor@gmail.com> | 2022-11-15 00:45:26 +0530 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2022-11-14 21:52:45 -0800 |
| commit | 2de2669b4e52b2ae2f118bfc310004f50b47f0f5 (patch) | |
| tree | 6380e8ea79e0d1b7febff75a6954af7d53f2ca97 /net/ethtool/eeprom.c | |
| parent | f0c5941ff5b255413d31425bb327c2aec3625673 (diff) | |
| download | linux-2de2669b4e52b2ae2f118bfc310004f50b47f0f5.tar.gz linux-2de2669b4e52b2ae2f118bfc310004f50b47f0f5.tar.bz2 linux-2de2669b4e52b2ae2f118bfc310004f50b47f0f5.zip | |
bpf: Rename RET_PTR_TO_ALLOC_MEM
Currently, the verifier has two return types, RET_PTR_TO_ALLOC_MEM, and
RET_PTR_TO_ALLOC_MEM_OR_NULL, however the former is confusingly named to
imply that it carries MEM_ALLOC, while only the latter does. This causes
confusion during code review leading to conclusions like that the return
value of RET_PTR_TO_DYNPTR_MEM_OR_NULL (which is RET_PTR_TO_ALLOC_MEM |
PTR_MAYBE_NULL) may be consumable by bpf_ringbuf_{submit,commit}.
Rename it to make it clear MEM_ALLOC needs to be tacked on top of
RET_PTR_TO_MEM.
Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Link: https://lore.kernel.org/r/20221114191547.1694267-6-memxor@gmail.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'net/ethtool/eeprom.c')
0 files changed, 0 insertions, 0 deletions