From: Lan Chunhe-B25806 <B25806@freescale.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: bug report: signedness issue in ds3232_update_alarm()
Date: Thu, 28 Oct 2010 10:15:46 +0000 [thread overview]
Message-ID: <op.vk96skovfud0ec@localhost.localdomain> (raw)
In-Reply-To: <20101028083503.GZ6062@bicker>
On Thu, 28 Oct 2010 16:55:22 +0800, Dan Carpenter <error27@gmail.com>
wrote:
> Jack's email <jack.lan@freescale.com> is dead. B25806, could you take
> a look?
Sorry, you can use b25806@freescale.com OR chunhe.lan@gmail.com.
> regards,
> dan carpenter
>
> On Thu, Oct 28, 2010 at 10:35:03AM +0200, Dan Carpenter wrote:
>> Hi Jack,
>>
>> This code was added in f46418c5cadf "drivers/rtc/rtc-ds3232.c: add alarm
>> function". Smatch complains because bcd2bin() returns an unsigned so
>> it's never less than zero and the whole block is a no-op. I'm not sure
>> what was intended here, could you take a look?
Of course, bcd2bin()/Time is never less than zero. But it is fault
tolerant.
When time has exceptional data, it set time to the default value.
>> drivers/rtc/rtc-ds3232.c +292 ds3232_update_alarm(13)
>> warn: unsigned 'bcd2bin(buf[0])' is never less than zero.
>> 291
>> 292 buf[0] = bcd2bin(buf[0]) < 0 || (ds3232->rtc->irq_data
>> & RTC_UF) ?
>> 293 0x80 : buf[0];
>> 294 buf[1] = bcd2bin(buf[1]) < 0 || (ds3232->rtc->irq_data
>> & RTC_UF) ?
>> 295 0x80 : buf[1];
>> 296 buf[2] = bcd2bin(buf[2]) < 0 || (ds3232->rtc->irq_data
>> & RTC_UF) ?
>> 297 0x80 : buf[2];
>> 298 buf[3] = bcd2bin(buf[3]) < 0 || (ds3232->rtc->irq_data
>> & RTC_UF) ?
>> 299 0x80 : buf[3];
>> 300
>>
>> regards,
>> dan carpenter
Thanks.
Jack Lan
next prev parent reply other threads:[~2010-10-28 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 8:35 bug report: signedness issue in ds3232_update_alarm() Dan Carpenter
2010-10-28 8:55 ` Dan Carpenter
2010-10-28 10:15 ` Lan Chunhe-B25806 [this message]
2010-10-28 10:58 ` Dan Carpenter
2010-10-28 11:17 ` Lan Chunhe-B25806
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=op.vk96skovfud0ec@localhost.localdomain \
--to=b25806@freescale.com \
--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.