From: Andi Shyti <andi.shyti@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: Inki Dae <inki.dae@samsung.com>,
dri-devel@lists.freedesktop.org,
linux-samsung-soc@vger.kernel.org,
Andi Shyti <andi.shyti@kernel.org>
Subject: Re: [PATCH] drm/exynos: vidi: fix a wrong error return
Date: Fri, 19 May 2023 04:37:01 +0200 [thread overview]
Message-ID: <ZGbgza6w6taNIXAl@ashyti-mobl2.lan> (raw)
In-Reply-To: <ZGbCO9/5yEstym+c@ashyti-mobl2.lan>
Hi Inki,
On Fri, May 19, 2023 at 02:26:40AM +0200, Andi Shyti wrote:
> Hi Inki,
>
> On Fri, May 19, 2023 at 09:04:07AM +0900, Inki Dae wrote:
> > Fix a wrong error return by dropping an error return.
> >
> > When vidi driver is remvoed, if ctx->raw_edid isn't same as fake_edid_info
> > then only what we have to is to free ctx->raw_edid so that driver removing
> > can work correctly - it's not an error case.
> >
> > Signed-off-by: Inki Dae <inki.dae@samsung.com>
> > ---
> > drivers/gpu/drm/exynos/exynos_drm_vidi.c | 2 --
> > 1 file changed, 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/exynos/exynos_drm_vidi.c b/drivers/gpu/drm/exynos/exynos_drm_vidi.c
> > index 4d56c8c799c5..f5e1adfcaa51 100644
> > --- a/drivers/gpu/drm/exynos/exynos_drm_vidi.c
> > +++ b/drivers/gpu/drm/exynos/exynos_drm_vidi.c
> > @@ -469,8 +469,6 @@ static int vidi_remove(struct platform_device *pdev)
> > if (ctx->raw_edid != (struct edid *)fake_edid_info) {
> > kfree(ctx->raw_edid);
> > ctx->raw_edid = NULL;
> > -
> > - return -EINVAL;
>
> It doesn't look right to me, I think the correct patch should be:
>
> - if (ctx->raw_edid != (struct edid *)fake_edid_info) {
> - kfree(ctx->raw_edid);
> - ctx->raw_edid = NULL;
> -
> - return -EINVAL;
> - }
> -
> + ctx->raw_edid = NULL;
>
> because "ctx->raw_edid" points to a non allocated memory in the
> .data segment and you cannot free it.
>
> A follow-up cleanup should be to remove the "const" from
> fake_edid_info because you are assigning its address to pointers
> (raw_edid), so that what's the point for having it const? You are
> just fooling the compiler :)
please ignore, this is what happens when reading patches at
2.26am, that a "!=" becomes "==". The patch is correct, still
some cleanups is needed here, though.
Reviewed-by: Andi Shyti <andi.shyti@kernel.org>
Andi
PS I was actually sleeping and this woke me up :)
> Andi
>
> > }
> >
> > component_del(&pdev->dev, &vidi_component_ops);
> > --
> > 2.25.1
next prev parent reply other threads:[~2023-05-19 2:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230519000408epcas1p4f5d90f588e7250d2d168d2943adef4f7@epcas1p4.samsung.com>
2023-05-19 0:04 ` [PATCH] drm/exynos: vidi: fix a wrong error return Inki Dae
2023-05-19 0:26 ` Andi Shyti
2023-05-19 2:37 ` Andi Shyti [this message]
2023-05-19 4:22 ` 대인기
2023-05-19 9:21 ` Andi Shyti
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=ZGbgza6w6taNIXAl@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=linux-samsung-soc@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