[ext4?] KASAN: use-after-free Read in get_max_inline_xattr_value_size
已查看 8 次
跳至第一个未读帖子
syzbot
2023年1月6日 02:27:432023/1/6
收件人 syzkaller-a...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 4a947285bcca UPSTREAM: dma-buf: system_heap: Avoid warning..
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=12f21c94480000
kernel config: https://syzkaller.appspot.com/x/.config?x=b4f7fdc1fca3154e
dashboard link: https://syzkaller.appspot.com/bug?extid=83f4272d07a60d313711
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b962c72968d3/disk-4a947285.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b2bc3b543b67/vmlinux-4a947285.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5630795b1da7/bzImage-4a947285.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+83f427...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in get_max_inline_xattr_value_size+0x373/0x510 fs/ext4/inline.c:61
Read of size 4 at addr ffff8881ed263010 by task syz-executor.5/31817
CPU: 1 PID: 31817 Comm: syz-executor.5 Not tainted 5.4.219-syzkaller-00013-g4a947285bcca #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1d8/0x241 lib/dump_stack.c:118
print_address_description+0x8c/0x630 mm/kasan/report.c:384
__kasan_report+0xf6/0x130 mm/kasan/report.c:516
kasan_report+0x30/0x60 mm/kasan/common.c:653
get_max_inline_xattr_value_size+0x373/0x510 fs/ext4/inline.c:61
ext4_get_max_inline_size+0x139/0x1f0 fs/ext4/inline.c:112
ext4_try_to_write_inline_data+0xd9/0x1750 fs/ext4/inline.c:673
ext4_write_begin+0x247/0x1d50 fs/ext4/inode.c:1312
ext4_da_write_begin+0x4a8/0xf80 fs/ext4/inode.c:3110
generic_perform_write+0x2f9/0x5a0 mm/filemap.c:3311
__generic_file_write_iter+0x239/0x490 mm/filemap.c:3440
ext4_file_write_iter+0x495/0x10e0 fs/ext4/file.c:270
call_write_iter include/linux/fs.h:1976 [inline]
new_sync_write fs/read_write.c:483 [inline]
__vfs_write+0x5e3/0x780 fs/read_write.c:496
vfs_write+0x210/0x4f0 fs/read_write.c:558
ksys_write+0x198/0x2c0 fs/read_write.c:611
do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Allocated by task 28620:
save_stack mm/kasan/common.c:70 [inline]
set_track mm/kasan/common.c:78 [inline]
__kasan_kmalloc+0x131/0x1e0 mm/kasan/common.c:529
slab_post_alloc_hook mm/slab.h:584 [inline]
slab_alloc_node mm/slub.c:2829 [inline]
slab_alloc mm/slub.c:2837 [inline]
kmem_cache_alloc+0xd0/0x210 mm/slub.c:2842
skb_clone+0x1b7/0x380 net/core/skbuff.c:1459
do_one_broadcast net/netlink/af_netlink.c:1445 [inline]
netlink_broadcast_filtered+0x65b/0x11d0 net/netlink/af_netlink.c:1520
netlink_broadcast net/netlink/af_netlink.c:1544 [inline]
netlink_sendmsg+0x9bb/0xcc0 net/netlink/af_netlink.c:1931
sock_sendmsg_nosec net/socket.c:638 [inline]
sock_sendmsg net/socket.c:658 [inline]
____sys_sendmsg+0x5a6/0x8f0 net/socket.c:2287
___sys_sendmsg net/socket.c:2341 [inline]
__sys_sendmsg+0x2b7/0x3a0 net/socket.c:2387
do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Freed by task 28620:
save_stack mm/kasan/common.c:70 [inline]
set_track mm/kasan/common.c:78 [inline]
kasan_set_free_info mm/kasan/common.c:345 [inline]
__kasan_slab_free+0x178/0x240 mm/kasan/common.c:487
slab_free_hook mm/slub.c:1455 [inline]
slab_free_freelist_hook+0x80/0x150 mm/slub.c:1494
slab_free mm/slub.c:3080 [inline]
kmem_cache_free+0xa9/0x1d0 mm/slub.c:3096
do_one_broadcast net/netlink/af_netlink.c:1469 [inline]
netlink_broadcast_filtered+0x6d7/0x11d0 net/netlink/af_netlink.c:1520
netlink_broadcast net/netlink/af_netlink.c:1544 [inline]
netlink_sendmsg+0x9bb/0xcc0 net/netlink/af_netlink.c:1931
sock_sendmsg_nosec net/socket.c:638 [inline]
sock_sendmsg net/socket.c:658 [inline]
____sys_sendmsg+0x5a6/0x8f0 net/socket.c:2287
___sys_sendmsg net/socket.c:2341 [inline]
__sys_sendmsg+0x2b7/0x3a0 net/socket.c:2387
do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
The buggy address belongs to the object at ffff8881ed263000
which belongs to the cache skbuff_head_cache of size 240
The buggy address is located 16 bytes inside of
240-byte region [ffff8881ed263000, ffff8881ed2630f0)
The buggy address belongs to the page:
page:ffffea0007b498c0 refcount:1 mapcount:0 mapping:ffff8881f1ddd400 index:0x0
flags: 0x8000000000000200(slab)
raw: 8000000000000200 ffffea0007ba1d80 0000000400000004 ffff8881f1ddd400
raw: 0000000000000000 00000000000c000c 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x12a20(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY)
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook mm/page_alloc.c:2165 [inline]
prep_new_page+0x194/0x380 mm/page_alloc.c:2171
get_page_from_freelist+0x524/0x560 mm/page_alloc.c:3794
__alloc_pages_nodemask+0x372/0x860 mm/page_alloc.c:4891
alloc_slab_page+0x39/0x3e0 mm/slub.c:343
allocate_slab mm/slub.c:1683 [inline]
new_slab+0x97/0x450 mm/slub.c:1749
new_slab_objects mm/slub.c:2505 [inline]
___slab_alloc+0x320/0x4a0 mm/slub.c:2667
__slab_alloc+0x5a/0x90 mm/slub.c:2707
slab_alloc_node mm/slub.c:2792 [inline]
slab_alloc mm/slub.c:2837 [inline]
kmem_cache_alloc+0x100/0x210 mm/slub.c:2842
kmem_cache_alloc_node include/linux/slab.h:427 [inline]
__alloc_skb+0x78/0x4d0 net/core/skbuff.c:198
__napi_alloc_skb+0x11f/0x540 net/core/skbuff.c:516
napi_alloc_skb include/linux/skbuff.h:2877 [inline]
page_to_skb+0x39/0x910 drivers/net/virtio_net.c:412
receive_mergeable+0x7e2/0x23d0 drivers/net/virtio_net.c:997
receive_buf+0x140/0x1a30 drivers/net/virtio_net.c:1107
virtnet_receive drivers/net/virtio_net.c:1399 [inline]
virtnet_poll+0x4ae/0x1200 drivers/net/virtio_net.c:1508
napi_poll+0x195/0x670 net/core/dev.c:6353
net_rx_action+0x37f/0x9c0 net/core/dev.c:6421
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1176 [inline]
free_pcp_prepare+0x1a4/0x290 mm/page_alloc.c:1233
free_unref_page_prepare mm/page_alloc.c:3085 [inline]
free_unref_page mm/page_alloc.c:3134 [inline]
free_the_page mm/page_alloc.c:4951 [inline]
__free_pages+0x9c/0x250 mm/page_alloc.c:4959
__free_slab+0x22b/0x2e0 mm/slub.c:1774
free_slab mm/slub.c:1789 [inline]
discard_slab mm/slub.c:1795 [inline]
unfreeze_partials+0x14f/0x180 mm/slub.c:2288
put_cpu_partial+0xb5/0x150 mm/slub.c:2324
__slab_free+0x2ac/0x370 mm/slub.c:2971
qlist_free_all+0x4c/0xb0 mm/kasan/quarantine.c:167
quarantine_reduce+0x174/0x190 mm/kasan/quarantine.c:260
__kasan_kmalloc+0x43/0x1e0 mm/kasan/common.c:507
slab_post_alloc_hook mm/slab.h:584 [inline]
slab_alloc_node mm/slub.c:2829 [inline]
slab_alloc mm/slub.c:2837 [inline]
kmem_cache_alloc+0xd0/0x210 mm/slub.c:2842
kmem_cache_alloc_node include/linux/slab.h:427 [inline]
__alloc_skb+0x78/0x4d0 net/core/skbuff.c:198
alloc_skb_fclone include/linux/skbuff.h:1110 [inline]
sk_stream_alloc_skb+0x1ee/0xa80 net/ipv4/tcp.c:887
tcp_sendmsg_locked+0xe3f/0x3780 net/ipv4/tcp.c:1296
tcp_sendmsg+0x2c/0x40 net/ipv4/tcp.c:1446
sock_sendmsg_nosec net/socket.c:638 [inline]
sock_sendmsg net/socket.c:658 [inline]
sock_write_iter+0x33f/0x460 net/socket.c:990
call_write_iter include/linux/fs.h:1976 [inline]
new_sync_write fs/read_write.c:483 [inline]
__vfs_write+0x5e3/0x780 fs/read_write.c:496
Memory state around the buggy address:
ffff8881ed262f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881ed262f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8881ed263000: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff8881ed263080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc
ffff8881ed263100: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb
==================================================================
EXT4-fs error (device loop5): ext4_read_block_bitmap_nowait:430: comm syz-executor.5: Invalid block bitmap block 0 in block_group 0
---
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 found the following issue on:
HEAD commit: 4a947285bcca UPSTREAM: dma-buf: system_heap: Avoid warning..
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=12f21c94480000
kernel config: https://syzkaller.appspot.com/x/.config?x=b4f7fdc1fca3154e
dashboard link: https://syzkaller.appspot.com/bug?extid=83f4272d07a60d313711
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b962c72968d3/disk-4a947285.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b2bc3b543b67/vmlinux-4a947285.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5630795b1da7/bzImage-4a947285.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+83f427...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in get_max_inline_xattr_value_size+0x373/0x510 fs/ext4/inline.c:61
Read of size 4 at addr ffff8881ed263010 by task syz-executor.5/31817
CPU: 1 PID: 31817 Comm: syz-executor.5 Not tainted 5.4.219-syzkaller-00013-g4a947285bcca #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1d8/0x241 lib/dump_stack.c:118
print_address_description+0x8c/0x630 mm/kasan/report.c:384
__kasan_report+0xf6/0x130 mm/kasan/report.c:516
kasan_report+0x30/0x60 mm/kasan/common.c:653
get_max_inline_xattr_value_size+0x373/0x510 fs/ext4/inline.c:61
ext4_get_max_inline_size+0x139/0x1f0 fs/ext4/inline.c:112
ext4_try_to_write_inline_data+0xd9/0x1750 fs/ext4/inline.c:673
ext4_write_begin+0x247/0x1d50 fs/ext4/inode.c:1312
ext4_da_write_begin+0x4a8/0xf80 fs/ext4/inode.c:3110
generic_perform_write+0x2f9/0x5a0 mm/filemap.c:3311
__generic_file_write_iter+0x239/0x490 mm/filemap.c:3440
ext4_file_write_iter+0x495/0x10e0 fs/ext4/file.c:270
call_write_iter include/linux/fs.h:1976 [inline]
new_sync_write fs/read_write.c:483 [inline]
__vfs_write+0x5e3/0x780 fs/read_write.c:496
vfs_write+0x210/0x4f0 fs/read_write.c:558
ksys_write+0x198/0x2c0 fs/read_write.c:611
do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Allocated by task 28620:
save_stack mm/kasan/common.c:70 [inline]
set_track mm/kasan/common.c:78 [inline]
__kasan_kmalloc+0x131/0x1e0 mm/kasan/common.c:529
slab_post_alloc_hook mm/slab.h:584 [inline]
slab_alloc_node mm/slub.c:2829 [inline]
slab_alloc mm/slub.c:2837 [inline]
kmem_cache_alloc+0xd0/0x210 mm/slub.c:2842
skb_clone+0x1b7/0x380 net/core/skbuff.c:1459
do_one_broadcast net/netlink/af_netlink.c:1445 [inline]
netlink_broadcast_filtered+0x65b/0x11d0 net/netlink/af_netlink.c:1520
netlink_broadcast net/netlink/af_netlink.c:1544 [inline]
netlink_sendmsg+0x9bb/0xcc0 net/netlink/af_netlink.c:1931
sock_sendmsg_nosec net/socket.c:638 [inline]
sock_sendmsg net/socket.c:658 [inline]
____sys_sendmsg+0x5a6/0x8f0 net/socket.c:2287
___sys_sendmsg net/socket.c:2341 [inline]
__sys_sendmsg+0x2b7/0x3a0 net/socket.c:2387
do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Freed by task 28620:
save_stack mm/kasan/common.c:70 [inline]
set_track mm/kasan/common.c:78 [inline]
kasan_set_free_info mm/kasan/common.c:345 [inline]
__kasan_slab_free+0x178/0x240 mm/kasan/common.c:487
slab_free_hook mm/slub.c:1455 [inline]
slab_free_freelist_hook+0x80/0x150 mm/slub.c:1494
slab_free mm/slub.c:3080 [inline]
kmem_cache_free+0xa9/0x1d0 mm/slub.c:3096
do_one_broadcast net/netlink/af_netlink.c:1469 [inline]
netlink_broadcast_filtered+0x6d7/0x11d0 net/netlink/af_netlink.c:1520
netlink_broadcast net/netlink/af_netlink.c:1544 [inline]
netlink_sendmsg+0x9bb/0xcc0 net/netlink/af_netlink.c:1931
sock_sendmsg_nosec net/socket.c:638 [inline]
sock_sendmsg net/socket.c:658 [inline]
____sys_sendmsg+0x5a6/0x8f0 net/socket.c:2287
___sys_sendmsg net/socket.c:2341 [inline]
__sys_sendmsg+0x2b7/0x3a0 net/socket.c:2387
do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
The buggy address belongs to the object at ffff8881ed263000
which belongs to the cache skbuff_head_cache of size 240
The buggy address is located 16 bytes inside of
240-byte region [ffff8881ed263000, ffff8881ed2630f0)
The buggy address belongs to the page:
page:ffffea0007b498c0 refcount:1 mapcount:0 mapping:ffff8881f1ddd400 index:0x0
flags: 0x8000000000000200(slab)
raw: 8000000000000200 ffffea0007ba1d80 0000000400000004 ffff8881f1ddd400
raw: 0000000000000000 00000000000c000c 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x12a20(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY)
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook mm/page_alloc.c:2165 [inline]
prep_new_page+0x194/0x380 mm/page_alloc.c:2171
get_page_from_freelist+0x524/0x560 mm/page_alloc.c:3794
__alloc_pages_nodemask+0x372/0x860 mm/page_alloc.c:4891
alloc_slab_page+0x39/0x3e0 mm/slub.c:343
allocate_slab mm/slub.c:1683 [inline]
new_slab+0x97/0x450 mm/slub.c:1749
new_slab_objects mm/slub.c:2505 [inline]
___slab_alloc+0x320/0x4a0 mm/slub.c:2667
__slab_alloc+0x5a/0x90 mm/slub.c:2707
slab_alloc_node mm/slub.c:2792 [inline]
slab_alloc mm/slub.c:2837 [inline]
kmem_cache_alloc+0x100/0x210 mm/slub.c:2842
kmem_cache_alloc_node include/linux/slab.h:427 [inline]
__alloc_skb+0x78/0x4d0 net/core/skbuff.c:198
__napi_alloc_skb+0x11f/0x540 net/core/skbuff.c:516
napi_alloc_skb include/linux/skbuff.h:2877 [inline]
page_to_skb+0x39/0x910 drivers/net/virtio_net.c:412
receive_mergeable+0x7e2/0x23d0 drivers/net/virtio_net.c:997
receive_buf+0x140/0x1a30 drivers/net/virtio_net.c:1107
virtnet_receive drivers/net/virtio_net.c:1399 [inline]
virtnet_poll+0x4ae/0x1200 drivers/net/virtio_net.c:1508
napi_poll+0x195/0x670 net/core/dev.c:6353
net_rx_action+0x37f/0x9c0 net/core/dev.c:6421
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1176 [inline]
free_pcp_prepare+0x1a4/0x290 mm/page_alloc.c:1233
free_unref_page_prepare mm/page_alloc.c:3085 [inline]
free_unref_page mm/page_alloc.c:3134 [inline]
free_the_page mm/page_alloc.c:4951 [inline]
__free_pages+0x9c/0x250 mm/page_alloc.c:4959
__free_slab+0x22b/0x2e0 mm/slub.c:1774
free_slab mm/slub.c:1789 [inline]
discard_slab mm/slub.c:1795 [inline]
unfreeze_partials+0x14f/0x180 mm/slub.c:2288
put_cpu_partial+0xb5/0x150 mm/slub.c:2324
__slab_free+0x2ac/0x370 mm/slub.c:2971
qlist_free_all+0x4c/0xb0 mm/kasan/quarantine.c:167
quarantine_reduce+0x174/0x190 mm/kasan/quarantine.c:260
__kasan_kmalloc+0x43/0x1e0 mm/kasan/common.c:507
slab_post_alloc_hook mm/slab.h:584 [inline]
slab_alloc_node mm/slub.c:2829 [inline]
slab_alloc mm/slub.c:2837 [inline]
kmem_cache_alloc+0xd0/0x210 mm/slub.c:2842
kmem_cache_alloc_node include/linux/slab.h:427 [inline]
__alloc_skb+0x78/0x4d0 net/core/skbuff.c:198
alloc_skb_fclone include/linux/skbuff.h:1110 [inline]
sk_stream_alloc_skb+0x1ee/0xa80 net/ipv4/tcp.c:887
tcp_sendmsg_locked+0xe3f/0x3780 net/ipv4/tcp.c:1296
tcp_sendmsg+0x2c/0x40 net/ipv4/tcp.c:1446
sock_sendmsg_nosec net/socket.c:638 [inline]
sock_sendmsg net/socket.c:658 [inline]
sock_write_iter+0x33f/0x460 net/socket.c:990
call_write_iter include/linux/fs.h:1976 [inline]
new_sync_write fs/read_write.c:483 [inline]
__vfs_write+0x5e3/0x780 fs/read_write.c:496
Memory state around the buggy address:
ffff8881ed262f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881ed262f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8881ed263000: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff8881ed263080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc
ffff8881ed263100: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb
==================================================================
EXT4-fs error (device loop5): ext4_read_block_bitmap_nowait:430: comm syz-executor.5: Invalid block bitmap block 0 in block_group 0
---
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
2023年1月6日 02:47:402023/1/6
收件人 syzkaller-a...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 4a947285bcca UPSTREAM: dma-buf: system_heap: Avoid warning..
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=146592b2480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14084e8a480000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b962c72968d3/disk-4a947285.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b2bc3b543b67/vmlinux-4a947285.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5630795b1da7/bzImage-4a947285.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0bfa9ee05a7f/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+83f427...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in get_max_inline_xattr_value_size+0x373/0x510 fs/ext4/inline.c:61
Read of size 4 at addr ffff8881de7e4084 by task syz-executor374/300
CPU: 0 PID: 300 Comm: syz-executor374 Not tainted 5.4.219-syzkaller-00013-g4a947285bcca #0
__alloc_file+0x26/0x300 fs/file_table.c:101
alloc_empty_file+0xa9/0x1b0 fs/file_table.c:151
path_openat+0x116/0x3ea0 fs/namei.c:3603
do_filp_open+0x208/0x450 fs/namei.c:3644
do_sys_open+0x393/0x7e0 fs/open.c:1113
do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Freed by task 9:
rcu_do_batch+0x49e/0xa10 kernel/rcu/tree.c:2167
rcu_core+0x4ba/0xca0 kernel/rcu/tree.c:2387
__do_softirq+0x23e/0x643 kernel/softirq.c:292
The buggy address belongs to the object at ffff8881de7e4000
which belongs to the cache filp of size 280
The buggy address is located 132 bytes inside of
280-byte region [ffff8881de7e4000, ffff8881de7e4118)
flags: 0x8000000000010200(slab|head)
raw: 8000000000010200 dead000000000100 dead000000000122 ffff8881f5cf8500
raw: 0000000000000000 0000000000150015 00000001ffffffff 0000000000000000
__alloc_file+0x26/0x300 fs/file_table.c:101
alloc_empty_file+0xa9/0x1b0 fs/file_table.c:151
path_openat+0x116/0x3ea0 fs/namei.c:3603
do_filp_open+0x208/0x450 fs/namei.c:3644
do_sys_open+0x393/0x7e0 fs/open.c:1113
do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
page_owner free stack trace missing
Memory state around the buggy address:
ffff8881de7e3f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881de7e4000: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff8881de7e4080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff8881de7e4100: fb fb fb fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff8881de7e4180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
EXT4-fs error (device loop0): ext4_read_block_bitmap_nowait:430: comm syz-executor374: Invalid block bitmap block 0 in block_group 0
syz-executor374 (300) used greatest stack depth: 22872 bytes left
HEAD commit: 4a947285bcca UPSTREAM: dma-buf: system_heap: Avoid warning..
git tree: android12-5.4
kernel config: https://syzkaller.appspot.com/x/.config?x=b4f7fdc1fca3154e
dashboard link: https://syzkaller.appspot.com/bug?extid=83f4272d07a60d313711
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1622af5c480000
dashboard link: https://syzkaller.appspot.com/bug?extid=83f4272d07a60d313711
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14084e8a480000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b962c72968d3/disk-4a947285.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b2bc3b543b67/vmlinux-4a947285.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5630795b1da7/bzImage-4a947285.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+83f427...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in get_max_inline_xattr_value_size+0x373/0x510 fs/ext4/inline.c:61
CPU: 0 PID: 300 Comm: syz-executor374 Not tainted 5.4.219-syzkaller-00013-g4a947285bcca #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1d8/0x241 lib/dump_stack.c:118
print_address_description+0x8c/0x630 mm/kasan/report.c:384
__kasan_report+0xf6/0x130 mm/kasan/report.c:516
kasan_report+0x30/0x60 mm/kasan/common.c:653
get_max_inline_xattr_value_size+0x373/0x510 fs/ext4/inline.c:61
ext4_get_max_inline_size+0x139/0x1f0 fs/ext4/inline.c:112
ext4_try_to_write_inline_data+0xd9/0x1750 fs/ext4/inline.c:673
ext4_write_begin+0x247/0x1d50 fs/ext4/inode.c:1312
ext4_da_write_begin+0x4a8/0xf80 fs/ext4/inode.c:3110
generic_perform_write+0x2f9/0x5a0 mm/filemap.c:3311
__generic_file_write_iter+0x239/0x490 mm/filemap.c:3440
ext4_file_write_iter+0x495/0x10e0 fs/ext4/file.c:270
call_write_iter include/linux/fs.h:1976 [inline]
new_sync_write fs/read_write.c:483 [inline]
__vfs_write+0x5e3/0x780 fs/read_write.c:496
vfs_write+0x210/0x4f0 fs/read_write.c:558
ksys_write+0x198/0x2c0 fs/read_write.c:611
do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Allocated by task 295:
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1d8/0x241 lib/dump_stack.c:118
print_address_description+0x8c/0x630 mm/kasan/report.c:384
__kasan_report+0xf6/0x130 mm/kasan/report.c:516
kasan_report+0x30/0x60 mm/kasan/common.c:653
get_max_inline_xattr_value_size+0x373/0x510 fs/ext4/inline.c:61
ext4_get_max_inline_size+0x139/0x1f0 fs/ext4/inline.c:112
ext4_try_to_write_inline_data+0xd9/0x1750 fs/ext4/inline.c:673
ext4_write_begin+0x247/0x1d50 fs/ext4/inode.c:1312
ext4_da_write_begin+0x4a8/0xf80 fs/ext4/inode.c:3110
generic_perform_write+0x2f9/0x5a0 mm/filemap.c:3311
__generic_file_write_iter+0x239/0x490 mm/filemap.c:3440
ext4_file_write_iter+0x495/0x10e0 fs/ext4/file.c:270
call_write_iter include/linux/fs.h:1976 [inline]
new_sync_write fs/read_write.c:483 [inline]
__vfs_write+0x5e3/0x780 fs/read_write.c:496
vfs_write+0x210/0x4f0 fs/read_write.c:558
ksys_write+0x198/0x2c0 fs/read_write.c:611
do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
save_stack mm/kasan/common.c:70 [inline]
set_track mm/kasan/common.c:78 [inline]
__kasan_kmalloc+0x131/0x1e0 mm/kasan/common.c:529
slab_post_alloc_hook mm/slab.h:584 [inline]
slab_alloc_node mm/slub.c:2829 [inline]
slab_alloc mm/slub.c:2837 [inline]
kmem_cache_alloc+0xd0/0x210 mm/slub.c:2842
kmem_cache_zalloc include/linux/slab.h:680 [inline]
set_track mm/kasan/common.c:78 [inline]
__kasan_kmalloc+0x131/0x1e0 mm/kasan/common.c:529
slab_post_alloc_hook mm/slab.h:584 [inline]
slab_alloc_node mm/slub.c:2829 [inline]
slab_alloc mm/slub.c:2837 [inline]
kmem_cache_alloc+0xd0/0x210 mm/slub.c:2842
__alloc_file+0x26/0x300 fs/file_table.c:101
alloc_empty_file+0xa9/0x1b0 fs/file_table.c:151
path_openat+0x116/0x3ea0 fs/namei.c:3603
do_filp_open+0x208/0x450 fs/namei.c:3644
do_sys_open+0x393/0x7e0 fs/open.c:1113
do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Freed by task 9:
save_stack mm/kasan/common.c:70 [inline]
set_track mm/kasan/common.c:78 [inline]
kasan_set_free_info mm/kasan/common.c:345 [inline]
__kasan_slab_free+0x178/0x240 mm/kasan/common.c:487
slab_free_hook mm/slub.c:1455 [inline]
slab_free_freelist_hook+0x80/0x150 mm/slub.c:1494
slab_free mm/slub.c:3080 [inline]
kmem_cache_free+0xa9/0x1d0 mm/slub.c:3096
__rcu_reclaim kernel/rcu/rcu.h:222 [inline]
set_track mm/kasan/common.c:78 [inline]
kasan_set_free_info mm/kasan/common.c:345 [inline]
__kasan_slab_free+0x178/0x240 mm/kasan/common.c:487
slab_free_hook mm/slub.c:1455 [inline]
slab_free_freelist_hook+0x80/0x150 mm/slub.c:1494
slab_free mm/slub.c:3080 [inline]
kmem_cache_free+0xa9/0x1d0 mm/slub.c:3096
rcu_do_batch+0x49e/0xa10 kernel/rcu/tree.c:2167
rcu_core+0x4ba/0xca0 kernel/rcu/tree.c:2387
__do_softirq+0x23e/0x643 kernel/softirq.c:292
The buggy address belongs to the object at ffff8881de7e4000
which belongs to the cache filp of size 280
The buggy address is located 132 bytes inside of
280-byte region [ffff8881de7e4000, ffff8881de7e4118)
The buggy address belongs to the page:
page:ffffea000779f900 refcount:1 mapcount:0 mapping:ffff8881f5cf8500 index:0x0 compound_mapcount: 0
flags: 0x8000000000010200(slab|head)
raw: 8000000000010200 dead000000000100 dead000000000122 ffff8881f5cf8500
raw: 0000000000000000 0000000000150015 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 1, migratetype Unmovable, gfp_mask 0xd20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC)
page_owner tracks the page as allocated
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook mm/page_alloc.c:2165 [inline]
prep_new_page+0x194/0x380 mm/page_alloc.c:2171
get_page_from_freelist+0x524/0x560 mm/page_alloc.c:3794
__alloc_pages_nodemask+0x372/0x860 mm/page_alloc.c:4891
alloc_slab_page+0x39/0x3e0 mm/slub.c:343
allocate_slab mm/slub.c:1683 [inline]
new_slab+0x97/0x450 mm/slub.c:1749
new_slab_objects mm/slub.c:2505 [inline]
___slab_alloc+0x320/0x4a0 mm/slub.c:2667
__slab_alloc+0x5a/0x90 mm/slub.c:2707
slab_alloc_node mm/slub.c:2792 [inline]
slab_alloc mm/slub.c:2837 [inline]
kmem_cache_alloc+0x100/0x210 mm/slub.c:2842
kmem_cache_zalloc include/linux/slab.h:680 [inline]
post_alloc_hook mm/page_alloc.c:2165 [inline]
prep_new_page+0x194/0x380 mm/page_alloc.c:2171
get_page_from_freelist+0x524/0x560 mm/page_alloc.c:3794
__alloc_pages_nodemask+0x372/0x860 mm/page_alloc.c:4891
alloc_slab_page+0x39/0x3e0 mm/slub.c:343
allocate_slab mm/slub.c:1683 [inline]
new_slab+0x97/0x450 mm/slub.c:1749
new_slab_objects mm/slub.c:2505 [inline]
___slab_alloc+0x320/0x4a0 mm/slub.c:2667
__slab_alloc+0x5a/0x90 mm/slub.c:2707
slab_alloc_node mm/slub.c:2792 [inline]
slab_alloc mm/slub.c:2837 [inline]
kmem_cache_alloc+0x100/0x210 mm/slub.c:2842
__alloc_file+0x26/0x300 fs/file_table.c:101
alloc_empty_file+0xa9/0x1b0 fs/file_table.c:151
path_openat+0x116/0x3ea0 fs/namei.c:3603
do_filp_open+0x208/0x450 fs/namei.c:3644
do_sys_open+0x393/0x7e0 fs/open.c:1113
do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
page_owner free stack trace missing
Memory state around the buggy address:
ffff8881de7e4000: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff8881de7e4080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff8881de7e4100: fb fb fb fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff8881de7e4180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
EXT4-fs error (device loop0): ext4_read_block_bitmap_nowait:430: comm syz-executor374: Invalid block bitmap block 0 in block_group 0
syz-executor374 (300) used greatest stack depth: 22872 bytes left
syzbot
2023年1月6日 03:19:352023/1/6
收件人 syzkaller-a...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: c73b4619ad86 ANDROID: abi preservation for fscrypt change ..
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=112e986a480000
kernel config: https://syzkaller.appspot.com/x/.config?x=d7c9bd3bb9661aad
dashboard link: https://syzkaller.appspot.com/bug?extid=b3bf4746131622e759a4
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15d9ecfa480000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d4a785f6c196/disk-c73b4619.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e2fba875c9ab/vmlinux-c73b4619.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a870e2543ec9/bzImage-c73b4619.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/b4846beb1817/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b3bf47...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in get_max_inline_xattr_value_size+0x387/0x530 fs/ext4/inline.c:62
Read of size 4 at addr ffff88811a9b9084 by task syz-executor294/430
CPU: 1 PID: 430 Comm: syz-executor294 Not tainted 5.15.78-syzkaller-00911-gc73b4619ad86 #0
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
print_address_description+0x87/0x3d0 mm/kasan/report.c:256
__kasan_report mm/kasan/report.c:435 [inline]
kasan_report+0x1a6/0x1f0 mm/kasan/report.c:452
__asan_report_load4_noabort+0x14/0x20 mm/kasan/report_generic.c:308
get_max_inline_xattr_value_size+0x387/0x530 fs/ext4/inline.c:62
ext4_get_max_inline_size+0x142/0x200 fs/ext4/inline.c:113
ext4_try_to_write_inline_data+0xdd/0x11e0 fs/ext4/inline.c:677
ext4_write_begin+0x23b/0x1360 fs/ext4/inode.c:1172
ext4_da_write_begin+0x4ac/0xbf0 fs/ext4/inode.c:2979
generic_perform_write+0x2cd/0x5d0 mm/filemap.c:3825
ext4_buffered_write_iter+0x49b/0x630 fs/ext4/file.c:271
ext4_file_write_iter+0x448/0x1cc0
call_write_iter include/linux/fs.h:2138 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xc8d/0x1050 fs/read_write.c:594
ksys_write+0x198/0x2c0 fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__x64_sys_write+0x7b/0x90 fs/read_write.c:656
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7feccd6e7529
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 14 00 00 90 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:00007fff3d2b4c98 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007feccd6e7529
RDX: 0000000000000018 RSI: 0000000020000700 RDI: 0000000000000004
RBP: 0000000000000000 R08: 00007feccd755ec0 R09: 00007feccd755ec0
R10: 00007feccd755ec0 R11: 0000000000000246 R12: 00007fff3d2b4cc0
R13: 0000000000000000 R14: 431bde82d7b634db R15: 0000000000000000
</TASK>
Allocated by task 316:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track mm/kasan/common.c:45 [inline]
set_alloc_info mm/kasan/common.c:433 [inline]
__kasan_slab_alloc+0xb2/0xe0 mm/kasan/common.c:466
kasan_slab_alloc include/linux/kasan.h:244 [inline]
slab_post_alloc_hook mm/slab.h:550 [inline]
slab_alloc_node mm/slub.c:3236 [inline]
slab_alloc mm/slub.c:3244 [inline]
kmem_cache_alloc+0x189/0x2f0 mm/slub.c:3249
skb_clone+0x1df/0x3d0 net/core/skbuff.c:1547
dev_queue_xmit_nit+0x283/0xa60 net/core/dev.c:2297
xmit_one+0x88/0x480 net/core/dev.c:3592
dev_hard_start_xmit+0xad/0x1c0 net/core/dev.c:3613
sch_direct_xmit+0x295/0x9b0 net/sched/sch_generic.c:342
__dev_xmit_skb+0xb93/0x1650 net/core/dev.c:3824
__dev_queue_xmit+0x8f3/0x1b50 net/core/dev.c:4193
dev_queue_xmit+0x17/0x20 net/core/dev.c:4261
neigh_hh_output include/net/neighbour.h:508 [inline]
neigh_output include/net/neighbour.h:522 [inline]
ip_finish_output2+0xc0f/0xf00 net/ipv4/ip_output.c:228
__ip_finish_output+0x163/0x370
ip_finish_output+0x20b/0x220 net/ipv4/ip_output.c:316
NF_HOOK_COND include/linux/netfilter.h:299 [inline]
ip_output+0x1e9/0x410 net/ipv4/ip_output.c:430
dst_output include/net/dst.h:450 [inline]
ip_local_out net/ipv4/ip_output.c:126 [inline]
__ip_queue_xmit+0x10b1/0x1be0 net/ipv4/ip_output.c:532
ip_queue_xmit+0x4b/0x70 net/ipv4/ip_output.c:546
__tcp_transmit_skb+0x1ef4/0x3a20 net/ipv4/tcp_output.c:1403
__tcp_send_ack+0x2f4/0x700 net/ipv4/tcp_output.c:3989
tcp_send_ack+0x3a/0x50 net/ipv4/tcp_output.c:3995
tcp_cleanup_rbuf+0x27f/0x5d0 net/ipv4/tcp.c:1602
tcp_recvmsg_locked+0x22a7/0x2920 net/ipv4/tcp.c:2529
tcp_recvmsg+0x269/0x870 net/ipv4/tcp.c:2560
inet_recvmsg+0x157/0x500 net/ipv4/af_inet.c:858
sock_recvmsg_nosec net/socket.c:947 [inline]
sock_recvmsg net/socket.c:965 [inline]
sock_read_iter+0x3a7/0x4d0 net/socket.c:1038
call_read_iter include/linux/fs.h:2132 [inline]
new_sync_read fs/read_write.c:404 [inline]
vfs_read+0xabc/0xd80 fs/read_write.c:485
ksys_read+0x198/0x2c0 fs/read_write.c:623
__do_sys_read fs/read_write.c:633 [inline]
__se_sys_read fs/read_write.c:631 [inline]
__x64_sys_read+0x7b/0x90 fs/read_write.c:631
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
Freed by task 316:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4c/0x70 mm/kasan/common.c:45
kasan_set_free_info+0x23/0x40 mm/kasan/generic.c:370
____kasan_slab_free+0x126/0x160 mm/kasan/common.c:365
__kasan_slab_free+0x11/0x20 mm/kasan/common.c:373
kasan_slab_free include/linux/kasan.h:220 [inline]
slab_free_hook mm/slub.c:1721 [inline]
slab_free_freelist_hook+0xc9/0x1a0 mm/slub.c:1747
slab_free mm/slub.c:3515 [inline]
kmem_cache_free+0x11a/0x2e0 mm/slub.c:3531
__kfree_skb+0x13e/0x1c0 net/core/skbuff.c:758
consume_skb+0x72/0x1f0 net/core/skbuff.c:930
packet_rcv+0x157/0x1430 net/packet/af_packet.c:2183
dev_queue_xmit_nit+0x9cd/0xa60 net/core/dev.c:2329
xmit_one+0x88/0x480 net/core/dev.c:3592
dev_hard_start_xmit+0xad/0x1c0 net/core/dev.c:3613
sch_direct_xmit+0x295/0x9b0 net/sched/sch_generic.c:342
__dev_xmit_skb+0xb93/0x1650 net/core/dev.c:3824
__dev_queue_xmit+0x8f3/0x1b50 net/core/dev.c:4193
dev_queue_xmit+0x17/0x20 net/core/dev.c:4261
neigh_hh_output include/net/neighbour.h:508 [inline]
neigh_output include/net/neighbour.h:522 [inline]
ip_finish_output2+0xc0f/0xf00 net/ipv4/ip_output.c:228
__ip_finish_output+0x163/0x370
ip_finish_output+0x20b/0x220 net/ipv4/ip_output.c:316
NF_HOOK_COND include/linux/netfilter.h:299 [inline]
ip_output+0x1e9/0x410 net/ipv4/ip_output.c:430
dst_output include/net/dst.h:450 [inline]
ip_local_out net/ipv4/ip_output.c:126 [inline]
__ip_queue_xmit+0x10b1/0x1be0 net/ipv4/ip_output.c:532
ip_queue_xmit+0x4b/0x70 net/ipv4/ip_output.c:546
__tcp_transmit_skb+0x1ef4/0x3a20 net/ipv4/tcp_output.c:1403
__tcp_send_ack+0x2f4/0x700 net/ipv4/tcp_output.c:3989
tcp_send_ack+0x3a/0x50 net/ipv4/tcp_output.c:3995
tcp_cleanup_rbuf+0x27f/0x5d0 net/ipv4/tcp.c:1602
tcp_recvmsg_locked+0x22a7/0x2920 net/ipv4/tcp.c:2529
tcp_recvmsg+0x269/0x870 net/ipv4/tcp.c:2560
inet_recvmsg+0x157/0x500 net/ipv4/af_inet.c:858
sock_recvmsg_nosec net/socket.c:947 [inline]
sock_recvmsg net/socket.c:965 [inline]
sock_read_iter+0x3a7/0x4d0 net/socket.c:1038
call_read_iter include/linux/fs.h:2132 [inline]
new_sync_read fs/read_write.c:404 [inline]
vfs_read+0xabc/0xd80 fs/read_write.c:485
ksys_read+0x198/0x2c0 fs/read_write.c:623
__do_sys_read fs/read_write.c:633 [inline]
__se_sys_read fs/read_write.c:631 [inline]
__x64_sys_read+0x7b/0x90 fs/read_write.c:631
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
The buggy address belongs to the object at ffff88811a9b9000
which belongs to the cache skbuff_head_cache of size 248
flags: 0x4000000000000200(slab|zone=1)
raw: 4000000000000200 0000000000000000 dead000000000122 ffff8881087d3200
raw: 0000000000000000 00000000000c000c 00000001ffffffff 0000000000000000
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0x1ab/0x1b0 mm/page_alloc.c:2495
prep_new_page mm/page_alloc.c:2501 [inline]
get_page_from_freelist+0x38b/0x400 mm/page_alloc.c:4281
__alloc_pages+0x3a8/0x7c0 mm/page_alloc.c:5548
allocate_slab+0x62/0x580 mm/slub.c:1928
new_slab mm/slub.c:1991 [inline]
___slab_alloc+0x2e2/0x6f0 mm/slub.c:3024
__slab_alloc+0x4a/0x90 mm/slub.c:3111
slab_alloc_node mm/slub.c:3202 [inline]
slab_alloc mm/slub.c:3244 [inline]
kmem_cache_alloc+0x205/0x2f0 mm/slub.c:3249
skb_clone+0x1df/0x3d0 net/core/skbuff.c:1547
dev_queue_xmit_nit+0x283/0xa60 net/core/dev.c:2297
xmit_one+0x88/0x480 net/core/dev.c:3592
dev_hard_start_xmit+0xad/0x1c0 net/core/dev.c:3613
sch_direct_xmit+0x295/0x9b0 net/sched/sch_generic.c:342
__dev_xmit_skb+0xb93/0x1650 net/core/dev.c:3824
__dev_queue_xmit+0x8f3/0x1b50 net/core/dev.c:4193
dev_queue_xmit+0x17/0x20 net/core/dev.c:4261
neigh_hh_output include/net/neighbour.h:508 [inline]
neigh_output include/net/neighbour.h:522 [inline]
ip_finish_output2+0xc0f/0xf00 net/ipv4/ip_output.c:228
free_pages_prepare mm/page_alloc.c:1364 [inline]
free_pcp_prepare+0x448/0x450 mm/page_alloc.c:1435
free_unref_page_prepare mm/page_alloc.c:3433 [inline]
free_unref_page+0x9c/0x370 mm/page_alloc.c:3513
__put_single_page mm/swap.c:98 [inline]
__put_page+0xb0/0xd0 mm/swap.c:129
put_page include/linux/mm.h:1288 [inline]
anon_pipe_buf_release+0x17b/0x1e0 fs/pipe.c:137
pipe_buf_release include/linux/pipe_fs_i.h:203 [inline]
pipe_read+0x5c1/0x1060 fs/pipe.c:323
call_read_iter include/linux/fs.h:2132 [inline]
new_sync_read fs/read_write.c:404 [inline]
vfs_read+0xabc/0xd80 fs/read_write.c:485
ksys_read+0x198/0x2c0 fs/read_write.c:623
__do_sys_read fs/read_write.c:633 [inline]
__se_sys_read fs/read_write.c:631 [inline]
__x64_sys_read+0x7b/0x90 fs/read_write.c:631
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
Memory state around the buggy address:
ffff88811a9b8f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff88811a9b9000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88811a9b9080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fc
^
ffff88811a9b9100: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb
ffff88811a9b9180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
EXT4-fs error (device loop0): ext4_read_block_bitmap_nowait:437: comm syz-executor294: Invalid block bitmap block 0 in block_group 0
syz-executor294 (430) used greatest stack depth: 21792 bytes left
---
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
syzbot found the following issue on:
HEAD commit: c73b4619ad86 ANDROID: abi preservation for fscrypt change ..
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=112e986a480000
kernel config: https://syzkaller.appspot.com/x/.config?x=d7c9bd3bb9661aad
dashboard link: https://syzkaller.appspot.com/bug?extid=b3bf4746131622e759a4
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c63c52480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15d9ecfa480000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d4a785f6c196/disk-c73b4619.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e2fba875c9ab/vmlinux-c73b4619.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a870e2543ec9/bzImage-c73b4619.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/b4846beb1817/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
==================================================================
BUG: KASAN: use-after-free in get_max_inline_xattr_value_size+0x387/0x530 fs/ext4/inline.c:62
Read of size 4 at addr ffff88811a9b9084 by task syz-executor294/430
CPU: 1 PID: 430 Comm: syz-executor294 Not tainted 5.15.78-syzkaller-00911-gc73b4619ad86 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
<TASK>
Call Trace:
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
print_address_description+0x87/0x3d0 mm/kasan/report.c:256
__kasan_report mm/kasan/report.c:435 [inline]
kasan_report+0x1a6/0x1f0 mm/kasan/report.c:452
__asan_report_load4_noabort+0x14/0x20 mm/kasan/report_generic.c:308
get_max_inline_xattr_value_size+0x387/0x530 fs/ext4/inline.c:62
ext4_get_max_inline_size+0x142/0x200 fs/ext4/inline.c:113
ext4_try_to_write_inline_data+0xdd/0x11e0 fs/ext4/inline.c:677
ext4_write_begin+0x23b/0x1360 fs/ext4/inode.c:1172
ext4_da_write_begin+0x4ac/0xbf0 fs/ext4/inode.c:2979
generic_perform_write+0x2cd/0x5d0 mm/filemap.c:3825
ext4_buffered_write_iter+0x49b/0x630 fs/ext4/file.c:271
ext4_file_write_iter+0x448/0x1cc0
call_write_iter include/linux/fs.h:2138 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xc8d/0x1050 fs/read_write.c:594
ksys_write+0x198/0x2c0 fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__x64_sys_write+0x7b/0x90 fs/read_write.c:656
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7feccd6e7529
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 14 00 00 90 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:00007fff3d2b4c98 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007feccd6e7529
RDX: 0000000000000018 RSI: 0000000020000700 RDI: 0000000000000004
RBP: 0000000000000000 R08: 00007feccd755ec0 R09: 00007feccd755ec0
R10: 00007feccd755ec0 R11: 0000000000000246 R12: 00007fff3d2b4cc0
R13: 0000000000000000 R14: 431bde82d7b634db R15: 0000000000000000
</TASK>
Allocated by task 316:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track mm/kasan/common.c:45 [inline]
set_alloc_info mm/kasan/common.c:433 [inline]
__kasan_slab_alloc+0xb2/0xe0 mm/kasan/common.c:466
kasan_slab_alloc include/linux/kasan.h:244 [inline]
slab_post_alloc_hook mm/slab.h:550 [inline]
slab_alloc_node mm/slub.c:3236 [inline]
slab_alloc mm/slub.c:3244 [inline]
kmem_cache_alloc+0x189/0x2f0 mm/slub.c:3249
skb_clone+0x1df/0x3d0 net/core/skbuff.c:1547
dev_queue_xmit_nit+0x283/0xa60 net/core/dev.c:2297
xmit_one+0x88/0x480 net/core/dev.c:3592
dev_hard_start_xmit+0xad/0x1c0 net/core/dev.c:3613
sch_direct_xmit+0x295/0x9b0 net/sched/sch_generic.c:342
__dev_xmit_skb+0xb93/0x1650 net/core/dev.c:3824
__dev_queue_xmit+0x8f3/0x1b50 net/core/dev.c:4193
dev_queue_xmit+0x17/0x20 net/core/dev.c:4261
neigh_hh_output include/net/neighbour.h:508 [inline]
neigh_output include/net/neighbour.h:522 [inline]
ip_finish_output2+0xc0f/0xf00 net/ipv4/ip_output.c:228
__ip_finish_output+0x163/0x370
ip_finish_output+0x20b/0x220 net/ipv4/ip_output.c:316
NF_HOOK_COND include/linux/netfilter.h:299 [inline]
ip_output+0x1e9/0x410 net/ipv4/ip_output.c:430
dst_output include/net/dst.h:450 [inline]
ip_local_out net/ipv4/ip_output.c:126 [inline]
__ip_queue_xmit+0x10b1/0x1be0 net/ipv4/ip_output.c:532
ip_queue_xmit+0x4b/0x70 net/ipv4/ip_output.c:546
__tcp_transmit_skb+0x1ef4/0x3a20 net/ipv4/tcp_output.c:1403
__tcp_send_ack+0x2f4/0x700 net/ipv4/tcp_output.c:3989
tcp_send_ack+0x3a/0x50 net/ipv4/tcp_output.c:3995
tcp_cleanup_rbuf+0x27f/0x5d0 net/ipv4/tcp.c:1602
tcp_recvmsg_locked+0x22a7/0x2920 net/ipv4/tcp.c:2529
tcp_recvmsg+0x269/0x870 net/ipv4/tcp.c:2560
inet_recvmsg+0x157/0x500 net/ipv4/af_inet.c:858
sock_recvmsg_nosec net/socket.c:947 [inline]
sock_recvmsg net/socket.c:965 [inline]
sock_read_iter+0x3a7/0x4d0 net/socket.c:1038
call_read_iter include/linux/fs.h:2132 [inline]
new_sync_read fs/read_write.c:404 [inline]
vfs_read+0xabc/0xd80 fs/read_write.c:485
ksys_read+0x198/0x2c0 fs/read_write.c:623
__do_sys_read fs/read_write.c:633 [inline]
__se_sys_read fs/read_write.c:631 [inline]
__x64_sys_read+0x7b/0x90 fs/read_write.c:631
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
Freed by task 316:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4c/0x70 mm/kasan/common.c:45
kasan_set_free_info+0x23/0x40 mm/kasan/generic.c:370
____kasan_slab_free+0x126/0x160 mm/kasan/common.c:365
__kasan_slab_free+0x11/0x20 mm/kasan/common.c:373
kasan_slab_free include/linux/kasan.h:220 [inline]
slab_free_hook mm/slub.c:1721 [inline]
slab_free_freelist_hook+0xc9/0x1a0 mm/slub.c:1747
slab_free mm/slub.c:3515 [inline]
kmem_cache_free+0x11a/0x2e0 mm/slub.c:3531
__kfree_skb+0x13e/0x1c0 net/core/skbuff.c:758
consume_skb+0x72/0x1f0 net/core/skbuff.c:930
packet_rcv+0x157/0x1430 net/packet/af_packet.c:2183
dev_queue_xmit_nit+0x9cd/0xa60 net/core/dev.c:2329
xmit_one+0x88/0x480 net/core/dev.c:3592
dev_hard_start_xmit+0xad/0x1c0 net/core/dev.c:3613
sch_direct_xmit+0x295/0x9b0 net/sched/sch_generic.c:342
__dev_xmit_skb+0xb93/0x1650 net/core/dev.c:3824
__dev_queue_xmit+0x8f3/0x1b50 net/core/dev.c:4193
dev_queue_xmit+0x17/0x20 net/core/dev.c:4261
neigh_hh_output include/net/neighbour.h:508 [inline]
neigh_output include/net/neighbour.h:522 [inline]
ip_finish_output2+0xc0f/0xf00 net/ipv4/ip_output.c:228
__ip_finish_output+0x163/0x370
ip_finish_output+0x20b/0x220 net/ipv4/ip_output.c:316
NF_HOOK_COND include/linux/netfilter.h:299 [inline]
ip_output+0x1e9/0x410 net/ipv4/ip_output.c:430
dst_output include/net/dst.h:450 [inline]
ip_local_out net/ipv4/ip_output.c:126 [inline]
__ip_queue_xmit+0x10b1/0x1be0 net/ipv4/ip_output.c:532
ip_queue_xmit+0x4b/0x70 net/ipv4/ip_output.c:546
__tcp_transmit_skb+0x1ef4/0x3a20 net/ipv4/tcp_output.c:1403
__tcp_send_ack+0x2f4/0x700 net/ipv4/tcp_output.c:3989
tcp_send_ack+0x3a/0x50 net/ipv4/tcp_output.c:3995
tcp_cleanup_rbuf+0x27f/0x5d0 net/ipv4/tcp.c:1602
tcp_recvmsg_locked+0x22a7/0x2920 net/ipv4/tcp.c:2529
tcp_recvmsg+0x269/0x870 net/ipv4/tcp.c:2560
inet_recvmsg+0x157/0x500 net/ipv4/af_inet.c:858
sock_recvmsg_nosec net/socket.c:947 [inline]
sock_recvmsg net/socket.c:965 [inline]
sock_read_iter+0x3a7/0x4d0 net/socket.c:1038
call_read_iter include/linux/fs.h:2132 [inline]
new_sync_read fs/read_write.c:404 [inline]
vfs_read+0xabc/0xd80 fs/read_write.c:485
ksys_read+0x198/0x2c0 fs/read_write.c:623
__do_sys_read fs/read_write.c:633 [inline]
__se_sys_read fs/read_write.c:631 [inline]
__x64_sys_read+0x7b/0x90 fs/read_write.c:631
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
The buggy address belongs to the object at ffff88811a9b9000
which belongs to the cache skbuff_head_cache of size 248
The buggy address is located 132 bytes inside of
248-byte region [ffff88811a9b9000, ffff88811a9b90f8)
The buggy address belongs to the page:
page:ffffea00046a6e40 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x11a9b9
flags: 0x4000000000000200(slab|zone=1)
raw: 4000000000000200 0000000000000000 dead000000000122 ffff8881087d3200
raw: 0000000000000000 00000000000c000c 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x12a20(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY), pid 316, ts 11127644083, free_ts 10964759012
page_owner tracks the page as allocated
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0x1ab/0x1b0 mm/page_alloc.c:2495
prep_new_page mm/page_alloc.c:2501 [inline]
get_page_from_freelist+0x38b/0x400 mm/page_alloc.c:4281
__alloc_pages+0x3a8/0x7c0 mm/page_alloc.c:5548
allocate_slab+0x62/0x580 mm/slub.c:1928
new_slab mm/slub.c:1991 [inline]
___slab_alloc+0x2e2/0x6f0 mm/slub.c:3024
__slab_alloc+0x4a/0x90 mm/slub.c:3111
slab_alloc_node mm/slub.c:3202 [inline]
slab_alloc mm/slub.c:3244 [inline]
kmem_cache_alloc+0x205/0x2f0 mm/slub.c:3249
skb_clone+0x1df/0x3d0 net/core/skbuff.c:1547
dev_queue_xmit_nit+0x283/0xa60 net/core/dev.c:2297
xmit_one+0x88/0x480 net/core/dev.c:3592
dev_hard_start_xmit+0xad/0x1c0 net/core/dev.c:3613
sch_direct_xmit+0x295/0x9b0 net/sched/sch_generic.c:342
__dev_xmit_skb+0xb93/0x1650 net/core/dev.c:3824
__dev_queue_xmit+0x8f3/0x1b50 net/core/dev.c:4193
dev_queue_xmit+0x17/0x20 net/core/dev.c:4261
neigh_hh_output include/net/neighbour.h:508 [inline]
neigh_output include/net/neighbour.h:522 [inline]
ip_finish_output2+0xc0f/0xf00 net/ipv4/ip_output.c:228
page last free stack trace:
reset_page_owner include/linux/page_owner.h:26 [inline]
free_pages_prepare mm/page_alloc.c:1364 [inline]
free_pcp_prepare+0x448/0x450 mm/page_alloc.c:1435
free_unref_page_prepare mm/page_alloc.c:3433 [inline]
free_unref_page+0x9c/0x370 mm/page_alloc.c:3513
__put_single_page mm/swap.c:98 [inline]
__put_page+0xb0/0xd0 mm/swap.c:129
put_page include/linux/mm.h:1288 [inline]
anon_pipe_buf_release+0x17b/0x1e0 fs/pipe.c:137
pipe_buf_release include/linux/pipe_fs_i.h:203 [inline]
pipe_read+0x5c1/0x1060 fs/pipe.c:323
call_read_iter include/linux/fs.h:2132 [inline]
new_sync_read fs/read_write.c:404 [inline]
vfs_read+0xabc/0xd80 fs/read_write.c:485
ksys_read+0x198/0x2c0 fs/read_write.c:623
__do_sys_read fs/read_write.c:633 [inline]
__se_sys_read fs/read_write.c:631 [inline]
__x64_sys_read+0x7b/0x90 fs/read_write.c:631
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
Memory state around the buggy address:
ffff88811a9b9000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88811a9b9080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fc
^
ffff88811a9b9100: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb
ffff88811a9b9180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
EXT4-fs error (device loop0): ext4_read_block_bitmap_nowait:437: comm syz-executor294: Invalid block bitmap block 0 in block_group 0
syz-executor294 (430) used greatest stack depth: 21792 bytes left
---
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.
https://goo.gl/tpsmEJ#testing-patches
syzbot
2023年4月20日 13:02:372023/4/20
收件人 jone...@google.com、syzkaller-a...@googlegroups.com、tudor....@linaro.org
This bug is marked as fixed by commit:
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
Kernel: Android 5.15
Dashboard link: https://syzkaller.appspot.com/bug?extid=b3bf4746131622e759a4
---
[1] I expect the commit to be present in:
1. android13-5.15-lts branch of
https://android.googlesource.com/kernel/common
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
Kernel: Android 5.15
Dashboard link: https://syzkaller.appspot.com/bug?extid=b3bf4746131622e759a4
---
[1] I expect the commit to be present in:
1. android13-5.15-lts branch of
https://android.googlesource.com/kernel/common
syzbot
2023年4月20日 13:14:322023/4/20
收件人 jone...@google.com、syzkaller-a...@googlegroups.com、tudor....@linaro.org
This bug is marked as fixed by commit:
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
Kernel: Android 5.4
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
Dashboard link: https://syzkaller.appspot.com/bug?extid=83f4272d07a60d313711
---
[1] I expect the commit to be present in:
https://android.googlesource.com/kernel/common
syzbot
2023年5月4日 13:02:512023/5/4
收件人 jone...@google.com、syzkaller-a...@googlegroups.com、tudor....@linaro.org
This bug is marked as fixed by commit:
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
---
[1] I expect the commit to be present in:
[1] I expect the commit to be present in:
syzbot
2023年5月4日 13:14:572023/5/4
收件人 jone...@google.com、syzkaller-a...@googlegroups.com、tudor....@linaro.org
This bug is marked as fixed by commit:
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
---
[1] I expect the commit to be present in:
[1] I expect the commit to be present in:
syzbot
2023年5月18日 13:02:552023/5/18
收件人 jone...@google.com、syzkaller-a...@googlegroups.com、tudor....@linaro.org
This bug is marked as fixed by commit:
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
---
[1] I expect the commit to be present in:
[1] I expect the commit to be present in:
syzbot
2023年5月18日 13:15:522023/5/18
收件人 jone...@google.com、syzkaller-a...@googlegroups.com、tudor....@linaro.org
This bug is marked as fixed by commit:
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
---
[1] I expect the commit to be present in:
[1] I expect the commit to be present in:
syzbot
2023年6月1日 13:03:482023/6/1
收件人 jone...@google.com、syzkaller-a...@googlegroups.com、tudor....@linaro.org
This bug is marked as fixed by commit:
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
---
[1] I expect the commit to be present in:
[1] I expect the commit to be present in:
syzbot
2023年6月1日 13:16:572023/6/1
收件人 jone...@google.com、syzkaller-a...@googlegroups.com、tudor....@linaro.org
This bug is marked as fixed by commit:
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
ext4: add inode table check in __ext4_get_inode_loc to aovid
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
---
[1] I expect the commit to be present in:
[1] I expect the commit to be present in:
Tudor Ambarus
2023年6月5日 05:55:292023/6/5
收件人 syzbot、jone...@google.com、syzkaller-a...@googlegroups.com
#syz fix: ext4: add inode table check in __ext4_get_inode_loc to aovid possible infinite loop
Tudor Ambarus
2023年6月5日 05:56:112023/6/5
收件人 syzbot、jone...@google.com、syzkaller-a...@googlegroups.com
#syz fix: ext4: add inode table check in __ext4_get_inode_loc to aovid possible infinite loop
回复全部
回复作者
转发
0 个新帖子