From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9786 Path: news.gmane.org!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: Libc-Test: Tests failing on Ubuntu VM Date: Wed, 30 Mar 2016 20:04:43 +0200 Message-ID: <20160330180442.GM9862@port70.net> References: <20160330164737.GL9862@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1459361098 2303 80.91.229.3 (30 Mar 2016 18:04:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 30 Mar 2016 18:04:58 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9799-gllmg-musl=m.gmane.org@lists.openwall.com Wed Mar 30 20:04:58 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1alKUE-0007Ff-3X for gllmg-musl@m.gmane.org; Wed, 30 Mar 2016 20:04:58 +0200 Original-Received: (qmail 13506 invoked by uid 550); 30 Mar 2016 18:04:55 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 13488 invoked from network); 30 Mar 2016 18:04:54 -0000 Mail-Followup-To: musl@lists.openwall.com Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Xref: news.gmane.org gmane.linux.lib.musl.general:9786 Archived-At: * Max Ruttenberg [2016-03-30 13:22:19 -0400]: > this is what my src/regression/REPORT file looks like: > > ****************************************************************************************************************************** > src/regression/malloc-brk-fail.c:33: malloc did not fail with ENOMEM, got > Operation not permitted > FAIL ./src/regression/malloc-brk-fail-static.exe [status 1] > src/regression/malloc-brk-fail.c:33: malloc did not fail with ENOMEM, got > Operation not permitted > FAIL ./src/regression/malloc-brk-fail.exe [status 1] > src/regression/malloc-oom.c:16: expected ENOMEM, got Operation not permitted > FAIL ./src/regression/malloc-oom-static.exe [status 1] > src/regression/malloc-oom.c:16: expected ENOMEM, got Operation not permitted > FAIL ./src/regression/malloc-oom.exe [status 1] > FAIL ./src/regression/putenv-doublefree-static.exe [signal Segmentation > fault] > FAIL ./src/regression/putenv-doublefree.exe [signal Segmentation fault] > src/regression/setenv-oom.c:23: expected ENOMEM, got Operation not permitted > FAIL ./src/regression/setenv-oom-static.exe [status 1] > src/regression/setenv-oom.c:23: expected ENOMEM, got Operation not permitted > FAIL ./src/regression/setenv-oom.exe [status 1] > ****************************************************************************************************************************** > > Is the brk system call still kosher? I thought malloc was supposed to use > something mmap. > i've seen such things: mmap fails with EPERM instead of ENOMEM when the system runs out of virtual address space, i don't remember the details though, you can debug it with strace. if you figure it out i'd like to know when this happens (probably a kernel bug). putenv-doublefree was recently fixed, so your musl is probably not up to date.