Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 2 Dec 2023 09:48:58 +0100
From: Markus Wichmann <>
Cc: Anuraag Agrawal <>
Subject: Re: Large overflow in __intscan ignored

Am Sat, Dec 02, 2023 at 10:42:11AM +0900 schrieb Anuraag Agrawal:
> Hello,
> Thanks for checking and very sorry for the noise, I didn't read the loop
> condition correctly. I am using Webassembly so the issue must be specific
> to it somehow. I will report on wasi-libc to follow up.
> Thanks,

Don't worry about it. The only way I see this could overflow is if
ULLONG_MAX is not the correct limit for what the compiler implements as
"unsigned long long". Though I don't see how that could be, since musl
defines ULLONG_MAX as the minimum value the type can have according to
the C standard.

Or else, of course, maybe the compiler's implementation of 64-bit
multiplication is broken.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.