new mount options do not match the existing superblock, will be ignored
==================================================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer syzkaller/managers/linux-4-19/kernel/./include/linux/fb.h:674 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned syzkaller/managers/linux-4-19/kernel/drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xbaf/0xd10 syzkaller/managers/linux-4-19/kernel/drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff88b65870 by task syz-executor.1/10748

CPU: 0 PID: 10748 Comm: syz-executor.1 Not tainted 4.19.172-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack syzkaller/managers/linux-4-19/kernel/lib/dump_stack.c:77 [inline]
 dump_stack+0x1fc/0x2ef syzkaller/managers/linux-4-19/kernel/lib/dump_stack.c:118
 print_address_description.cold+0x5/0x219 syzkaller/managers/linux-4-19/kernel/mm/kasan/report.c:256
 kasan_report_error.cold+0x8a/0x1b9 syzkaller/managers/linux-4-19/kernel/mm/kasan/report.c:354
 kasan_report syzkaller/managers/linux-4-19/kernel/mm/kasan/report.c:412 [inline]
 __asan_report_load1_noabort+0x88/0x90 syzkaller/managers/linux-4-19/kernel/mm/kasan/report.c:430
 __fb_pad_aligned_buffer syzkaller/managers/linux-4-19/kernel/./include/linux/fb.h:674 [inline]
 bit_putcs_aligned syzkaller/managers/linux-4-19/kernel/drivers/video/fbdev/core/bitblit.c:96 [inline]
 bit_putcs+0xbaf/0xd10 syzkaller/managers/linux-4-19/kernel/drivers/video/fbdev/core/bitblit.c:185
 fbcon_putcs+0x336/0x4f0 syzkaller/managers/linux-4-19/kernel/drivers/video/fbdev/core/fbcon.c:1269
 do_update_region+0x399/0x630 syzkaller/managers/linux-4-19/kernel/drivers/tty/vt/vt.c:683
 update_region+0x144/0x190 syzkaller/managers/linux-4-19/kernel/drivers/tty/vt/vt.c:701
 vcs_write+0x403/0xc30 syzkaller/managers/linux-4-19/kernel/drivers/tty/vt/vc_screen.c:604
 __vfs_write+0xf7/0x770 syzkaller/managers/linux-4-19/kernel/fs/read_write.c:485
 vfs_write+0x1f3/0x540 syzkaller/managers/linux-4-19/kernel/fs/read_write.c:549
 ksys_write+0x12b/0x2a0 syzkaller/managers/linux-4-19/kernel/fs/read_write.c:599
 do_syscall_64+0xf9/0x620 syzkaller/managers/linux-4-19/kernel/arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x465b09
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc34e77c188 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465b09
RDX: 0000000000000051 RSI: 0000000020000100 RDI: 0000000000000003
RBP: 00000000004b069f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf60
R13: 00007fffb32ac01f R14: 00007fc34e77c300 R15: 0000000000022000

The buggy address belongs to the variable:
 oid_index+0x1b0/0xa60

Memory state around the buggy address:
 ffffffff88b65700: 00 00 00 00 00 00 06 fa fa fa fa fa 00 02 fa fa
 ffffffff88b65780: fa fa fa fa 00 01 fa fa fa fa fa fa 00 00 02 fa
>ffffffff88b65800: fa fa fa fa 00 03 fa fa fa fa fa fa 06 fa fa fa
                                                             ^
 ffffffff88b65880: fa fa fa fa 05 fa fa fa fa fa fa fa 00 06 fa fa
 ffffffff88b65900: fa fa fa fa 07 fa fa fa fa fa fa fa 00 01 fa fa
==================================================================