From: Dan Carpenter <dan.carpenter@oracle.com>
To: Ricardo Rivera-Matos <r-rivera-matos@ti.com>
Cc: linux-pm@vger.kernel.org
Subject: Re: [EXTERNAL] [bug report] power: supply: bq256xx: Introduce the BQ256XX charger driver
Date: Wed, 13 Jan 2021 12:13:56 +0300 [thread overview]
Message-ID: <20210113091356.GF5105@kadam> (raw)
In-Reply-To: <d0a0fccf-d7c5-c5a4-c4f0-68a8a01b7c34@ti.com>
On Tue, Jan 12, 2021 at 05:44:52PM -0600, Ricardo Rivera-Matos wrote:
> Dan,
>
> On 1/12/21 2:54 AM, Dan Carpenter wrote:
> > Hello Ricardo Rivera-Matos,
> >
> > The patch 32e4978bb920: "power: supply: bq256xx: Introduce the
> > BQ256XX charger driver" from Jan 6, 2021, leads to the following
> > static checker warning:
> >
> > drivers/power/supply/bq256xx_charger.c:1512 bq256xx_hw_init()
> > error: buffer overflow 'bq256xx_watchdog_time' 8 <= 8
> >
> > drivers/power/supply/bq256xx_charger.c
> > 1503 static int bq256xx_hw_init(struct bq256xx_device *bq)
> > 1504 {
> > 1505 struct power_supply_battery_info bat_info = { };
> > 1506 int wd_reg_val = BQ256XX_WATCHDOG_DIS;
> > 1507 int ret = 0;
> > 1508 int i;
> > 1509
> > 1510 for (i = 0; i < BQ256XX_NUM_WD_VAL; i++) {
> > 1511 if (bq->watchdog_timer > bq256xx_watchdog_time[i] &&
> > 1512 bq->watchdog_timer < bq256xx_watchdog_time[i + 1])
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > The last four members of this array are all zero.
> ACK, BQ256XX_NUM_WD_VAL should actually be 4 instead of 8
> >
> > On the last iteration through the loop this will read beyond the end of
> > the array possibly setting "wd_reg_val = 7" uninitentionally.
> ACK, bq256xx_parse_dt() will clamp bq->watchdog_timer so then in
> bq256xx_hw_init()
>
> for (i = 0; i < BQ256XX_NUM_WD_VAL; i++) {
> if (bq->watchdog_timer == bq256xx_watchdog_time[i]) {
> wd_reg_val = i;
> break;
> }
> if (bq->watchdog_timer > bq256xx_watchdog_time[i] &&
> bq->watchdog_timer < bq256xx_watchdog_time[i + 1])
> wd_reg_val = i;
> }
>
> The first if will catch the exact matches and the second if will catch the
> "in-betweens" and round down. The final iteration will always fall into the
> first if statement and break.
>
This looks good. This is a patch you are proposing or it's already
merged in an upstream tree somewhere? Either way, that sounds fine.
Thank!
regards,
dan carpenter
next prev parent reply other threads:[~2021-01-13 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 8:54 [bug report] power: supply: bq256xx: Introduce the BQ256XX charger driver Dan Carpenter
2021-01-12 23:44 ` [EXTERNAL] " Ricardo Rivera-Matos
2021-01-13 9:13 ` Dan Carpenter [this message]
2021-01-13 22:51 ` Ricardo Rivera-Matos
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=20210113091356.GF5105@kadam \
--to=dan.carpenter@oracle.com \
--cc=linux-pm@vger.kernel.org \
--cc=r-rivera-matos@ti.com \
/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