From: syzbot <syzbot+58ea3177ba8bd0a5d8ee@syzkaller.appspotmail.com>
To: airlied@gmail.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
syzkaller-bugs@googlegroups.com, tzimmermann@suse.de
Subject: [syzbot] memory leak in vma_node_allow
Date: Sun, 12 Feb 2023 16:25:50 -0800 [thread overview]
Message-ID: <000000000000a47fd205f489e34b@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 0983f6bf2bfc Merge tag 'devicetree-fixes-for-6.2-2' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=134dab4d480000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e55e71813900595
dashboard link: https://syzkaller.appspot.com/bug?extid=58ea3177ba8bd0a5d8ee
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15052a83480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13073cfb480000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dfe2e2ac7b39/disk-0983f6bf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bd09e355e210/vmlinux-0983f6bf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8409e5f10fab/bzImage-0983f6bf.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+58ea3177ba8bd0a5d8ee@syzkaller.appspotmail.com
Warning: Permanently added '10.128.1.168' (ECDSA) to the list of known hosts.
executing program
executing program
BUG: memory leak
unreferenced object 0xffff88810f1c75c0 (size 64):
comm "syz-executor750", pid 5060, jiffies 4294945258 (age 13.860s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 d6 e4 04 81 88 ff ff ................
backtrace:
[<ffffffff81508f84>] kmalloc_trace+0x24/0x90 mm/slab_common.c:1062
[<ffffffff82787cca>] kmalloc include/linux/slab.h:580 [inline]
[<ffffffff82787cca>] vma_node_allow+0x3a/0x150 drivers/gpu/drm/drm_vma_manager.c:255
[<ffffffff8276788e>] drm_gem_handle_create_tail+0x10e/0x250 drivers/gpu/drm/drm_gem.c:377
[<ffffffff8278ed4d>] drm_gem_shmem_create_with_handle drivers/gpu/drm/drm_gem_shmem_helper.c:432 [inline]
[<ffffffff8278ed4d>] drm_gem_shmem_dumb_create+0xbd/0x200 drivers/gpu/drm/drm_gem_shmem_helper.c:534
[<ffffffff82753a5b>] drm_mode_create_dumb+0x11b/0x150 drivers/gpu/drm/drm_dumb_buffers.c:96
[<ffffffff82768e28>] drm_ioctl_kernel+0x148/0x260 drivers/gpu/drm/drm_ioctl.c:788
[<ffffffff82769230>] drm_ioctl+0x2f0/0x500 drivers/gpu/drm/drm_ioctl.c:891
[<ffffffff81642600>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff81642600>] __do_sys_ioctl fs/ioctl.c:870 [inline]
[<ffffffff81642600>] __se_sys_ioctl fs/ioctl.c:856 [inline]
[<ffffffff81642600>] __x64_sys_ioctl+0x100/0x140 fs/ioctl.c:856
[<ffffffff8498c889>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff8498c889>] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
[<ffffffff84a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
BUG: memory leak
unreferenced object 0xffff888109662d80 (size 64):
comm "syz-executor750", pid 5060, jiffies 4294945258 (age 13.870s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 d6 e4 04 81 88 ff ff ................
backtrace:
[<ffffffff81508f84>] kmalloc_trace+0x24/0x90 mm/slab_common.c:1062
[<ffffffff82787cca>] kmalloc include/linux/slab.h:580 [inline]
[<ffffffff82787cca>] vma_node_allow+0x3a/0x150 drivers/gpu/drm/drm_vma_manager.c:255
[<ffffffff8276788e>] drm_gem_handle_create_tail+0x10e/0x250 drivers/gpu/drm/drm_gem.c:377
[<ffffffff8278ed4d>] drm_gem_shmem_create_with_handle drivers/gpu/drm/drm_gem_shmem_helper.c:432 [inline]
[<ffffffff8278ed4d>] drm_gem_shmem_dumb_create+0xbd/0x200 drivers/gpu/drm/drm_gem_shmem_helper.c:534
[<ffffffff82753a5b>] drm_mode_create_dumb+0x11b/0x150 drivers/gpu/drm/drm_dumb_buffers.c:96
[<ffffffff82768e28>] drm_ioctl_kernel+0x148/0x260 drivers/gpu/drm/drm_ioctl.c:788
[<ffffffff82769230>] drm_ioctl+0x2f0/0x500 drivers/gpu/drm/drm_ioctl.c:891
[<ffffffff81642600>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff81642600>] __do_sys_ioctl fs/ioctl.c:870 [inline]
[<ffffffff81642600>] __se_sys_ioctl fs/ioctl.c:856 [inline]
[<ffffffff81642600>] __x64_sys_ioctl+0x100/0x140 fs/ioctl.c:856
[<ffffffff8498c889>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff8498c889>] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
[<ffffffff84a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
BUG: memory leak
unreferenced object 0xffff888109662900 (size 64):
comm "syz-executor750", pid 5069, jiffies 4294945834 (age 8.110s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 ce 8f 09 81 88 ff ff ................
backtrace:
[<ffffffff81508f84>] kmalloc_trace+0x24/0x90 mm/slab_common.c:1062
[<ffffffff82787cca>] kmalloc include/linux/slab.h:580 [inline]
[<ffffffff82787cca>] vma_node_allow+0x3a/0x150 drivers/gpu/drm/drm_vma_manager.c:255
[<ffffffff8276788e>] drm_gem_handle_create_tail+0x10e/0x250 drivers/gpu/drm/drm_gem.c:377
[<ffffffff8278ed4d>] drm_gem_shmem_create_with_handle drivers/gpu/drm/drm_gem_shmem_helper.c:432 [inline]
[<ffffffff8278ed4d>] drm_gem_shmem_dumb_create+0xbd/0x200 drivers/gpu/drm/drm_gem_shmem_helper.c:534
[<ffffffff82753a5b>] drm_mode_create_dumb+0x11b/0x150 drivers/gpu/drm/drm_dumb_buffers.c:96
[<ffffffff82768e28>] drm_ioctl_kernel+0x148/0x260 drivers/gpu/drm/drm_ioctl.c:788
[<ffffffff82769230>] drm_ioctl+0x2f0/0x500 drivers/gpu/drm/drm_ioctl.c:891
[<ffffffff81642600>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff81642600>] __do_sys_ioctl fs/ioctl.c:870 [inline]
[<ffffffff81642600>] __se_sys_ioctl fs/ioctl.c:856 [inline]
[<ffffffff81642600>] __x64_sys_ioctl+0x100/0x140 fs/ioctl.c:856
[<ffffffff8498c889>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff8498c889>] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
[<ffffffff84a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
BUG: memory leak
unreferenced object 0xffff888109662940 (size 64):
comm "syz-executor750", pid 5069, jiffies 4294945834 (age 8.110s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 ce 8f 09 81 88 ff ff ................
backtrace:
[<ffffffff81508f84>] kmalloc_trace+0x24/0x90 mm/slab_common.c:1062
[<ffffffff82787cca>] kmalloc include/linux/slab.h:580 [inline]
[<ffffffff82787cca>] vma_node_allow+0x3a/0x150 drivers/gpu/drm/drm_vma_manager.c:255
[<ffffffff8276788e>] drm_gem_handle_create_tail+0x10e/0x250 drivers/gpu/drm/drm_gem.c:377
[<ffffffff8278ed4d>] drm_gem_shmem_create_with_handle drivers/gpu/drm/drm_gem_shmem_helper.c:432 [inline]
[<ffffffff8278ed4d>] drm_gem_shmem_dumb_create+0xbd/0x200 drivers/gpu/drm/drm_gem_shmem_helper.c:534
[<ffffffff82753a5b>] drm_mode_create_dumb+0x11b/0x150 drivers/gpu/drm/drm_dumb_buffers.c:96
[<ffffffff82768e28>] drm_ioctl_kernel+0x148/0x260 drivers/gpu/drm/drm_ioctl.c:788
[<ffffffff82769230>] drm_ioctl+0x2f0/0x500 drivers/gpu/drm/drm_ioctl.c:891
[<ffffffff81642600>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff81642600>] __do_sys_ioctl fs/ioctl.c:870 [inline]
[<ffffffff81642600>] __se_sys_ioctl fs/ioctl.c:856 [inline]
[<ffffffff81642600>] __x64_sys_ioctl+0x100/0x140 fs/ioctl.c:856
[<ffffffff8498c889>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff8498c889>] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
[<ffffffff84a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
---
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@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2023-02-13 0:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000a47fd205f489e34b@google.com \
--to=syzbot+58ea3177ba8bd0a5d8ee@syzkaller.appspotmail.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.