Re: NetBSD syzbot broken?

["'Aleksandr Nogikh' via syzkaller-netbsd-bugs" <syzkaller-netbsd-bugs%googlegroups.com@localhost>]

Thanks for reaching out!

On Fri, Dec 20, 2024 at 2:01 AM Taylor R Campbell <riastradh%netbsd.org@localhost> wrote:
>
> Looks like the NetBSD syzbot is still not running, but for different
> reasons now:
>
> https://syzkaller.appspot.com/bug?extid=848e5b707cc911337a29 looks
> like a bug in the NetBSD build which was fixed back in October by
> adding shquote(3) to libnbcompat during the tools build

Does something need to be done on the syzbot side to incorporate this fix?

>
> https://syzkaller.appspot.com/bug?extid=85f03a4da9f6aedf4c44 looks
> like a golang build problem that probably isn't NetBSD specific?
>
> --- FAIL: TestFuzz (11.34s)
>     testutil.go:35: seed=1733770450604578864
>     fuzzer_test.go:210: CRASH: first bug
>     fuzzer_test.go:210: CRASH: second bug
>     fuzzer_test.go:88: resulting corpus:
>     testing.go:1231: TempDir RemoveAll cleanup: unlinkat /tmp/TestFuzz1015377258/001: directory not empty
> FAIL

This looks like a one-off reincarnation of
https://github.com/google/syzkaller/issues/4920
It may cause syzbot sometimes to not update to a newer revision, but
it should not prevent it from doing fuzzing.

>
> https://syzkaller.appspot.com/bug?extid=ed1ef9cf91c3de65d44b looks
> like a testbed problem with posix_spawnp -- presumably this is
> happening before anything even starts running NetBSD?

Yes, it happens when syzbot tries to update to a newer NetBSD kernel
revision. It runs syz-manager with a "-mode=smoke-test" option and
that quickly fails with "SYZFAIL: posix_spawnp failed".

This must have begun after
https://github.com/google/syzkaller/commit/bc1a1b50f942408a9139887b914f745d9fa02adc

>
> Can I trouble any of you folks to help get syzbot again on NetBSD?
> Anything I can do to help make it happen?

It would really help if you could take a look at the posix_spawnp()
invocation in the commit I referenced above. On NetBSD, the syscall
fails with "errno 22: Invalid argument". What could be that invalid
argument? Why was posix_spawn() working fine?

-- 
Aleksandr

-- 
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 visit https://groups.google.com/d/msgid/syzkaller-netbsd-bugs/CANp29Y7vQ4%2BxHn8d8CnbR6UTEyzmyu%3DsragzZPQZQMCiyr-vRw%40mail.gmail.com.