From: syzbot <syzbot+263f159eb37a1c4c67a4@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, chaitanyas.prakash@arm.com,
davem@davemloft.net, david@redhat.com, edumazet@google.com,
hdanton@sina.com, horms@kernel.org, jack@suse.cz,
kuba@kernel.org, kuniyu@google.com,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, perex@perex.cz,
ryan.roberts@arm.com, syzkaller-bugs@googlegroups.com,
tiwai@suse.com, willemb@google.com
Subject: Re: [syzbot] [sound?] kernel BUG in filemap_fault (2)
Date: Sun, 14 Sep 2025 03:51:03 -0700 [thread overview]
Message-ID: <68c69e17.050a0220.3c6139.04e1.GAE@google.com> (raw)
In-Reply-To: <684ffc59.a00a0220.279073.0037.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit bdb86f6b87633cc020f8225ae09d336da7826724
Author: Ryan Roberts <ryan.roberts@arm.com>
Date: Mon Jun 9 09:27:23 2025 +0000
mm/readahead: honour new_order in page_cache_ra_order()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1100b934580000
start commit: b4911fb0b060 Merge tag 'mmc-v6.16-rc1' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=3f6ddf055b5c86f8
dashboard link: https://syzkaller.appspot.com/bug?extid=263f159eb37a1c4c67a4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=157cf48c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=146a948c580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mm/readahead: honour new_order in page_cache_ra_order()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-09-14 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 11:13 [syzbot] [sound?] kernel BUG in filemap_fault (2) syzbot
2025-07-03 16:43 ` [syzbot] [net?] " syzbot
2025-09-14 10:51 ` syzbot [this message]
2025-09-16 12:50 ` [syzbot] [sound?] " Ryan Roberts
2025-09-16 13:05 ` Jan Kara
2025-09-17 7:57 ` David Hildenbrand
2025-09-17 8:35 ` Jan Kara
2025-09-17 9:04 ` 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=68c69e17.050a0220.3c6139.04e1.GAE@google.com \
--to=syzbot+263f159eb37a1c4c67a4@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=chaitanyas.prakash@arm.com \
--cc=davem@davemloft.net \
--cc=david@redhat.com \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=horms@kernel.org \
--cc=jack@suse.cz \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=perex@perex.cz \
--cc=ryan.roberts@arm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox