From: Markus Elfring <Markus.Elfring@web•de>
To: Navid Emamdoost <navid.emamdoost@gmail•com>,
dri-devel@lists•freedesktop.org, kernel@pengutronix•de,
linux-arm-kernel@lists•infradead.org, linux-imx@nxp•com
Cc: kernel-janitors@vger•kernel.org,
Philipp Zabel <p.zabel@pengutronix•de>,
David Airlie <airlied@linux•ie>, Shawn Guo <shawnguo@kernel•org>,
Sascha Hauer <s.hauer@pengutronix•de>, Kangjie Lu <kjlu@umn•edu>,
LKML <linux-kernel@vger•kernel.org>,
Navid Emamdoost <emamd001@umn•edu>,
Daniel Vetter <daniel@ffwll•ch>,
Stephen McCamant <smccaman@umn•edu>,
Fabio Estevam <festevam@gmail•com>
Subject: Re: drm/imx: Checking a kmemdup() call in imx_pd_bind()
Date: Sun, 6 Oct 2019 11:33:21 +0200 [thread overview]
Message-ID: <540321eb-7699-1d51-59d5-dde5ffcb8fc4@web.de> (raw)
In-Reply-To: <20191004190938.15353-1-navid.emamdoost@gmail.com>
I have taken another look also at the implementation of the function “imx_pd_bind”.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/imx/parallel-display.c?id=43b815c6a8e7dbccb5b8bd9c4b099c24bc22d135#n197
https://elixir.bootlin.com/linux/v5.4-rc1/source/drivers/gpu/drm/imx/parallel-display.c#L197
Now I find an unchecked call of the function “kmemdup” suspicious.
Will this detail trigger further software development considerations?
Regards,
Markus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-06 9:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 19:09 [PATCH] drm/imx: fix memory leak in imx_pd_bind Navid Emamdoost
2019-10-05 15:02 ` Markus Elfring
2019-10-12 11:54 ` Markus Elfring
2019-10-12 19:22 ` Navid Emamdoost
2019-10-06 9:33 ` Markus Elfring [this message]
2019-10-07 4:26 ` drm/imx: Checking a kmemdup() call in imx_pd_bind() Navid Emamdoost
2019-10-07 7:44 ` Markus Elfring
2019-10-12 9:04 ` [PATCH 0/2] drm/imx: Adjustments for two functions Markus Elfring
2019-10-12 9:07 ` [PATCH 1/2] drm/imx: Fix error handling for a kmemdup() call in imx_pd_bind() Markus Elfring
2019-10-12 19:16 ` Navid Emamdoost
2019-10-12 19:24 ` Julia Lawall
2019-10-12 9:10 ` [PATCH 2/2] drm/imx: Fix error handling for a kmemdup() call in imx_ldb_panel_ddc() Markus Elfring
2019-11-21 18:31 ` [PATCH] drm/imx: fix memory leak in imx_pd_bind Navid Emamdoost
2019-11-22 7:22 ` Marco Felsch
2019-11-22 17:43 ` Navid Emamdoost
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=540321eb-7699-1d51-59d5-dde5ffcb8fc4@web.de \
--to=markus.elfring@web$(echo .)de \
--cc=airlied@linux$(echo .)ie \
--cc=daniel@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=emamd001@umn$(echo .)edu \
--cc=festevam@gmail$(echo .)com \
--cc=kernel-janitors@vger$(echo .)kernel.org \
--cc=kernel@pengutronix$(echo .)de \
--cc=kjlu@umn$(echo .)edu \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-imx@nxp$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=navid.emamdoost@gmail$(echo .)com \
--cc=p.zabel@pengutronix$(echo .)de \
--cc=s.hauer@pengutronix$(echo .)de \
--cc=shawnguo@kernel$(echo .)org \
--cc=smccaman@umn$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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