From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.0 required=5.0 tests=MAILING_LIST_MULTI,
	RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RDNS_NONE,
	SPF_PASS autolearn=ham autolearn_force=no version=3.4.2
Received: (qmail 2909 invoked from network); 24 Mar 2020 14:01:40 -0000
Received-SPF:  pass (mother.openwall.net: domain of lists.openwall.com
  designates 195.42.179.200 as permitted sender)
  receiver=inbox.vuxu.org; client-ip=195.42.179.200
  envelope-from=<musl-return-15607-ml=inbox.vuxu.org@lists.openwall.com>
Received: from unknown (HELO mother.openwall.net) (195.42.179.200)
  by inbox.vuxu.org with ESMTP; 24 Mar 2020 14:01:40 -0000
Received: (qmail 17619 invoked by uid 550); 24 Mar 2020 14:01:37 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 17598 invoked from network); 24 Mar 2020 14:01:36 -0000
Date: Tue, 24 Mar 2020 10:01:24 -0400
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Message-ID: <20200324140124.GX11469@brightrain.aerifal.cx>
References: <CALqoRwx+6LKnB_K-wvFhYTv=pzEYJL31AmraL9jC4wJSobeDiw@mail.gmail.com>
 <20200323163829.GR11469@brightrain.aerifal.cx>
 <CALqoRwy+zePYh5-iA9YTe9R448RvBRP=j+fk9s9iFoiN=5Ti9g@mail.gmail.com>
 <CALqoRwyFBQ9DxWwRzW8uyC27aY-Kena-aZHJpuvc0QBVqyu2UQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALqoRwyFBQ9DxWwRzW8uyC27aY-Kena-aZHJpuvc0QBVqyu2UQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [musl] [Bug] Do not ignore membarrier return code

On Tue, Mar 24, 2020 at 02:53:21PM +0100, Julio Guerra wrote:
> > But I wanted to give you more details with stack traces of the
> > segfault by retrying today with gdb but I cannot reproduce it
> > anymore...!
> > I'll retry later to see if I see the error again...
> 
> The node:10.19-alpine image has been updated since yesterday! That may
> be why I don't have the issue anymore? It updated the latest
> alpine:3.11 image, so 3.11.5.
> The changelog talks says "main/musl: backport fixes from 1.2.0":
> https://www.alpinelinux.org/posts/Alpine-3.11.5-released.html

I'm not aware of any changes that are at all related to your problem.

Rich