syzkaller: testing failed: failed to run ["go" "test" "-short" "./..."]: exit status 1 (25)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:
git tree: https://github.com/google/syzkaller.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=10d9c20f980000
dashboard link: https://syzkaller.appspot.com/bug?extid=94080caf3163d1964354
compiler: go version go1.23.0 openbsd/amd64

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



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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[Greg Steuck]

Something is not quite right with this test. I managed to repro it once, then it wouldn't repro. The test seems to be non-repeatable and we don't set SYZ_SEED so this shouldn't be surprising.

@Dmitry Vyukov do you know what is supposed to be happening with NONBLOCKING? I can't seem to figure out where it should be coming from on OpenBSD. At least the executor/common.h isn't included hence the symbol is not found.

--
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 visit https://groups.google.com/d/msgid/syzkaller-openbsd-bugs/67597013.050a0220.17f54a.003a.GAE%40google.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

[Aleksandr Nogikh]

Hi Greg,

On Sat, Dec 14, 2024 at 7:44 PM Greg Steuck <gr...@nest.cx> wrote:
>
> Something is not quite right with this test. I managed to repro it once, then it wouldn't repro. The test seems to be non-repeatable and we don't set SYZ_SEED so this shouldn't be surprising.

It seems to be set, though it's weird that it's set twice.

--- FAIL: TestGenerate (13.85s)
--- FAIL: TestGenerate/openbsd/amd64 (0.22s)
testutil.go:35: seed=1733914331015041346
testutil.go:35: seed=1733914331229339601

>
> @Dmitry Vyukov do you know what is supposed to be happening with NONBLOCKING? I can't seem to figure out where it should be coming from on OpenBSD. At least the executor/common.h isn't included hence the symbol is not found.

Did you mean NONFAILING?
OpenBSD should have used this one:
https://github.com/google/syzkaller/blob/7cbfbb3ab457b0a8ecf525a27a65a2078c5dcaa8/executor/common.h#L150

It seems as if SYZ_HANDLE_SEGV ended up not being defined for some reason.

[Greg Steuck]

On Sat, Dec 14, 2024 at 11:51 PM Aleksandr Nogikh <nog...@google.com> wrote:

Hi Greg,

On Sat, Dec 14, 2024 at 7:44 PM Greg Steuck <gr...@nest.cx> wrote:
>
> Something is not quite right with this test. I managed to repro it once, then it wouldn't repro. The test seems to be non-repeatable and we don't set SYZ_SEED so this shouldn't be surprising.

It seems to be set, though it's weird that it's set twice.

--- FAIL: TestGenerate (13.85s)
    --- FAIL: TestGenerate/openbsd/amd64 (0.22s)
        testutil.go:35: seed=1733914331015041346
        testutil.go:35: seed=1733914331229339601

>
> @Dmitry Vyukov do you know what is supposed to be happening with NONBLOCKING? I can't seem to figure out where it should be coming from on OpenBSD. At least the executor/common.h isn't included hence the symbol is not found.

Did you mean NONFAILING?
OpenBSD should have used this one:
https://github.com/google/syzkaller/blob/7cbfbb3ab457b0a8ecf525a27a65a2078c5dcaa8/executor/common.h#L150

It seems as if SYZ_HANDLE_SEGV ended up not being defined for some reason.

Yeah, the reproducibility of this test is not great. E.g. here it passed: https://syzkaller.appspot.com/text?tag=CrashLog&x=109274f8580000

OTOH, this other test failed:

--- FAIL: TestRotationCoverage (13.68s)
    testutil.go:35: seed=1734435646254357437
    rotation_test.go:100: #    0:  9658 socket$nl_generic
    rotation_test.go:100: #    1:  7108 bpf$TOKEN_CREATE
    rotation_test.go:100: #    2:  6619 bpf$MAP_CREATE_CONST_STR

...

    rotation_test.go:100: # 6588:    0 ioctl$F2FS_IOC_COMPRESS_FILE
    rotation_test.go:103: uncovered syscalls: 1
FAIL
FAIL github.com/google/syzkaller/prog 49.354s

 

[syzbot]

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