From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] chromium: allow SYS_sched_getparam and SYS_sched_get_scheduler
Date: Tue, 08 Oct 2019 22:10:51 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15268@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 350 bytes --]
There is a new pull request by jnbr against master on the void-packages repository
https://github.com/jnbr/void-packages chromium-sandbox
https://github.com/void-linux/void-packages/pull/15268
chromium: allow SYS_sched_getparam and SYS_sched_get_scheduler
A patch file from https://github.com/void-linux/void-packages/pull/15268.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-chromium-sandbox-15268.patch --]
[-- Type: text/x-diff, Size: 2125 bytes --]
From 864d2066aeece10cebee83c394076629ba3723e8 Mon Sep 17 00:00:00 2001
From: Johannes <johannes.brechtmann@gmail.com>
Date: Tue, 8 Oct 2019 21:15:16 +0200
Subject: [PATCH] chromium: allow SYS_sched_getparam and
SYS_sched_get_scheduler in render policy
fixes #14980
[ci skip]
---
.../patches/sandbox-sched_getparam.patch | 20 +++++++++++++++++++
srcpkgs/chromium/template | 2 +-
2 files changed, 21 insertions(+), 1 deletion(-)
create mode 100644 srcpkgs/chromium/patches/sandbox-sched_getparam.patch
diff --git a/srcpkgs/chromium/patches/sandbox-sched_getparam.patch b/srcpkgs/chromium/patches/sandbox-sched_getparam.patch
new file mode 100644
index 00000000000..aa2d9aa1846
--- /dev/null
+++ b/srcpkgs/chromium/patches/sandbox-sched_getparam.patch
@@ -0,0 +1,20 @@
+Allow SYS_sched_getparam and SYS_sched_getscheduler
+musl uses them for pthread_getschedparam()
+
+source: https://git.alpinelinux.org/aports/commit/community/chromium?id=54af9f8ac24f52d382c5758e2445bf0206eff40e
+
+--- services/service_manager/sandbox/linux/bpf_renderer_policy_linux.cc.orig 2019-10-08 21:03:18.253080425 +0200
++++ services/service_manager/sandbox/linux/bpf_renderer_policy_linux.cc 2019-10-08 21:04:19.648549718 +0200
+@@ -88,10 +88,10 @@
+ case __NR_sysinfo:
+ case __NR_times:
+ case __NR_uname:
+- return Allow();
+- case __NR_sched_getaffinity:
+ case __NR_sched_getparam:
+ case __NR_sched_getscheduler:
++ return Allow();
++ case __NR_sched_getaffinity:
+ case __NR_sched_setscheduler:
+ return sandbox::RestrictSchedTarget(GetPolicyPid(), sysno);
+ case __NR_prlimit64:
diff --git a/srcpkgs/chromium/template b/srcpkgs/chromium/template
index 304251bf6c9..24ef78d74ee 100644
--- a/srcpkgs/chromium/template
+++ b/srcpkgs/chromium/template
@@ -2,7 +2,7 @@
pkgname=chromium
# See http://www.chromium.org/developers/calendar for the latest version
version=77.0.3865.90
-revision=1
+revision=2
archs="i686 x86_64*"
short_desc="Google's attempt at creating a safer, faster, and more stable browser"
maintainer="Enno Boland <gottox@voidlinux.org>"
next reply other threads:[~2019-10-08 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 20:10 voidlinux-github [this message]
2019-10-14 20:42 ` voidlinux-github
2019-10-14 20:42 ` [PR PATCH] [Closed]: " voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15268@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).