From: Daniel Vetter <daniel@ffwll.ch>
To: Christoph Jaeger <christophjaeger@linux.com>
Cc: daniel.vetter@ffwll.ch, jani.nikula@linux.intel.com,
airlied@linux.ie, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Fix memory leak in intel_dsi_init() error path
Date: Fri, 13 Jun 2014 22:09:05 +0200 [thread overview]
Message-ID: <20140613200904.GX5821@phenom.ffwll.local> (raw)
In-Reply-To: <1402689082-20211-1-git-send-email-christophjaeger@linux.com>
On Fri, Jun 13, 2014 at 09:51:22PM +0200, Christoph Jaeger wrote:
> intel_dsi_init() bails out without freeing the memory 'intel_dsi' and
> 'intel_connector' point to. Simply bail out before allocating memory.
>
> Picked up by Coverity - CID 1222750.
>
> Signed-off-by: Christoph Jaeger <christophjaeger@linux.com>
Queued for -next, thanks for the patch. I've had to rebase the patch a
bit to resolve conflicts. Imo also not for -fixes because of this conflict
potential, so will land in 3.17.
-Daniel
> ---
> drivers/gpu/drm/i915/intel_dsi.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dsi.c b/drivers/gpu/drm/i915/intel_dsi.c
> index 02f99d7..6965627 100644
> --- a/drivers/gpu/drm/i915/intel_dsi.c
> +++ b/drivers/gpu/drm/i915/intel_dsi.c
> @@ -675,6 +675,13 @@ bool intel_dsi_init(struct drm_device *dev)
> if (!dev_priv->vbt.has_mipi)
> return false;
>
> + if (IS_VALLEYVIEW(dev)) {
> + dev_priv->mipi_mmio_base = VLV_MIPI_BASE;
> + } else {
> + DRM_ERROR("Unsupported Mipi device to reg base");
> + return false;
> + }
> +
> intel_dsi = kzalloc(sizeof(*intel_dsi), GFP_KERNEL);
> if (!intel_dsi)
> return false;
> @@ -689,13 +696,6 @@ bool intel_dsi_init(struct drm_device *dev)
> encoder = &intel_encoder->base;
> intel_dsi->attached_connector = intel_connector;
>
> - if (IS_VALLEYVIEW(dev)) {
> - dev_priv->mipi_mmio_base = VLV_MIPI_BASE;
> - } else {
> - DRM_ERROR("Unsupported Mipi device to reg base");
> - return false;
> - }
> -
> connector = &intel_connector->base;
>
> drm_encoder_init(dev, encoder, &intel_dsi_funcs, DRM_MODE_ENCODER_DSI);
> --
> 1.9.3
>
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-06-13 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 19:51 Christoph Jaeger
2014-06-13 20:09 ` Daniel Vetter [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=20140613200904.GX5821@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=christophjaeger@linux.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®