From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42883) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uaczd-0001tl-H9 for qemu-devel@nongnu.org; Thu, 09 May 2013 22:23:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uaczc-0007au-7b for qemu-devel@nongnu.org; Thu, 09 May 2013 22:23:33 -0400 Received: from mail-ia0-x22b.google.com ([2607:f8b0:4001:c02::22b]:43750) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uaczc-0007ap-1c for qemu-devel@nongnu.org; Thu, 09 May 2013 22:23:32 -0400 Received: by mail-ia0-f171.google.com with SMTP id r13so4047953iar.16 for ; Thu, 09 May 2013 19:23:31 -0700 (PDT) Sender: fluxion From: Michael Roth Date: Thu, 9 May 2013 21:20:58 -0500 Message-Id: <1368152462-13219-7-git-send-email-mdroth@linux.vnet.ibm.com> In-Reply-To: <1368152462-13219-1-git-send-email-mdroth@linux.vnet.ibm.com> References: <1368152462-13219-1-git-send-email-mdroth@linux.vnet.ibm.com> Subject: [Qemu-devel] [PATCH 06/10] json-parser: fix handling of large whole number values List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: akong@redhat.com, lersek@redhat.com, lcapitulino@redhat.com Currently our JSON parser assumes that numbers lacking a mantissa are integers and attempts to store them as QInt/int64 values. This breaks in the case where the number overflows/underflows int64 values (which is still valid JSON) Fix this by detecting such cases and using a QFloat to store the value instead. Signed-off-by: Michael Roth --- qobject/json-parser.c | 26 +++++++++++++++++++++++--- 1 file changed, 23 insertions(+), 3 deletions(-) diff --git a/qobject/json-parser.c b/qobject/json-parser.c index 05279c1..4d14e71 100644 --- a/qobject/json-parser.c +++ b/qobject/json-parser.c @@ -640,9 +640,29 @@ static QObject *parse_literal(JSONParserContext *ctxt) case JSON_STRING: obj = QOBJECT(qstring_from_escaped_str(ctxt, token)); break; - case JSON_INTEGER: - obj = QOBJECT(qint_from_int(strtoll(token_get_value(token), NULL, 10))); - break; + case JSON_INTEGER: { + /* A possibility exists that this is a whole-valued float where the + * mantissa was left out due to being 0 (.0). It's not a big deal to + * treat these as ints in the parser, so long as users of the + * resulting QObject know to expect a QInt in place of a QFloat in + * cases like these. + * + * However, in some cases these values will overflow/underflow a + * QInt/int64 container, thus we should assume these are to be handled + * as QFloats/doubles rather than silently changing their values. + * + * strtoll() indicates these instances by setting errno to ERANGE + */ + int64_t value; + + errno = 0; /* strtoll doesn't set errno on success */ + value = strtoll(token_get_value(token), NULL, 10); + if (errno != ERANGE) { + obj = QOBJECT(qint_from_int(value)); + break; + } + /* fall through to JSON_FLOAT */ + } case JSON_FLOAT: /* FIXME dependent on locale */ obj = QOBJECT(qfloat_from_double(strtod(token_get_value(token), NULL))); -- 1.7.9.5