mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Pirmin Walthert <pirmin.walthert@wwcom.ch>
To: musl@lists.openwall.com
Subject: Re: gethostbyname2.c / 6476b8135760659b25c93ff9308425ca98a9e777 breaking asterisk 13 compatibility
Date: Thu, 24 Aug 2017 15:09:47 +0200	[thread overview]
Message-ID: <1503580187.12219.25.camel@wwcom.ch> (raw)
In-Reply-To: <20170824155827.0606f740@vostro.util.wtbts.net>

Hi Timo

Thanks, we use Asterisk 13 since months on about 100 VM's with musl, we
have only one strange issue that leads to a crashes from time to time,
especially when using PickupChan. Somehow I couldn't reproduce the
crash when using only hostnames in FROM headers that I'd put into
/etc/hosts (but as it is hard to reproduce anyway it's not sure whether
this is really the reason). However I've seen that some pjsip functions
used in the multihomed module (in asterisk 13 at least) are using
gethostbyname (not gethostbyname_r). 

I'm waiting for feedback from the asterisk team whether it's possible
that several threads are using the multihomed code at the same time.

Asterisk 14 has some changes in the resolver, so maybe that's the
reason why Asterisk 14 isn't affected.

Best regards,

Pirmin

Am Donnerstag, den 24.08.2017, 15:58 +0300 schrieb Timo Teras:
> On Thu, 24 Aug 2017 13:39:08 +0200
> Pirmin Walthert <pirmin.walthert@wwcom.ch> wrote:
> 
> > First thing:
> > http://git.musl-libc.org/cgit/musl/commit/?id=6476b8135760
> > 659b25c93ff9308425ca98a9e777 seems to break Asterisk compatibilty.
> > Asterisk crashes on every startup while loading modules. Using
> > musl-git combined with the latest dynlink.c version before this
> > commit works fine. (1.1.16 has some startup crashes as well because
> > of the bug fixed with 27b3fd68f67b674440d21ea7ca5cf918d2e1559f).
> 
> I am using asterisk 14 just fine on Alpine linux with current musl
> git
> master. We needed few patches though. Maybe those help you too:
> https://git.alpinelinux.org/cgit/aports/tree/main/asterisk
> 
> Though, some issues might be relevant to specific modules.
> 
> Timo


  reply	other threads:[~2017-08-24 13:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 11:39 Pirmin Walthert
2017-08-24 11:40 ` Pirmin Walthert
2017-08-24 12:47   ` Shiz
2017-08-24 13:02     ` Pirmin Walthert
2017-08-24 12:58 ` Timo Teras
2017-08-24 13:09   ` Pirmin Walthert [this message]
2017-08-24 16:17 ` Rich Felker
2017-08-24 16:24   ` Pirmin Walthert

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=1503580187.12219.25.camel@wwcom.ch \
    --to=pirmin.walthert@wwcom.ch \
    --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).