From: James Bottomley <jbottomley@odin.com>
To: "vkuznets@redhat.com" <vkuznets@redhat.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 v2] lib/string_helpers.c: fix infinite loop in string_get_size()
Date: Mon, 14 Sep 2015 15:15:58 +0000 [thread overview]
Message-ID: <1442243758.2214.9.camel@Odin.com> (raw)
In-Reply-To: <1442235476-31837-1-git-send-email-vkuznets@redhat.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2135 bytes --]
On Mon, 2015-09-14 at 14:57 +0200, Vitaly Kuznetsov wrote:
> Some string_get_size() calls (e.g.:
> string_get_size(1, 512, STRING_UNITS_10, ..., ...)
> string_get_size(15, 64, STRING_UNITS_10, ..., ...)
> ) result in an infinite loop. The problem is that if size is equal to
> divisor[units]/blk_size and is smaller than divisor[units] we'll end
> up with size == 0 when we start doing sf_cap calculations:
>
> For string_get_size(1, 512, STRING_UNITS_10, ..., ...) case:
> ...
> remainder = do_div(size, divisor[units]); -> size is 0, remainder is 1
> remainder *= blk_size; -> remainder is 512
> ...
> size *= blk_size; -> size is still 0
> size += remainder / divisor[units]; -> size is still 0
>
> The caller causing the issue is sd_read_capacity(), the problem was noticed
> on Hyper-V, such weird size was reported by host when scanning collides
> with device removal. This is probably a separate issue worth fixing, this
> patch is intended to prevent the library routing from infinite looping.
>
> 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..d0e607c 100644
> --- a/lib/string_helpers.c
> +++ b/lib/string_helpers.c
> @@ -59,7 +59,7 @@ void string_get_size(u64 size, u64 blk_size, const enum string_size_units units,
> }
>
> exp = divisor[units] / (u32)blk_size;
Add a comment here explaining to those who come after why strict greater
than is necessary. Something like:
/* size must be strictly greater than exp here to ensure
* that remainder is greater than divisor[units] coming out of the if */
> - if (size >= exp) {
> + if (size > exp) {
> remainder = do_div(size, divisor[units]);
> remainder *= blk_size;
> i++;
So when pushed, you finally found the algorithmic problem. Well done.
Acked-by: James Bottomley <JBottomley@Odin.com>
James
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
prev parent reply other threads:[~2015-09-14 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 12:57 [PATCH v2] lib/string_helpers.c: fix infinite loop in string_get_size() Vitaly Kuznetsov
2015-09-14 15:15 ` James Bottomley [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=1442243758.2214.9.camel@Odin.com \
--to=jbottomley@odin.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=vkuznets@redhat.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