[syzbot] upstream boot error: general protection fault in mm_alloc

4 views
Skip to first unread message

syzbot

unread,
Aug 15, 2022, 1:59:25 PM8/15/22
to ak...@linux-foundation.org, big...@linutronix.de, b...@vger.kernel.org, bra...@kernel.org, da...@redhat.com, ebie...@xmission.com, linux-...@vger.kernel.org, lu...@kernel.org, syzkall...@googlegroups.com, tg...@linutronix.de
Hello,

syzbot found the following issue on:

HEAD commit: 5d6a0f4da927 Merge tag 'for-linus-6.0-rc1b-tag' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1668343d080000
kernel config: https://syzkaller.appspot.com/x/.config?x=f83c035536d7b2e3
dashboard link: https://syzkaller.appspot.com/bug?extid=97f830ad641de86d08c0
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2

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

general protection fault, probably for non-canonical address 0xffff00d300000338: 0000 [#1] PREEMPT SMP KASAN
KASAN: maybe wild-memory-access in range [0xfff82698000019c0-0xfff82698000019c7]
CPU: 1 PID: 1155 Comm: kworker/u4:4 Not tainted 5.19.0-syzkaller-14374-g5d6a0f4da927 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:slab_alloc mm/slub.c:3251 [inline]
RIP: 0010:__kmem_cache_alloc_lru mm/slub.c:3258 [inline]
RIP: 0010:kmem_cache_alloc+0x12d/0x310 mm/slub.c:3268
Code: 84 1c 01 00 00 48 83 78 10 00 0f 84 11 01 00 00 49 8b 3f 40 f6 c7 0f 0f 85 e3 01 00 00 45 84 c0 0f 84 dc 01 00 00 41 8b 47 28 <49> 8b 5c 05 00 48 8d 4a 08 4c 89 e8 65 48 0f c7 0f 0f 94 c0 a8 01
RSP: 0000:ffffc90004bcfda8 EFLAGS: 00010202
RAX: 0000000000000338 RBX: 0000000000000cc0 RCX: 0000000000000000
RDX: 0000000000000b89 RSI: 0000000000000cc0 RDI: 0000000000040aa0
RBP: ffffffff8150835f R08: dffffc0000000001 R09: fffffbfff1c4ade6
R10: fffffbfff1c4ade6 R11: 1ffffffff1c4ade5 R12: ffffffff8d38ce40
R13: ffff00d300000000 R14: ffffffff8150835f R15: ffff8881400068c0
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000000ca8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
mm_alloc+0x1f/0xb0 kernel/fork.c:1171
bprm_mm_init fs/exec.c:369 [inline]
alloc_bprm+0x1ef/0x3b0 fs/exec.c:1534
kernel_execve+0x97/0xa00 fs/exec.c:1974
call_usermodehelper_exec_async+0x262/0x3b0 kernel/umh.c:112
ret_from_fork+0x1f/0x30
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:slab_alloc mm/slub.c:3251 [inline]
RIP: 0010:__kmem_cache_alloc_lru mm/slub.c:3258 [inline]
RIP: 0010:kmem_cache_alloc+0x12d/0x310 mm/slub.c:3268
Code: 84 1c 01 00 00 48 83 78 10 00 0f 84 11 01 00 00 49 8b 3f 40 f6 c7 0f 0f 85 e3 01 00 00 45 84 c0 0f 84 dc 01 00 00 41 8b 47 28 <49> 8b 5c 05 00 48 8d 4a 08 4c 89 e8 65 48 0f c7 0f 0f 94 c0 a8 01
RSP: 0000:ffffc90004bcfda8 EFLAGS: 00010202
RAX: 0000000000000338 RBX: 0000000000000cc0 RCX: 0000000000000000
RDX: 0000000000000b89 RSI: 0000000000000cc0 RDI: 0000000000040aa0
RBP: ffffffff8150835f R08: dffffc0000000001 R09: fffffbfff1c4ade6
R10: fffffbfff1c4ade6 R11: 1ffffffff1c4ade5 R12: ffffffff8d38ce40
R13: ffff00d300000000 R14: ffffffff8150835f R15: ffff8881400068c0
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000000ca8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 84 1c 01 test %bl,(%rcx,%rax,1)
3: 00 00 add %al,(%rax)
5: 48 83 78 10 00 cmpq $0x0,0x10(%rax)
a: 0f 84 11 01 00 00 je 0x121
10: 49 8b 3f mov (%r15),%rdi
13: 40 f6 c7 0f test $0xf,%dil
17: 0f 85 e3 01 00 00 jne 0x200
1d: 45 84 c0 test %r8b,%r8b
20: 0f 84 dc 01 00 00 je 0x202
26: 41 8b 47 28 mov 0x28(%r15),%eax
* 2a: 49 8b 5c 05 00 mov 0x0(%r13,%rax,1),%rbx <-- trapping instruction
2f: 48 8d 4a 08 lea 0x8(%rdx),%rcx
33: 4c 89 e8 mov %r13,%rax
36: 65 48 0f c7 0f cmpxchg16b %gs:(%rdi)
3b: 0f 94 c0 sete %al
3e: a8 01 test $0x1,%al


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

Guenter Roeck

unread,
Aug 15, 2022, 2:01:37 PM8/15/22
to syzkaller-bugs
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git  fc4d146e8d7d25ef88d409bea1f2e9aff7f30635

syzbot

unread,
Aug 15, 2022, 2:01:40 PM8/15/22
to 'Guenter Roeck' via syzkaller-bugs, syzkall...@googlegroups.com
> #syz test https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git

I see the command but can't find the corresponding bug.
Please resend the email to syzbo...@syzkaller.appspotmail.com address
that is the sender of the bug report (also present in the Reported-by tag).
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/68cf3e5d-46a2-40d7-95da-f8d1976a5715n%40googlegroups.com.

syzbot

unread,
Aug 15, 2022, 3:14:12 PM8/15/22
to li...@roeck-us.net, syzkall...@googlegroups.com
Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+97f830...@syzkaller.appspotmail.com

Tested on:

commit: fc4d146e virtio_net: Revert "virtio_net: set the defau..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git
kernel config: https://syzkaller.appspot.com/x/.config?x=f267ed4fb258122a
dashboard link: https://syzkaller.appspot.com/bug?extid=97f830ad641de86d08c0
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

syzbot

unread,
Aug 15, 2022, 4:16:12 PM8/15/22
to li...@roeck-us.net, syzkall...@googlegroups.com
Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+97f830...@syzkaller.appspotmail.com

Tested on:

commit: 568035b0 Linux 6.0-rc1
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git v6.0-rc1
kernel config: https://syzkaller.appspot.com/x/.config?x=f267ed4fb258122a
dashboard link: https://syzkaller.appspot.com/bug?extid=97f830ad641de86d08c0
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=146c8e5b080000

syzbot

unread,
Dec 14, 2022, 1:44:28 AM12/14/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