Hello,
syzbot found the following issue on:
HEAD commit: d9b4a0c83a2d Linux 5.15.98
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=11a32114c80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=b57cfa804330c3b7
dashboard link:
https://syzkaller.appspot.com/bug?extid=325e6b0a1e7cf9035cc0
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/8088989394e3/disk-d9b4a0c8.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/2651d6753959/vmlinux-d9b4a0c8.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/f3fa3f994f9a/Image-d9b4a0c8.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+325e6b...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 17270 at fs/nilfs2/dat.c:158 nilfs_dat_prepare_end+0x2ac/0x2f4 fs/nilfs2/dat.c:158
Modules linked in:
CPU: 0 PID: 17270 Comm: syz-executor.4 Not tainted 5.15.98-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : nilfs_dat_prepare_end+0x2ac/0x2f4 fs/nilfs2/dat.c:158
lr : nilfs_dat_prepare_end+0x2ac/0x2f4 fs/nilfs2/dat.c:158
sp : ffff80001da36fd0
x29: ffff80001da36fe0 x28: 1fffe00022122689 x27: 1fffe0002212266c
x26: dfff800000000000 x25: dfff800000000000 x24: 0000000001000008
x23: 1ffff00003b46e0c x22: 00000000fffffffe x21: ffff000110910158
x20: ffff80001da37060 x19: ffff80001da37078 x18: 0000000000000000
x17: ff80800009cb8c5c x16: 0000000000000002 x15: ffff800009cb8c5c
x14: 00000000ffffffef x13: ffffffffffffffff x12: 0000000000040000
x11: 000000000003461b x10: ffff800020609000 x9 : ffff800009cd2da0
x8 : 000000000003461c x7 : 0000000000000000 x6 : ffff80000805dafc
x5 : ffff00010f58b938 x4 : 0000000000000000 x3 : ffff800008a6a8e4
x2 : 0000000000000001 x1 : 00000000fffffffe x0 : 00000000fffffffe
Call trace:
nilfs_dat_prepare_end+0x2ac/0x2f4 fs/nilfs2/dat.c:158
nilfs_bmap_prepare_end_ptr fs/nilfs2/bmap.h:211 [inline]
nilfs_direct_delete+0x154/0x2c0 fs/nilfs2/direct.c:155
nilfs_bmap_do_delete fs/nilfs2/bmap.c:176 [inline]
nilfs_bmap_do_truncate fs/nilfs2/bmap.c:264 [inline]
nilfs_bmap_truncate+0x2a0/0x4c0 fs/nilfs2/bmap.c:297
nilfs_truncate_bmap+0x198/0x314 fs/nilfs2/inode.c:850
nilfs_truncate+0x1f8/0x404 fs/nilfs2/inode.c:880
nilfs_setattr+0x1d4/0x278 fs/nilfs2/inode.c:976
notify_change+0xae4/0xd80 fs/attr.c:426
do_truncate+0x1bc/0x288 fs/open.c:65
handle_truncate fs/namei.c:3136 [inline]
do_open fs/namei.c:3484 [inline]
path_openat+0x20c0/0x26c4 fs/namei.c:3615
do_filp_open+0x1a8/0x3b4 fs/namei.c:3642
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 <unknown>:584
irq event stamp: 8828
hardirqs last enabled at (8827): [<ffff8000088c98f4>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:231
hardirqs last disabled at (8828): [<ffff800011976650>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (8518): [<ffff800008030c58>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (8516): [<ffff800008030c24>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace 294247d8aebe429e ]---
NILFS (loop4): error -2 truncating bmap (ino=16)
---
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.