From: Dan Carpenter <dan.carpenter@oracle.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: xen-devel@lists.xenproject.org, kernel-janitors@vger.kernel.org,
dri-devel@lists.freedesktop.org,
oleksandr_andrushchenko@epam.com
Subject: Re: [bug report] drm/xen-front: Add support for Xen PV display frontend
Date: Tue, 21 Apr 2020 17:52:20 +0000 [thread overview]
Message-ID: <20200421175220.GE2659@kadam> (raw)
In-Reply-To: <alpine.DEB.2.21.2004211728360.3118@hadrien>
On Tue, Apr 21, 2020 at 05:29:02PM +0200, Julia Lawall wrote:
>
>
> On Tue, 21 Apr 2020, Dan Carpenter wrote:
>
> > Hi Kernel Janitors,
> >
> > Here is another idea that someone could work on, fixing the
> > IS_ERR_OR_NULL() checks in the xen driver.
> >
> > The patch c575b7eeb89f: "drm/xen-front: Add support for Xen PV
> > display frontend" from Apr 3, 2018, leads to the following static
> > checker warning:
> >
> > drivers/gpu/drm/xen/xen_drm_front_gem.c:140 xen_drm_front_gem_create()
> > warn: passing zero to 'ERR_CAST'
> >
> > drivers/gpu/drm/xen/xen_drm_front_gem.c
> > 133 struct drm_gem_object *xen_drm_front_gem_create(struct drm_device *dev,
> > 134 size_t size)
> > 135 {
> > 136 struct xen_gem_object *xen_obj;
> > 137
> > 138 xen_obj = gem_create(dev, size);
> > 139 if (IS_ERR_OR_NULL(xen_obj))
> > 140 return ERR_CAST(xen_obj);
>
> Are the other occurrences of this also a possible problem? There are a
> few others outside of xen.
We sometimes check a parameter for IS_ERR_OR_NULL().
void free_function(struct something *p)
{
if (IS_ERR_OR_NULL(p))
return;
}
That's fine, absolutely harmless and not a bug. But if we are checking
a return value like this then probably most of the time it's invalid
code. Normally it's again like this code where we're dealing with an
impossible thing because the return is never NULL. The common bugs are
that it returns NULL to a caller which only expects error pointers or it
returns success instead of failure. But sometimes returning success can
be valid:
obj = get_feature(dev);
if (IS_ERR_OR_NULL(obj))
return PTR_ERR(obj);
It deliberately returns success because the rest of the function is
useless when we don't have the feature.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: xen-devel@lists.xenproject.org, kernel-janitors@vger.kernel.org,
dri-devel@lists.freedesktop.org,
oleksandr_andrushchenko@epam.com
Subject: Re: [bug report] drm/xen-front: Add support for Xen PV display frontend
Date: Tue, 21 Apr 2020 20:52:20 +0300 [thread overview]
Message-ID: <20200421175220.GE2659@kadam> (raw)
In-Reply-To: <alpine.DEB.2.21.2004211728360.3118@hadrien>
On Tue, Apr 21, 2020 at 05:29:02PM +0200, Julia Lawall wrote:
>
>
> On Tue, 21 Apr 2020, Dan Carpenter wrote:
>
> > Hi Kernel Janitors,
> >
> > Here is another idea that someone could work on, fixing the
> > IS_ERR_OR_NULL() checks in the xen driver.
> >
> > The patch c575b7eeb89f: "drm/xen-front: Add support for Xen PV
> > display frontend" from Apr 3, 2018, leads to the following static
> > checker warning:
> >
> > drivers/gpu/drm/xen/xen_drm_front_gem.c:140 xen_drm_front_gem_create()
> > warn: passing zero to 'ERR_CAST'
> >
> > drivers/gpu/drm/xen/xen_drm_front_gem.c
> > 133 struct drm_gem_object *xen_drm_front_gem_create(struct drm_device *dev,
> > 134 size_t size)
> > 135 {
> > 136 struct xen_gem_object *xen_obj;
> > 137
> > 138 xen_obj = gem_create(dev, size);
> > 139 if (IS_ERR_OR_NULL(xen_obj))
> > 140 return ERR_CAST(xen_obj);
>
> Are the other occurrences of this also a possible problem? There are a
> few others outside of xen.
We sometimes check a parameter for IS_ERR_OR_NULL().
void free_function(struct something *p)
{
if (IS_ERR_OR_NULL(p))
return;
}
That's fine, absolutely harmless and not a bug. But if we are checking
a return value like this then probably most of the time it's invalid
code. Normally it's again like this code where we're dealing with an
impossible thing because the return is never NULL. The common bugs are
that it returns NULL to a caller which only expects error pointers or it
returns success instead of failure. But sometimes returning success can
be valid:
obj = get_feature(dev);
if (IS_ERR_OR_NULL(obj))
return PTR_ERR(obj);
It deliberately returns success because the rest of the function is
useless when we don't have the feature.
regards,
dan carpenter
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: xen-devel@lists.xenproject.org, kernel-janitors@vger.kernel.org,
dri-devel@lists.freedesktop.org,
oleksandr_andrushchenko@epam.com
Subject: Re: [bug report] drm/xen-front: Add support for Xen PV display frontend
Date: Tue, 21 Apr 2020 20:52:20 +0300 [thread overview]
Message-ID: <20200421175220.GE2659@kadam> (raw)
In-Reply-To: <alpine.DEB.2.21.2004211728360.3118@hadrien>
On Tue, Apr 21, 2020 at 05:29:02PM +0200, Julia Lawall wrote:
>
>
> On Tue, 21 Apr 2020, Dan Carpenter wrote:
>
> > Hi Kernel Janitors,
> >
> > Here is another idea that someone could work on, fixing the
> > IS_ERR_OR_NULL() checks in the xen driver.
> >
> > The patch c575b7eeb89f: "drm/xen-front: Add support for Xen PV
> > display frontend" from Apr 3, 2018, leads to the following static
> > checker warning:
> >
> > drivers/gpu/drm/xen/xen_drm_front_gem.c:140 xen_drm_front_gem_create()
> > warn: passing zero to 'ERR_CAST'
> >
> > drivers/gpu/drm/xen/xen_drm_front_gem.c
> > 133 struct drm_gem_object *xen_drm_front_gem_create(struct drm_device *dev,
> > 134 size_t size)
> > 135 {
> > 136 struct xen_gem_object *xen_obj;
> > 137
> > 138 xen_obj = gem_create(dev, size);
> > 139 if (IS_ERR_OR_NULL(xen_obj))
> > 140 return ERR_CAST(xen_obj);
>
> Are the other occurrences of this also a possible problem? There are a
> few others outside of xen.
We sometimes check a parameter for IS_ERR_OR_NULL().
void free_function(struct something *p)
{
if (IS_ERR_OR_NULL(p))
return;
}
That's fine, absolutely harmless and not a bug. But if we are checking
a return value like this then probably most of the time it's invalid
code. Normally it's again like this code where we're dealing with an
impossible thing because the return is never NULL. The common bugs are
that it returns NULL to a caller which only expects error pointers or it
returns success instead of failure. But sometimes returning success can
be valid:
obj = get_feature(dev);
if (IS_ERR_OR_NULL(obj))
return PTR_ERR(obj);
It deliberately returns success because the rest of the function is
useless when we don't have the feature.
regards,
dan carpenter
next prev parent reply other threads:[~2020-04-21 17:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 10:45 [bug report] drm/xen-front: Add support for Xen PV display frontend Dan Carpenter
2020-04-21 10:45 ` Dan Carpenter
2020-04-21 10:45 ` Dan Carpenter
2020-04-21 11:34 ` Oleksandr Andrushchenko
2020-04-21 11:34 ` Oleksandr Andrushchenko
2020-04-21 11:34 ` Oleksandr Andrushchenko
2020-04-21 11:51 ` Dan Carpenter
2020-04-21 11:51 ` Dan Carpenter
2020-04-21 11:51 ` Dan Carpenter
2020-04-21 12:54 ` Oleksandr Andrushchenko
2020-04-21 12:54 ` Oleksandr Andrushchenko
2020-04-21 12:54 ` Oleksandr Andrushchenko
2020-05-08 7:34 ` Oleksandr Andrushchenko
2020-05-08 7:34 ` Oleksandr Andrushchenko
2020-05-08 7:34 ` Oleksandr Andrushchenko
2020-04-21 15:29 ` Julia Lawall
2020-04-21 15:29 ` Julia Lawall
2020-04-21 15:29 ` Julia Lawall
2020-04-21 17:52 ` Dan Carpenter [this message]
2020-04-21 17:52 ` Dan Carpenter
2020-04-21 17:52 ` Dan Carpenter
2020-04-21 18:59 ` Julia Lawall
2020-04-21 18:59 ` Julia Lawall
2020-04-21 18:59 ` Julia Lawall
2020-04-21 19:33 ` Dan Carpenter
2020-04-21 19:33 ` Dan Carpenter
2020-04-21 19:33 ` Dan Carpenter
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=20200421175220.GE2659@kadam \
--to=dan.carpenter@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.