[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <lqzgi7abe2onda3faavn5ays6gdw4syiu32hmrfaibrh6cmozs@pjf3llvnnefk>
Date: Tue, 16 Sep 2025 15:05:14 +0200
From: Jan Kara <jack@...e.cz>
To: Ryan Roberts <ryan.roberts@....com>
Cc: syzbot <syzbot+263f159eb37a1c4c67a4@...kaller.appspotmail.com>,
akpm@...ux-foundation.org, chaitanyas.prakash@....com, davem@...emloft.net,
david@...hat.com, edumazet@...gle.com, hdanton@...a.com, horms@...nel.org,
jack@...e.cz, kuba@...nel.org, kuniyu@...gle.com, linux-kernel@...r.kernel.org,
linux-sound@...r.kernel.org, netdev@...r.kernel.org, pabeni@...hat.com, perex@...ex.cz,
syzkaller-bugs@...glegroups.com, tiwai@...e.com, willemb@...gle.com
Subject: Re: [syzbot] [sound?] kernel BUG in filemap_fault (2)
On Tue 16-09-25 13:50:08, Ryan Roberts wrote:
> On 14/09/2025 11:51, syzbot wrote:
> > syzbot suspects this issue was fixed by commit:
> >
> > commit bdb86f6b87633cc020f8225ae09d336da7826724
> > Author: Ryan Roberts <ryan.roberts@....com>
> > Date: Mon Jun 9 09:27:23 2025 +0000
> >
> > mm/readahead: honour new_order in page_cache_ra_order()
>
> I'm not sure what original bug you are claiming this is fixing? Perhaps this?
>
> https://lore.kernel.org/linux-mm/6852b77e.a70a0220.79d0a.0214.GAE@google.com/
I think it was:
https://lore.kernel.org/all/684ffc59.a00a0220.279073.0037.GAE@google.com/
at least that's what the syzbot email replies to... And it doesn't make a
lot of sense but it isn't totally off either. So I'd just let the syzbot
bug autoclose after some timeout.
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists