Hello,
syzbot found the following issue on:
HEAD commit: 6139f2a02fe0 Linux 5.15.148
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=15847f68180000
kernel config:
https://syzkaller.appspot.com/x/.config?x=c3cfb017ec09dfb8
dashboard link:
https://syzkaller.appspot.com/bug?extid=c0ffed3897231d71f047
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/863dea226ad0/disk-6139f2a0.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/db1a0715548e/vmlinux-6139f2a0.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/edd9bd0f16ff/Image-6139f2a0.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+c0ffed...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4003 at fs/iomap/buffered-io.c:80 iomap_page_release+0x30c/0x438 fs/iomap/buffered-io.c:79
Modules linked in:
CPU: 1 PID: 4003 Comm: syz-executor.4 Not tainted 5.15.148-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : iomap_page_release+0x30c/0x438 fs/iomap/buffered-io.c:79
lr : iomap_page_release+0x30c/0x438 fs/iomap/buffered-io.c:79
sp : ffff80001ce27480
x29: ffff80001ce27480 x28: 0000000000000008 x27: ffff800011b4d5a0
x26: 1fffff8000917139 x25: dfff800000000000 x24: 0000000000000000
x23: 0000000000000002 x22: 0000000000000002 x21: 05ffc00000000011
x20: ffff0000d87f1200 x19: 0000000000000000 x18: 0000000000000000
x17: 0000000000000000 x16: ffff80001198323c x15: 0000000000000406
x14: 00000000ffff8000 x13: 00000000895682e3 x12: 0000000000000001
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000c2d9d1c0
x8 : ffff800008b3aa64 x7 : 0000000000000000 x6 : 000000000000003f
x5 : 0000000000000040 x4 : 0000000000000000 x3 : ffff800008b3a974
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
iomap_page_release+0x30c/0x438 fs/iomap/buffered-io.c:79
iomap_invalidatepage+0x2c4/0x568 fs/iomap/buffered-io.c:490
do_invalidatepage mm/truncate.c:157 [inline]
truncate_cleanup_page+0x15c/0x414 mm/truncate.c:176
truncate_inode_pages_range+0x254/0xbe0 mm/truncate.c:325
truncate_inode_pages mm/truncate.c:425 [inline]
truncate_inode_pages_final+0x94/0xd0 mm/truncate.c:464
evict+0x26c/0x68c fs/inode.c:589
dispose_list fs/inode.c:620 [inline]
evict_inodes+0x6b4/0x74c fs/inode.c:670
generic_shutdown_super+0x9c/0x29c fs/super.c:454
kill_block_super+0x70/0xdc fs/super.c:1414
deactivate_locked_super+0xb8/0x13c fs/super.c:335
deactivate_super+0x108/0x128 fs/super.c:366
cleanup_mnt+0x3c0/0x474 fs/namespace.c:1143
__cleanup_mnt+0x20/0x30 fs/namespace.c:1150
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
irq event stamp: 6397580
hardirqs last enabled at (6397579): [<ffff8000088cc9e0>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:231
hardirqs last disabled at (6397580): [<ffff80001197e8c8>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (6397050): [<ffff8000080300b4>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (6397048): [<ffff800008030080>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace d360b60ff329656e ]---
XFS (loop4): Unmounting Filesystem
---
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 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