From: Daniel Borkmann <daniel@iogearbox.net>
To: Stanislav Fomichev <sdf@google.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, ast@kernel.org, bhole_prashant_q7@lab.ntt.co.jp
Subject: Re: [PATCH bpf] selftests/bpf: add missing pointer dereference for map stacktrace fixup
Date: Mon, 10 Dec 2018 20:22:00 +0100 [thread overview]
Message-ID: <d07608df-043f-ccd6-1b78-8ed296720d5c@iogearbox.net> (raw)
In-Reply-To: <e569eb1296ed11bba05a12ff4b3bb91e70423793.1544156000.git.sdf@google.com>
On 12/07/2018 05:14 AM, Stanislav Fomichev wrote:
> I get a segfault without it, other fixups always do dereference, and
> without dereference I don't understand how it can ever work.
>
> Fixes: 7c85c448e7d74 ("selftests/bpf: test_verifier, check
> bpf_map_lookup_elem access in bpf prog")
>
> Signed-off-by: Stanislav Fomichev <sdf@google.com>
Applied to bpf, thanks Stanislav!
prev parent reply other threads:[~2018-12-10 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 4:14 [PATCH bpf] selftests/bpf: add missing pointer dereference for map stacktrace fixup Stanislav Fomichev
2018-12-07 4:31 ` Prashant Bhole
2018-12-10 19:22 ` Daniel Borkmann [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=d07608df-043f-ccd6-1b78-8ed296720d5c@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bhole_prashant_q7@lab.ntt.co.jp \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.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