musl - Re: dynlink.c: bug in reclaim_gaps leading to segfault in __libc_exit

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+bHwpp_UXDEVY2jY9ALwPSKoJ7zeXdNEHQ1cTo_EojU9svMZg@mail.gmail.com>
Date: Wed, 17 Feb 2016 01:16:55 -0500
From: Hugues Bruant <hugues@...ofs.com>
To: musl@...ts.openwall.com
Subject: Re: dynlink.c: bug in reclaim_gaps leading to segfault in __libc_exit_fini

I packaged a small reproducer in a docker image:

docker run huguesb/dmg-musl-crash-repro dmg build /repro.dmg.hfs /repro.dmg

Should successfully create a dmg from the hfs file and return exit code 139
due to the segfault in __libc_exit_fini

The failure is 100% reproducible on all the hosts I've tried so far, which
gives me some confidence that it's not a bad interaction with the kernel:
  - boot2docker 1.10.1 with kernel 4.1.17 / docker 1.10.1 / aufs
  - CoreOS 899.6.0 with kernel 4.3.3 / docker 1.9.1 / overlayfs
  - Ubuntu 14.04 with kernel 3.19.0-43 / docker 1.9.1 / aufs
  - Alpine 3.3.1 with kernel 4.1.15 / docker 1.9.1 / overlayfs

Although my main use case is for this to run inside a container, for
completeness I copied the hfs file out of the docker image on the alpine
host (docker cp). The issue still manifests, which rules out any bad
interaction with docker.

Please let me know if there's anything more I can do.

Regards,
Hugues


Content of type "text/html" skipped

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