From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ecree@solarflare.com, ast@fb.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] bpf: fix liveness propagation to parent in spilled stack slots
Date: Thu, 17 Aug 2017 10:16:11 -0700 (PDT) [thread overview]
Message-ID: <20170817.101611.23983207839678338.davem@davemloft.net> (raw)
In-Reply-To: <058693b94f456324fd1a3d5946fa486e3a09ca06.1502974643.git.daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Thu, 17 Aug 2017 14:59:40 +0200
> Using parent->regs[] when propagating REG_LIVE_READ for spilled regs
> doesn't work since parent->regs[] denote the set of normal registers
> but not spilled ones. Propagate to the correct regs.
>
> Fixes: dc503a8ad984 ("bpf/verifier: track liveness for pruning")
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Acked-by: Edward Cree <ecree@solarflare.com>
Applied.
prev parent reply other threads:[~2017-08-17 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 12:59 [PATCH net-next] bpf: fix liveness propagation to parent in spilled stack slots Daniel Borkmann
2017-08-17 17:16 ` 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=20170817.101611.23983207839678338.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=ecree@solarflare.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).