From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: James Bottomley <jbottomley@odin.com>
Cc: "akpm\@linux-foundation.org" <akpm@linux-foundation.org>,
"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>,
"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:16:55 +0200 [thread overview]
Message-ID: <87d1xl1htk.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <1441996263.6276.4.camel@Odin.com> (James Bottomley's message of "Fri, 11 Sep 2015 18:31:07 +0000")
James Bottomley <jbottomley@odin.com> writes:
> On Thu, 2015-09-10 at 16:08 -0700, Andrew Morton wrote:
>> On Fri, 4 Sep 2015 14:56:33 +0200 Vitaly Kuznetsov <vkuznets@redhat.com> 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.
>>
>> When fixing bugs, please provide enough info for others to be able to
>> understand which kernel version(s) need the fix. In this case: what
>> end-user action triggers this bug? (iow, how does sdkp->capacity
>> become zero?)
>
> Any more details. The attached programme, which is cut straight out of
> the algorithm in string_helpers.c and modified for a C environment
> slightly (only in do_div and the typedefs) produces this
>
> hello
> STRING IS 512 B
>
> With your input, so I don't think the problem is where you think it
> is.
Sorry for delayed reply, I was traveling.
Please change
string_get_size(1, 512, STRING_UNITS_2, buf, sizeof(buf));
to
string_get_size(1, 512, STRING_UNITS_10, buf, sizeof(buf));
in your test.c program to see the issue, it will enter the infinite loop
as well.
Regardless to Hyper-V I think such library function shouldn't do such
nasty things (but I'll try to investigate why such small size was
reported).
--
Vitaly
next prev parent reply other threads:[~2015-09-14 9:16 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 [this message]
2015-09-11 1:22 ` James Bottomley
2015-09-14 9:19 ` Vitaly Kuznetsov
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=87d1xl1htk.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 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.