ci starts bisection 2023-01-24 23:35:59.163441618 +0000 UTC m=+188673.109503683 bisecting fixing commit since a5088ee7251e5106a4efa9588a73866eb4b4154e building syzkaller on eab8f94940b33c0a2cbc7d8eb2219862b6864b19 ensuring issue is reproducible on original commit a5088ee7251e5106a4efa9588a73866eb4b4154e testing commit a5088ee7251e5106a4efa9588a73866eb4b4154e gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 0bca8c399e25ae3f7be0e749c6c9889a7d8fa4c02b51f45c2e2f15b91438e768 run #0: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #1: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #2: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #3: crashed: invalid opcode in corrupted run #4: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #5: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #6: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #7: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #8: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #9: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #10: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #11: crashed: BUG: unable to handle kernel paging request in truncate_inode_pages_final run #12: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #13: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #14: crashed: BUG: unable to handle kernel paging request in truncate_inode_pages_final run #15: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #16: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #17: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #18: OK run #19: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback testing current HEAD 7c46948a6e9cf47ed03b0d489fde894ad46f1437 testing commit 7c46948a6e9cf47ed03b0d489fde894ad46f1437 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 8101bb7982efdb52132ac9dee2f1752b56461fc7956d7269f23a4446eec6aed3 all runs: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync revisions tested: 2, total time: 32m50.001990246s (build: 13m35.967382843s, test: 18m11.174797666s) the crash still happens on HEAD commit msg: Merge tag 'fs.fuse.acl.v6.2-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/idmapping crash: KASAN: out-of-bounds Write in end_buffer_read_sync ================================================================== BUG: KASAN: out-of-bounds in instrument_atomic_read_write include/linux/instrumented.h:102 [inline] BUG: KASAN: out-of-bounds in atomic_dec include/linux/atomic/atomic-instrumented.h:257 [inline] BUG: KASAN: out-of-bounds in put_bh include/linux/buffer_head.h:320 [inline] BUG: KASAN: out-of-bounds in end_buffer_read_sync+0x5c/0x90 fs/buffer.c:160 Write of size 4 at addr ffffc900049879a8 by task ksoftirqd/1/21 CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.2.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x57/0x7d lib/dump_stack.c:106 print_address_description mm/kasan/report.c:306 [inline] print_report+0x15e/0x45d mm/kasan/report.c:417 kasan_report+0xbb/0x1f0 mm/kasan/report.c:517 check_region_inline mm/kasan/generic.c:183 [inline] kasan_check_range+0x13d/0x180 mm/kasan/generic.c:189 instrument_atomic_read_write include/linux/instrumented.h:102 [inline] atomic_dec include/linux/atomic/atomic-instrumented.h:257 [inline] put_bh include/linux/buffer_head.h:320 [inline] end_buffer_read_sync+0x5c/0x90 fs/buffer.c:160 end_bio_bh_io_sync+0xa9/0xf0 fs/buffer.c:2655 req_bio_endio block/blk-mq.c:794 [inline] blk_update_request+0x31f/0x10a0 block/blk-mq.c:926 blk_mq_end_request+0x46/0x70 block/blk-mq.c:1053 blk_complete_reqs+0xa0/0xd0 block/blk-mq.c:1131 __do_softirq+0x1f7/0xad8 kernel/softirq.c:571 run_ksoftirqd kernel/softirq.c:934 [inline] run_ksoftirqd+0x2d/0x60 kernel/softirq.c:926 smpboot_thread_fn+0x548/0x8f0 kernel/smpboot.c:164 kthread+0x294/0x330 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 The buggy address belongs to the virtual mapping at [ffffc90004980000, ffffc90004989000) created by: kernel_clone+0xb8/0x720 kernel/fork.c:2681 The buggy address belongs to the physical page: page:ffffea00007feb40 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1ffad memcg:ffff888016193a02 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff888016193a02 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x102dc2(GFP_HIGHUSER|__GFP_NOWARN|__GFP_ZERO), pid 5496, tgid 5496 (syz-executor.0), ts 319444760804, free_ts 319438246251 prep_new_page mm/page_alloc.c:2531 [inline] get_page_from_freelist+0x119c/0x2ce0 mm/page_alloc.c:4283 __alloc_pages+0x1c7/0x5a0 mm/page_alloc.c:5549 vm_area_alloc_pages mm/vmalloc.c:2989 [inline] __vmalloc_area_node mm/vmalloc.c:3057 [inline] __vmalloc_node_range+0x712/0x1010 mm/vmalloc.c:3227 alloc_thread_stack_node kernel/fork.c:311 [inline] dup_task_struct kernel/fork.c:987 [inline] copy_process+0x10a9/0x6bb0 kernel/fork.c:2097 kernel_clone+0xb8/0x720 kernel/fork.c:2681 __do_sys_clone+0xa1/0xe0 kernel/fork.c:2822 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd page last free stack trace: reset_page_owner include/linux/page_owner.h:24 [inline] free_pages_prepare mm/page_alloc.c:1446 [inline] free_pcp_prepare+0x65c/0xc00 mm/page_alloc.c:1496 free_unref_page_prepare mm/page_alloc.c:3369 [inline] free_unref_page_list+0x172/0xcc0 mm/page_alloc.c:3510 release_pages+0x31c/0x10c0 mm/swap.c:1076 __pagevec_release+0x59/0xb0 mm/swap.c:1096 pagevec_release include/linux/pagevec.h:71 [inline] folio_batch_release include/linux/pagevec.h:135 [inline] truncate_inode_pages_range+0x234/0xb60 mm/truncate.c:372 kill_bdev block/bdev.c:76 [inline] blkdev_flush_mapping+0x11a/0x250 block/bdev.c:662 blkdev_put_whole+0xa0/0xd0 block/bdev.c:693 blkdev_put+0x1c7/0x660 block/bdev.c:953 blkdev_close+0x5f/0x90 block/fops.c:492 __fput+0x1fa/0x9a0 fs/file_table.c:320 task_work_run+0x12b/0x220 kernel/task_work.c:179 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline] exit_to_user_mode_loop kernel/entry/common.c:171 [inline] exit_to_user_mode_prepare+0x23c/0x250 kernel/entry/common.c:203 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline] syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:296 do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x63/0xcd Memory state around the buggy address: ffffc90004987880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc90004987900: 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 >ffffc90004987980: 00 f3 f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 ^ ffffc90004987a00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc90004987a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================