Hello,
syzbot found the following issue on:
HEAD commit: 4878aadf2d15 Linux 5.15.161
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=10830671980000
kernel config:
https://syzkaller.appspot.com/x/.config?x=875d98826c53bf16
dashboard link:
https://syzkaller.appspot.com/bug?extid=f26744b52ab87f2864e3
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/f227a150ea92/disk-4878aadf.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/6cfc50bf8b4e/vmlinux-4878aadf.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/23f7adc3c761/bzImage-4878aadf.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+f26744...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3849 at mm/page_alloc.c:5398 __alloc_pages+0x5cf/0x700
Modules linked in:
CPU: 1 PID: 3849 Comm: syz.3.96 Not tainted 5.15.161-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:__alloc_pages+0x5cf/0x700 mm/page_alloc.c:5398
Code: 00 48 ba 00 00 00 00 00 fc ff df e9 1d fd ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 2e fd ff ff e8 16 40 0a 00 e9 24 fd ff ff <0f> 0b 45 31 e4 e9 70 fd ff ff 48 8d 4c 24 50 80 e1 07 80 c1 03 38
RSP: 0018:ffffc90002ff78a0 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: 000000000000000b RCX: 0000000000000000
RDX: 0000000000000028 RSI: 0000000000000000 RDI: ffffc90002ff7928
RBP: ffffc90002ff79b8 R08: dffffc0000000000 R09: ffffc90002ff7900
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000040dc0
R13: 1ffff920005fef1c R14: ffffc90002ff7900 R15: 1ffff920005fef18
FS: 00007f32a329f6c0(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2eeefff8 CR3: 0000000019adc000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
kmalloc_order+0x41/0x150 mm/slab_common.c:966
kmalloc_order_trace+0x15/0xe0 mm/slab_common.c:982
kmalloc_large include/linux/slab.h:520 [inline]
__kmalloc+0x214/0x300 mm/slub.c:4396
kmalloc_array include/linux/slab.h:631 [inline]
kcalloc include/linux/slab.h:660 [inline]
fill_object_idr drivers/gpu/drm/drm_lease.c:386 [inline]
drm_mode_create_lease_ioctl+0x3f9/0x1120 drivers/gpu/drm/drm_lease.c:523
drm_ioctl_kernel+0x345/0x4f0 drivers/gpu/drm/drm_ioctl.c:801
drm_ioctl+0x60d/0x9d0 drivers/gpu/drm/drm_ioctl.c:904
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f32a481eb99
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f32a329f048 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f32a49acfa0 RCX: 00007f32a481eb99
RDX: 0000000020000040 RSI: 00000000c01864c6 RDI: 0000000000000003
RBP: 00007f32a489f77e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f32a49acfa0 R15: 00007ffdaf2cced8
</TASK>
---
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
syzk...@googlegroups.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 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