mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: incompatibility between libtheora/mmx and musl ?
Date: Tue, 13 Sep 2016 16:43:04 -0400	[thread overview]
Message-ID: <20160913204304.GY15995@brightrain.aerifal.cx> (raw)
In-Reply-To: <20160913180649.GN16436@example.net>

On Tue, Sep 13, 2016 at 08:06:49PM +0200, u-uy74@aetey.se wrote:
> Hello,
> 
> Libtheora contains an assembler part for ia32 and x86_64 which has been
> in use for many years, with at least both glibc and uclibc.
> 
> Now, musl-based builds of libtheora for ia32 with this code enabled
> lead to the encoder segfaulting. No problem when using the C version.
> 
> This is seen when building at Aetey. Ffmpeg in Alpine exhibits the same
> problem, too (strictly speaking, possibly another problem but ffmpeg
> crashes there with the same pattern, when encoding to theora).
> 
> People at Xiph do not have any musl-based system and want really detailed
> debugging info which implies tracing through musl and following malloc's
> internal data (which is what seems to become corrupted).
> 
> In other words, the detailed knowledge (xiph and musl) is located
> separately from each other and also from the motivation (aetey, alpine
> and possibly others).
> 
> I would appreciate some help and suggestions. The alternative is diving
> into mmx-assembler and musl code or resorting to C-only routines which
> give roughly half of the performance of the assembler ones.
> 
> More details are there at
> 
>  https://trac.xiph.org/ticket/2287
> 
> There is also a corresponding
> 
>  https://bugs.alpinelinux.org/issues/6132

The most likely explanation is that they're overflowing a heap buffer.
Perhaps it would be possible to pad all their malloc/realloc calls
with +64 or so to see if that makes the problem go away. If so that
gives a good starting point for tracking down the bug.

Rich


  parent reply	other threads:[~2016-09-13 20:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 18:06 u-uy74
2016-09-13 19:20 ` Markus Wichmann
2016-09-13 20:41   ` Rich Felker
2016-09-13 20:43 ` Rich Felker [this message]
2016-09-14 10:32   ` u-uy74
2016-09-14 11:24     ` Szabolcs Nagy
2016-09-14 14:04       ` u-uy74
2016-09-14 14:28         ` Rich Felker
2016-09-14 14:31           ` Timo Teras
2016-09-14 14:39             ` Rich Felker
2016-09-14 14:40           ` Rich Felker
2016-09-14 14:41           ` Szabolcs Nagy
2016-09-14 15:11             ` u-uy74
2016-10-02 10:59             ` "non-float" malloc (was: incompatibility between libtheora/mmx and musl) u-uy74
2016-10-02 11:17               ` u-uy74
2016-10-02 12:08               ` Szabolcs Nagy
2016-10-02 12:24                 ` u-uy74
2016-10-02 13:24                   ` u-uy74

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=20160913204304.GY15995@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).