[v5.15] kernel BUG in unaccount_page_cache_page

0 views
Skip to first unread message

syzbot

unread,
Mar 13, 2024, 5:58:22 AMMar 13
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 574362648507 Linux 5.15.151
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=173d0859180000
kernel config: https://syzkaller.appspot.com/x/.config?x=9f05b19a5fda27f0
dashboard link: https://syzkaller.appspot.com/bug?extid=6c76736fd94bfa80a8d0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1300f61a180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=161489b6180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3b670cadd741/disk-57436264.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8160de48506f/vmlinux-57436264.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9cd83ff92303/Image-57436264.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6c7673...@syzkaller.appspotmail.com

raw: 05ffc00000080017 fffffc00037f2708 fffffc00037f2788 ffff0000c1cbe098
raw: 0000000000000000 0000000000000000 0000000400000000 ffff0000c08a4000
page dumped because: VM_BUG_ON_PAGE(page_mapped(page))
------------[ cut here ]------------
kernel BUG at mm/filemap.c:166!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 3961 Comm: syz-executor235 Not tainted 5.15.151-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : unaccount_page_cache_page+0x600/0x744 mm/filemap.c:166
lr : unaccount_page_cache_page+0x600/0x744 mm/filemap.c:166
sp : ffff80001cdd7160
x29: ffff80001cdd7160 x28: dfff800000000000 x27: 1ffff000039bae90
x26: 1fffff80006fe4e9 x25: dfff800000000000 x24: fffffc00037f2708
x23: 0000000000000000 x22: fffffc00037f2708 x21: fffffc00037f2748
x20: ffff0000c1cbe098 x19: fffffc00037f2740 x18: 0000000000000002
x17: 0000000000000000 x16: ffff80001197884c x15: 00000000ffffffff
x14: ffff0000dac351c0 x13: 0000000000000001 x12: 0000000000000001
x11: 0000000000000001 x10: 0000000000000000 x9 : 8e9670d46ac93b00
x8 : 8e9670d46ac93b00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001cdd65d8 x4 : ffff8000149ef720 x3 : ffff80000854e218
x2 : 0000000000000001 x1 : 0000000100000001 x0 : 0000000000000036
Call trace:
unaccount_page_cache_page+0x600/0x744 mm/filemap.c:166
__delete_from_page_cache+0xc8/0x6d4 mm/filemap.c:231
delete_from_page_cache+0x108/0x17c mm/filemap.c:266
truncate_inode_page+0x98/0xc8 mm/truncate.c:219
shmem_undo_range+0x448/0x1460 mm/shmem.c:960
shmem_truncate_range mm/shmem.c:1063 [inline]
shmem_evict_inode+0x1c4/0x844 mm/shmem.c:1145
evict+0x260/0x68c fs/inode.c:587
iput_final fs/inode.c:1705 [inline]
iput+0x744/0x824 fs/inode.c:1731
dentry_unlink_inode+0x370/0x4b0 fs/dcache.c:376
__dentry_kill+0x324/0x5e4 fs/dcache.c:582
dentry_kill+0xc8/0x250
dput+0x21c/0x458 fs/dcache.c:889
__fput+0x500/0x7f0 fs/file_table.c:288
____fput+0x20/0x30 fs/file_table.c:308
task_work_run+0x130/0x1e4 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
do_notify_resume+0x262c/0x32b8 arch/arm64/kernel/signal.c:946
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
el0_svc+0xfc/0x1f0 arch/arm64/kernel/entry-common.c:609
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: f004a341 913c8021 aa1303e0 94037048 (d4210000)
---[ end trace fb26667d676d4a42 ]---


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages