On Wed, May 27, 2020 at 1:33 AM Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > > Hi Dmitry, > > On Tue, 26 May 2020 14:09:28 +0200 Dmitry Vyukov <dvyukov@xxxxxxxxxx> wrote: > > > > On Fri, May 22, 2020 at 6:29 AM Tetsuo Handa > > <penguin-kernel@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > Hello. > > > > > > This report is already reporting next problem. Since the location seems to be > > > different, this might be caused by OOM due to too much parallel compilation. > > > Maybe syzbot can detect "gcc: fatal error: Killed signal terminated program cc1" > > > sequence and retry with reduced "make -j$NUM" settings. > > > > > > gcc: fatal error: Killed signal terminated program cc1 > > > compilation terminated. > > > scripts/Makefile.build:272: recipe for target 'fs/xfs/libxfs/xfs_btree.o' failed > > > make[2]: *** [fs/xfs/libxfs/xfs_btree.o] Error 1 > > > make[2]: *** Waiting for unfinished jobs.... > > > > +linux-next and XFS maintainers > > What version of linux-next is this? There was a problem last week with > some changes in the tip tree that caused large memory usage. Hi Stephen, Detailed info about each syzbot crash is always available over the dashboard link: https://syzkaller.appspot.com/bug?extid=792dec47d693ccdc05a0 Crashes (4): Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro ci-upstream-linux-next-kasan-gce-root 2020/05/22 01:23 linux-next e8f32747 5afa2ddd .config log report ci-upstream-linux-next-kasan-gce-root 2020/05/21 15:01 linux-next e8f32747 1f30020f .config log report ci-upstream-linux-next-kasan-gce-root 2020/05/19 18:24 linux-next fb57b1fa 6d882fd2 .config log report ci-upstream-linux-next-kasan-gce-root 2020/03/18 16:19 linux-next 47780d78 0a96a13c .config log report
