From: Linus Torvalds <torvalds@linux-foundation.org>
To: rong.a.chen@intel.com
Cc: peter@lekensteyn.nl, kraxel@redhat.com,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [LKP] [bochs] df2052cc92: WARNING:at_drivers/gpu/drm/drm_mode_config.c:#drm_mode_config_cleanup
Date: Fri, 21 Dec 2018 11:25:41 -0800 [thread overview]
Message-ID: <CAHk-=whM09ZxdrrN-o3k1JOAn0keF5aXtPAcEYiukn7kW7yp2g@mail.gmail.com> (raw)
In-Reply-To: <20181221083226.GI23332@shao2-debian>
On Fri, Dec 21, 2018 at 12:32 AM kernel test robot
<rong.a.chen@intel.com> wrote:
>
> FYI, we noticed commit df2052cc9221 ("bochs: convert to
> drm_fb_helper_fbdev_setup/teardown") caused
>
> [ 487.591733] WARNING: CPU: 0 PID: 1 at drivers/gpu/drm/drm_mode_config.c:478 drm_mode_config_cleanup+0x270/0x290
Ok, this is apparently just a leak for what appears to be a not
particularly interesting error case, but the warning is new to 4.20
(*) so it would be nice to have somebody look at it.
That commit is supposed to fix a leak, but there's apparently
something still there.
Daniel, Peter, Gerd?
Linus
(*) the *problem* is probably not new, it's just now exposed by the
switch to drm_mode_config_cleanup().
next prev parent reply other threads:[~2018-12-21 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 8:32 [LKP] [bochs] df2052cc92: WARNING:at_drivers/gpu/drm/drm_mode_config.c:#drm_mode_config_cleanup kernel test robot
2018-12-21 19:25 ` Linus Torvalds [this message]
2018-12-23 0:43 ` Peter Wu
2018-12-23 0:55 ` [PATCH] drm/fb-helper: fix leaks in error path of drm_fb_helper_fbdev_setup Peter Wu
2018-12-23 13:55 ` Noralf Trønnes
2018-12-23 23:10 ` Peter Wu
2018-12-24 14:52 ` Noralf Trønnes
2018-12-24 15:03 ` Peter Wu
2019-01-05 18:25 ` Noralf Trønnes
2019-01-08 17:55 ` Noralf Trønnes
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='CAHk-=whM09ZxdrrN-o3k1JOAn0keF5aXtPAcEYiukn7kW7yp2g@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=peter@lekensteyn.nl \
--cc=rong.a.chen@intel.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;
as well as URLs for NNTP newsgroup(s).