[v6.1] KASAN: use-after-free Read in hfsplus_btree_open (2)
0 views
Skip to first unread message
syzbot
Jan 23, 2024, 4:41:27 AMJan 23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 8fd7f4462453 Linux 6.1.74
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11e99e73e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=641b679746d8a982
dashboard link: https://syzkaller.appspot.com/bug?extid=f7a1dc366d96d138ba2c
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b6812fcc348f/disk-8fd7f446.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0cf26d0b8083/vmlinux-8fd7f446.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2d7f8217691a/bzImage-8fd7f446.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f7a1dc...@syzkaller.appspotmail.com
loop3: detected capacity change from 0 to 1024
==================================================================
BUG: KASAN: use-after-free in hfsplus_btree_open+0x927/0xd10 fs/hfsplus/btree.c:155
Read of size 4 at addr ffff88808212bc74 by task syz-executor.3/23063
CPU: 1 PID: 23063 Comm: syz-executor.3 Not tainted 6.1.74-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
print_address_description mm/kasan/report.c:284 [inline]
print_report+0x15f/0x4f0 mm/kasan/report.c:395
kasan_report+0x136/0x160 mm/kasan/report.c:495
hfsplus_btree_open+0x927/0xd10 fs/hfsplus/btree.c:155
hfsplus_fill_super+0xaba/0x1c90 fs/hfsplus/super.c:473
mount_bdev+0x2c9/0x3f0 fs/super.c:1432
legacy_get_tree+0xeb/0x180 fs/fs_context.c:632
vfs_get_tree+0x88/0x270 fs/super.c:1562
do_new_mount+0x28b/0xae0 fs/namespace.c:3040
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fbc8d67e4aa
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbc8c3fdef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fbc8c3fdf80 RCX: 00007fbc8d67e4aa
RDX: 0000000020000600 RSI: 0000000020000180 RDI: 00007fbc8c3fdf40
RBP: 0000000020000600 R08: 00007fbc8c3fdf80 R09: 0000000002010410
R10: 0000000002010410 R11: 0000000000000202 R12: 0000000020000180
R13: 00007fbc8c3fdf40 R14: 000000000000063a R15: 0000000020000440
</TASK>
Allocated by task 9826:
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:52
__kasan_slab_alloc+0x65/0x70 mm/kasan/common.c:328
kasan_slab_alloc include/linux/kasan.h:201 [inline]
slab_post_alloc_hook+0x52/0x3a0 mm/slab.h:737
slab_alloc_node mm/slub.c:3398 [inline]
slab_alloc mm/slub.c:3406 [inline]
__kmem_cache_alloc_lru mm/slub.c:3413 [inline]
kmem_cache_alloc_lru+0x10c/0x2d0 mm/slub.c:3429
alloc_inode_sb include/linux/fs.h:3177 [inline]
f2fs_alloc_inode+0x171/0x540 fs/f2fs/super.c:1400
alloc_inode fs/inode.c:261 [inline]
iget_locked+0x1c8/0x830 fs/inode.c:1330
f2fs_iget+0x52/0x4a30 fs/f2fs/inode.c:503
f2fs_fill_super+0x4a53/0x7c40 fs/f2fs/super.c:4265
mount_bdev+0x2c9/0x3f0 fs/super.c:1432
legacy_get_tree+0xeb/0x180 fs/fs_context.c:632
vfs_get_tree+0x88/0x270 fs/super.c:1562
do_new_mount+0x28b/0xae0 fs/namespace.c:3040
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Last potentially related work creation:
kasan_save_stack+0x3b/0x60 mm/kasan/common.c:45
__kasan_record_aux_stack+0xb0/0xc0 mm/kasan/generic.c:486
call_rcu+0x163/0xa10 kernel/rcu/tree.c:2812
f2fs_put_super+0x65d/0xc00 fs/f2fs/super.c:1631
generic_shutdown_super+0x130/0x340 fs/super.c:501
kill_block_super+0x7a/0xe0 fs/super.c:1459
kill_f2fs_super+0x2ff/0x3c0 fs/f2fs/super.c:4646
deactivate_locked_super+0xa0/0x110 fs/super.c:332
cleanup_mnt+0x490/0x520 fs/namespace.c:1186
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xde/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Second to last potentially related work creation:
kasan_save_stack+0x3b/0x60 mm/kasan/common.c:45
__kasan_record_aux_stack+0xb0/0xc0 mm/kasan/generic.c:486
call_rcu+0x163/0xa10 kernel/rcu/tree.c:2812
f2fs_put_super+0x65d/0xc00 fs/f2fs/super.c:1631
generic_shutdown_super+0x130/0x340 fs/super.c:501
kill_block_super+0x7a/0xe0 fs/super.c:1459
kill_f2fs_super+0x2ff/0x3c0 fs/f2fs/super.c:4646
deactivate_locked_super+0xa0/0x110 fs/super.c:332
cleanup_mnt+0x490/0x520 fs/namespace.c:1186
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xde/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
The buggy address belongs to the object at ffff88808212b540
which belongs to the cache f2fs_inode_cache of size 2144
The buggy address is located 1844 bytes inside of
2144-byte region [ffff88808212b540, ffff88808212bda0)
The buggy address belongs to the physical page:
page:ffffea0002084a00 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888082128000 pfn:0x82128
head:ffffea0002084a00 order:3 compound_mapcount:0 compound_pincount:0
memcg:ffff88807b0fab01
flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000010200 0000000000000000 dead000000000001 ffff88814232f280
raw: ffff888082128000 00000000800e0001 00000001ffffffff ffff88807b0fab01
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Reclaimable, gfp_mask 0x1d2050(__GFP_IO|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL|__GFP_RECLAIMABLE), pid 4880, tgid 4876 (syz-executor.3), ts 240344155227, free_ts 215149842325
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x18d/0x1b0 mm/page_alloc.c:2513
prep_new_page mm/page_alloc.c:2520 [inline]
get_page_from_freelist+0x31a1/0x3320 mm/page_alloc.c:4279
__alloc_pages+0x28d/0x770 mm/page_alloc.c:5545
alloc_slab_page+0x6a/0x150 mm/slub.c:1794
allocate_slab mm/slub.c:1939 [inline]
new_slab+0x84/0x2d0 mm/slub.c:1992
___slab_alloc+0xc20/0x1270 mm/slub.c:3180
__slab_alloc mm/slub.c:3279 [inline]
slab_alloc_node mm/slub.c:3364 [inline]
slab_alloc mm/slub.c:3406 [inline]
__kmem_cache_alloc_lru mm/slub.c:3413 [inline]
kmem_cache_alloc_lru+0x1a5/0x2d0 mm/slub.c:3429
alloc_inode_sb include/linux/fs.h:3177 [inline]
f2fs_alloc_inode+0x171/0x540 fs/f2fs/super.c:1400
alloc_inode fs/inode.c:261 [inline]
iget_locked+0x1c8/0x830 fs/inode.c:1330
f2fs_iget+0x52/0x4a30 fs/f2fs/inode.c:503
f2fs_fill_super+0x4a53/0x7c40 fs/f2fs/super.c:4265
mount_bdev+0x2c9/0x3f0 fs/super.c:1432
legacy_get_tree+0xeb/0x180 fs/fs_context.c:632
vfs_get_tree+0x88/0x270 fs/super.c:1562
do_new_mount+0x28b/0xae0 fs/namespace.c:3040
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3568
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1440 [inline]
free_pcp_prepare mm/page_alloc.c:1490 [inline]
free_unref_page_prepare+0xf63/0x1120 mm/page_alloc.c:3358
free_unref_page+0x33/0x3e0 mm/page_alloc.c:3453
qlink_free mm/kasan/quarantine.c:168 [inline]
qlist_free_all+0x76/0xe0 mm/kasan/quarantine.c:187
kasan_quarantine_reduce+0x156/0x170 mm/kasan/quarantine.c:294
__kasan_slab_alloc+0x1f/0x70 mm/kasan/common.c:305
kasan_slab_alloc include/linux/kasan.h:201 [inline]
slab_post_alloc_hook+0x52/0x3a0 mm/slab.h:737
slab_alloc_node mm/slub.c:3398 [inline]
__kmem_cache_alloc_node+0x137/0x260 mm/slub.c:3437
__do_kmalloc_node mm/slab_common.c:954 [inline]
__kmalloc+0xa1/0x230 mm/slab_common.c:968
kmalloc include/linux/slab.h:558 [inline]
inotify_handle_inode_event+0x1c4/0x530 fs/notify/inotify/inotify_fsnotify.c:96
inotify_ignored_and_remove_idr+0x25/0x70 fs/notify/inotify/inotify_user.c:527
__do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:817 [inline]
__se_sys_inotify_rm_watch+0x164/0x230 fs/notify/inotify/inotify_user.c:794
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Memory state around the buggy address:
ffff88808212bb00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff88808212bb80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88808212bc00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff88808212bc80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff88808212bd00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: 8fd7f4462453 Linux 6.1.74
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11e99e73e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=641b679746d8a982
dashboard link: https://syzkaller.appspot.com/bug?extid=f7a1dc366d96d138ba2c
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b6812fcc348f/disk-8fd7f446.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0cf26d0b8083/vmlinux-8fd7f446.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2d7f8217691a/bzImage-8fd7f446.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f7a1dc...@syzkaller.appspotmail.com
loop3: detected capacity change from 0 to 1024
==================================================================
BUG: KASAN: use-after-free in hfsplus_btree_open+0x927/0xd10 fs/hfsplus/btree.c:155
Read of size 4 at addr ffff88808212bc74 by task syz-executor.3/23063
CPU: 1 PID: 23063 Comm: syz-executor.3 Not tainted 6.1.74-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
print_address_description mm/kasan/report.c:284 [inline]
print_report+0x15f/0x4f0 mm/kasan/report.c:395
kasan_report+0x136/0x160 mm/kasan/report.c:495
hfsplus_btree_open+0x927/0xd10 fs/hfsplus/btree.c:155
hfsplus_fill_super+0xaba/0x1c90 fs/hfsplus/super.c:473
mount_bdev+0x2c9/0x3f0 fs/super.c:1432
legacy_get_tree+0xeb/0x180 fs/fs_context.c:632
vfs_get_tree+0x88/0x270 fs/super.c:1562
do_new_mount+0x28b/0xae0 fs/namespace.c:3040
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fbc8d67e4aa
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbc8c3fdef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fbc8c3fdf80 RCX: 00007fbc8d67e4aa
RDX: 0000000020000600 RSI: 0000000020000180 RDI: 00007fbc8c3fdf40
RBP: 0000000020000600 R08: 00007fbc8c3fdf80 R09: 0000000002010410
R10: 0000000002010410 R11: 0000000000000202 R12: 0000000020000180
R13: 00007fbc8c3fdf40 R14: 000000000000063a R15: 0000000020000440
</TASK>
Allocated by task 9826:
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:52
__kasan_slab_alloc+0x65/0x70 mm/kasan/common.c:328
kasan_slab_alloc include/linux/kasan.h:201 [inline]
slab_post_alloc_hook+0x52/0x3a0 mm/slab.h:737
slab_alloc_node mm/slub.c:3398 [inline]
slab_alloc mm/slub.c:3406 [inline]
__kmem_cache_alloc_lru mm/slub.c:3413 [inline]
kmem_cache_alloc_lru+0x10c/0x2d0 mm/slub.c:3429
alloc_inode_sb include/linux/fs.h:3177 [inline]
f2fs_alloc_inode+0x171/0x540 fs/f2fs/super.c:1400
alloc_inode fs/inode.c:261 [inline]
iget_locked+0x1c8/0x830 fs/inode.c:1330
f2fs_iget+0x52/0x4a30 fs/f2fs/inode.c:503
f2fs_fill_super+0x4a53/0x7c40 fs/f2fs/super.c:4265
mount_bdev+0x2c9/0x3f0 fs/super.c:1432
legacy_get_tree+0xeb/0x180 fs/fs_context.c:632
vfs_get_tree+0x88/0x270 fs/super.c:1562
do_new_mount+0x28b/0xae0 fs/namespace.c:3040
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Last potentially related work creation:
kasan_save_stack+0x3b/0x60 mm/kasan/common.c:45
__kasan_record_aux_stack+0xb0/0xc0 mm/kasan/generic.c:486
call_rcu+0x163/0xa10 kernel/rcu/tree.c:2812
f2fs_put_super+0x65d/0xc00 fs/f2fs/super.c:1631
generic_shutdown_super+0x130/0x340 fs/super.c:501
kill_block_super+0x7a/0xe0 fs/super.c:1459
kill_f2fs_super+0x2ff/0x3c0 fs/f2fs/super.c:4646
deactivate_locked_super+0xa0/0x110 fs/super.c:332
cleanup_mnt+0x490/0x520 fs/namespace.c:1186
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xde/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Second to last potentially related work creation:
kasan_save_stack+0x3b/0x60 mm/kasan/common.c:45
__kasan_record_aux_stack+0xb0/0xc0 mm/kasan/generic.c:486
call_rcu+0x163/0xa10 kernel/rcu/tree.c:2812
f2fs_put_super+0x65d/0xc00 fs/f2fs/super.c:1631
generic_shutdown_super+0x130/0x340 fs/super.c:501
kill_block_super+0x7a/0xe0 fs/super.c:1459
kill_f2fs_super+0x2ff/0x3c0 fs/f2fs/super.c:4646
deactivate_locked_super+0xa0/0x110 fs/super.c:332
cleanup_mnt+0x490/0x520 fs/namespace.c:1186
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xde/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
The buggy address belongs to the object at ffff88808212b540
which belongs to the cache f2fs_inode_cache of size 2144
The buggy address is located 1844 bytes inside of
2144-byte region [ffff88808212b540, ffff88808212bda0)
The buggy address belongs to the physical page:
page:ffffea0002084a00 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888082128000 pfn:0x82128
head:ffffea0002084a00 order:3 compound_mapcount:0 compound_pincount:0
memcg:ffff88807b0fab01
flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000010200 0000000000000000 dead000000000001 ffff88814232f280
raw: ffff888082128000 00000000800e0001 00000001ffffffff ffff88807b0fab01
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Reclaimable, gfp_mask 0x1d2050(__GFP_IO|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL|__GFP_RECLAIMABLE), pid 4880, tgid 4876 (syz-executor.3), ts 240344155227, free_ts 215149842325
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x18d/0x1b0 mm/page_alloc.c:2513
prep_new_page mm/page_alloc.c:2520 [inline]
get_page_from_freelist+0x31a1/0x3320 mm/page_alloc.c:4279
__alloc_pages+0x28d/0x770 mm/page_alloc.c:5545
alloc_slab_page+0x6a/0x150 mm/slub.c:1794
allocate_slab mm/slub.c:1939 [inline]
new_slab+0x84/0x2d0 mm/slub.c:1992
___slab_alloc+0xc20/0x1270 mm/slub.c:3180
__slab_alloc mm/slub.c:3279 [inline]
slab_alloc_node mm/slub.c:3364 [inline]
slab_alloc mm/slub.c:3406 [inline]
__kmem_cache_alloc_lru mm/slub.c:3413 [inline]
kmem_cache_alloc_lru+0x1a5/0x2d0 mm/slub.c:3429
alloc_inode_sb include/linux/fs.h:3177 [inline]
f2fs_alloc_inode+0x171/0x540 fs/f2fs/super.c:1400
alloc_inode fs/inode.c:261 [inline]
iget_locked+0x1c8/0x830 fs/inode.c:1330
f2fs_iget+0x52/0x4a30 fs/f2fs/inode.c:503
f2fs_fill_super+0x4a53/0x7c40 fs/f2fs/super.c:4265
mount_bdev+0x2c9/0x3f0 fs/super.c:1432
legacy_get_tree+0xeb/0x180 fs/fs_context.c:632
vfs_get_tree+0x88/0x270 fs/super.c:1562
do_new_mount+0x28b/0xae0 fs/namespace.c:3040
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3568
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1440 [inline]
free_pcp_prepare mm/page_alloc.c:1490 [inline]
free_unref_page_prepare+0xf63/0x1120 mm/page_alloc.c:3358
free_unref_page+0x33/0x3e0 mm/page_alloc.c:3453
qlink_free mm/kasan/quarantine.c:168 [inline]
qlist_free_all+0x76/0xe0 mm/kasan/quarantine.c:187
kasan_quarantine_reduce+0x156/0x170 mm/kasan/quarantine.c:294
__kasan_slab_alloc+0x1f/0x70 mm/kasan/common.c:305
kasan_slab_alloc include/linux/kasan.h:201 [inline]
slab_post_alloc_hook+0x52/0x3a0 mm/slab.h:737
slab_alloc_node mm/slub.c:3398 [inline]
__kmem_cache_alloc_node+0x137/0x260 mm/slub.c:3437
__do_kmalloc_node mm/slab_common.c:954 [inline]
__kmalloc+0xa1/0x230 mm/slab_common.c:968
kmalloc include/linux/slab.h:558 [inline]
inotify_handle_inode_event+0x1c4/0x530 fs/notify/inotify/inotify_fsnotify.c:96
inotify_ignored_and_remove_idr+0x25/0x70 fs/notify/inotify/inotify_user.c:527
__do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:817 [inline]
__se_sys_inotify_rm_watch+0x164/0x230 fs/notify/inotify/inotify_user.c:794
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Memory state around the buggy address:
ffff88808212bb00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff88808212bb80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88808212bc00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff88808212bc80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff88808212bd00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages