From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/10976 Path: news.gmane.org!.POSTED!not-for-mail From: He X Newsgroups: gmane.linux.lib.musl.general Subject: Re: getrlimit failed (chromium on musl) Date: Sun, 29 Jan 2017 12:54:44 +0800 Message-ID: References: <20170128205935.GI1533@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c14c268905c8f05473480a2 X-Trace: blaine.gmane.org 1485665728 27403 195.159.176.226 (29 Jan 2017 04:55:28 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 29 Jan 2017 04:55:28 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-10991-gllmg-musl=m.gmane.org@lists.openwall.com Sun Jan 29 05:55:20 2017 Return-path: 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 ) id 1cXhWD-0005uD-Oq for gllmg-musl@m.gmane.org; Sun, 29 Jan 2017 05:55:13 +0100 Original-Received: (qmail 9734 invoked by uid 550); 29 Jan 2017 04:55:17 -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 9705 invoked from network); 29 Jan 2017 04:55:16 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=6vnYG0hJP1t9oHrSZkRBKP8VtsnIrFF0vGRanP37wno=; b=boQsjGh4QfLCwEoZlD+hmJCYHOxmqLC4PSpD00fPsrpSzvwh4E/9QZKX4WSIvUhxqN SpDXCJX5mEPrN4BMHA+o/tIItdvu36xXzw+gvqcSOQmdD80UHk0E4edDpUYQYCUbbThT wcgbVrPk3Tu15cW0qgdaopAp7LS41T2ib7FuXPCAe16qVyeyi24U16y42nXKH03Nk1b2 66m6sP4T9xhJhEPhgvSUjSrc0Uydx5yP9skwXCV5PDY4Jo7XlS/PtXdc0bZMW3cpo7nX MK/K3CicNpp1uQzMmWEA7LhG5ZW603zibg9Qx6ftAp246Sgumhp+UKxty1QN4oYSJ3RM HvMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=6vnYG0hJP1t9oHrSZkRBKP8VtsnIrFF0vGRanP37wno=; b=scKBck6ovQte5BmJkNldS0Sjyp94UHjkkr0z+kYxFsjf5Lv2LQvmJvPl6UnLng/qVy NZFalr5RPkW8N7AuK9kBOzM6OzNQCZowVH618Ld+dg+uCLTAFdYgqadmpD8nOrxk6SH5 dHHN1e7JkYBzJVMPtvme0meRgfmfQKbRTRhAjt+D+3LnuB0NtO+qFPlGN6z0boJcfZ71 ISqRvfIFUdqAV3I20UB63iPMbPaW8LG+f/fWmiWS9vw3kkF2KCS7MsAQiDnms0/66QcU CWzZJVOA5fCXVSuHfkifyjOfFIpfK3iJp9OypKPlBkvOV+JYeCgxX8CmrQR8ZhXB2bfa VzOA== X-Gm-Message-State: AIkVDXKfLZjUoO6VVJ8FL1hI2ajxJ15DPUJEp7N9/xRwW5pbq8ZZ3LVzjxL6ZZVDUKTfDzxAwNMxMEjBD4ixng== X-Received: by 10.31.242.11 with SMTP id q11mr8022338vkh.54.1485665704367; Sat, 28 Jan 2017 20:55:04 -0800 (PST) In-Reply-To: <20170128205935.GI1533@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:10976 Archived-At: --94eb2c14c268905c8f05473480a2 Content-Type: text/plain; charset=UTF-8 guys, i cleared, this is another bug about intl, check my another mail: http://www.openwall.com/lists/musl/2017/01/29/1 2017-01-29 4:59 GMT+08:00 Rich Felker : > On Sat, Jan 28, 2017 at 01:45:25PM -0600, Samuel Holland wrote: > > Hello, > > > > On 01/28/17 00:00, He X wrote: > > >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] > > > > I have had zero crashes with chromium and this patch (over more than a > > month of use). > > > > >strace output(should be this one): > > >13:52:37.479810 prlimit64(0, RLIMIT_NOFILE, {rlim_cur=4*1024, > > >rlim_max=4*1024}, NULL) = 0 > > >13:52:37.479835 futex(0x7f98cbc02b6c, FUTEX_WAKE_PRIVATE, 1) = 1 > > >13:52:37.479862 futex(0x7f98cbc02b4c, FUTEX_WAIT_PRIVATE, 4294967295, > > >NULL) = 0 > > >13:52:37.479961 rt_sigreturn({mask=[]}) = 61 > > >13:52:37.479982 wait4(29341, NULL, 0, NULL) = ? ERESTARTSYS (To be > > >restarted if SA_RESTART is set) > > >13:52:37.851264 wait4(29341, NULL, 0, NULL) = ? ERESTARTSYS (To be > > >restarted if SA_RESTART is set) > > >13:52:42.127096 wait4(29341, NULL, 0, NULL) = ? ERESTARTSYS (To be > > >restarted if SA_RESTART is set) > > >13:53:23.970709 wait4(29341, ) = ? > > >13:53:30.693847 +++ killed by SIGSEGV +++ > > > > Given the 53 seconds between the prlimit64 call and the crash, I doubt > > they are related. > > Agreed. But there does seem to be something else causing musl-linked > chromium to crash [more often] when sandbox is enabled. I suspect > there's something else they're doing wrong with seccomp that's > breaking it. This strace seems to be done without -f, making it mostly > useless. > > Rich > --94eb2c14c268905c8f05473480a2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
guys, i cleared, this is another bug about intl, check my = another mail:=C2=A0http://www.openwall.com/lists/musl/2017/01/29/1

