[ext4?] general protection fault in ext4_release_dquot

4 views
Skip to first unread message

syzbot

unread,
May 13, 2023, 3:57:40 AM5/13/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ba0ad6ed89fd media: nxp: imx8-isi: fix buiding on 32-bit
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10ac2646280000
kernel config: https://syzkaller.appspot.com/x/.config?x=38526bf24c8d961b
dashboard link: https://syzkaller.appspot.com/bug?extid=1536e19aa38aef752cec
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [adilger...@dilger.ca linux...@vger.kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org ll...@lists.linux.dev nat...@kernel.org ndesau...@google.com tr...@redhat.com ty...@mit.edu]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d90fd81625c3/disk-ba0ad6ed.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/40278f703ebe/vmlinux-ba0ad6ed.xz
kernel image: https://storage.googleapis.com/syzbot-assets/582ba2804f3e/bzImage-ba0ad6ed.xz

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

general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
CPU: 0 PID: 5034 Comm: syz-executor.3 Not tainted 6.4.0-rc1-syzkaller-00001-gba0ad6ed89fd #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:ext4_release_dquot+0x1f3/0x3a0 fs/ext4/super.c:6817
Code: 9c df 30 02 00 00 48 89 d8 48 c1 e8 03 42 80 3c 28 00 74 08 48 89 df e8 cb 33 96 ff 48 8b 1b 48 83 c3 28 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 74 08 48 89 df e8 ae 33 96 ff bd 78 06 00 00 48 03
RSP: 0018:ffffc90003e0f918 EFLAGS: 00010206
RAX: 0000000000000005 RBX: 0000000000000028 RCX: ffff88802c088000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 0000000000000100 R08: ffffffff824d0128 R09: fffffbfff1982901
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff11006b9fccc
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff8880693f0000
FS: 0000555556443400(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2dc21000 CR3: 000000004037d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
dqput+0x1da/0x860 fs/quota/dquot.c:812
dqput_all fs/quota/dquot.c:396 [inline]
__dquot_drop fs/quota/dquot.c:1590 [inline]
dquot_drop+0x222/0x2a0 fs/quota/dquot.c:1615
ext4_clear_inode+0x5a/0x1b0 fs/ext4/super.c:1492
ext4_evict_inode+0xaa9/0xf20 fs/ext4/inode.c:318
evict+0x2a4/0x620 fs/inode.c:665
dispose_list fs/inode.c:698 [inline]
evict_inodes+0x5f8/0x690 fs/inode.c:748
generic_shutdown_super+0x98/0x340 fs/super.c:479
kill_block_super+0x84/0xf0 fs/super.c:1407
deactivate_locked_super+0xa4/0x110 fs/super.c:331
cleanup_mnt+0x426/0x4c0 fs/namespace.c:1177
task_work_run+0x24a/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xd9/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x64/0x280 kernel/entry/common.c:297
do_syscall_64+0x4d/0xc0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fd0e108d5d7
Code: ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 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:00007ffdca96fd38 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fd0e108d5d7
RDX: 00007ffdca96fe0a RSI: 000000000000000a RDI: 00007ffdca96fe00
RBP: 00007ffdca96fe00 R08: 00000000ffffffff R09: 00007ffdca96fbd0
R10: 0000555556444893 R11: 0000000000000246 R12: 00007fd0e10e6cdc
R13: 00007ffdca970ec0 R14: 0000555556444810 R15: 00007ffdca970f00
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ext4_release_dquot+0x1f3/0x3a0 fs/ext4/super.c:6817
Code: 9c df 30 02 00 00 48 89 d8 48 c1 e8 03 42 80 3c 28 00 74 08 48 89 df e8 cb 33 96 ff 48 8b 1b 48 83 c3 28 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 74 08 48 89 df e8 ae 33 96 ff bd 78 06 00 00 48 03
RSP: 0018:ffffc90003e0f918 EFLAGS: 00010206
RAX: 0000000000000005 RBX: 0000000000000028 RCX: ffff88802c088000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 0000000000000100 R08: ffffffff824d0128 R09: fffffbfff1982901
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff11006b9fccc
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff8880693f0000
FS: 0000555556443400(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fac1edfa000 CR3: 000000004037d000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 9c pushfq
1: df 30 fbstp (%rax)
3: 02 00 add (%rax),%al
5: 00 48 89 add %cl,-0x77(%rax)
8: d8 48 c1 fmuls -0x3f(%rax)
b: e8 03 42 80 3c callq 0x3c804213
10: 28 00 sub %al,(%rax)
12: 74 08 je 0x1c
14: 48 89 df mov %rbx,%rdi
17: e8 cb 33 96 ff callq 0xff9633e7
1c: 48 8b 1b mov (%rbx),%rbx
1f: 48 83 c3 28 add $0x28,%rbx
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 48 89 df mov %rbx,%rdi
34: e8 ae 33 96 ff callq 0xff9633e7
39: bd 78 06 00 00 mov $0x678,%ebp
3e: 48 rex.W
3f: 03 .byte 0x3


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Aug 7, 2023, 3:51:41 AM8/7/23
to syzkaller-upst...@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