WARNING in check_for_bios_corruption

4 views
Skip to first unread message

syzbot

unread,
Oct 14, 2019, 4:13:07 AM10/14/19
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: dafd6344 Linux 4.19.79
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=108a5653600000
kernel config: https://syzkaller.appspot.com/x/.config?x=f825f73d8fea6b52
dashboard link: https://syzkaller.appspot.com/bug?extid=d6725605e81212aa5b13
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14d5c008e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=148ba87f600000

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

Corrupted low memory at 00000000b113e72f (2900 phys) = 000000e8
------------[ cut here ]------------
Memory corruption detected in low memory
WARNING: CPU: 1 PID: 24 at arch/x86/kernel/check.c:157
check_for_bios_corruption arch/x86/kernel/check.c:157 [inline]
WARNING: CPU: 1 PID: 24 at arch/x86/kernel/check.c:157
check_for_bios_corruption+0x10c/0x1a0 arch/x86/kernel/check.c:135
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 24 Comm: kworker/1:1 Not tainted 4.19.79 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: events check_corruption
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x172/0x1f0 lib/dump_stack.c:113
panic+0x263/0x507 kernel/panic.c:185
__warn.cold+0x20/0x4a kernel/panic.c:540
report_bug+0x263/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x204/0x360 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1037
RIP: 0010:check_for_bios_corruption arch/x86/kernel/check.c:157 [inline]
RIP: 0010:check_for_bios_corruption+0x10c/0x1a0 arch/x86/kernel/check.c:135
Code: c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d c3 c3 80 3d 9e 49 09 08 00 75 e7
48 c7 c7 e0 e0 47 87 c6 05 8e 49 09 08 01 e8 82 40 10 00 <0f> 0b eb d0 48
89 df 89 55 d0 e8 55 5d 73 00 8b 55 d0 eb 9a 48 89
RSP: 0018:ffff8880aa3afce0 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff888000010000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8155f4a6 RDI: ffffed1015475f8e
RBP: ffff8880aa3afd18 R08: ffff8880aa3a0640 R09: ffffed1015d23ee3
R10: ffffed1015d23ee2 R11: ffff8880ae91f717 R12: ffff888000010000
R13: dffffc0000000000 R14: 0000000000000001 R15: ffff888000000000
check_corruption+0xd/0x67 arch/x86/kernel/check.c:165
process_one_work+0x989/0x1750 kernel/workqueue.c:2153
worker_thread+0x98/0xe40 kernel/workqueue.c:2296
kthread+0x354/0x420 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages