From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <hotforest@gmail.com>
Cc: daniel@iogearbox.net, ast@kernel.org, kafai@fb.com, yhs@fb.com,
andrii@kernel.org, davem@davemloft.net, kuba@kernel.org,
john.fastabend@gmail.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, houtao1@huawei.com,
syzbot+5ad567a418794b9b5983@syzkaller.appspotmail.com
Subject: Re: [PATCH bpf-next v2] bpf: use VM_MAP instead of VM_ALLOC for ringbuf
Date: Thu, 03 Feb 2022 07:30:09 +0000 [thread overview]
Message-ID: <164387340989.17246.1195357867240982633.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220202060158.6260-1-houtao1@huawei.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Andrii Nakryiko <andrii@kernel.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
prev parent reply other threads:[~2022-02-03 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 6:01 [PATCH bpf-next v2] bpf: use VM_MAP instead of VM_ALLOC for ringbuf Hou Tao
2022-02-02 12:26 ` Daniel Borkmann
2022-02-03 5:14 ` Hou Tao
2022-02-03 7:24 ` Andrii Nakryiko
2022-02-03 7:30 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=164387340989.17246.1195357867240982633.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hotforest@gmail.com \
--cc=houtao1@huawei.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+5ad567a418794b9b5983@syzkaller.appspotmail.com \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.