multicore test error: SYZFATAL: BUG: program execution failed: executor NUM: EOF

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c1cc27a74adf hw.power, machdep.lidaction, machdep.pwractio..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1216d2e2880000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=a981186b8fa5af7d9667

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3b125592f9fd/disk-c1cc27a7.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/5b720d7e8c52/bsd-c1cc27a7.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d8a4916718ba/kernel-c1cc27a7.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a98118...@syzkaller.appspotmail.com

2022/10/21 22:40:59 SYZFATAL: BUG: program execution failed: executor 0: EOF
SYZFAIL: mmap of input file failed
want 0x82bf8fce000, got 0xffffffffffffffff (errno 1: Operation not permitted)



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

[Anton Lindqvist]

Hopefully fixed by: https://github.com/google/syzkaller/pull/3461

#syz invalid

[Greg Steuck]

I see the commit is in the syzbot tree yet the builds are still marked as failing.

https://syzkaller.appspot.com/bug?id=236057dba836dfa7c3a634327fec096d1ecd63c8

On Sun, Oct 23, 2022 at 12:04 PM Anton Lindqvist <an...@basename.se> wrote:

Hopefully fixed by: https://github.com/google/syzkaller/pull/3461

#syz invalid

--
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/Y1WQU68O9vai6qJ5%40amd64.basename.se.

--

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

[Greg Steuck]

I suspect we need a new OpenBSD image because the newer kernels are likely incompatible enough.

At least I got past this problem locally using the Oct 22 snapshot when I ran it this way:

$ bin/openbsd_amd64/syz-executor exec 3</dev/zero 4>/dev/zero

[Anton Lindqvist]

On Sun, Oct 23, 2022 at 04:14:09PM -0700, Greg Steuck wrote:
> I suspect we need a new OpenBSD image because the newer kernels are likely
> incompatible enough.
>
> At least I got past this problem locally using the Oct 22 snapshot when I
> ran it this way:
>
> $ bin/openbsd_amd64/syz-executor exec 3</dev/zero 4>/dev/zero

Who does the updates nowadays?

[Aleksandr Nogikh]

I've just run the
https://github.com/google/syzkaller/blob/master/dashboard/config/openbsd/recreate.sh
script, but the image testing problems seem to remain.

> --
> 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/Y1Yb1anyxgN7tPTq%40amd64.basename.se.

[Anton Lindqvist]

On Sun, Oct 23, 2022 at 04:14:09PM -0700, Greg Steuck wrote:

> I suspect we need a new OpenBSD image because the newer kernels are likely
> incompatible enough.
>
> At least I got past this problem locally using the Oct 22 snapshot when I
> ran it this way:
>
> $ bin/openbsd_amd64/syz-executor exec 3</dev/zero 4>/dev/zero

Seems like things are back to normal now, currently at syzkaller commit:

https://github.com/google/syzkaller/commits/456454209820a5cf121a82aff83aa4d47316cf14