From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109389] memory leak in `amdgpu_bo_create()`
Date: Fri, 18 Jan 2019 21:11:33 +0000 [thread overview]
Message-ID: <bug-109389-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2964 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109389
Bug ID: 109389
Summary: memory leak in `amdgpu_bo_create()`
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: pmenzel+bugs.freedesktop.org@molgen.mpg.de
Created attachment 143156
--> https://bugs.freedesktop.org/attachment.cgi?id=143156&action=edit
Output of kmemleak
With Linux 5.0-rc2+ the memory leaks below are reported by kmemleak.
```
unreferenced object 0xffff9f83850c5000 (size 2048):
comm "gnome-shell", pid 569, jiffies 4294682217 (age 9133.583s)
hex dump (first 32 bytes):
02 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 ................
02 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<000000001aec1dd8>] amdgpu_bo_create+0x40/0x220 [amdgpu]
[<000000007da39c30>] amdgpu_gem_object_create+0x9e/0x120 [amdgpu]
[<00000000099484e9>] amdgpu_gem_create_ioctl+0x1d3/0x290 [amdgpu]
[<000000009d8251d3>] drm_ioctl_kernel+0xa9/0xf0
[<0000000050b61811>] drm_ioctl+0x201/0x3a0
[<000000007c88aae3>] amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
[<0000000083291747>] do_vfs_ioctl+0xa4/0x630
[<00000000722b6176>] ksys_ioctl+0x60/0x90
[<000000001bfa30dc>] __x64_sys_ioctl+0x16/0x20
[<000000007862c966>] do_syscall_64+0x55/0x170
[<00000000a8eeee88>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[<000000001242345f>] 0xffffffffffffffff
unreferenced object 0xffff9f837cdd36c0 (size 64):
comm "gnome-shell", pid 569, jiffies 4294682217 (age 9133.583s)
hex dump (first 32 bytes):
d4 23 b4 d5 ab e2 45 94 d0 53 43 86 83 9f ff ff .#....E..SC.....
01 00 00 00 04 00 00 00 60 ab cc 5c 83 9f ff ff ........`..\....
backtrace:
[<000000000768e015>] ttm_bo_mem_space+0x41/0x4a0
[<00000000f11076b2>] ttm_bo_validate+0xc7/0x130
[<00000000c820992e>] ttm_bo_init_reserved+0x32f/0x390
[<00000000fcfd5ce2>] amdgpu_bo_do_create+0x1ed/0x420 [amdgpu]
[<000000001aec1dd8>] amdgpu_bo_create+0x40/0x220 [amdgpu]
[<000000007da39c30>] amdgpu_gem_object_create+0x9e/0x120 [amdgpu]
[<00000000099484e9>] amdgpu_gem_create_ioctl+0x1d3/0x290 [amdgpu]
[<000000009d8251d3>] drm_ioctl_kernel+0xa9/0xf0
[<0000000050b61811>] drm_ioctl+0x201/0x3a0
[<000000007c88aae3>] amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
[<0000000083291747>] do_vfs_ioctl+0xa4/0x630
[<00000000722b6176>] ksys_ioctl+0x60/0x90
[<000000001bfa30dc>] __x64_sys_ioctl+0x16/0x20
[<000000007862c966>] do_syscall_64+0x55/0x170
[<00000000a8eeee88>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[<000000001242345f>] 0xffffffffffffffff
```
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4563 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-01-18 21:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 21:11 bugzilla-daemon [this message]
2019-01-18 21:13 ` [Bug 109389] memory leak in `amdgpu_bo_create()` bugzilla-daemon
2019-01-19 1:16 ` bugzilla-daemon
2019-01-25 16:19 ` bugzilla-daemon
2019-02-12 15:05 ` bugzilla-daemon
2019-09-03 20:41 ` bugzilla-daemon
2019-09-03 20:49 ` bugzilla-daemon
2019-09-03 20:52 ` bugzilla-daemon
2019-09-03 21:31 ` bugzilla-daemon
2019-09-06 21:14 ` bugzilla-daemon
2019-09-06 21:16 ` bugzilla-daemon
2019-10-15 18:33 ` bugzilla-daemon
2019-11-19 9:11 ` bugzilla-daemon
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=bug-109389-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox