[moderation] [xfs?] BUG: unable to handle kernel paging request in xfs_inode_mark_reclaimable
0 views
Skip to first unread message
syzbot
May 30, 2024, 9:56:27 PMMay 30
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 1613e604df0c Linux 6.10-rc1
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11740cb2980000
kernel config: https://syzkaller.appspot.com/x/.config?x=733cc7a95171d8e7
dashboard link: https://syzkaller.appspot.com/bug?extid=687e4f27156e74a3f0bd
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386
CC: [chanda...@oracle.com djw...@kernel.org linux-...@vger.kernel.org linu...@vger.kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-1613e604.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bdfe02141e4c/vmlinux-1613e604.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e655c2629f1/bzImage-1613e604.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+687e4f...@syzkaller.appspotmail.com
BUG: unable to handle page fault for address: fffffbfff300f7f4
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 7ffc3067 P4D 7ffc3067 PUD 7ffc2067 PMD 0
Oops: Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 PID: 11680 Comm: syz-executor.1 Not tainted 6.10.0-rc1-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:bytes_is_nonzero mm/kasan/generic.c:87 [inline]
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:104 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:129 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:161 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:180 [inline]
RIP: 0010:kasan_check_range+0x10e/0x1a0 mm/kasan/generic.c:189
Code: 00 7c 0b 44 89 c2 e8 e1 ea ff ff 83 f0 01 5b 5d 41 5c c3 cc cc cc cc 48 85 d2 74 4f 48 01 ea eb 09 48 83 c0 01 48 39 d0 74 41 <80> 38 00 74 f2 eb b2 41 bc 08 00 00 00 45 29 dc 49 8d 14 2c eb 0c
RSP: 0018:ffffc900277af908 EFLAGS: 00010086
RAX: fffffbfff300f7f4 RBX: fffffbfff300f7f5 RCX: ffffffff816c6aaa
RDX: fffffbfff300f7f5 RSI: 0000000000000008 RDI: ffffffff9807bfa0
RBP: fffffbfff300f7f4 R08: 0000000000000000 R09: fffffbfff300f7f4
R10: ffffffff9807bfa7 R11: 0000000000000001 R12: ffffed10025b45e3
R13: ffff888012da2f20 R14: ffff888012da2f70 R15: 0000000000000002
FS: 0000000000000000(0000) GS:ffff88802c000000(0063) knlGS:0000000057ddd400
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: fffffbfff300f7f4 CR3: 0000000053792000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
instrument_atomic_read include/linux/instrumented.h:68 [inline]
_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
__lock_acquire+0xeba/0x3b30 kernel/locking/lockdep.c:5107
lock_acquire kernel/locking/lockdep.c:5754 [inline]
lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5719
touch_work_lockdep_map kernel/workqueue.c:3894 [inline]
start_flush_work kernel/workqueue.c:4148 [inline]
__flush_work+0x477/0xc60 kernel/workqueue.c:4181
xfs_inodegc_queue fs/xfs/xfs_icache.c:2119 [inline]
xfs_inode_mark_reclaimable+0x6e8/0xf60 fs/xfs/xfs_icache.c:2149
destroy_inode+0xc4/0x1b0 fs/inode.c:311
iput_final fs/inode.c:1741 [inline]
iput.part.0+0x5a8/0x7f0 fs/inode.c:1767
iput+0x5c/0x80 fs/inode.c:1757
do_unlinkat+0x613/0x750 fs/namei.c:4414
__do_sys_unlink fs/namei.c:4455 [inline]
__se_sys_unlink fs/namei.c:4453 [inline]
__ia32_sys_unlink+0xc6/0x110 fs/namei.c:4453
do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline]
__do_fast_syscall_32+0x73/0x120 arch/x86/entry/common.c:386
do_fast_syscall_32+0x32/0x80 arch/x86/entry/common.c:411
entry_SYSENTER_compat_after_hwframe+0x84/0x8e
RIP: 0023:0xf72ed579
Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000ffde715c EFLAGS: 00000296 ORIG_RAX: 000000000000000a
RAX: ffffffffffffffda RBX: 00000000ffde7200 RCX: 0000000000008000
RDX: 00000000f7443ff4 RSI: 0000000000000000 RDI: 00000000ffde82a0
RBP: 00000000ffde7200 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:
CR2: fffffbfff300f7f4
---[ end trace 0000000000000000 ]---
RIP: 0010:bytes_is_nonzero mm/kasan/generic.c:87 [inline]
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:104 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:129 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:161 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:180 [inline]
RIP: 0010:kasan_check_range+0x10e/0x1a0 mm/kasan/generic.c:189
Code: 00 7c 0b 44 89 c2 e8 e1 ea ff ff 83 f0 01 5b 5d 41 5c c3 cc cc cc cc 48 85 d2 74 4f 48 01 ea eb 09 48 83 c0 01 48 39 d0 74 41 <80> 38 00 74 f2 eb b2 41 bc 08 00 00 00 45 29 dc 49 8d 14 2c eb 0c
RSP: 0018:ffffc900277af908 EFLAGS: 00010086
RAX: fffffbfff300f7f4 RBX: fffffbfff300f7f5 RCX: ffffffff816c6aaa
RDX: fffffbfff300f7f5 RSI: 0000000000000008 RDI: ffffffff9807bfa0
RBP: fffffbfff300f7f4 R08: 0000000000000000 R09: fffffbfff300f7f4
R10: ffffffff9807bfa7 R11: 0000000000000001 R12: ffffed10025b45e3
R13: ffff888012da2f20 R14: ffff888012da2f70 R15: 0000000000000002
FS: 0000000000000000(0000) GS:ffff88802c000000(0063) knlGS:0000000057ddd400
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: fffffbfff300f7f4 CR3: 0000000053792000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 00 7c 0b 44 add %bh,0x44(%rbx,%rcx,1)
4: 89 c2 mov %eax,%edx
6: e8 e1 ea ff ff call 0xffffeaec
b: 83 f0 01 xor $0x1,%eax
e: 5b pop %rbx
f: 5d pop %rbp
10: 41 5c pop %r12
12: c3 ret
13: cc int3
14: cc int3
15: cc int3
16: cc int3
17: 48 85 d2 test %rdx,%rdx
1a: 74 4f je 0x6b
1c: 48 01 ea add %rbp,%rdx
1f: eb 09 jmp 0x2a
21: 48 83 c0 01 add $0x1,%rax
25: 48 39 d0 cmp %rdx,%rax
28: 74 41 je 0x6b
* 2a: 80 38 00 cmpb $0x0,(%rax) <-- trapping instruction
2d: 74 f2 je 0x21
2f: eb b2 jmp 0xffffffe3
31: 41 bc 08 00 00 00 mov $0x8,%r12d
37: 45 29 dc sub %r11d,%r12d
3a: 49 8d 14 2c lea (%r12,%rbp,1),%rdx
3e: eb 0c jmp 0x4c
---
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
syzbot found the following issue on:
HEAD commit: 1613e604df0c Linux 6.10-rc1
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11740cb2980000
kernel config: https://syzkaller.appspot.com/x/.config?x=733cc7a95171d8e7
dashboard link: https://syzkaller.appspot.com/bug?extid=687e4f27156e74a3f0bd
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386
CC: [chanda...@oracle.com djw...@kernel.org linux-...@vger.kernel.org linu...@vger.kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-1613e604.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bdfe02141e4c/vmlinux-1613e604.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e655c2629f1/bzImage-1613e604.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+687e4f...@syzkaller.appspotmail.com
BUG: unable to handle page fault for address: fffffbfff300f7f4
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 7ffc3067 P4D 7ffc3067 PUD 7ffc2067 PMD 0
Oops: Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 PID: 11680 Comm: syz-executor.1 Not tainted 6.10.0-rc1-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:bytes_is_nonzero mm/kasan/generic.c:87 [inline]
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:104 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:129 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:161 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:180 [inline]
RIP: 0010:kasan_check_range+0x10e/0x1a0 mm/kasan/generic.c:189
Code: 00 7c 0b 44 89 c2 e8 e1 ea ff ff 83 f0 01 5b 5d 41 5c c3 cc cc cc cc 48 85 d2 74 4f 48 01 ea eb 09 48 83 c0 01 48 39 d0 74 41 <80> 38 00 74 f2 eb b2 41 bc 08 00 00 00 45 29 dc 49 8d 14 2c eb 0c
RSP: 0018:ffffc900277af908 EFLAGS: 00010086
RAX: fffffbfff300f7f4 RBX: fffffbfff300f7f5 RCX: ffffffff816c6aaa
RDX: fffffbfff300f7f5 RSI: 0000000000000008 RDI: ffffffff9807bfa0
RBP: fffffbfff300f7f4 R08: 0000000000000000 R09: fffffbfff300f7f4
R10: ffffffff9807bfa7 R11: 0000000000000001 R12: ffffed10025b45e3
R13: ffff888012da2f20 R14: ffff888012da2f70 R15: 0000000000000002
FS: 0000000000000000(0000) GS:ffff88802c000000(0063) knlGS:0000000057ddd400
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: fffffbfff300f7f4 CR3: 0000000053792000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
instrument_atomic_read include/linux/instrumented.h:68 [inline]
_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
__lock_acquire+0xeba/0x3b30 kernel/locking/lockdep.c:5107
lock_acquire kernel/locking/lockdep.c:5754 [inline]
lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5719
touch_work_lockdep_map kernel/workqueue.c:3894 [inline]
start_flush_work kernel/workqueue.c:4148 [inline]
__flush_work+0x477/0xc60 kernel/workqueue.c:4181
xfs_inodegc_queue fs/xfs/xfs_icache.c:2119 [inline]
xfs_inode_mark_reclaimable+0x6e8/0xf60 fs/xfs/xfs_icache.c:2149
destroy_inode+0xc4/0x1b0 fs/inode.c:311
iput_final fs/inode.c:1741 [inline]
iput.part.0+0x5a8/0x7f0 fs/inode.c:1767
iput+0x5c/0x80 fs/inode.c:1757
do_unlinkat+0x613/0x750 fs/namei.c:4414
__do_sys_unlink fs/namei.c:4455 [inline]
__se_sys_unlink fs/namei.c:4453 [inline]
__ia32_sys_unlink+0xc6/0x110 fs/namei.c:4453
do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline]
__do_fast_syscall_32+0x73/0x120 arch/x86/entry/common.c:386
do_fast_syscall_32+0x32/0x80 arch/x86/entry/common.c:411
entry_SYSENTER_compat_after_hwframe+0x84/0x8e
RIP: 0023:0xf72ed579
Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000ffde715c EFLAGS: 00000296 ORIG_RAX: 000000000000000a
RAX: ffffffffffffffda RBX: 00000000ffde7200 RCX: 0000000000008000
RDX: 00000000f7443ff4 RSI: 0000000000000000 RDI: 00000000ffde82a0
RBP: 00000000ffde7200 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:
CR2: fffffbfff300f7f4
---[ end trace 0000000000000000 ]---
RIP: 0010:bytes_is_nonzero mm/kasan/generic.c:87 [inline]
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:104 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:129 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:161 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:180 [inline]
RIP: 0010:kasan_check_range+0x10e/0x1a0 mm/kasan/generic.c:189
Code: 00 7c 0b 44 89 c2 e8 e1 ea ff ff 83 f0 01 5b 5d 41 5c c3 cc cc cc cc 48 85 d2 74 4f 48 01 ea eb 09 48 83 c0 01 48 39 d0 74 41 <80> 38 00 74 f2 eb b2 41 bc 08 00 00 00 45 29 dc 49 8d 14 2c eb 0c
RSP: 0018:ffffc900277af908 EFLAGS: 00010086
RAX: fffffbfff300f7f4 RBX: fffffbfff300f7f5 RCX: ffffffff816c6aaa
RDX: fffffbfff300f7f5 RSI: 0000000000000008 RDI: ffffffff9807bfa0
RBP: fffffbfff300f7f4 R08: 0000000000000000 R09: fffffbfff300f7f4
R10: ffffffff9807bfa7 R11: 0000000000000001 R12: ffffed10025b45e3
R13: ffff888012da2f20 R14: ffff888012da2f70 R15: 0000000000000002
FS: 0000000000000000(0000) GS:ffff88802c000000(0063) knlGS:0000000057ddd400
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: fffffbfff300f7f4 CR3: 0000000053792000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 00 7c 0b 44 add %bh,0x44(%rbx,%rcx,1)
4: 89 c2 mov %eax,%edx
6: e8 e1 ea ff ff call 0xffffeaec
b: 83 f0 01 xor $0x1,%eax
e: 5b pop %rbx
f: 5d pop %rbp
10: 41 5c pop %r12
12: c3 ret
13: cc int3
14: cc int3
15: cc int3
16: cc int3
17: 48 85 d2 test %rdx,%rdx
1a: 74 4f je 0x6b
1c: 48 01 ea add %rbp,%rdx
1f: eb 09 jmp 0x2a
21: 48 83 c0 01 add $0x1,%rax
25: 48 39 d0 cmp %rdx,%rax
28: 74 41 je 0x6b
* 2a: 80 38 00 cmpb $0x0,(%rax) <-- trapping instruction
2d: 74 f2 je 0x21
2f: eb b2 jmp 0xffffffe3
31: 41 bc 08 00 00 00 mov $0x8,%r12d
37: 45 29 dc sub %r11d,%r12d
3a: 49 8d 14 2c lea (%r12,%rbp,1),%rdx
3e: eb 0c jmp 0x4c
---
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
Reply all
Reply to author
Forward
0 new messages