The latest usable and stable version of Syzkaller

[Zhang Zhiyu]

Hi community,

In the past, I was using a version of Syzkaller released at the end of last year. Recently, I found that there are many changes happened in syz-manager, syz-fuzzer and pkg (key modules reprensenting the mechanisms of Syzkaller) by glancing over the code along with the commits. Many functions have been re-constructured and many new features have been introduced. 

However, there are also some commits which do not pass the stages of Git Action or are proposed for fixing typos and bugs, which indicating the versions ahead of these commits may not be reliable. (I tested 3ba885b on 5.15.y Linux kernel for many times and obverved two unexpected exits after a period of normal fuzzing. I lost the printed error logs but this can confirm my concerns on the usability and stability)

So if I want to use the latest Syzkaller with newer features, could you tell me a usable and stable version/commit?

Best!

Zhiyu

[Aleksandr Nogikh]

Hi Zhiyu,

We don't designate some stable branches / tags as opposed to
development / unstable ones. Things break at times, but we try to fix
critical issues as soon as possible.

There have indeed been many changes recently, though I'm not aware of
any known, but not yet fixed bugs that should cause syzkaller to exit
unexpectedly. If you observe crashes on the latest revision, please
share the logs with us and we'll address the problem(s).

3ba885b is quite old already. Could
https://github.com/google/syzkaller/issues/4715 have been the issue
that you saw?

--
Aleksandr

> --
> You received this message because you are subscribed to the Google Groups "syzkaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller/984db989-028e-41fa-95e5-bee7f8f230a9n%40googlegroups.com.

[Zhang Zhiyu]

Hi Aleksandr

Thanks for your reply. The issue #4715 is extactlly what I have encountered on 3ba885b.

> There have indeed been many changes recently, though I'm not aware of any known, but not yet fixed bugs that should cause syzkaller to exit unexpectedly. If you observe crashes on the latest revision, please share the logs with us and we'll address the problem(s).

Sure. Does the red X marked as failed in Git Action affect the usability of the commit? Is commit https://github.com/google/syzkaller/commit/1014eca a good choice for reprensenting the latest stable Syzkaller with new features?

Best!

Zhiyu

[Aleksandr Nogikh]

Hi Zhiyu,

On Fri, May 24, 2024 at 11:34 AM Zhang Zhiyu <zhiyuz...@gmail.com> wrote:
>
> Hi Aleksandr
>
> Thanks for your reply. The issue #4715 is extactlly what I have encountered on 3ba885b.
>
> > There have indeed been many changes recently, though I'm not aware of any known, but not yet fixed bugs that should cause syzkaller to exit unexpectedly. If you observe crashes on the latest revision, please share the logs with us and we'll address the problem(s).
>
> Sure. Does the red X marked as failed in Git Action affect the usability of the commit?

Not necessarily. These tests are the same as our presubmit tests, so
those commits wouldn't have been merged in the first place if they
were not passing them. If you see red X in our commit history, it's
usually due to sporadic problems with GitHub action runners or some
flaky tests.

> Is commit https://github.com/google/syzkaller/commit/1014eca a good choice for reprensenting the latest stable Syzkaller with new features?

I cannot really say. As long as no problem has been found, all commits
are good :)

--
Aleksandr