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,  <unfinished ...>) = ?
> >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