All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: possible IO map leak in drm/gem
Date: Thu, 21 Jan 2021 15:47:59 +0100	[thread overview]
Message-ID: <86bd5aff-ca8a-517f-1474-1be1d26255ae@suse.de> (raw)
In-Reply-To: <632F0FCB-8719-4E8B-B35A-DC0A2DF49369@oracle.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2142 bytes --]

(cc'ing dri-devel)

Hi,

thanks for reporting the bug.

Am 21.01.21 um 15:35 schrieb Chuck Lever:
> Hi Thomas-
> 
> I was not able to find an appropriate mailing list entry in MAINTAINERS,

That would be dri-devel@lists.freedesktop.org

> so I'm mailing you directly as committer of record for:
> 
> 43676605f890 ("drm/ttm: Add vmap/vunmap to TTM and TTM GEM helpers")
> 
> I've noticed that since putting v5.11-rc on my test systems, overnight
> on an otherwise idle system the load average seems to grow as the result
> of a kernel worker thread.

Earlier this week I fixed a couple of leaks in that code. Could you 
please apply the patch at [1] and report back if it fixes the issue.

If it's a separate problem, I'll take a closer look.

Best regards
Thomas

[1] 
https://lore.kernel.org/dri-devel/20210118144639.27307-1-tzimmermann@suse.de/

> 
> I used "perf top" to see what it had gotten up to, and it appears that
> it was spending lots of time walking an interval tree on behalf of
> memtype_reserve().
> 
> The most frequently-observed stack trace seems to be:
> 
>       kworker/3:1-2355  [003] 60950.150928: function:             memtype_reserve
>       kworker/3:1-2355  [003] 60950.150942: kernel_stack:         <stack trace>
> => ffffffffc0c66083
> => memtype_reserve (ffffffffa005f9d5)
> => __ioremap_caller (ffffffffa005aac1)
> => ttm_bo_vmap (ffffffffc040f266)
> => drm_gem_vram_vmap (ffffffffc042c5cd)
> => drm_gem_vmap (ffffffffc0506a7f)
> => drm_client_buffer_vmap (ffffffffc0523741)
> => drm_fb_helper_damage_work (ffffffffc049a34a)
> => process_one_work (ffffffffa00dd92e)
> => worker_thread (ffffffffa00dde46)
> => kthread (ffffffffa00e22c4)
> => ret_from_fork (ffffffffa0004192)
> 
> I see a regular call to memtype_reserve(), but never a matching call to
> memtype_free(), thus I suspect a leak of I/O maps in this code.
> 
> --
> Chuck Lever
> 
> 
> 

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 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

       reply	other threads:[~2021-01-21 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <632F0FCB-8719-4E8B-B35A-DC0A2DF49369@oracle.com>
2021-01-21 14:47 ` Thomas Zimmermann [this message]
2021-01-21 15:05   ` possible IO map leak in drm/gem Chuck Lever
2021-01-22 14:27     ` Chuck Lever
2021-01-22 14:46       ` Thomas Zimmermann

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=86bd5aff-ca8a-517f-1474-1be1d26255ae@suse.de \
    --to=tzimmermann@suse.de \
    --cc=chuck.lever@oracle.com \
    --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 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.