BUG: unable to handle kernel paging request in bitfill_aligned

8 views
Skip to first unread message

syzbot

unread,
Dec 10, 2021, 5:17:21 AM12/10/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12a27fc5b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=bf64c3acbb5e0eff4bec
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=164305bdb00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=163849bdb00000

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

BUG: unable to handle kernel paging request at ffff888001000030
PGD de01067 P4D de01067 PUD de02067 PMD 80000000010001e1
Oops: 0003 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 8127 Comm: syz-executor115 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__writeq arch/x86/include/asm/io.h:100 [inline]
RIP: 0010:bitfill_aligned drivers/video/fbdev/core/cfbfillrect.c:75 [inline]
RIP: 0010:bitfill_aligned+0x17f/0x200 drivers/video/fbdev/core/cfbfillrect.c:35
Code: 49 01 c5 e8 23 c4 c7 fd 41 8d 6f ff 31 ff 44 89 fe e8 85 c5 c7 fd 45 85 ff 74 28 4d 89 ec e8 08 c4 c7 fd 4c 89 e0 49 83 c4 08 <48> 89 18 31 ff 89 ee 83 ed 01 e8 62 c5 c7 fd 83 fd ff 75 e0 4f 8d
RSP: 0018:ffff8880b140f2b0 EFLAGS: 00010282
RAX: ffff888001000030 RBX: 0000000000000000 RCX: ffffffff839ac15b
RDX: 0000000000000000 RSI: ffffffff839ac168 RDI: 0000000000000005
RBP: 0000000000000001 R08: 0000000000000080 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888001000038
R13: ffff888001000030 R14: 0000000000000000 R15: 0000000000000002
FS: 0000555556491300(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff888001000030 CR3: 000000009a26c000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
cfb_fillrect+0x40b/0x7b0 drivers/video/fbdev/core/cfbfillrect.c:327
vga16fb_fillrect+0x683/0x1940 drivers/video/fbdev/vga16fb.c:951
bit_clear_margins+0x3f6/0x4b0 drivers/video/fbdev/core/bitblit.c:224
fbcon_clear_margins+0x1e2/0x350 drivers/video/fbdev/core/fbcon.c:1288
fbcon_switch+0xf0d/0x1ba0 drivers/video/fbdev/core/fbcon.c:2155
redraw_screen+0x37d/0x870 drivers/tty/vt/vt.c:1015
vc_do_resize+0x1145/0x1440 drivers/tty/vt/vt.c:1341
fbcon_do_set_font+0x470/0x870 drivers/video/fbdev/core/fbcon.c:2420
fbcon_set_font+0x761/0x8a0 drivers/video/fbdev/core/fbcon.c:2515
con_font_set drivers/tty/vt/vt.c:4555 [inline]
con_font_op+0x94b/0xf20 drivers/tty/vt/vt.c:4599
vt_ioctl+0x1543/0x2380 drivers/tty/vt/vt_ioctl.c:993
tty_ioctl+0x5b0/0x1630 drivers/tty/tty_io.c:2669
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7ffb6d7004d9
Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd1145ab88 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ffb6d7004d9
RDX: 0000000020000400 RSI: 0000000000004b72 RDI: 0000000000000004
RBP: 00007ffb6d6c4360 R08: 000000000000000d R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffb6d6c43f0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
CR2: ffff888001000030
---[ end trace 1f6436287063ab0f ]---
RIP: 0010:__writeq arch/x86/include/asm/io.h:100 [inline]
RIP: 0010:bitfill_aligned drivers/video/fbdev/core/cfbfillrect.c:75 [inline]
RIP: 0010:bitfill_aligned+0x17f/0x200 drivers/video/fbdev/core/cfbfillrect.c:35
Code: 49 01 c5 e8 23 c4 c7 fd 41 8d 6f ff 31 ff 44 89 fe e8 85 c5 c7 fd 45 85 ff 74 28 4d 89 ec e8 08 c4 c7 fd 4c 89 e0 49 83 c4 08 <48> 89 18 31 ff 89 ee 83 ed 01 e8 62 c5 c7 fd 83 fd ff 75 e0 4f 8d
RSP: 0018:ffff8880b140f2b0 EFLAGS: 00010282
RAX: ffff888001000030 RBX: 0000000000000000 RCX: ffffffff839ac15b
RDX: 0000000000000000 RSI: ffffffff839ac168 RDI: 0000000000000005
RBP: 0000000000000001 R08: 0000000000000080 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888001000038
R13: ffff888001000030 R14: 0000000000000000 R15: 0000000000000002
FS: 0000555556491300(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff888001000030 CR3: 000000009a26c000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 49 01 c5 add %rax,%r13
3: e8 23 c4 c7 fd callq 0xfdc7c42b
8: 41 8d 6f ff lea -0x1(%r15),%ebp
c: 31 ff xor %edi,%edi
e: 44 89 fe mov %r15d,%esi
11: e8 85 c5 c7 fd callq 0xfdc7c59b
16: 45 85 ff test %r15d,%r15d
19: 74 28 je 0x43
1b: 4d 89 ec mov %r13,%r12
1e: e8 08 c4 c7 fd callq 0xfdc7c42b
23: 4c 89 e0 mov %r12,%rax
26: 49 83 c4 08 add $0x8,%r12
* 2a: 48 89 18 mov %rbx,(%rax) <-- trapping instruction
2d: 31 ff xor %edi,%edi
2f: 89 ee mov %ebp,%esi
31: 83 ed 01 sub $0x1,%ebp
34: e8 62 c5 c7 fd callq 0xfdc7c59b
39: 83 fd ff cmp $0xffffffff,%ebp
3c: 75 e0 jne 0x1e
3e: 4f rex.WRXB
3f: 8d .byte 0x8d


---
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
Reply all
Reply to author
Forward
0 new messages