BUG: unable to handle kernel paging request in dquot_add_inodes

8 views
Skip to first unread message

syzbot

unread,
Dec 2, 2020, 10:42:18 AM12/2/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c196b3a9 Linux 4.14.210
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=168126e9500000
kernel config: https://syzkaller.appspot.com/x/.config?x=5e5088ac39d46cc4
dashboard link: https://syzkaller.appspot.com/bug?extid=0cd189ef1a1d4a7d13da
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=149773fd500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12bf1a07500000

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

EXT4-fs (loop0): mounted filesystem without journal. Opts: ,errors=continue
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 kernel paging request at fffffbffff07e4ee
IP: __lock_acquire+0x1cc/0x3f20 kernel/locking/lockdep.c:3369
PGD 23fff0067 P4D 23fff0067 PUD 23ffef067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 7986 Comm: syz-executor347 Not tainted 4.14.210-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff888095848540 task.stack: ffff8880b3608000
RIP: 0010:__lock_acquire+0x1cc/0x3f20 kernel/locking/lockdep.c:3369
RSP: 0018:ffff8880b360f660 EFLAGS: 00010806
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 1fffffffff07e4ee RSI: 0000000000000000 RDI: fffffffff83f2773
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: ffff888095848540 R12: fffffffff83f2773
R13: 0000000000000000 R14: 0000000000000001 R15: ffffffff8beb4d40
FS: 0000000001b6d880(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffbffff07e4ee CR3: 000000009d069000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:152
spin_lock include/linux/spinlock.h:317 [inline]
dquot_add_inodes+0x34/0x870 fs/quota/dquot.c:1259
__dquot_transfer+0xdb2/0x16d0 fs/quota/dquot.c:1990
dquot_transfer+0x25a/0x3e6 fs/quota/dquot.c:2096
ext4_setattr+0x3ba/0x22f0 fs/ext4/inode.c:5455
notify_change+0x56b/0xd10 fs/attr.c:313
chown_common+0x40b/0x4b0 fs/open.c:631
SYSC_fchownat fs/open.c:661 [inline]
SyS_fchownat+0xf6/0x190 fs/open.c:641
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x4447b9
RSP: 002b:00007ffe1735b9e8 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
Code: 18 00 00 00 00 48 81 c4 80 01 00 00 44 89 e8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 b8 00 00 00 00 00 fc ff df 4c 89 e2 48 c1 ea 03 <80> 3c 02 00 0f 85 67 2a 00 00 49 81 3c 24 a0 07 2e 8b 0f 84 5f
RIP: __lock_acquire+0x1cc/0x3f20 kernel/locking/lockdep.c:3369 RSP: ffff8880b360f660
CR2: fffffbffff07e4ee
---[ end trace 54cd6823bc09ae31 ]---


---
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 23, 2021, 11:27:14 AM1/23/21
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:

commit a9c625fcddc078624e1e7a673443b29c71be3431
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=130e36b4d00000
start commit: 3f2ecb86 Linux 4.14.212
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=80549830ca6ffbb2
dashboard link: https://syzkaller.appspot.com/bug?extid=0cd189ef1a1d4a7d13da
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12caf250d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1014398f500000

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