From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+263f159eb37a1c4c67a4@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] kernel BUG in filemap_fault (2)
Date: Fri, 4 Jul 2025 10:20:15 +0800 [thread overview]
Message-ID: <20250704022016.2331-1-hdanton@sina.com> (raw)
In-Reply-To: <6866b332.a00a0220.c7b3.0005.GAE@google.com>
> Date: Thu, 03 Jul 2025 09:43:30 -0700
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: b4911fb0b060 Merge tag 'mmc-v6.16-rc1' of git://git.kernel..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=16568c8c580000
> 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
#syz test
--- x/mm/filemap.c
+++ y/mm/filemap.c
@@ -3439,7 +3439,6 @@ retry_find:
folio_put(folio);
goto retry_find;
}
- VM_BUG_ON_FOLIO(!folio_contains(folio, index), folio);
/*
* We have a locked folio in the page cache, now we need to check
@@ -3490,6 +3489,7 @@ retry_find:
return VM_FAULT_SIGBUS;
}
+ VM_BUG_ON_FOLIO(!folio_contains(folio, index), folio);
vmf->page = folio_file_page(folio, index);
return ret | VM_FAULT_LOCKED;
--
next prev parent reply other threads:[~2025-07-04 2:20 UTC|newest]
Thread overview: 10+ 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-07-04 2:20 ` Hillf Danton [this message]
2025-07-04 3:00 ` syzbot
2025-09-14 10:51 ` [syzbot] [sound?] " syzbot
2025-09-16 12:50 ` 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=20250704022016.2331-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+263f159eb37a1c4c67a4@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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