From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: James Bottomley <jbottomley@odin.com>
Cc: "linux\@rasmusvillemoes.dk" <linux@rasmusvillemoes.dk>,
"andriy.shevchenko\@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm\@linux-foundation.org" <akpm@linux-foundation.org>,
"kys\@microsoft.com" <kys@microsoft.com>
Subject: Re: [PATCH] lib/string_helpers.c: fix infinite loop in string_get_size()
Date: Mon, 14 Sep 2015 11:19:26 +0200 [thread overview]
Message-ID: <878u891hpd.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <1441934529.13610.4.camel@Odin.com> (James Bottomley's message of "Fri, 11 Sep 2015 01:22:43 +0000")
James Bottomley <jbottomley@odin.com> writes:
> On Fri, 2015-09-04 at 14:56 +0200, Vitaly Kuznetsov wrote:
>> string_get_size(1, 512, 0, ..., ...) call results in an infinite loop. The
>> problem is that if size == 0 when we start calculating sf_cap this loop
>> will never end.
>>
>> The caller causing the issue is sd_read_capacity(), the problem was noticed
>> on Hyper-V.
>>
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>> ---
>> lib/string_helpers.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/string_helpers.c b/lib/string_helpers.c
>> index c98ae81..a155c7b 100644
>> --- a/lib/string_helpers.c
>> +++ b/lib/string_helpers.c
>> @@ -76,7 +76,7 @@ void string_get_size(u64 size, u64 blk_size, const enum string_size_units units,
>> i++;
>> }
>>
>> - sf_cap = size;
>> + sf_cap = size ? size : 1;
>
> If size can become zero after the scale adjustment, then there's a fault
> in the algorithm, and this probably isn't the right fix. However, I did
> a brief calculation, and I can't see how size becomes zero ...
... but it does ...
> it might be that I haven't looked at this long enough (I am on holiday).
The function itself looks over complicated to me but you're probably
right and I'll try to find the root cause of the issue in the algorythm.
Thanks,
>
> James
>
>> for (j = 0; sf_cap*10 < 1000; j++)
>> sf_cap *= 10;
>>
--
Vitaly
prev parent reply other threads:[~2015-09-14 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 12:56 [PATCH] lib/string_helpers.c: fix infinite loop in string_get_size() Vitaly Kuznetsov
2015-09-10 23:08 ` Andrew Morton
2015-09-11 18:31 ` James Bottomley
2015-09-14 9:06 ` Andy Shevchenko
2015-09-14 12:43 ` Vitaly Kuznetsov
2015-09-14 14:33 ` Andy Shevchenko
2015-09-14 9:16 ` Vitaly Kuznetsov
2015-09-11 1:22 ` James Bottomley
2015-09-14 9:19 ` Vitaly Kuznetsov [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=878u891hpd.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jbottomley@odin.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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