From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: ieee1394 incorrect unsigned tests
Date: Sat, 19 Apr 2008 14:47:30 +0000 [thread overview]
Message-ID: <480A0602.3050108@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080419134736.GI20637@parisc-linux.org>
Matthew Wilcox wrote:
> On Fri, Apr 18, 2008 at 09:08:55PM +0200, Julia Lawall wrote:
>> I found 63 occurrences of this problem with the following semantic match
>> (http://www.emn.fr/x-info/coccinelle/):
>>
>> @@ unsigned int i; @@
>>
>> * i < 0
...
>> diff -u -p a/drivers/ieee1394/dv1394.c b/drivers/ieee1394/dv1394.c
>> *** a/drivers/ieee1394/dv1394.c 2008-03-12 14:13:13.000000000 +0100
>> @@ -918,7 +918,7 @@ static int do_dv1394_init(struct video_c
>> /* default SYT offset is 3 cycles */
>> init->syt_offset = 3;
>>
>> * if ( (init->channel > 63) || (init->channel < 0) )
>> init->channel = 63;
>>
>> chan_mask = (u64)1 << init->channel;
>> diff -u -p a/drivers/ieee1394/video1394.c b/drivers/ieee1394/video1394.c
>> *** a/drivers/ieee1394/video1394.c 2008-03-12 14:13:13.000000000 +0100
>> @@ -893,7 +893,7 @@ static long video1394_ioctl(struct file
>> if (unlikely(d = NULL))
>> return -EFAULT;
>>
>> * if (unlikely((v.buffer<0) || (v.buffer>=d->num_desc - 1))) {
>> PRINT(KERN_ERR, ohci->host->id,
>> "Buffer %d out of range",v.buffer);
>> return -EINVAL;
>> @@ -959,7 +959,7 @@ static long video1394_ioctl(struct file
>> if (unlikely(d = NULL))
>> return -EFAULT;
>>
>> * if (unlikely((v.buffer<0) || (v.buffer>d->num_desc - 1))) {
>> PRINT(KERN_ERR, ohci->host->id,
>> "Buffer %d out of range",v.buffer);
>> return -EINVAL;
>> @@ -1030,7 +1030,7 @@ static long video1394_ioctl(struct file
>> d = find_ctx(&ctx->context_list, OHCI_ISO_TRANSMIT, v.channel);
>> if (d = NULL) return -EFAULT;
>>
>> * if ((v.buffer<0) || (v.buffer>=d->num_desc - 1)) {
>> PRINT(KERN_ERR, ohci->host->id,
>> "Buffer %d out of range",v.buffer);
>> return -EINVAL;
>> @@ -1137,7 +1137,7 @@ static long video1394_ioctl(struct file
>> d = find_ctx(&ctx->context_list, OHCI_ISO_TRANSMIT, v.channel);
>> if (d = NULL) return -EFAULT;
>>
>> * if ((v.buffer<0) || (v.buffer>=d->num_desc-1)) {
>> PRINT(KERN_ERR, ohci->host->id,
>> "Buffer %d out of range",v.buffer);
>> return -EINVAL;
>
> I believe all these are essentially harmless. Due to the wrapping
> nature of unsigned arithmetic, while the first condition (x < 0) is
> always false, the condition it's attempting to catch will be caught by
> the second condition.
I agree.
> We should probably remove the tests for < 0.
We could. It also wouldn't hurt to leave the code as is, because gcc
comes to the same conclusion as we do and removes these tests for us.
(I checked with gcc 4.1.2 here.)
I gladly take patches, but there is no hurry because nobody works with
this code anymore. Both dv1394 and video1394 are nowadays only touched
if serious bugs are to be fixed, and dv1394 is deprecated anyway.
So the only apparent benefit of patching this would be to move these
four sites out of the picture of scripted code checks.
--
Stefan Richter
-===-=--- -=-- =--=
http://arcgraph.de/sr/
prev parent reply other threads:[~2008-04-19 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 13:47 ieee1394 incorrect unsigned tests Matthew Wilcox
2008-04-19 14:47 ` Stefan Richter [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=480A0602.3050108@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=kernel-janitors@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 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.