| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <000000000000615c23061bd15fc4@google.com> Date: Wed, 26 Jun 2024 14:05:22 -0700 From: syzbot <syzbot+6754751ad05524dae739@...kaller.appspotmail.com> To: airlied@...il.com, daniel@...ll.ch, dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org, maarten.lankhorst@...ux.intel.com, mripard@...nel.org, syzkaller-bugs@...glegroups.com, tzimmermann@...e.de Subject: [syzbot] [dri?] WARNING in drm_mode_create_lease_ioctl Hello, syzbot found the following issue on: HEAD commit: ac2193b4b460 Merge branches 'for-next/misc', 'for-next/kse.. git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci console output: https://syzkaller.appspot.com/x/log.txt?x=101cc882980000 kernel config: https://syzkaller.appspot.com/x/.config?x=36900d37ec67d13f dashboard link: https://syzkaller.appspot.com/bug?extid=6754751ad05524dae739 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: arm64 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16c17cd6980000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15879c82980000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/2c4f87d36ca3/disk-ac2193b4.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/8410475de662/vmlinux-ac2193b4.xz kernel image: https://storage.googleapis.com/syzbot-assets/495a4ced254d/Image-ac2193b4.gz.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+6754751ad05524dae739@...kaller.appspotmail.com ------------[ cut here ]------------ WARNING: CPU: 0 PID: 6281 at mm/page_alloc.c:4654 __alloc_pages_noprof+0x324/0x6c0 mm/page_alloc.c:4654 Modules linked in: CPU: 0 PID: 6281 Comm: syz-executor181 Tainted: G W 6.10.0-rc3-syzkaller-gac2193b4b460 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __alloc_pages_noprof+0x324/0x6c0 mm/page_alloc.c:4654 lr : __alloc_pages_noprof+0xc8/0x6c0 mm/page_alloc.c:4648 sp : ffff800099017600 x29: ffff8000990176f0 x28: ffff800099017620 x27: dfff800000000000 x26: ffff700013202ec4 x25: 0000000000000000 x24: ffff800099017640 x23: 0000000000000000 x22: 0000000000040dc0 x21: 1ffff00013202ec8 x20: ffff800099017660 x19: 000000000000000b x18: ffff8000990176e0 x17: 000000000000c88a x16: ffff80008afa5980 x15: 0000000000000005 x14: 1ffff00013202ecc x13: 0000000000000000 x12: 0000000000000000 x11: ffff700013202ed1 x10: 1ffff00013202ed0 x9 : 0000000000000001 x8 : ffff80009232a000 x7 : 0000000000000000 x6 : ffff0000e07d0900 x5 : ffff0000e07d0900 x4 : 0000000000000000 x3 : 0000000000000020 x2 : 0000000000000008 x1 : 0000000000000000 x0 : ffff800099017660 Call trace: __alloc_pages_noprof+0x324/0x6c0 mm/page_alloc.c:4654 __alloc_pages_node_noprof include/linux/gfp.h:269 [inline] alloc_pages_node_noprof include/linux/gfp.h:296 [inline] __kmalloc_large_node+0xbc/0x200 mm/slub.c:4067 __do_kmalloc_node mm/slub.c:4110 [inline] __kmalloc_noprof+0x360/0x494 mm/slub.c:4135 kmalloc_noprof include/linux/slab.h:664 [inline] kmalloc_array_noprof include/linux/slab.h:699 [inline] fill_object_idr drivers/gpu/drm/drm_lease.c:389 [inline] drm_mode_create_lease_ioctl+0x4b0/0x17e4 drivers/gpu/drm/drm_lease.c:522 drm_ioctl_kernel+0x26c/0x368 drivers/gpu/drm/drm_ioctl.c:744 drm_ioctl+0x5e4/0xae4 drivers/gpu/drm/drm_ioctl.c:841 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl fs/ioctl.c:893 [inline] __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:893 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:133 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:152 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 irq event stamp: 14766 hardirqs last enabled at (14765): [<ffff80008b0693e8>] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:85 [inline] hardirqs last enabled at (14765): [<ffff80008b0693e8>] exit_to_kernel_mode+0xdc/0x10c arch/arm64/kernel/entry-common.c:95 hardirqs last disabled at (14766): [<ffff80008b066ee4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:470 softirqs last enabled at (8860): [<ffff8000801ea3cc>] softirq_handle_end kernel/softirq.c:400 [inline] softirqs last enabled at (8860): [<ffff8000801ea3cc>] handle_softirqs+0xa3c/0xbfc kernel/softirq.c:582 softirqs last disabled at (8855): [<ffff800080020de8>] __do_softirq+0x14/0x20 kernel/softirq.c:588 ---[ end trace 0000000000000000 ]--- --- 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 syzkaller@...glegroups.com. 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
Powered by blists - more mailing lists