From: David Miller <davem@davemloft.net>
To: kraigatgoog@gmail.com
Cc: ast@fb.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2] bpf: fix verifier NULL pointer dereference
Date: Fri, 03 Nov 2017 15:50:16 +0900 (KST) [thread overview]
Message-ID: <20171103.155016.1716862120175860397.davem@davemloft.net> (raw)
In-Reply-To: <20171102151801.24500-1-kraigatgoog@gmail.com>
From: Craig Gallek <kraigatgoog@gmail.com>
Date: Thu, 2 Nov 2017 11:18:01 -0400
> From: Craig Gallek <kraig@google.com>
>
> do_check() can fail early without allocating env->cur_state under
> memory pressure. Syzkaller found the stack below on the linux-next
> tree because of this.
...
> Fixes: 638f5b90d460 ("bpf: reduce verifier memory consumption")
> Fixes: 1969db47f8d0 ("bpf: fix verifier memory leaks")
> Signed-off-by: Craig Gallek <kraig@google.com>
Applied, thanks Craig.
prev parent reply other threads:[~2017-11-03 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 14:21 [PATCH net-next] bpf: fix verifier NULL pointer dereference Craig Gallek
2017-11-02 15:07 ` Alexei Starovoitov
2017-11-02 15:12 ` Craig Gallek
2017-11-02 15:18 ` [PATCH net-next v2] " Craig Gallek
2017-11-02 15:28 ` Alexei Starovoitov
2017-11-02 22:22 ` Daniel Borkmann
2017-11-03 6:50 ` David Miller [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=20171103.155016.1716862120175860397.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@fb.com \
--cc=kraigatgoog@gmail.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).