From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Ben Skeggs <bskeggs@redhat.com>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: drm/nouveau/core/memory: kmemleak 684 new suspected memory leaks
Date: Fri, 17 May 2019 16:35:05 +0900 [thread overview]
Message-ID: <20190517073505.GA7102@jagdpanzerIV> (raw)
In-Reply-To: <20190517072737.GA651@jagdpanzerIV>
On (05/17/19 16:27), Sergey Senozhatsky wrote:
> > ... but most likely it's utterly wrong.
> >
>
> JFI, I removed kmemleak annotation
meeehhh....
kmemleak: 2046 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
unreferenced object 0xffff95cbea4e6060 (size 16):
comm "Web Content", pid 1191, jiffies 4294795669 (age 735.950s)
hex dump (first 16 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<00000000d0781ea4>] nvkm_memory_tags_get+0x8e/0x130
[<00000000061f3c89>] gf100_vmm_valid+0x196/0x2f0
[<00000000d79084b7>] nvkm_vmm_map+0xa8/0x360
[<00000000e3174e33>] nvkm_vram_map+0x48/0x50
[<00000000006adddb>] nvkm_uvmm_mthd+0x658/0x770
[<00000000b36f3a8b>] nvkm_ioctl+0xdf/0x177
[<0000000003acea2c>] nvif_object_mthd+0xd4/0x100
[<0000000033824292>] nvif_vmm_map+0xeb/0x100
[<00000000537f8629>] nouveau_mem_map+0x79/0xd0
[<00000000c3b20b73>] nouveau_vma_new+0x19d/0x1c0
[<00000000dc91383f>] nouveau_gem_object_open+0xd4/0x140
[<000000005a53123b>] drm_gem_handle_create_tail+0xe3/0x160
[<00000000e733f5a8>] nouveau_gem_ioctl_new+0x6e/0xd0
[<00000000b5bebef5>] drm_ioctl_kernel+0x8c/0xd0
[<000000004f28d8a6>] drm_ioctl+0x1c4/0x360
[<00000000b08b5723>] nouveau_drm_ioctl+0x63/0xb0
-ss
prev parent reply other threads:[~2019-05-17 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 6:13 drm/nouveau/core/memory: kmemleak 684 new suspected memory leaks Sergey Senozhatsky
2019-05-17 6:31 ` Sergey Senozhatsky
2019-05-17 6:45 ` Sergey Senozhatsky
2019-05-17 7:27 ` Sergey Senozhatsky
2019-05-17 7:35 ` Sergey Senozhatsky [this message]
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=20190517073505.GA7102@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=sergey.senozhatsky@gmail.com \
/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