From: Rich Felker <dalias@libc.org>
To: Markus Wichmann <nullplan@gmx.net>
Cc: musl@lists.openwall.com, Anuraag Agrawal <anuraaga@gmail.com>
Subject: Re: [musl] Large overflow in __intscan ignored
Date: Sun, 25 Feb 2024 20:30:56 -0500 [thread overview]
Message-ID: <20240226013056.GE4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <20231202162941.GC4163@brightrain.aerifal.cx>
On Sat, Dec 02, 2023 at 11:29:41AM -0500, Rich Felker wrote:
> On Sat, Dec 02, 2023 at 09:48:58AM +0100, Markus Wichmann wrote:
> > 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.
>
> Ouch, sounds like this is going to be some sort of big wasm bug...
Was this bug ever reported/tracked-down/fixed on the wasm side?
Rich
prev parent reply other threads:[~2024-02-26 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 5:08 Anuraag Agrawal
2023-12-01 5:14 ` [musl] " Anuraag Agrawal
2023-12-01 15:52 ` Rich Felker
2023-12-01 16:21 ` [musl] " Markus Wichmann
2023-12-02 1:42 ` Anuraag Agrawal
2023-12-02 8:48 ` Markus Wichmann
2023-12-02 16:29 ` Rich Felker
2024-02-26 1:30 ` Rich Felker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240226013056.GE4163@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=anuraaga@gmail.com \
--cc=musl@lists.openwall.com \
--cc=nullplan@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).