Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <4e345a16-bdc9-6f1e-9bb9-0ba35fa69e3e@bytedance.com>
Date:   Thu, 6 Apr 2023 17:37:26 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
 Gecko/20100101 Thunderbird/102.9.1
Subject: Re: [syzbot] Monthly mm report
To:     syzkaller@googlegroups.com,
        syzbot+listf2f28c8e4d5809654f88@syzkaller.appspotmail.com
References: <00000000000032660805f8337db1@google.com>
Content-Language: en-US
Cc:     linux-kernel@vger.kernel.org, linux-mm@kvack.org,
        syzkaller-bugs@googlegroups.com
From:   Gang Li <ligang.bdlg@bytedance.com>
In-Reply-To: <00000000000032660805f8337db1@google.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi, syzbot engineers.

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.

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@googlegroups.com.
>