From: "David Hildenbrand (Arm)" <david@kernel.org>
To: syzbot <syzbot+8961cb270ae74b4129fb@syzkaller.appspotmail.com>,
Liam.Howlett@oracle.com, akpm@linux-foundation.org,
baohua@kernel.org, baolin.wang@linux.alibaba.com,
dev.jain@arm.com, lance.yang@linux.dev,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org,
npache@redhat.com, ryan.roberts@arm.com,
syzkaller-bugs@googlegroups.com, ziy@nvidia.com
Subject: Re: [syzbot] [mm?] kernel BUG in collapse_scan_file
Date: Thu, 19 Mar 2026 08:22:49 +0100 [thread overview]
Message-ID: <ede0988a-a031-4d8d-82c3-ed6f3de89e6d@kernel.org> (raw)
In-Reply-To: <69bba3c0.050a0220.227207.002b.GAE@google.com>
On 3/19/26 08:20, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 95c541ddfb08 Add linux-next specific files for 20260316
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=15ccc216580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ed431987028345c6
> dashboard link: https://syzkaller.appspot.com/bug?extid=8961cb270ae74b4129fb
> compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12f778da580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12cc006a580000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/c40f27ad73d8/disk-95c541dd.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/bd811888f684/vmlinux-95c541dd.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/3b72363d7dbd/bzImage-95c541dd.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+8961cb270ae74b4129fb@syzkaller.appspotmail.com
@Nico, maybe related to your changes?
--
Cheers,
David
next prev parent reply other threads:[~2026-03-19 7:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 7:20 [syzbot] [mm?] kernel BUG in collapse_scan_file syzbot
2026-03-19 7:22 ` David Hildenbrand (Arm) [this message]
2026-03-19 8:05 ` Lance Yang
2026-03-19 8:53 ` Lorenzo Stoakes (Oracle)
2026-03-19 9:00 ` David Hildenbrand (Arm)
2026-03-19 9:14 ` Lance Yang
2026-03-19 9:21 ` David Hildenbrand (Arm)
2026-03-19 10:27 ` Lorenzo Stoakes (Oracle)
2026-03-19 10:59 ` David Hildenbrand (Arm)
2026-03-19 11:07 ` Lorenzo Stoakes (Oracle)
2026-03-19 11:10 ` David Hildenbrand (Arm)
2026-03-19 11:12 ` Lorenzo Stoakes (Oracle)
2026-03-19 10:56 ` Vlastimil Babka
2026-03-19 11:04 ` Lorenzo Stoakes (Oracle)
2026-03-19 12:17 ` Mark Brown
2026-03-20 12:39 ` Mark Brown
2026-03-20 13:17 ` Lorenzo Stoakes (Oracle)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ede0988a-a031-4d8d-82c3-ed6f3de89e6d@kernel.org \
--to=david@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=syzbot+8961cb270ae74b4129fb@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.