From: walter harms <wharms@bfs.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
linux-media@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] [media] coda: improve safety in coda_register_device()
Date: Thu, 08 Jan 2015 11:04:20 +0000 [thread overview]
Message-ID: <54AE6434.4070805@bfs.de> (raw)
In-Reply-To: <20150108100708.GA10597@mwanda>
Am 08.01.2015 11:07, schrieb Dan Carpenter:
> The "i" variable is used as an offset into both the dev->vfd[] and the
> dev->devtype->vdevs[] arrays. The second array is smaller so we should
> use that as a limit instead of ARRAY_SIZE(dev->vfd). Also the original
> check was off by one.
>
> We should use a format string as well in case the ->name has any funny
> characters and also to stop static checkers from complaining.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/drivers/media/platform/coda/coda-common.c b/drivers/media/platform/coda/coda-common.c
> index 39330a7..5dd6cae 100644
> --- a/drivers/media/platform/coda/coda-common.c
> +++ b/drivers/media/platform/coda/coda-common.c
> @@ -1844,10 +1844,11 @@ static int coda_register_device(struct coda_dev *dev, int i)
> {
> struct video_device *vfd = &dev->vfd[i];
>
> - if (i > ARRAY_SIZE(dev->vfd))
> + if (i >= dev->devtype->num_vdevs)
> return -EINVAL;
hi,
just a minor question. if i can not be trusted, i feel you should move the
array access:
struct video_device *vfd = &dev->vfd[i];
after the check
i >= dev->devtype->num_vdevs
at least that would improve the readability by not trigger my internal alarm
"check after access"
re,
wh
> - snprintf(vfd->name, sizeof(vfd->name), dev->devtype->vdevs[i]->name);
> + snprintf(vfd->name, sizeof(vfd->name), "%s",
> + dev->devtype->vdevs[i]->name);
> vfd->fops = &coda_fops;
> vfd->ioctl_ops = &coda_ioctl_ops;
> vfd->release = video_device_release_empty,
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
WARNING: multiple messages have this Message-ID (diff)
From: walter harms <wharms@bfs.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
linux-media@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] [media] coda: improve safety in coda_register_device()
Date: Thu, 08 Jan 2015 12:04:20 +0100 [thread overview]
Message-ID: <54AE6434.4070805@bfs.de> (raw)
In-Reply-To: <20150108100708.GA10597@mwanda>
Am 08.01.2015 11:07, schrieb Dan Carpenter:
> The "i" variable is used as an offset into both the dev->vfd[] and the
> dev->devtype->vdevs[] arrays. The second array is smaller so we should
> use that as a limit instead of ARRAY_SIZE(dev->vfd). Also the original
> check was off by one.
>
> We should use a format string as well in case the ->name has any funny
> characters and also to stop static checkers from complaining.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/drivers/media/platform/coda/coda-common.c b/drivers/media/platform/coda/coda-common.c
> index 39330a7..5dd6cae 100644
> --- a/drivers/media/platform/coda/coda-common.c
> +++ b/drivers/media/platform/coda/coda-common.c
> @@ -1844,10 +1844,11 @@ static int coda_register_device(struct coda_dev *dev, int i)
> {
> struct video_device *vfd = &dev->vfd[i];
>
> - if (i > ARRAY_SIZE(dev->vfd))
> + if (i >= dev->devtype->num_vdevs)
> return -EINVAL;
hi,
just a minor question. if i can not be trusted, i feel you should move the
array access:
struct video_device *vfd = &dev->vfd[i];
after the check
i >= dev->devtype->num_vdevs
at least that would improve the readability by not trigger my internal alarm
"check after access"
re,
wh
> - snprintf(vfd->name, sizeof(vfd->name), dev->devtype->vdevs[i]->name);
> + snprintf(vfd->name, sizeof(vfd->name), "%s",
> + dev->devtype->vdevs[i]->name);
> vfd->fops = &coda_fops;
> vfd->ioctl_ops = &coda_ioctl_ops;
> vfd->release = video_device_release_empty,
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-01-08 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 10:07 [patch] [media] coda: improve safety in coda_register_device() Dan Carpenter
2015-01-08 10:07 ` Dan Carpenter
2015-01-08 11:04 ` walter harms [this message]
2015-01-08 11:04 ` walter harms
2015-01-08 11:49 ` Dan Carpenter
2015-01-08 11:49 ` 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=54AE6434.4070805@bfs.de \
--to=wharms@bfs.de \
--cc=dan.carpenter@oracle.com \
--cc=grant.likely@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@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 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.