BUG: unable to handle kernel paging request in dqput

10 views
Skip to first unread message

syzbot

unread,
Oct 5, 2020, 6:29:17 AM10/5/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: b09c3451 Linux 4.19.149
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=161720e7900000
kernel config: https://syzkaller.appspot.com/x/.config?x=d7c6dfb55644e8fd
dashboard link: https://syzkaller.appspot.com/bug?extid=ccb97de0f3007739c39c
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11cdd3c7900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13a7b78f900000

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

EXT4-fs (loop0): re-mounted. Opts:
Quota error (device loop0): qtree_write_dquot: Error -394896789 occurred while creating quota
EXT4-fs error (device loop0): ext4_mb_generate_buddy:744: group 0, block bitmap and bg descriptor inconsistent: 8192 vs 22 free clusters
Quota error (device loop0): write_blk: dquota write failed
Quota error (device loop0): qtree_write_dquot: Error -28 occurred while creating quota
BUG: unable to handle kernel paging request at fffffbfffd0ecb6c
PGD 21ffed067 P4D 21ffed067 PUD 21ffec067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 6485 Comm: syz-executor700 Not tainted 4.19.149-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:bytes_is_nonzero mm/kasan/kasan.c:167 [inline]
RIP: 0010:memory_is_nonzero mm/kasan/kasan.c:184 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/kasan.c:210 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/kasan.c:241 [inline]
RIP: 0010:check_memory_region_inline mm/kasan/kasan.c:257 [inline]
RIP: 0010:check_memory_region+0xc8/0x170 mm/kasan/kasan.c:267
Code: 39 d0 74 0e 80 38 00 74 f2 48 85 c0 0f 85 9c 00 00 00 5b 5d 41 5c c3 48 85 d2 74 f6 48 01 ea eb 09 48 83 c0 01 48 39 d0 74 e8 <80> 38 00 74 f2 eb d8 41 bc 08 00 00 00 48 89 ea 45 29 dc 4e 8d 5c
RSP: 0018:ffff8880897ff870 EFLAGS: 00010282
RAX: fffffbfffd0ecb6c RBX: fffffbfffd0ecb6d RCX: ffffffff81d2496e
RDX: fffffbfffd0ecb6d RSI: 0000000000000004 RDI: ffffffffe8765b63
RBP: fffffbfffd0ecb6c R08: 0000000000000000 R09: fffffbfffd0ecb6c
R10: ffffffffe8765b66 R11: 0000000000000001 R12: ffffffffe8765b63
R13: 0000000000000006 R14: fffffbfffd0ecb6c R15: ffff888080035598
FS: 0000000000cfb880(0000) GS:ffff8880ae300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffbfffd0ecb6c CR3: 000000000946d000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
atomic_read include/asm-generic/atomic-instrumented.h:21 [inline]
dqput.part.0+0xae/0x850 fs/quota/dquot.c:765
dqput fs/quota/dquot.c:752 [inline]
dqput_all fs/quota/dquot.c:391 [inline]
__dquot_drop+0x1c6/0x2a0 fs/quota/dquot.c:1568
dquot_drop+0x14b/0x1a0 fs/quota/dquot.c:1593
ext4_clear_inode+0x31/0x1d0 fs/ext4/super.c:1180
ext4_evict_inode+0x25b/0x1830 fs/ext4/inode.c:348
evict+0x2ed/0x780 fs/inode.c:559
dispose_list+0x124/0x1f0 fs/inode.c:594
evict_inodes+0x341/0x430 fs/inode.c:644
generic_shutdown_super+0xb3/0x370 fs/super.c:448
kill_block_super+0x97/0xf0 fs/super.c:1185
deactivate_locked_super+0x8c/0x100 fs/super.c:329
deactivate_super+0x174/0x1a0 fs/super.c:360
cleanup_mnt+0x1da/0x300 fs/namespace.c:1098
task_work_run+0x141/0x1c0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xc09/0x2d80 kernel/exit.c:887
do_group_exit+0x125/0x320 kernel/exit.c:990
__do_sys_exit_group kernel/exit.c:1001 [inline]
__se_sys_exit_group kernel/exit.c:999 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:999
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x443a18
Code: Bad RIP value.
RSP: 002b:00007ffdfe3bd128 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 0000000000443a18
RDX: 0000000000000001 RSI: 000000000000003c RDI: 0000000000000001
RBP: 00000000004c3eb0 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 00007ffdfe3bd010 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d6180 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
CR2: fffffbfffd0ecb6c
---[ end trace e68f272e61674ea6 ]---
RIP: 0010:bytes_is_nonzero mm/kasan/kasan.c:167 [inline]
RIP: 0010:memory_is_nonzero mm/kasan/kasan.c:184 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/kasan.c:210 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/kasan.c:241 [inline]
RIP: 0010:check_memory_region_inline mm/kasan/kasan.c:257 [inline]
RIP: 0010:check_memory_region+0xc8/0x170 mm/kasan/kasan.c:267
Code: 39 d0 74 0e 80 38 00 74 f2 48 85 c0 0f 85 9c 00 00 00 5b 5d 41 5c c3 48 85 d2 74 f6 48 01 ea eb 09 48 83 c0 01 48 39 d0 74 e8 <80> 38 00 74 f2 eb d8 41 bc 08 00 00 00 48 89 ea 45 29 dc 4e 8d 5c
RSP: 0018:ffff8880897ff870 EFLAGS: 00010282
RAX: fffffbfffd0ecb6c RBX: fffffbfffd0ecb6d RCX: ffffffff81d2496e
RDX: fffffbfffd0ecb6d RSI: 0000000000000004 RDI: ffffffffe8765b63
RBP: fffffbfffd0ecb6c R08: 0000000000000000 R09: fffffbfffd0ecb6c
R10: ffffffffe8765b66 R11: 0000000000000001 R12: ffffffffe8765b63
R13: 0000000000000006 R14: fffffbfffd0ecb6c R15: ffff888080035598
FS: 0000000000cfb880(0000) GS:ffff8880ae300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004439ee CR3: 000000000946d000 CR4: 00000000001406e0
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,
Jan 12, 2021, 12:45:07 PM1/12/21
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:

commit 7bae84821b47e2ffa87a7afcb6891dd7e61c65ef
Author: Jan Kara <ja...@suse.cz>
Date: Mon Nov 2 15:16:29 2020 +0000

quota: Sanity-check quota file headers on load

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1662bc00d00000
start commit: a1b977b4 Linux 4.19.150
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=c14008c8da1ca4d4
dashboard link: https://syzkaller.appspot.com/bug?extid=ccb97de0f3007739c39c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16b98a94500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=142c7207900000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: quota: Sanity-check quota file headers on load

For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages