netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Roberts <ryan.roberts@arm.com>
To: syzbot <syzbot+263f159eb37a1c4c67a4@syzkaller.appspotmail.com>,
	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,
	syzkaller-bugs@googlegroups.com, tiwai@suse.com,
	willemb@google.com
Subject: Re: [syzbot] [sound?] kernel BUG in filemap_fault (2)
Date: Tue, 16 Sep 2025 13:50:08 +0100	[thread overview]
Message-ID: <80840307-942d-4e7b-849d-2ca9bb4bbefa@arm.com> (raw)
In-Reply-To: <68c69e17.050a0220.3c6139.04e1.GAE@google.com>

On 14/09/2025 11:51, syzbot wrote:
> 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()

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/

If so, the fix for that was squashed into the original patch before it was
merged upstream. That is now Commit 38b0ece6d763 ("mm/filemap: allow arch to
request folio size for exec memory").

Thanks,
Ryan


> 
> 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


  reply	other threads:[~2025-09-16 12:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <684ffc59.a00a0220.279073.0037.GAE@google.com>
2025-07-03 16:43 ` [syzbot] [net?] kernel BUG in filemap_fault (2) syzbot
2025-09-14 10:51 ` [syzbot] [sound?] " syzbot
2025-09-16 12:50   ` Ryan Roberts [this message]
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=80840307-942d-4e7b-849d-2ca9bb4bbefa@arm.com \
    --to=ryan.roberts@arm.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=syzbot+263f159eb37a1c4c67a4@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).