linux-kernel - Re: [syzbot] Monthly mm report

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 6 Apr 2023 11:53:06 +0200
From:   Aleksandr Nogikh <nogikh@...gle.com>
To:     Gang Li <ligang.bdlg@...edance.com>
Cc:     syzkaller@...glegroups.com,
        syzbot+listf2f28c8e4d5809654f88@...kaller.appspotmail.com,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org,
        syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] Monthly mm report

On Thu, Apr 6, 2023 at 11:38 AM 'Gang Li' via syzkaller
<syzkaller@...glegroups.com> wrote:
>
> Hi, syzbot engineers.

Hi!

>
> As far as I know, syzkaller provides a reproduction code for each error.
> However, I couldn't find the code in the website[1]. Did I miss
> something? How can I get the reproduction code?
>
> I want to help fix some bugs.

That's really great!

Yes, for most bugs syzbot succeeds in finding a C reproducer. If a
repro is found, we alway give a link to the reproducer in email bug
reports.

To find it on the web dashboard, you first need to go to the specific
bug page (click on one of the bug titles in [1]). E.g.
https://syzkaller.appspot.com/bug?id=4ecce7e55e02002f794e28cbac1682346d423737

At the bottom of such a bug page, there will be a list of crashes. And
in that table, there's a "C repro" column with links to C reproducers
that have been found for the bug.

--
Aleksandr

>
> Thanks!
>
> [1] https://syzkaller.appspot.com/upstream/s/mm
>
> On 2023/3/31 23:01, syzbot wrote:
> > Hello mm maintainers/developers,
> >
> > This is a 30-day syzbot report for the mm subsystem.
> > All related reports/information can be found at:
> > https://syzkaller.appspot.com/upstream/s/mm
> >
> > During the period, 15 new issues were detected and 2 were fixed.
> > In total, 120 issues are still open and 197 have been fixed so far.
> >
> > Some of the still happening issues:
> >
> > Crashes Repro Title
> > 1899    Yes   WARNING in split_huge_page_to_list (2)
> >                https://syzkaller.appspot.com/bug?extid=07a218429c8d19b1fb25
> > 176     Yes   INFO: task hung in do_read_cache_folio
> >                https://syzkaller.appspot.com/bug?extid=be946efe33b2d9664348
> > 92      Yes   INFO: task hung in __filemap_get_folio
> >                https://syzkaller.appspot.com/bug?extid=0e9dc403e57033a74b1d
> > 52      Yes   INFO: task hung in __lru_add_drain_all
> >                https://syzkaller.appspot.com/bug?extid=a9b681dcbc06eb2bca04
> > 38      Yes   INFO: rcu detected stall in syscall_exit_to_user_mode (2)
> >                https://syzkaller.appspot.com/bug?extid=a68ef3b1f46bc3aced5c
> > 18      Yes   kernel BUG in folio_end_writeback
> >                https://syzkaller.appspot.com/bug?extid=7e5cf1d80677ec185e63
> >
> > ---
> > 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 syzkaller@...glegroups.com.
> >
>