[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ce979f3d-671e-a575-2143-e4b1f75048d6@sholland.org>
Date: Wed, 18 Jan 2017 09:51:29 -0600
From: Samuel Holland <samuel@...lland.org>
To: musl@...ts.openwall.com
Subject: Re: getrlimit failed (chromium on musl)
On 01/18/17 08:08, Alba Pompeo wrote:
> Hi.
>
> Running chromium on a musl system spams this message.
>
> getrlimit(RLIMIT_NOFILE) failed
>
> Any idea how to figure out what's wrong?
The problem is that the sandbox blocks prlimit64 with EPERM, but musl
only falls back to getrlimit on ENOSYS. The diff below will fix the
error. From the linked bug, the only reason it is blocked in the first
place is ChromeOS, and this change should be fine even there.
---
chromium-55.0.2883.75/content/common/sandbox_linux/bpf_renderer_policy_linux.cc.orig
+++
chromium-55.0.2883.75/content/common/sandbox_linux/bpf_renderer_policy_linux.cc
@@ -88,7 +88,7 @@ ResultExpr RendererProcessPolicy::EvaluateSyscall(int
sysno) const {
case __NR_sched_setscheduler:
return sandbox::RestrictSchedTarget(GetPolicyPid(), sysno);
case __NR_prlimit64:
- return Error(EPERM); // See crbug.com/160157.
+ return Error(ENOSYS); // See crbug.com/160157.
default:
// Default on the content baseline policy.
return SandboxBPFBasePolicy::EvaluateSyscall(sysno);
> Thanks.
Regards,
Samuel
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
