From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Yonghong Song <yhs@fb.com>
Cc: ast@fb.com, daniel@iogearbox.net, edumazet@google.com,
netdev@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 0/2] bpf: fix kernel page fault in lpm map trie_get_next_key
Date: Fri, 26 Jan 2018 17:10:56 -0800 [thread overview]
Message-ID: <20180127011054.xlet3kkjmm2nf6a2@ast-mbp> (raw)
In-Reply-To: <20180126230608.2175374-1-yhs@fb.com>
On Fri, Jan 26, 2018 at 03:06:06PM -0800, Yonghong Song wrote:
> A kernel page fault which happens in lpm map trie_get_next_key is reported
> by syzbot and Eric. The issue was introduced by commit b471f2f1de8b
> ("bpf: implement MAP_GET_NEXT_KEY command for LPM_TRIE map").
> Patch #1 fixed the issue in the kernel and patch #2 adds a multithreaded
> test case in tools/testing/selftests/bpf/test_lpm_map.
Applied to bpf-next, thank you Yonghong!
prev parent reply other threads:[~2018-01-27 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 23:06 [PATCH bpf-next 0/2] bpf: fix kernel page fault in lpm map trie_get_next_key Yonghong Song
2018-01-26 23:06 ` [PATCH bpf-next 1/2] " Yonghong Song
2018-01-26 23:06 ` [PATCH bpf-next 2/2] tools/bpf: add a multithreaded stress test in bpf selftests test_lpm_map Yonghong Song
2018-01-27 1:10 ` Alexei Starovoitov [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=20180127011054.xlet3kkjmm2nf6a2@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=edumazet@google.com \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox