From: Jiri Slaby <jslaby@suse.cz>
To: minyard@acm.org
Cc: jirislaby@gmail.com, linux-kernel@vger.kernel.org,
Tomas Cech <tcech@suse.cz>,
openipmi-developer@lists.sourceforge.net,
Rocky Craig <rocky.craig@hp.com>
Subject: Re: [PATCH 1/1] Char: ipmi_bt_sm, fix infinite loop
Date: Mon, 24 Mar 2014 13:24:21 +0100 [thread overview]
Message-ID: <533023F5.40909@suse.cz> (raw)
In-Reply-To: <530D1021.1050402@acm.org>
On 02/25/2014 10:50 PM, Corey Minyard wrote:
> Looks right to me. Rocky, copying you in case there's an issue with this.
Hi,
any updates here, I don't see it in the -next tree yet?
Thanks.
> On 02/25/2014 04:14 AM, Jiri Slaby wrote:
>> In read_all_bytes, we do
>> unsigned char i;
>> ...
>> bt->read_data[0] = BMC2HOST;
>> bt->read_count = bt->read_data[0];
>> ...
>> for (i = 1; i <= bt->read_count; i++)
>> bt->read_data[i] = BMC2HOST;
>>
>> If bt->read_data[0] == bt->read_count == 255, we loop infinitely in
>> the 'for' loop. Make 'i' an 'int' instead of 'char' to get rid of the
>> overflow and finish the loop after 255 iterations every time.
>>
>> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
>> Reported-and-debugged-by: Rui Hui Dian <rhdian@novell.com>
>> Cc: Tomas Cech <tcech@suse.cz>
>> Cc: Corey Minyard <minyard@acm.org>
>> Cc: <openipmi-developer@lists.sourceforge.net>
>> ---
>> drivers/char/ipmi/ipmi_bt_sm.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/char/ipmi/ipmi_bt_sm.c b/drivers/char/ipmi/ipmi_bt_sm.c
>> index f5e4cd7617f6..61e71616689b 100644
>> --- a/drivers/char/ipmi/ipmi_bt_sm.c
>> +++ b/drivers/char/ipmi/ipmi_bt_sm.c
>> @@ -352,7 +352,7 @@ static inline void write_all_bytes(struct si_sm_data *bt)
>>
>> static inline int read_all_bytes(struct si_sm_data *bt)
>> {
>> - unsigned char i;
>> + unsigned int i;
>>
>> /*
>> * length is "framing info", minimum = 4: NetFn, Seq, Cmd, cCode.
>
--
js
suse labs
next prev parent reply other threads:[~2014-03-24 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 10:14 Jiri Slaby
2014-02-25 21:50 ` Corey Minyard
2014-03-24 12:24 ` Jiri Slaby [this message]
2014-03-24 18:59 ` Corey Minyard
2014-04-17 13:21 ` Torsten Duwe
2014-04-17 13:33 ` Corey Minyard
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=533023F5.40909@suse.cz \
--to=jslaby@suse.cz \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=rocky.craig@hp.com \
--cc=tcech@suse.cz \
/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
Powered by JetHome