panic: runtime error: invalid memory address or nil pointer dereference (7)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8bad472766c2 Not only BCM4378, but all PCIe core revisions..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=15e615edb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=fe55924c11e64b0a
dashboard link: https://syzkaller.appspot.com/bug?extid=d565f67bb8355e40e10e

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+d565f6...@syzkaller.appspotmail.com

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x7 pc=0x4114d0]

goroutine 1 [running]:
github.com/google/syzkaller/pkg/signal.(*Signal).Merge(0xc000001350, 0xc0012b1d40)
/syzkaller/gopath/src/github.com/google/syzkaller/pkg/signal/signal.go:150 +0x16c
main.(*Fuzzer).addInputToCorpus(0xc0000011e0, 0xc000f79600, 0xc0012b1d40, {0xb, 0x7f, 0xc6, 0x12, 0xb6, 0xc1, 0x58, ...})
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/fuzzer.go:525 +0x2da
main.(*Fuzzer).addInputFromAnotherFuzzer(0xc0000011e0, {{0xc00140d874, 0xc}, {0xc000abe780, 0x1c1, 0x1c1}, {{0xc000393900, 0x320, 0x320}, {0xc00022e380, ...}}, ...})
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/fuzzer.go:445 +0x145
main.(*Fuzzer).poll(0xc0000011e0, 0x1, 0xc00110c540)
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/fuzzer.go:417 +0x585
main.(*Fuzzer).pollLoop(0xc0000011e0)
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/fuzzer.go:394 +0x3c5
main.main()
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/fuzzer.go:297 +0x1be7


OpenBSD/amd64 (Amnesiac) (tty00)

login:


---
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.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.