From 2dc4378f0225c80d2755f7531ad0de4c2044727a Mon Sep 17 00:00:00 2001
From: Dmitry Vyukov <dvyukov@google.com>
Date: Sun, 19 Aug 2018 00:13:24 -0700
Subject: prog: don't add fallback signal after seccomp

seccomp filter can produce arbitrary errno values for subsequent syscalls.
Don't trust anything afterwards.
---
 executor/syscalls.h | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'executor/syscalls.h')

diff --git a/executor/syscalls.h b/executor/syscalls.h
index 6aaa5d7be..47c7b1af8 100644
--- a/executor/syscalls.h
+++ b/executor/syscalls.h
@@ -11628,6 +11628,8 @@ const call_t syscalls[] = {
 
 #if GOARCH_64
 const call_t syscalls[] = {
+    {"fallback$0", 0},
+    {"fallback$1", 0},
     {"foo$any0", 0},
     {"foo$anyres", 0},
     {"foo$fmt0", 0},
@@ -11645,6 +11647,7 @@ const call_t syscalls[] = {
     {"mutate6", 0},
     {"mutate7", 0},
     {"mutate8", 0},
+    {"seccomp", 0},
     {"serialize0", 0},
     {"serialize1", 0},
     {"syz_compare", 0, (syscall_t)syz_compare},
-- 
cgit mrf-deployment