2017-01-29 4:59 GMT+08:00 Rich = Felker <dalias@libc.org>:
On Sat, Jan 28, 2017 at 01:45:25PM -0= 600, Samuel Holland wrote:
> Hello,
>
> On 01/28/17 00:00, He X wrote:
> >After patched,=C2=A0 chromium segfault three times in two days, e.= g. when
> >i try to upload a file in a baiduyun, crash when i click the uploa= d
> >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]
>
> I have had zero crashes with chromium and this patch (over more than a=
> month of use).
>
> >strace output(should be this one):
> >13:52:37.479810 prlimit64(0, RLIMIT_NOFILE, {rlim_cur=3D4*1024, > >rlim_max=3D4*1024}, NULL) =3D 0
> >13:52:37.479835 futex(0x7f98cbc02b6c, FUTEX_WAKE_PRIVATE, 1) =3D 1=
> >13:52:37.479862 futex(0x7f98cbc02b4c, FUTEX_WAIT_PRIVATE, 42949672= 95,
> >NULL) =3D 0
> >13:52:37.479961 rt_sigreturn({mask=3D[]}) =3D 61
> >13:52:37.479982 wait4(29341, NULL, 0, NULL) =3D ? ERESTARTSYS (To = be
> >restarted if SA_RESTART is set)
> >13:52:37.851264 wait4(29341, NULL, 0, NULL) =3D ? ERESTARTSYS (To = be
> >restarted if SA_RESTART is set)
> >13:52:42.127096 wait4(29341, NULL, 0, NULL) =3D ? ERESTARTSYS (To = be
> >restarted if SA_RESTART is set)
> >13:53:23.970709 wait4(29341,=C2=A0 <unfinished ...>) =3D ? > >13:53:30.693847 +++ killed by SIGSEGV +++
>
> Given the 53 seconds between the prlimit64 call and the crash, I doubt=
> they are related.

Agreed. But there does seem to be something else causing musl-l= inked
chromium to crash [more often] when sandbox is enabled. I suspect
there's something else they're doing wrong with seccomp that's<= br> breaking it. This strace seems to be done without -f, making it mostly
useless.

Rich

--94eb2c14c268905c8f05473480a2--