The patch titled
lib/vsprintf.c: wrong conversion function used
has been added to the -mm tree. Its filename is
lib-vsprintfc-wrong-conversion-function-used.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: lib/vsprintf.c: wrong conversion function used
From: Swen Schillig <swen@xxxxxxxxxxxx>
The macro define_strict_strtoux() is using the simple_strtoul () function
as opposed to the simple_strtoull() function. This leads to false
conversions on non-64bit machines (here 31bit System z).
The following patch fixes the issue introduced by
commit 06b2a76d25d3cfbd14680021c1d356c91be6904e
Author: Yi Yang <yi.y.yang@xxxxxxxxx>
Date: Fri Feb 8 04:21:57 2008 -0800
Signed-off-by: Swen Schillig <swen@xxxxxxxxxxxx>
Cc: Yi Yang <yi.y.yang@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
lib/vsprintf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN lib/vsprintf.c~lib-vsprintfc-wrong-conversion-function-used lib/vsprintf.c
--- a/lib/vsprintf.c~lib-vsprintfc-wrong-conversion-function-used
+++ a/lib/vsprintf.c
@@ -220,7 +220,7 @@ int strict_strtou##type(const char *cp,
if (len == 0) \
return -EINVAL; \
\
- val = simple_strtoul(cp, &tail, base); \
+ val = simple_strtoull(cp, &tail, base); \
if ((*tail == '\0') || \
((len == (size_t)(tail - cp) + 1) && (*tail == '\n'))) {\
*res = val; \
_
Patches currently in -mm which might be from swen@xxxxxxxxxxxx are
lib-vsprintfc-wrong-conversion-function-used.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
