On Fri, Sep 25, 2015 at 10:41 AM, Rasmus Villemoes
<li...@rasmusvillemoes.dk> wrote:
> Quoting from 2aa2f9e21e4e ("lib/vsprintf.c: improve sanity check in
> vsnprintf()"):
>
> On 64 bit, size may very well be huge even if bit 31 happens to be 0.
> Somehow it doesn't feel right that one can pass a 5 GiB buffer but not a
> 3 GiB one. So cap at INT_MAX as was probably the intention all along.
> This is also the made-up value passed by sprintf and vsprintf.
>
> I should have seen this copy-pasted instance back then, but let's just
> do it now.
>
> Signed-off-by: Rasmus Villemoes <li...@rasmusvillemoes.dk>
Acked-by: Kees Cook <keesc...@chromium.org>
-Kees
--
Kees Cook
Chrome OS Security
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
