From b803944b58cdc273bc8da9d09d9902e3ffa99904 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Wed, 15 Jan 2020 16:52:52 +0100 Subject: prog: don't add fallback coverage after prctl The same reason as with seccomp. --- prog/analysis.go | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'prog/analysis.go') diff --git a/prog/analysis.go b/prog/analysis.go index 519d5ba84..896ee4bd9 100644 --- a/prog/analysis.go +++ b/prog/analysis.go @@ -209,8 +209,9 @@ func (p *Prog) FallbackSignal(info []CallInfo) { if inf.Errno != 0 { continue } - if c.Meta.CallName == "seccomp" { - // seccomp filter can produce arbitrary errno values for subsequent syscalls. Don't trust anything afterwards. + if c.Meta.CallName == "seccomp" || c.Meta.CallName == "prctl" { + // seccomp filter can produce arbitrary errno values for subsequent syscalls. + // Don't trust anything afterwards. prctl can setup seccomp too. break } ForeachArg(c, func(arg Arg, _ *ArgCtx) { -- cgit mrf-deployment