[syzbot] WARNING in writeback_single_inode

12 views
Skip to first unread message

syzbot

unread,
Aug 30, 2022, 5:43:29 PM8/30/22
to linux-...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com, vi...@zeniv.linux.org.uk
Hello,

syzbot found the following issue on:

HEAD commit: a41a877bc12d Merge branch 'for-next/fixes' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=178fc957080000
kernel config: https://syzkaller.appspot.com/x/.config?x=5cea15779c42821c
dashboard link: https://syzkaller.appspot.com/bug?extid=fc721e2fe15a5aac41d1
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

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

ntfs3: loop4: RAW NTFS volume: Filesystem size 0.00 Gb > volume size 0.00 Gb. Mount in read-only
------------[ cut here ]------------
WARNING: CPU: 0 PID: 24385 at fs/fs-writeback.c:1678 writeback_single_inode+0x374/0x388 fs/fs-writeback.c:1678
Modules linked in:
CPU: 0 PID: 24385 Comm: syz-executor.4 Not tainted 6.0.0-rc2-syzkaller-16455-ga41a877bc12d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : writeback_single_inode+0x374/0x388 fs/fs-writeback.c:1678
lr : writeback_single_inode+0x374/0x388 fs/fs-writeback.c:1678
sp : ffff800020d4b9c0
x29: ffff800020d4ba10 x28: ffff0000e4bc8000 x27: fffffc0003f22700
x26: 0000000000000a00 x25: 0000000000000000 x24: 0000000000000001
x23: 0000000000001000 x22: ffff800020d4ba60 x21: 0000000000000000
x20: ffff0000fd87f7b7 x19: ffff0000fd87f840 x18: 0000000000000369
x17: 0000000000000000 x16: ffff80000dbb8658 x15: ffff0000e1cc0000
x14: 0000000000000130 x13: 00000000ffffffff x12: 0000000000040000
x11: 000000000003ffff x10: ffff80001d55c000 x9 : ffff80000861f6d4
x8 : 0000000000040000 x7 : ffff80000861f3a4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
writeback_single_inode+0x374/0x388 fs/fs-writeback.c:1678
write_inode_now+0xb0/0xdc fs/fs-writeback.c:2723
iput_final fs/inode.c:1735 [inline]
iput+0x1d4/0x314 fs/inode.c:1774
ntfs_fill_super+0xc30/0x14a4 fs/ntfs/super.c:2994
get_tree_bdev+0x1e8/0x2a0 fs/super.c:1323
ntfs_fs_get_tree+0x28/0x38 fs/ntfs3/super.c:1358
vfs_get_tree+0x40/0x140 fs/super.c:1530
do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040
path_mount+0x358/0x914 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x2f8/0x408 fs/namespace.c:3568
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x154 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:624
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:642
el0t_64_sync+0x18c/0x190
irq event stamp: 3030
hardirqs last enabled at (3029): [<ffff800008163d78>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1367 [inline]
hardirqs last enabled at (3029): [<ffff800008163d78>] finish_lock_switch+0x94/0xe8 kernel/sched/core.c:4942
hardirqs last disabled at (3030): [<ffff80000bffe9cc>] el1_dbg+0x24/0x5c arch/arm64/kernel/entry-common.c:395
softirqs last enabled at (2780): [<ffff8000080102e4>] _stext+0x2e4/0x37c
softirqs last disabled at (1405): [<ffff800008104658>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (1405): [<ffff800008104658>] invoke_softirq+0x70/0xbc kernel/softirq.c:452
---[ end trace 0000000000000000 ]---
Unable to handle kernel paging request at virtual address 000000fd87f9e147
Mem abort info:
ESR = 0x0000000096000004
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x04: level 0 translation fault
Data abort info:
ISV = 0, ISS = 0x00000004
CM = 0, WnR = 0
user pgtable: 4k pages, 48-bit VAs, pgdp=0000000128316000
[000000fd87f9e147] pgd=0000000000000000, p4d=0000000000000000
Internal error: Oops: 96000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 24385 Comm: syz-executor.4 Tainted: G W 6.0.0-rc2-syzkaller-16455-ga41a877bc12d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : xa_marked include/linux/xarray.h:420 [inline]
pc : mapping_tagged include/linux/fs.h:461 [inline]
pc : writeback_single_inode+0x228/0x388 fs/fs-writeback.c:1703
lr : writeback_single_inode+0x218/0x388 fs/fs-writeback.c:1702
sp : ffff800020d4b9c0
x29: ffff800020d4ba10 x28: ffff0000e4bc8000 x27: fffffc0003f22700
x26: 0000000000000a00 x25: 0000000000001000 x24: 0000000000000001
x23: 0000000000000001 x22: ffff800020d4ba60 x21: ffff0000fd87f88f
x20: ffff0000fd87f7b7 x19: ffff0000fd87f840 x18: 0000000000000369
x17: 0000000000000000 x16: ffff80000dbb8658 x15: ffff0000e1cc0000
x14: 0000000000000130 x13: 00000000ffffffff x12: 0000000000040000
x11: ff8080000861f578 x10: 0000000000000002 x9 : ffff0000e1cc0000
x8 : ff0000fd87f9e0ff x7 : ffff80000861f3a4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
xa_marked include/linux/xarray.h:420 [inline]
mapping_tagged include/linux/fs.h:461 [inline]
writeback_single_inode+0x228/0x388 fs/fs-writeback.c:1703
write_inode_now+0xb0/0xdc fs/fs-writeback.c:2723
iput_final fs/inode.c:1735 [inline]
iput+0x1d4/0x314 fs/inode.c:1774
ntfs_fill_super+0xc30/0x14a4 fs/ntfs/super.c:2994
get_tree_bdev+0x1e8/0x2a0 fs/super.c:1323
ntfs_fs_get_tree+0x28/0x38 fs/ntfs3/super.c:1358
vfs_get_tree+0x40/0x140 fs/super.c:1530
do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040
path_mount+0x358/0x914 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x2f8/0x408 fs/namespace.c:3568
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x154 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:624
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:642
el0t_64_sync+0x18c/0x190
Code: 710006ff 54000281 f9401a88 2a1f03e0 (b9404917)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 710006ff cmp w23, #0x1
4: 54000281 b.ne 0x54 // b.any
8: f9401a88 ldr x8, [x20, #48]
c: 2a1f03e0 mov w0, wzr
* 10: b9404917 ldr w23, [x8, #72] <-- trapping instruction


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

Matthew Wilcox

unread,
Aug 30, 2022, 11:26:26 PM8/30/22
to syzbot, linux-...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com, vi...@zeniv.linux.org.uk, nt...@lists.linux.dev, Konstantin Komarov
Looks like an ntfs3 problem. cc's added.

syzbot

unread,
Sep 19, 2022, 5:04:41 PM9/19/22
to almaz.ale...@paragon-software.com, linux-...@vger.kernel.org, linux-...@vger.kernel.org, nt...@lists.linux.dev, syzkall...@googlegroups.com, vi...@zeniv.linux.org.uk, wi...@infradead.org
syzbot has found a reproducer for the following issue on:

HEAD commit: a6b443748715 Merge branch 'for-next/core', remote-tracking..
console output: https://syzkaller.appspot.com/x/log.txt?x=144f0654880000
kernel config: https://syzkaller.appspot.com/x/.config?x=14bf9ec0df433b27
dashboard link: https://syzkaller.appspot.com/bug?extid=fc721e2fe15a5aac41d1
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17cb3628880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1778ecb0880000

Downloadable assets:
disk image: https://storage.googleapis.com/81b491dd5861/disk-a6b44374.raw.xz
vmlinux: https://storage.googleapis.com/69c979cdc99a/vmlinux-a6b44374.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 7715 at fs/fs-writeback.c:1678 writeback_single_inode+0x374/0x388 fs/fs-writeback.c:1678
Modules linked in:
CPU: 0 PID: 7715 Comm: syz-executor169 Not tainted 6.0.0-rc4-syzkaller-17255-ga6b443748715 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : writeback_single_inode+0x374/0x388 fs/fs-writeback.c:1678
lr : writeback_single_inode+0x374/0x388 fs/fs-writeback.c:1678
sp : ffff800015f0b9c0
x29: ffff800015f0ba10 x28: ffff0000cf476000 x27: fffffc0003488dc0
x26: 0000000000000a00 x25: 0000000000000000 x24: 0000000000000001
x23: 0000000000001000 x22: ffff800015f0ba60 x21: 0000000000000000
x20: ffff0000ce87824f x19: ffff0000ce8782d8 x18: 0000000000000379
x17: ffff80000c00d6bc x16: ffff80000db78658 x15: ffff0000cf4c8000
x14: 00000000000000f0 x13: 00000000ffffffff x12: ffff0000cf4c8000
x11: ff80800008619b78 x10: 0000000000000000 x9 : ffff800008619b78
x8 : ffff0000cf4c8000 x7 : ffff800008619848 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
writeback_single_inode+0x374/0x388 fs/fs-writeback.c:1678
write_inode_now+0xb0/0xdc fs/fs-writeback.c:2723
iput_final fs/inode.c:1735 [inline]
iput+0x1e4/0x324 fs/inode.c:1774
ntfs_fill_super+0xc30/0x14a4 fs/ntfs/super.c:2994
get_tree_bdev+0x1e8/0x2a0 fs/super.c:1323
ntfs_fs_get_tree+0x28/0x38 fs/ntfs3/super.c:1358
vfs_get_tree+0x40/0x140 fs/super.c:1530
do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040
path_mount+0x358/0x914 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x2f8/0x408 fs/namespace.c:3568
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:624
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:642
el0t_64_sync+0x18c/0x190
irq event stamp: 1754
hardirqs last enabled at (1753): [<ffff800008162eec>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1367 [inline]
hardirqs last enabled at (1753): [<ffff800008162eec>] finish_lock_switch+0x94/0xe8 kernel/sched/core.c:4942
hardirqs last disabled at (1754): [<ffff80000bfc5c8c>] el1_dbg+0x24/0x5c arch/arm64/kernel/entry-common.c:395
softirqs last enabled at (546): [<ffff8000080102e4>] _stext+0x2e4/0x37c
softirqs last disabled at (541): [<ffff800008017c48>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:79
---[ end trace 0000000000000000 ]---
Unable to handle kernel paging request at virtual address 000000ce87847947
Mem abort info:
ESR = 0x0000000096000004
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x04: level 0 translation fault
Data abort info:
ISV = 0, ISS = 0x00000004
CM = 0, WnR = 0
user pgtable: 4k pages, 48-bit VAs, pgdp=00000001135a3000
[000000ce87847947] pgd=0000000000000000, p4d=0000000000000000
Internal error: Oops: 96000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 7715 Comm: syz-executor169 Tainted: G W 6.0.0-rc4-syzkaller-17255-ga6b443748715 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : xa_marked include/linux/xarray.h:420 [inline]
pc : mapping_tagged include/linux/fs.h:461 [inline]
pc : writeback_single_inode+0x228/0x388 fs/fs-writeback.c:1703
lr : writeback_single_inode+0x218/0x388 fs/fs-writeback.c:1702
sp : ffff800015f0b9c0
x29: ffff800015f0ba10 x28: ffff0000cf476000 x27: fffffc0003488dc0
x26: 0000000000000a00 x25: 0000000000001000 x24: 0000000000000001
x23: 0000000000000001 x22: ffff800015f0ba60 x21: ffff0000ce878327
x20: ffff0000ce87824f x19: ffff0000ce8782d8 x18: 0000000000000379
x17: ffff80000c00d6bc x16: ffff80000db78658 x15: ffff0000cf4c8000
x14: 00000000000000f0 x13: 00000000ffffffff x12: ffff0000cf4c8000
x11: ff80800008619a1c x10: 0000000000000000 x9 : ffff0000cf4c8000
x8 : ff0000ce878478ff x7 : ffff800008619848 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
xa_marked include/linux/xarray.h:420 [inline]
mapping_tagged include/linux/fs.h:461 [inline]
writeback_single_inode+0x228/0x388 fs/fs-writeback.c:1703
write_inode_now+0xb0/0xdc fs/fs-writeback.c:2723
iput_final fs/inode.c:1735 [inline]
iput+0x1e4/0x324 fs/inode.c:1774
ntfs_fill_super+0xc30/0x14a4 fs/ntfs/super.c:2994
get_tree_bdev+0x1e8/0x2a0 fs/super.c:1323
ntfs_fs_get_tree+0x28/0x38 fs/ntfs3/super.c:1358
vfs_get_tree+0x40/0x140 fs/super.c:1530
do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040
path_mount+0x358/0x914 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x2f8/0x408 fs/namespace.c:3568
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206

syzbot

unread,
Feb 20, 2024, 11:45:12 AMFeb 20
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages