summaryrefslogtreecommitdiffstats
path: root/fs/no-block.c
diff options
context:
space:
mode:
authorKumar Kartikeya Dwivedi <memxor@gmail.com>2022-11-15 00:45:27 +0530
committerAlexei Starovoitov <ast@kernel.org>2022-11-14 21:52:45 -0800
commit894f2a8b1673a355a1a7507a4dfa6a3c836d07c1 (patch)
treefdbba646d976546607fe90cc72fb227fae130df8 /fs/no-block.c
parent2de2669b4e52b2ae2f118bfc310004f50b47f0f5 (diff)
downloadlinux-894f2a8b1673a355a1a7507a4dfa6a3c836d07c1.tar.gz
linux-894f2a8b1673a355a1a7507a4dfa6a3c836d07c1.tar.bz2
linux-894f2a8b1673a355a1a7507a4dfa6a3c836d07c1.zip
bpf: Rename MEM_ALLOC to MEM_RINGBUF
Currently, verifier uses MEM_ALLOC type tag to specially tag memory returned from bpf_ringbuf_reserve helper. However, this is currently only used for this purpose and there is an implicit assumption that it only refers to ringbuf memory (e.g. the check for ARG_PTR_TO_ALLOC_MEM in check_func_arg_reg_off). Hence, rename MEM_ALLOC to MEM_RINGBUF to indicate this special relationship and instead open the use of MEM_ALLOC for more generic allocations made for user types. Also, since ARG_PTR_TO_ALLOC_MEM_OR_NULL is unused, simply drop it. Finally, update selftests using 'alloc_' verifier string to 'ringbuf_'. Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com> Link: https://lore.kernel.org/r/20221114191547.1694267-7-memxor@gmail.com Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'fs/no-block.c')
0 files changed, 0 insertions, 0 deletions