Hello,
syzbot found the following issue on:
HEAD commit: cbfa1702 Linux 4.14.198
git tree: linux-4.14.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=171b3cc3900000
kernel config:
https://syzkaller.appspot.com/x/.config?x=3990958d85b55e59
dashboard link:
https://syzkaller.appspot.com/bug?extid=f9c5c220be1661763989
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+f9c5c2...@syzkaller.appspotmail.com
BFS-fs: bfs_fill_super(): loop1 is unclean, continuing
==================================================================
BUG: KASAN: slab-out-of-bounds in find_first_zero_bit+0x84/0x90 lib/find_bit.c:105
Read of size 8 at addr ffff88809fca3c80 by task syz-executor.1/23433
CPU: 1 PID: 23433 Comm: syz-executor.1 Not tainted 4.14.198-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
UDF-fs: bad mount option "uid=forget8" or missing value
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
print_address_description.cold+0x54/0x1d3 mm/kasan/report.c:252
kasan_report_error.cold+0x8a/0x194 mm/kasan/report.c:351
kasan_report mm/kasan/report.c:409 [inline]
__asan_report_load8_noabort+0x68/0x70 mm/kasan/report.c:430
find_first_zero_bit+0x84/0x90 lib/find_bit.c:105
bfs_create+0xfb/0x620 fs/bfs/dir.c:92
lookup_open+0x77a/0x1750 fs/namei.c:3241
do_last fs/namei.c:3334 [inline]
path_openat+0xe08/0x2970 fs/namei.c:3569
do_filp_open+0x179/0x3c0 fs/namei.c:3603
do_sys_open+0x296/0x410 fs/open.c:1081
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45d5f9
RSP: 002b:00007fa8be40ac78 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00000000000225c0 RCX: 000000000045d5f9
RDX: 00000000001015c2 RSI: 0000000020000440 RDI: ffffffffffffff9c
RBP: 000000000118cf88 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
R13: 00007ffce945493f R14: 00007fa8be40b9c0 R15: 000000000118cf4c
Allocated by task 23433:
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc+0xeb/0x160 mm/kasan/kasan.c:551
__do_kmalloc mm/slab.c:3720 [inline]
__kmalloc+0x15a/0x400 mm/slab.c:3729
kmalloc include/linux/slab.h:493 [inline]
kzalloc include/linux/slab.h:661 [inline]
bfs_fill_super+0x3d5/0xd80 fs/bfs/inode.c:363
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
Freed by task 3654:
save_stack mm/kasan/kasan.c:447 [inline]
set_track mm/kasan/kasan.c:459 [inline]
kasan_slab_free+0xc3/0x1a0 mm/kasan/kasan.c:524
__cache_free mm/slab.c:3496 [inline]
kfree+0xc9/0x250 mm/slab.c:3815
security_context_to_sid_core+0x28a/0x3d0 security/selinux/ss/services.c:1460
selinux_inode_setsecurity+0x155/0x350 security/selinux/hooks.c:3377
selinux_inode_notifysecctx+0x2b/0x50 security/selinux/hooks.c:6152
security_inode_notifysecctx+0x76/0xb0 security/security.c:1314
kernfs_refresh_inode+0x328/0x4a0 fs/kernfs/inode.c:195
kernfs_iop_permission+0x59/0x90 fs/kernfs/inode.c:302
do_inode_permission fs/namei.c:384 [inline]
__inode_permission+0x1f1/0x2f0 fs/namei.c:426
inode_permission fs/namei.c:476 [inline]
may_lookup fs/namei.c:1717 [inline]
link_path_walk+0x86a/0x10a0 fs/namei.c:2097
path_lookupat+0xcb/0x780 fs/namei.c:2342
filename_lookup+0x18a/0x510 fs/namei.c:2377
user_path_at include/linux/namei.h:57 [inline]
vfs_statx+0xd1/0x180 fs/stat.c:185
vfs_lstat include/linux/fs.h:3070 [inline]
SYSC_newlstat fs/stat.c:350 [inline]
SyS_newlstat+0x83/0xe0 fs/stat.c:344
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
The buggy address belongs to the object at ffff88809fca3c80
which belongs to the cache kmalloc-32 of size 32
The buggy address is located 0 bytes inside of
32-byte region [ffff88809fca3c80, ffff88809fca3ca0)
The buggy address belongs to the page:
page:ffffea00027f28c0 count:1 mapcount:0 mapping:ffff88809fca3000 index:0xffff88809fca3fc1
flags: 0xfffe0000000100(slab)
raw: 00fffe0000000100 ffff88809fca3000 ffff88809fca3fc1 0000000100000035
raw: ffffea00027f9460 ffffea000283c520 ffff88812fe501c0 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff88809fca3b80: fb fb fb fb fc fc fc fc 05 fc fc fc fc fc fc fc
ffff88809fca3c00: 04 fc fc fc fc fc fc fc 05 fc fc fc fc fc fc fc
>ffff88809fca3c80: 07 fc fc fc fc fc fc fc fb fb fb fb fc fc fc fc
^
ffff88809fca3d00: fb fb fb fb fc fc fc fc fb fb fb fb fc fc fc fc
ffff88809fca3d80: fb fb fb fb fc fc fc fc fb fb fb fb fc fc fc fc
==================================================================
---
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.