From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/10972
Path: news.gmane.org!.POSTED!not-for-mail
From: Szabolcs Nagy <nsz@port70.net>
Newsgroups: gmane.linux.lib.musl.general
Subject: Re: getrlimit failed (chromium on musl)
Date: Sat, 28 Jan 2017 14:14:07 +0100
Message-ID: <20170128131406.GS17692@port70.net>
References: <CAJDAfTAYExERgqWe4wJCj8Af1M68B5_Wxkdwj9WwMnVEsBGZ6A@mail.gmail.com>
 <ce979f3d-671e-a575-2143-e4b1f75048d6@sholland.org>
 <CAJDAfTCfByePfcLnTH5ZoxqyL8EP4Ajed3aghs2RWv2+C92qFg@mail.gmail.com>
 <CAJDAfTBFuLuqxcRxsrFzme1eObnJmJshyLmkfBVpepmiwfj8ow@mail.gmail.com>
 <CAPG2z0_Vgo94xkO_6eVXGcMxHmmC6Da614gcJUKXh=JL743+qQ@mail.gmail.com>
Reply-To: musl@lists.openwall.com
NNTP-Posting-Host: blaine.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: blaine.gmane.org 1485609273 14992 195.159.176.226 (28 Jan 2017 13:14:33 GMT)
X-Complaints-To: usenet@blaine.gmane.org
NNTP-Posting-Date: Sat, 28 Jan 2017 13:14:33 +0000 (UTC)
User-Agent: Mutt/1.6.0 (2016-04-01)
To: musl@lists.openwall.com
Original-X-From: musl-return-10987-gllmg-musl=m.gmane.org@lists.openwall.com Sat Jan 28 14:14:29 2017
Return-path: <musl-return-10987-gllmg-musl=m.gmane.org@lists.openwall.com>
Envelope-to: gllmg-musl@m.gmane.org
Original-Received: from mother.openwall.net ([195.42.179.200])
	by blaine.gmane.org with smtp (Exim 4.84_2)
	(envelope-from <musl-return-10987-gllmg-musl=m.gmane.org@lists.openwall.com>)
	id 1cXSpd-0002ca-LX
	for gllmg-musl@m.gmane.org; Sat, 28 Jan 2017 14:14:17 +0100
Original-Received: (qmail 6099 invoked by uid 550); 28 Jan 2017 13:14:19 -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>
Original-Received: (qmail 6076 invoked from network); 28 Jan 2017 13:14:19 -0000
Mail-Followup-To: musl@lists.openwall.com
Content-Disposition: inline
In-Reply-To: <CAPG2z0_Vgo94xkO_6eVXGcMxHmmC6Da614gcJUKXh=JL743+qQ@mail.gmail.com>
Xref: news.gmane.org gmane.linux.lib.musl.general:10972
Archived-At: <http://permalink.gmane.org/gmane.linux.lib.musl.general/10972>

* He X <xw897002528@gmail.com> [2017-01-28 14:00:59 +0800]:
> After patched,  chromium segfault three times in two days, e.g. when i try
> to upload a file in a baiduyun, crash when i click the upload button, and
> suddenly crashed twice, when --disable-sandbox, no crashing:
> [65422.256448] chromium[12257]: segfault at 3c1 ip 00007f69e30e075c sp
> 00007ffe5442efc0 error 4 in libc.so[7f69e30b9000+a1000]
> 

can you provide your libc.so binary?

or at least objdump around address
0x00007f69e30e075c - 0x7f69e30b9000 = 0x2775c

objdump -rdw libc.so |grep -C 100 '2775c:'

make the context (-C) large enough so we see the function
entry, a proper backtrace would be useful too (e.g.
looking at the coredump from gdb).

> This patch is a bit dangerous, though it indeed solved the problem, i think
> EPERM is needed. Modifying musl is a better way, but is that correct?

disabling syscalls with EPERM is a chrome bug,
but this issue seems independent.