From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: syzbot <syzbot+c0673e1f1f054fac28c2@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, david@redhat.com, hdanton@sina.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com, willy@infradead.org
Subject: Re: [syzbot] [mm?] WARNING in __folio_rmap_sanity_checks (2)
Date: Fri, 10 Jan 2025 16:03:04 -0500 [thread overview]
Message-ID: <ggit5gyjshv2cha4yicgwms64dfpb7jvohei2xfjivws7ittbk@maulvw742inf> (raw)
In-Reply-To: <676fee37.050a0220.2f3838.0497.GAE@google.com>
* syzbot <syzbot+c0673e1f1f054fac28c2@syzkaller.appspotmail.com> [241228 07:25]:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 8155b4ef3466 Add linux-next specific files for 20241220
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1661050f980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=9c90bb7161a56c88
> dashboard link: https://syzkaller.appspot.com/bug?extid=c0673e1f1f054fac28c2
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17438af8580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=101006df980000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/98a974fc662d/disk-8155b4ef.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/2dea9b72f624/vmlinux-8155b4ef.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/593a42b9eb34/bzImage-8155b4ef.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/5f780361c9ef/mount_0.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+c0673e1f1f054fac28c2@syzkaller.appspotmail.com
>
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm mm-unstable
next prev parent reply other threads:[~2025-01-10 21:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 1:54 syzbot
2024-12-11 10:06 ` David Hildenbrand
2024-12-28 4:56 ` syzbot
2024-12-31 8:41 ` Hillf Danton
2024-12-31 9:09 ` syzbot
2025-01-10 16:35 ` David Hildenbrand
2025-01-11 1:00 ` Hillf Danton
2025-01-11 10:03 ` David Hildenbrand
2024-12-28 12:25 ` syzbot
2025-01-10 15:48 ` David Hildenbrand
2025-01-10 16:14 ` Matthew Wilcox
2025-01-10 16:19 ` David Hildenbrand
2025-01-10 16:27 ` Matthew Wilcox
2025-01-10 16:31 ` David Hildenbrand
2025-01-10 19:55 ` Liam R. Howlett
2025-01-10 21:24 ` Suren Baghdasaryan
2025-01-11 4:29 ` Liam R. Howlett
2025-01-10 21:03 ` Liam R. Howlett [this message]
2025-01-11 6:15 ` syzbot
2025-01-11 9:25 ` David Hildenbrand
2025-01-11 9:54 ` syzbot
2025-01-13 15:39 ` David Hildenbrand
2025-01-13 15:45 ` Liam R. Howlett
2025-01-13 15:50 ` David Hildenbrand
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=ggit5gyjshv2cha4yicgwms64dfpb7jvohei2xfjivws7ittbk@maulvw742inf \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+c0673e1f1f054fac28c2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox