Hello, syzbot found the following issue on:
HEAD commit: 6bda50f4333f Merge tag 'mips-fixes_6.18_2' of git://git.ke.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=17ab8512580000 kernel config: https://syzkaller.appspot.com/x/.config?x=f30cc590c4f6da44 dashboard link: https://syzkaller.appspot.com/bug?extid=3fc9eecaf97147282c87 compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14447cb4580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1094d508580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/864951cecf67/disk-6bda50f4.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/4692a21b76e7/vmlinux-6bda50f4.xz kernel image: https://storage.googleapis.com/syzbot-assets/a2898beb8301/bzImage-6bda50f4.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: [email protected] BUG: memory leak unreferenced object 0xffff888125711880 (size 128): comm "syz.0.18", pid 6089, jiffies 4294942955 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc f5a89fc0): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4983 [inline] slab_alloc_node mm/slub.c:5288 [inline] __kmalloc_cache_noprof+0x3a6/0x5b0 mm/slub.c:5766 kmalloc_noprof include/linux/slab.h:957 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] create_vblank_event drivers/gpu/drm/drm_atomic_uapi.c:931 [inline] prepare_signaling drivers/gpu/drm/drm_atomic_uapi.c:1221 [inline] drm_mode_atomic_ioctl+0x924/0x13d0 drivers/gpu/drm/drm_atomic_uapi.c:1529 drm_ioctl_kernel+0x125/0x1f0 drivers/gpu/drm/drm_ioctl.c:797 drm_ioctl+0x371/0x6b0 drivers/gpu/drm/drm_ioctl.c:894 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f BUG: memory leak unreferenced object 0xffff888125711780 (size 128): comm "syz.0.19", pid 6092, jiffies 4294942957 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc f5a89fc0): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4983 [inline] slab_alloc_node mm/slub.c:5288 [inline] __kmalloc_cache_noprof+0x3a6/0x5b0 mm/slub.c:5766 kmalloc_noprof include/linux/slab.h:957 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] create_vblank_event drivers/gpu/drm/drm_atomic_uapi.c:931 [inline] prepare_signaling drivers/gpu/drm/drm_atomic_uapi.c:1221 [inline] drm_mode_atomic_ioctl+0x924/0x13d0 drivers/gpu/drm/drm_atomic_uapi.c:1529 drm_ioctl_kernel+0x125/0x1f0 drivers/gpu/drm/drm_ioctl.c:797 drm_ioctl+0x371/0x6b0 drivers/gpu/drm/drm_ioctl.c:894 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f BUG: memory leak unreferenced object 0xffff888125711700 (size 128): comm "syz.0.20", pid 6121, jiffies 4294943534 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc f5a89fc0): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4983 [inline] slab_alloc_node mm/slub.c:5288 [inline] __kmalloc_cache_noprof+0x3a6/0x5b0 mm/slub.c:5766 kmalloc_noprof include/linux/slab.h:957 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] create_vblank_event drivers/gpu/drm/drm_atomic_uapi.c:931 [inline] prepare_signaling drivers/gpu/drm/drm_atomic_uapi.c:1221 [inline] drm_mode_atomic_ioctl+0x924/0x13d0 drivers/gpu/drm/drm_atomic_uapi.c:1529 drm_ioctl_kernel+0x125/0x1f0 drivers/gpu/drm/drm_ioctl.c:797 drm_ioctl+0x371/0x6b0 drivers/gpu/drm/drm_ioctl.c:894 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f BUG: memory leak unreferenced object 0xffff8881266fab80 (size 128): comm "syz.0.21", pid 6122, jiffies 4294943536 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc f5a89fc0): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4983 [inline] slab_alloc_node mm/slub.c:5288 [inline] __kmalloc_cache_noprof+0x3a6/0x5b0 mm/slub.c:5766 kmalloc_noprof include/linux/slab.h:957 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] create_vblank_event drivers/gpu/drm/drm_atomic_uapi.c:931 [inline] prepare_signaling drivers/gpu/drm/drm_atomic_uapi.c:1221 [inline] drm_mode_atomic_ioctl+0x924/0x13d0 drivers/gpu/drm/drm_atomic_uapi.c:1529 drm_ioctl_kernel+0x125/0x1f0 drivers/gpu/drm/drm_ioctl.c:797 drm_ioctl+0x371/0x6b0 drivers/gpu/drm/drm_ioctl.c:894 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF --- 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 [email protected]. 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 syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. 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
