ci starts bisection 2023-04-26 15:28:50.020588173 +0000 UTC m=+8873.694848064 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: 924871afe4e702d75c21b0d6b2b7b7e3d21b8707e59ea5c8c0e6df9511841798 run #0: crashed: WARNING: locking bug in inode_wait_for_writeback run #1: crashed: invalid opcode in corrupted run #2: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #3: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #4: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #5: crashed: WARNING: suspicious RCU usage in ntfs_fill_super 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 inode_wait_for_writeback 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 inode_wait_for_writeback 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: OK testing current HEAD 0cfd8703e7da687924371e9bc77a025bdeba9637 testing commit 0cfd8703e7da687924371e9bc77a025bdeba9637 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 5cfbb628afe1176048544473bcc262b958e7db06b16c8c69ebabdbdb659e02ef all runs: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync revisions tested: 2, total time: 33m57.358330005s (build: 13m47.574581307s, test: 19m13.597750426s) the crash still happens on HEAD commit msg: Merge tag 'pm-6.4-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm 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:96 [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:323 [inline] BUG: KASAN: out-of-bounds in end_buffer_read_sync+0x5c/0x90 fs/buffer.c:161 Write of size 4 at addr ffffc900031279a8 by task ksoftirqd/1/21 CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.3.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x60/0xa0 lib/dump_stack.c:106 print_address_description.constprop.0+0x2c/0x3c0 mm/kasan/report.c:319 print_report mm/kasan/report.c:430 [inline] kasan_report+0x118/0x130 mm/kasan/report.c:536 check_region_inline mm/kasan/generic.c:181 [inline] kasan_check_range+0x13d/0x180 mm/kasan/generic.c:187 instrument_atomic_read_write include/linux/instrumented.h:96 [inline] atomic_dec include/linux/atomic/atomic-instrumented.h:257 [inline] put_bh include/linux/buffer_head.h:323 [inline] end_buffer_read_sync+0x5c/0x90 fs/buffer.c:161 end_bio_bh_io_sync+0xa9/0xf0 fs/buffer.c:2700 req_bio_endio block/blk-mq.c:795 [inline] blk_update_request+0x2ee/0x1180 block/blk-mq.c:927 blk_mq_end_request+0x46/0x70 block/blk-mq.c:1054 blk_complete_reqs+0xa0/0xd0 block/blk-mq.c:1132 __do_softirq+0x1d0/0x901 kernel/softirq.c:571 run_ksoftirqd kernel/softirq.c:939 [inline] run_ksoftirqd+0x2d/0x60 kernel/softirq.c:931 smpboot_thread_fn+0x548/0x8c0 kernel/smpboot.c:164 kthread+0x2e6/0x3c0 kernel/kthread.c:379 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 The buggy address belongs to the virtual mapping at [ffffc90003120000, ffffc90003129000) created by: kernel_clone+0xb8/0x5f0 kernel/fork.c:2774 The buggy address belongs to the physical page: page:ffffea00006c9980 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1b266 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 9293, tgid 9293 (syz-executor.0), ts 167609995080, free_ts 167606334666 prep_new_page mm/page_alloc.c:2553 [inline] get_page_from_freelist+0x1190/0x2e20 mm/page_alloc.c:4326 __alloc_pages+0x1c7/0x490 mm/page_alloc.c:5592 vm_area_alloc_pages mm/vmalloc.c:2957 [inline] __vmalloc_area_node mm/vmalloc.c:3033 [inline] __vmalloc_node_range+0x7fb/0x1060 mm/vmalloc.c:3205 alloc_thread_stack_node kernel/fork.c:311 [inline] dup_task_struct kernel/fork.c:982 [inline] copy_process+0x1110/0x6ba0 kernel/fork.c:2190 kernel_clone+0xb8/0x5f0 kernel/fork.c:2774 __do_sys_clone+0xa1/0xe0 kernel/fork.c:2917 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:1454 [inline] free_pcp_prepare+0x5c7/0xa30 mm/page_alloc.c:1504 free_unref_page_prepare mm/page_alloc.c:3388 [inline] free_unref_page_list+0x172/0xbc0 mm/page_alloc.c:3529 release_pages+0x31c/0x10c0 mm/swap.c:1042 __pagevec_release+0x59/0xb0 mm/swap.c:1062 pagevec_release include/linux/pagevec.h:63 [inline] folio_batch_release include/linux/pagevec.h:132 [inline] truncate_inode_pages_range+0x234/0xb60 mm/truncate.c:372 kill_bdev block/bdev.c:76 [inline] blkdev_flush_mapping+0x11a/0x260 block/bdev.c:584 blkdev_put_whole+0xa0/0xd0 block/bdev.c:615 blkdev_put+0x1bd/0x660 block/bdev.c:875 blkdev_close+0x5f/0x90 block/fops.c:507 __fput+0x1fa/0x9a0 fs/file_table.c:321 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+0x210/0x240 kernel/entry/common.c:204 __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline] syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:297 do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x63/0xcd Memory state around the buggy address: ffffc90003127880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc90003127900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc90003127980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc90003127a00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc90003127a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================