From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: Infinite loop in malloc
Date: Fri, 25 Jan 2019 22:55:22 +0100 [thread overview]
Message-ID: <20190125215522.GF23924@voyager> (raw)
In-Reply-To: <20190125151350.GB20330@r>
Hi all,
one more idea I just had: This might be a use-after-free bug. If the
program had clobbered the chunk pointers, the a_and_64() in unbin()
wouldn't be triggered, leading to the infinite loop described in the OP.
Ciao,
Markus
next prev parent reply other threads:[~2019-01-25 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 15:13 r yang
2019-01-25 21:49 ` Markus Wichmann
2019-01-25 21:57 ` Szabolcs Nagy
2019-01-25 21:55 ` Markus Wichmann [this message]
2019-01-25 22:28 ` Szabolcs Nagy
2019-01-25 23:11 ` Szabolcs Nagy
2019-01-26 1:30 ` Rich Felker
2019-01-26 13:59 ` Szabolcs Nagy
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=20190125215522.GF23924@voyager \
--to=nullplan@gmx.net \
--cc=musl@lists.openwall.com \
/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).