diff options
author | Jakub Kicinski <jakub.kicinski@netronome.com> | 2019-03-21 14:34:36 -0700 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2019-03-21 19:57:02 -0700 |
commit | 83d163124cf1104cca5b668d5fe6325715a60855 (patch) | |
tree | 0efb88a71d45a495137c28f26eb94575bf28ff2c /block | |
parent | 0803278b0b4d8eeb2b461fb698785df65a725d9e (diff) | |
download | linux-83d163124cf1104cca5b668d5fe6325715a60855.tar.gz linux-83d163124cf1104cca5b668d5fe6325715a60855.tar.bz2 linux-83d163124cf1104cca5b668d5fe6325715a60855.zip |
bpf: verifier: propagate liveness on all frames
Commit 7640ead93924 ("bpf: verifier: make sure callees don't prune
with caller differences") connected up parentage chains of all
frames of the stack. It didn't, however, ensure propagate_liveness()
propagates all liveness information along those chains.
This means pruning happening in the callee may generate explored
states with incomplete liveness for the chains in lower frames
of the stack.
The included selftest is similar to the prior one from commit
7640ead93924 ("bpf: verifier: make sure callees don't prune with
caller differences"), where callee would prune regardless of the
difference in r8 state.
Now we also initialize r9 to 0 or 1 based on a result from get_random().
r9 is never read so the walk with r9 = 0 gets pruned (correctly) after
the walk with r9 = 1 completes.
The selftest is so arranged that the pruning will happen in the
callee. Since callee does not propagate read marks of r8, the
explored state at the pruning point prior to the callee will
now ignore r8.
Propagate liveness on all frames of the stack when pruning.
Fixes: f4d7e40a5b71 ("bpf: introduce function calls (verification)")
Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions