diff options
| author | Hou Tao <hotforest@gmail.com> | 2022-02-02 09:01:58 +0300 |
|---|---|---|
| committer | Andrii Nakryiko <andrii@kernel.org> | 2022-02-03 10:15:24 +0300 |
| commit | b293dcc473d22a62dc6d78de2b15e4f49515db56 (patch) | |
| tree | 284d9f6552a276acc56f3263694f5b23084fecca /tools/bpf/resolve_btfids | |
| parent | b7892f7d5cb2b8187c603dd8ea3a7c44059ccfc2 (diff) | |
| download | linux-b293dcc473d22a62dc6d78de2b15e4f49515db56.tar.xz | |
bpf: Use VM_MAP instead of VM_ALLOC for ringbuf
After commit 2fd3fb0be1d1 ("kasan, vmalloc: unpoison VM_ALLOC pages
after mapping"), non-VM_ALLOC mappings will be marked as accessible
in __get_vm_area_node() when KASAN is enabled. But now the flag for
ringbuf area is VM_ALLOC, so KASAN will complain out-of-bound access
after vmap() returns. Because the ringbuf area is created by mapping
allocated pages, so use VM_MAP instead.
After the change, info in /proc/vmallocinfo also changes from
[start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmalloc user
to
[start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmap user
Fixes: 457f44363a88 ("bpf: Implement BPF ring buffer and verifier support for it")
Reported-by: syzbot+5ad567a418794b9b5983@syzkaller.appspotmail.com
Signed-off-by: Hou Tao <houtao1@huawei.com>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Link: https://lore.kernel.org/bpf/20220202060158.6260-1-houtao1@huawei.com
Diffstat (limited to 'tools/bpf/resolve_btfids')
0 files changed, 0 insertions, 0 deletions