From: Dave Airlie <airlied@gmail.com>
To: Wang YanQing <udknight@gmail.com>, Dave Airlie <airlied@linux.ie>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 0/5] drm: fix resources leak in error handle code path
Date: Wed, 6 Nov 2013 13:45:31 +1000 [thread overview]
Message-ID: <CAPM=9tzgqeOcBLg__3+TriAcR1Yx7QKOJLEboRMvsoGmrS5bYg@mail.gmail.com> (raw)
In-Reply-To: <20131030230414.GA4064@udknight>
On Thu, Oct 31, 2013 at 9:04 AM, Wang YanQing <udknight@gmail.com> wrote:
> This series patches fix resource leak
> issue in error handle code path I meet
> with drm, vmalloc leak, etc.
Daniel this seems to cross over a bit with your cleanups,
I also am not sure that the drm_cleanup_in_dev isn't going to cause
issues as it reorders the unload operation with respect to other
operations, and I wonder if legacy drivers might start crashing in
this situation.
Dave.
next prev parent reply other threads:[~2013-11-06 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 23:04 [PATCH 0/5] drm: fix resources leak in error handle code path Wang YanQing
2013-11-06 3:45 ` Dave Airlie [this message]
2013-11-06 10:16 ` Daniel Vetter
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='CAPM=9tzgqeOcBLg__3+TriAcR1Yx7QKOJLEboRMvsoGmrS5bYg@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=udknight@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;
as well as URLs for NNTP newsgroup(s).