ci starts bisection 2023-01-24 22:55:30.261930808 +0000 UTC m=+186244.207992874 bisecting fixing commit since a962b54e162c2977ff37905726cab29728380835 building syzkaller on feb5635181eb12a6e3516172a3f5af06a3bc93e1 ensuring issue is reproducible on original commit a962b54e162c2977ff37905726cab29728380835 testing commit a962b54e162c2977ff37905726cab29728380835 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: fc61b2cfbcadff000cc3490c2891082933dc4f6776a039e1d8d449c340f8d17a run #0: crashed: INFO: rcu detected stall in corrupted run #1: crashed: INFO: rcu detected stall in corrupted run #2: crashed: INFO: rcu detected stall in corrupted run #3: crashed: INFO: rcu detected stall in corrupted run #4: crashed: INFO: rcu detected stall in corrupted run #5: crashed: INFO: rcu detected stall in corrupted run #6: crashed: INFO: rcu detected stall in corrupted run #7: crashed: INFO: rcu detected stall in corrupted run #8: OK run #9: OK run #10: OK run #11: OK run #12: OK run #13: OK run #14: OK run #15: OK run #16: OK run #17: OK run #18: OK run #19: OK reproducer seems to be flaky 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: 7a405ea38db303ad9195deb35b6725d72f063ca710b0b8456784885bb0959b28 run #0: crashed: INFO: rcu detected stall in corrupted run #1: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #2: crashed: INFO: rcu detected stall in corrupted run #3: crashed: INFO: rcu detected stall in corrupted run #4: crashed: INFO: rcu detected stall in corrupted run #5: crashed: INFO: rcu detected stall in corrupted run #6: crashed: INFO: rcu detected stall in corrupted run #7: crashed: INFO: rcu detected stall in corrupted run #8: crashed: INFO: rcu detected stall in corrupted run #9: crashed: INFO: rcu detected stall in corrupted run #10: crashed: INFO: rcu detected stall in corrupted run #11: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #12: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #13: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #14: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #15: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #16: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #17: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #18: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #19: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync Reproducer flagged being flaky revisions tested: 2, total time: 35m23.070598597s (build: 13m29.369328785s, test: 20m52.836017962s) 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 ffffc9000ac779a8 by task ksoftirqd/0/15 CPU: 0 PID: 15 Comm: ksoftirqd/0 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 [ffffc9000ac70000, ffffc9000ac79000) created by: kernel_clone+0xb8/0x720 kernel/fork.c:2681 The buggy address belongs to the physical page: page:ffffea0000733180 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1ccc6 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 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 0x102dc2(GFP_HIGHUSER|__GFP_NOWARN|__GFP_ZERO), pid 17363, tgid 17363 (dhcpcd-run-hook), ts 496219518103, free_ts 495491911207 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: ffffc9000ac77880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000ac77900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc9000ac77980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc9000ac77a00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000ac77a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================