On Fri, Sep 25, 2015 at 10:41 AM, Rasmus Villemoes
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
On Fri, Sep 25, 2015 at 10:41 AM, Rasmus Villemoes
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
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
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
4 matches
Mail list logo