[syzbot] BUG: unable to handle kernel paging request in inode_wait_for_writeback

9 views
Skip to first unread message

syzbot

unread,
May 7, 2022, 3:09:23 AM5/7/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: 4b97bac0756a Merge tag 'for-5.18-rc5-tag' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1265a2bcf00000
kernel config: https://syzkaller.appspot.com/x/.config?x=331feb185f8828e0
dashboard link: https://syzkaller.appspot.com/bug?extid=8fbf154f6ae28029c757
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

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+8fbf15...@syzkaller.appspotmail.com

BUG: unable to handle page fault for address: 0000000065d375c1
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 7cc07067 P4D 7cc07067 PUD 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 6611 Comm: syz-executor.5 Not tainted 5.18.0-rc5-syzkaller-00163-g4b97bac0756a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:lock_is_held include/linux/lockdep.h:283 [inline]
RIP: 0010:rcu_read_lock_sched_held+0x39/0x70 kernel/rcu/update.c:125
Code: 75 06 44 89 e0 41 5c c3 e8 24 8c 00 00 84 c0 74 41 e8 8b a8 00 00 84 c0 74 38 be ff ff ff ff 48 c7 c7 20 20 d8 8b e8 c6 a1 09 <08> 85 c0 75 d3 65 8b 05 cb c1 9e 7e a9 ff ff ff 7f 75 c5 9c 41 5c
RSP: 0018:ffffc9000545f9e0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 1ffff92000a8bf40 RCX: 0000000000000001
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffff8db92257
R10: fffffbfff1b7244a R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000000 R14: ffff88806a792f30 R15: 0000000000000000
FS: 00007f66a8337700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000065d375c1 CR3: 000000007d8c7000 CR4: 0000000000350ef0
Call Trace:
<TASK>
trace_lock_acquire include/trace/events/lock.h:13 [inline]
lock_acquire+0x442/0x510 kernel/locking/lockdep.c:5612
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:349 [inline]
inode_wait_for_writeback+0x1a/0x30 fs/fs-writeback.c:1466
evict+0x2b7/0x6b0 fs/inode.c:661
iput_final fs/inode.c:1744 [inline]
iput.part.0+0x562/0x820 fs/inode.c:1770
iput+0x58/0x70 fs/inode.c:1760
ntfs_fill_super+0x2e08/0x37b0 fs/ntfs3/super.c:1178
get_tree_bdev+0x440/0x760 fs/super.c:1292
vfs_get_tree+0x89/0x2f0 fs/super.c:1497
do_new_mount fs/namespace.c:3040 [inline]
path_mount+0x1320/0x1fa0 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]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f66a728a61a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f66a8336f88 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007f66a728a61a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f66a8336fe0
RBP: 00007f66a8337020 R08: 00007f66a8337020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000020000000
R13: 0000000020000100 R14: 00007f66a8336fe0 R15: 000000002007c6a0
</TASK>
Modules linked in:
CR2: 0000000065d375c1
---[ end trace 0000000000000000 ]---
RIP: 0010:lock_is_held include/linux/lockdep.h:283 [inline]
RIP: 0010:rcu_read_lock_sched_held+0x39/0x70 kernel/rcu/update.c:125
Code: 75 06 44 89 e0 41 5c c3 e8 24 8c 00 00 84 c0 74 41 e8 8b a8 00 00 84 c0 74 38 be ff ff ff ff 48 c7 c7 20 20 d8 8b e8 c6 a1 09 <08> 85 c0 75 d3 65 8b 05 cb c1 9e 7e a9 ff ff ff 7f 75 c5 9c 41 5c
RSP: 0018:ffffc9000545f9e0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 1ffff92000a8bf40 RCX: 0000000000000001
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffff8db92257
R10: fffffbfff1b7244a R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000000 R14: ffff88806a792f30 R15: 0000000000000000
FS: 00007f66a8337700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000065d375c1 CR3: 000000007d8c7000 CR4: 0000000000350ef0


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

syzbot

unread,
Sep 3, 2022, 8:33:21 PM9/3/22
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages