Re: bad config syzkaller param: can't find /syzkaller/jobs-2/netbsd/gopath/src/github.com/google/syzkaller/bin/netbsd_amd64/syz-executor

[Taylor R Campbell <riastradh%NetBSD.org@localhost>]

> Date: Wed, 19 Apr 2023 14:37:23 +0200
> From: Aleksandr Nogikh <nogikh%google.com@localhost>
> 
> On Wed, Apr 19, 2023 at 10:11 AM Taylor R Campbell <riastradh%netbsd.org@localhost> wrote:
> >
> > Looks like syzkaller is having trouble running NetBSD jobs again?
> >
> > https://syzkaller.appspot.com/text?tag=Error&x=17eb5d3fc80000
> 
> Thank you for reporting!
> Indeed, there seem to be some problems. I've looked into that for some
> time and filed https://github.com/google/syzkaller/issues/3819. I'll
> let you know when it's fixed.

Great, thanks!

> It's interesting that there are many "pmap_unwire: wiring for pmap
> <...> did not change!"-like messages in logs for both bugs [1] [2].
> What does it mean?
> 
> [1] https://syzkaller.appspot.com/text?tag=CrashLog&x=1455193fc80000
> [2] https://syzkaller.appspot.com/text?tag=CrashLog&x=15e5f9b7c80000

Both logs have this line in it, followed by opening and writing to
this file:

compat_50_mknod(&(0x7f0000000000)='./file0\x00', 0x2001, 0x400)

As Chuck explained, this creates a device node mapping the swap space;
if any swap files or devices are configured, writing to this device
node would likely corrupt userland process memory and/or crash
processes.  So I think both of these crash logs are red herrings.

-- 
You received this message because you are subscribed to the Google Groups "syzkaller-netbsd-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-netbsd-bugs+unsubscribe%googlegroups.com@localhost.
To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-netbsd-bugs/20230419194728.2A4366086C%40jupiter.mumble.net.