BUG: unable to handle kernel paging request in dquot_add_inodes

8 views
Skip to first unread message

syzbot

unread,
Dec 9, 2020, 8:44:13 PM12/9/20
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d7ec6808 Merge 5.4.82 into android12-5.4
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=13f4240f500000
kernel config: https://syzkaller.appspot.com/x/.config?x=57b7055521f684f8
dashboard link: https://syzkaller.appspot.com/bug?extid=126e960663d5d57b5972
compiler: Android (6032204 based on r370808) clang version 10.0.1 (https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=133a5f07500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1255080f500000

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

EXT4-fs (loop0): mounted filesystem without journal. Opts: ,errors=continue
ext4 filesystem being mounted at /root/file1 supports timestamps until 2038 (0x7fffffff)
Quota error (device loop0): qtree_write_dquot: Error -130079078 occurred while creating quota
Quota error (device loop0): qtree_write_dquot: Error -130079077 occurred while creating quota
BUG: unable to handle page fault for address: fffffbffff07e4df
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 23fff3067 P4D 23fff3067 PUD 23ffb6067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 350 Comm: syz-executor249 Not tainted 5.4.82-syzkaller-00042-gd7ec680881a1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:bytes_is_nonzero mm/kasan/generic.c:91 [inline]
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:108 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:134 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:165 [inline]
RIP: 0010:check_memory_region_inline mm/kasan/generic.c:181 [inline]
RIP: 0010:check_memory_region+0x70/0x2f0 mm/kasan/generic.c:191
Code: 49 bd 01 00 00 00 00 fc ff df 4d 01 ea 4d 89 d6 4d 29 ce 49 83 fe 10 7f 2b 4d 85 f6 0f 84 b9 01 00 00 4c 89 cb 4c 29 d3 66 90 <45> 0f b6 19 45 84 db 0f 85 03 02 00 00 49 ff c1 48 ff c3 75 eb e9
RSP: 0018:ffff8881e890f5d0 EFLAGS: 00010287
RAX: 0000000000000001 RBX: ffffffffffffffff RCX: ffffffff842c80b6
RDX: 0000000000000001 RSI: 0000000000000004 RDI: fffffffff83f26fb
RBP: ffff8881e890f6a0 R08: dffffc0000000000 R09: fffffbffff07e4df
R10: fffffbffff07e4e0 R11: 0000000000000004 R12: 1fffffffff07e4df
R13: dffffc0000000001 R14: 0000000000000001 R15: ffff8881e890f620
FS: 000000000161b880(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffbffff07e4df CR3: 00000001e88f7000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
atomic_try_cmpxchg include/asm-generic/atomic-instrumented.h:693 [inline]
queued_spin_lock include/asm-generic/qspinlock.h:78 [inline]
do_raw_spin_lock include/linux/spinlock.h:181 [inline]
__raw_spin_lock include/linux/spinlock_api_smp.h:143 [inline]
_raw_spin_lock+0x96/0x1b0 kernel/locking/spinlock.c:151
spin_lock include/linux/spinlock.h:338 [inline]
dquot_add_inodes+0x32/0xa90 fs/quota/dquot.c:1273
__dquot_transfer+0x65b/0x29c0 fs/quota/dquot.c:2002
dquot_transfer+0x347/0x4f0 fs/quota/dquot.c:2108
ext4_setattr+0x79f/0x1fb0 fs/ext4/inode.c:5654
notify_change+0xb13/0x1010 fs/attr.c:336
chown_common+0x3a1/0x660 fs/open.c:652
do_fchownat+0x165/0x240 fs/open.c:682
__do_sys_fchownat fs/open.c:697 [inline]
__se_sys_fchownat fs/open.c:694 [inline]
__x64_sys_fchownat+0xb1/0xc0 fs/open.c:694
do_syscall_64+0xcb/0x150 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x4447b9
Code: 8d d7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 5b d7 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fffeb68c4a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000104
RAX: ffffffffffffffda RBX: 00000000004002e0 RCX: 00000000004447b9
RDX: 000000000000ee00 RSI: 0000000020000040 RDI: 0000000000000005
RBP: 00000000006cf018 R08: 0000000000000000 R09: 00000000004002e0
R10: 000000000000ee00 R11: 0000000000000246 R12: 00000000004023a0
R13: 0000000000402430 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
CR2: fffffbffff07e4df
---[ end trace 6b24e6717dc27bf6 ]---
RIP: 0010:bytes_is_nonzero mm/kasan/generic.c:91 [inline]
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:108 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:134 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:165 [inline]
RIP: 0010:check_memory_region_inline mm/kasan/generic.c:181 [inline]
RIP: 0010:check_memory_region+0x70/0x2f0 mm/kasan/generic.c:191
Code: 49 bd 01 00 00 00 00 fc ff df 4d 01 ea 4d 89 d6 4d 29 ce 49 83 fe 10 7f 2b 4d 85 f6 0f 84 b9 01 00 00 4c 89 cb 4c 29 d3 66 90 <45> 0f b6 19 45 84 db 0f 85 03 02 00 00 49 ff c1 48 ff c3 75 eb e9
RSP: 0018:ffff8881e890f5d0 EFLAGS: 00010287
RAX: 0000000000000001 RBX: ffffffffffffffff RCX: ffffffff842c80b6
RDX: 0000000000000001 RSI: 0000000000000004 RDI: fffffffff83f26fb
RBP: ffff8881e890f6a0 R08: dffffc0000000000 R09: fffffbffff07e4df
R10: fffffbffff07e4e0 R11: 0000000000000004 R12: 1fffffffff07e4df
R13: dffffc0000000001 R14: 0000000000000001 R15: ffff8881e890f620
FS: 000000000161b880(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffbffff07e4df CR3: 00000001e88f7000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

syzbot

unread,
Apr 21, 2023, 10:16:35 PM4/21/23
to syzkaller-a...@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