Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Build bug #106

Closed
baishuai opened this issue Jan 5, 2017 · 3 comments
Closed

Build bug #106

baishuai opened this issue Jan 5, 2017 · 3 comments

Comments

@baishuai
Copy link
Contributor

baishuai commented Jan 5, 2017 •
edited 

➜  syzkaller git:(master) make execprog executor 
go build -o ./bin/syz-execprog github.com/google/syzkaller/tools/syz-execprog
# vendor/github.com/google/syzkaller/sys
../../../vendor/github.com/google/syzkaller/sys/align.go:29: undefined: Structs
../../../vendor/github.com/google/syzkaller/sys/decl.go:353: undefined: Resources
../../../vendor/github.com/google/syzkaller/sys/decl.go:384: undefined: Resources
../../../vendor/github.com/google/syzkaller/sys/decl.go:388: undefined: Resources
../../../vendor/github.com/google/syzkaller/sys/decl.go:515: undefined: initCalls
../../../vendor/github.com/google/syzkaller/sys/decl.go:516: undefined: initStructFields
Makefile:31: recipe for target 'execprog' failed
make: *** [execprog] Error 2

And env info

➜  syzkaller git:(master) uname -a
Linux Lenovo-Product 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

go env

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/bai/Syzkaller"
GORACE=""
GOROOT="/usr/lib/go-1.7"
GOTOOLDIR="/usr/lib/go-1.7/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build339475586=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
@baishuai
Copy link
Contributor Author

baishuai commented Jan 5, 2017

I think that I have wrong GOPATH setting, sorry

@baishuai baishuai closed this as completed Jan 5, 2017
@dvyukov
Copy link
Collaborator

dvyukov commented Jan 5, 2017

You need to run make rather than make execprog executor:
https://github.com/google/syzkaller#syzkaller

@baishuai
Copy link
Contributor Author

baishuai commented Jan 5, 2017

Thanks a lot.

@ramosian-glider ramosian-glider mentioned this issue May 9, 2023
Merged
ramosian-glider added a commit to ramosian-glider/syzkaller that referenced this issue May 9, 2023
@ramosian-glider
dashboard/config/linux: disable CONFIG_STACKPROTECTOR for KMSAN
96ae8e1 
Linux v6.4-rc1 built with Clang versions <= 16 with stack protector
enabled panic with the following stack trace:

Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: start_kernel+0xd8a/0xd90
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.3.0-rc1-00042-g9ea7e6b62c2b-dirty google#106
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88
 dump_stack_lvl+0x1bc/0x250 lib/dump_stack.c:106
 dump_stack+0x1e/0x20 lib/dump_stack.c:113
 panic+0x4cd/0xc10 kernel/panic.c:340
 __stack_chk_fail+0x18/0x20 kernel/panic.c:759
 start_kernel+0xd8a/0xd90 init/main.c:?
 x86_64_start_reservations+0x2e/0x30 arch/x86/kernel/head64.c:556
 x86_64_start_kernel+0x118/0x120 arch/x86/kernel/head64.c:537
 secondary_startup_64_no_verify+0xcf/0xdb arch/x86/kernel/head_64.S:358
 </TASK>

ClangBuiltLinux/linux#1815 describes the
problem, which is fixed on the Clang side
(https://reviews.llvm.org/D147975), but before the fix reaches syzbot
we'll have to keep the stack protector disabled.
ramosian-glider added a commit that referenced this issue May 9, 2023
@ramosian-glider
dashboard/config/linux: disable CONFIG_STACKPROTECTOR for KMSAN
30aa2a7 
Linux v6.4-rc1 built with Clang versions <= 16 with stack protector
enabled panic with the following stack trace:

Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: start_kernel+0xd8a/0xd90
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.3.0-rc1-00042-g9ea7e6b62c2b-dirty #106
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88
 dump_stack_lvl+0x1bc/0x250 lib/dump_stack.c:106
 dump_stack+0x1e/0x20 lib/dump_stack.c:113
 panic+0x4cd/0xc10 kernel/panic.c:340
 __stack_chk_fail+0x18/0x20 kernel/panic.c:759
 start_kernel+0xd8a/0xd90 init/main.c:?
 x86_64_start_reservations+0x2e/0x30 arch/x86/kernel/head64.c:556
 x86_64_start_kernel+0x118/0x120 arch/x86/kernel/head64.c:537
 secondary_startup_64_no_verify+0xcf/0xdb arch/x86/kernel/head_64.S:358
 </TASK>

ClangBuiltLinux/linux#1815 describes the
problem, which is fixed on the Clang side
(https://reviews.llvm.org/D147975), but before the fix reaches syzbot
we'll have to keep the stack protector disabled.
f0rm2l1n pushed a commit to f0rm2l1n/my-syzkaller that referenced this issue Jun 8, 2023
@ramosian-glider @f0rm2l1n
dashboard/config/linux: disable CONFIG_STACKPROTECTOR for KMSAN
1782278 
Linux v6.4-rc1 built with Clang versions <= 16 with stack protector
enabled panic with the following stack trace:

Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: start_kernel+0xd8a/0xd90
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.3.0-rc1-00042-g9ea7e6b62c2b-dirty google#106
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88
 dump_stack_lvl+0x1bc/0x250 lib/dump_stack.c:106
 dump_stack+0x1e/0x20 lib/dump_stack.c:113
 panic+0x4cd/0xc10 kernel/panic.c:340
 __stack_chk_fail+0x18/0x20 kernel/panic.c:759
 start_kernel+0xd8a/0xd90 init/main.c:?
 x86_64_start_reservations+0x2e/0x30 arch/x86/kernel/head64.c:556
 x86_64_start_kernel+0x118/0x120 arch/x86/kernel/head64.c:537
 secondary_startup_64_no_verify+0xcf/0xdb arch/x86/kernel/head_64.S:358
 </TASK>

ClangBuiltLinux/linux#1815 describes the
problem, which is fixed on the Clang side
(https://reviews.llvm.org/D147975), but before the fix reaches syzbot
we'll have to keep the stack protector disabled.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dvyukov @baishuai