[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164387340989.17246.1195357867240982633.git-patchwork-notify@kernel.org>
Date: Thu, 03 Feb 2022 07:30:09 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Hou Tao <hotforest@...il.com>
Cc: daniel@...earbox.net, ast@...nel.org, kafai@...com, yhs@...com,
andrii@...nel.org, davem@...emloft.net, kuba@...nel.org,
john.fastabend@...il.com, netdev@...r.kernel.org,
bpf@...r.kernel.org, houtao1@...wei.com,
syzbot+5ad567a418794b9b5983@...kaller.appspotmail.com
Subject: Re: [PATCH bpf-next v2] bpf: use VM_MAP instead of VM_ALLOC for ringbuf
Hello:
This patch was applied to bpf/bpf.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Wed, 2 Feb 2022 14:01:58 +0800 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf: use VM_MAP instead of VM_ALLOC for ringbuf
https://git.kernel.org/bpf/bpf/c/b293dcc473d2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists