Re: panic: bad arg kind

[Dmitry Vyukov]

On Tue, Oct 1, 2019 at 11:19 AM syzbot
<syzbot+01bd7b...@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 9eb03651 pwmreg(4)
> git tree: openbsd
> console output: https://syzkaller.appspot.com/x/log.txt?x=138c6905600000
> kernel config: https://syzkaller.appspot.com/x/.config?x=26ca0a9c07f16a3a
> dashboard link: https://syzkaller.appspot.com/bug?extid=01bd7bf4fb0810390845
>
> Unfortunately, I don't have any reproducer for this crash yet.
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+01bd7b...@syzkaller.appspotmail.com
>
> panic: bad arg kind
>
> goroutine 25 [running]:
> github.com/google/syzkaller/prog.clone(0x0, 0x0, 0xc003ab9e38,
> 0xc001037040, 0x10)

Interesting. We either got nil there somehow. Or it's a memory corruption.


> /syzkaller/gopath/src/github.com/google/syzkaller/prog/clone.go:75 +0x8b8
> github.com/google/syzkaller/prog.clone(0x97ca80, 0xc001d3f650,
> 0xc003ab9e38, 0xc00184bf70, 0x30)
> /syzkaller/gopath/src/github.com/google/syzkaller/prog/clone.go:53 +0x17c
> github.com/google/syzkaller/prog.clone(0x97ca80, 0xc001d3f680,
> 0xc003ab9e38, 0xc003ab9ec8, 0x30)
> /syzkaller/gopath/src/github.com/google/syzkaller/prog/clone.go:53 +0x17c
> github.com/google/syzkaller/prog.clone(0x97cac0, 0xc001d3f6b0,
> 0xc003ab9e38, 0x97cb00, 0xc0022c7940)
> /syzkaller/gopath/src/github.com/google/syzkaller/prog/clone.go:40 +0x570
> github.com/google/syzkaller/prog.(*Prog).Clone(0xc001d8d100, 0xc002fdb470)
> /syzkaller/gopath/src/github.com/google/syzkaller/prog/clone.go:20 +0x270
> main.(*Proc).loop(0xc002fc86c0)
> /syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/proc.go:98
> +0x3cb
> created by main.main
> /syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/fuzzer.go:258
> +0x111b
>
>
>
> ---
> This bug 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 bug report. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-openbsd-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-openbsd...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-openbsd-bugs/0000000000002910cb0593d5d830%40google.com.

[Greg Steuck]

Does it seem like a bug syzkaller rather than OpenBSD? I'm trying to determine how to dispose of this report.

To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-openbsd-bugs/CACT4Y%2BaEb4A9-0Z89KpjvYMV103Dst4W7e_EfH2%2BnoQYxODmKw%40mail.gmail.com.

--

nest.cx is Gmail hosted, use PGP: https://pgp.key-server.io/0x0B1542BD8DF5A1B0
Fingerprint: 5E2B 2D0E 1E03 2046 BEC3  4D50 0B15 42BD 8DF5 A1B0

[Dmitry Vyukov]

On Tue, Oct 1, 2019 at 6:24 PM Greg Steuck <gr...@nest.cx> wrote:
>
> Does it seem like a bug syzkaller rather than OpenBSD? I'm trying to determine how to dispose of this report.

Hard to say. So far it looks like a process/machine memory corruption,
which would be an OpenBSD bug ;)

Let's close this for now. If it will get back later, we will find this
report as well.

#syz invalid