You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
To fuzz an interface defined as a pseudo syscall which expect 11 arguments, I've increased the related maxArgs fields in both executor.cc and prog/types.go. However, for some unknown reason, the 11th argument becomes a pointer to the syscall name ("syz_my_target_iface").
To Reproduce
Define a bogus pseudo syscall with 11 arguments. Then do the following in it:
Describe the bug
To fuzz an interface defined as a pseudo syscall which expect 11 arguments, I've increased the related maxArgs fields in both
executor.cc
andprog/types.go
. However, for some unknown reason, the 11th argument becomes a pointer to the syscall name ("syz_my_target_iface").To Reproduce
Define a bogus pseudo syscall with 11 arguments. Then do the following in it:
Then call it e.g
./syz-execprog -debug -threaded=0 mytest
Expected behavior
kMaxArgs
ofexecutor.cc
andmaxArgs
ofprog/types.go
should have been enough to alter the max args support.Regards
The text was updated successfully, but these errors were encountered: