Hello,
syzbot found the following issue on:
HEAD commit: 34f394d7 UPSTREAM: mm/cma.c: remove redundant cma_mutex lock
git tree: android12-5.4
console output:
https://syzkaller.appspot.com/x/log.txt?x=135057c3d00000
kernel config:
https://syzkaller.appspot.com/x/.config?x=ba69bff6e4a0f1e0
dashboard link:
https://syzkaller.appspot.com/bug?extid=a0c760348ae2c3d65b07
compiler: Debian clang version 11.0.1-2
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+a0c760...@syzkaller.appspotmail.com
2021/05/10 11:29:05 USB emulation: enabled
2021/05/10 11:29:05 hci packet injection: /dev/vhci does not exist
2021/05/10 11:29:05 wifi device emulation: /sys/class/mac80211_hwsim/ does not exist
2021/05/10 11:29:05 802.15.4 emulation: /sys/bus/platform/devices/mac802154_hwsim does not exist
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x6e01c8]
goroutine 1 [running]:
github.com/google/syzkaller/prog.(*ChoiceTable).Enabled(...)
/syzkaller/gopath/src/
github.com/google/syzkaller/prog/prio.go:239
main.(*Fuzzer).checkDisabledCalls(0xc000093ba0, 0xc000324840)
/syzkaller/gopath/src/
github.com/google/syzkaller/syz-fuzzer/fuzzer.go:469 +0x68
main.(*Fuzzer).deserializeInput(0xc000093ba0, 0xc00033a000, 0xff, 0xff, 0x0)
/syzkaller/gopath/src/
github.com/google/syzkaller/syz-fuzzer/fuzzer.go:460 +0x14c
main.(*Fuzzer).addCandidateInput(0xc000093ba0, 0xc00033a000, 0xff, 0xff, 0x101)
/syzkaller/gopath/src/
github.com/google/syzkaller/syz-fuzzer/fuzzer.go:438 +0x4d
main.(*Fuzzer).poll(0xc000093ba0, 0xc00012f001, 0x0, 0xc0000a6cd0)
/syzkaller/gopath/src/
github.com/google/syzkaller/syz-fuzzer/fuzzer.go:409 +0x4d4
main.main()
/syzkaller/gopath/src/
github.com/google/syzkaller/syz-fuzzer/fuzzer.go:273 +0x1271
[K[ [0;1;31m* [0m [0;31m* [0m] A start job is running for dev-ttyS0.device (9s / 1min 30s) [K[ [0;31m* [0;1;31m* [0m [0;31m* [0m] A start job is running for dev-ttyS0.device (9s / 1min 30s) [K[ [0;31m* [0;1;31m* [0m [0;31m* [0m] A start job is running for dev-ttyS0.device (10s / 1min 30s) [K[ [0;31m* [0;1;31m* [0m [0;31m* [0m] A start job is running for dev-ttyS0.device (10s / 1min 30s) [K[ [0;31m* [0;1;31m* [0m [0;31m* [0m] A start job is running for dev-ttyS0.device (11s / 1min 30s) [K[ [0;31m* [0;1;31m* [0m] A start job is running for dev-ttyS0.device (12s / 1min 30s) [K[ [0;31m* [0m] A start job is running for dev-ttyS0.device (12s / 1min 30s) [K[ [0;31m* [0;1;31m* [0m] A start job is running for dev-ttyS0.device (13s / 1min 30s) [K[ [0;31m* [0;1;31m* [0m [0;31m* [0m] A start job is running for dev-ttyS0.device (14s / 1min 30s)
---
This report is generated by a bot. It may contain errors.
See
https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.