chromium: fix sandbox large file flag constant for ppc64

This commit is contained in:
q66 2020-09-04 02:06:42 +02:00
parent bba182874a
commit 99b84b6cb5
1 changed files with 4 additions and 8 deletions

View File

@ -249,19 +249,15 @@ index f51915edc..ca2f4f106 100644
// Ubuntu's version of glibc has a race condition in sem_post that can cause
// it to call futex(2) with bogus op arguments. To workaround this, we need
// to allow those futex(2) calls to fail with EINVAL, instead of crashing the
@@ -246,9 +261,11 @@ ResultExpr RestrictFcntlCommands() {
// operator.
// Glibc overrides the kernel's O_LARGEFILE value. Account for this.
@@ -248,6 +263,8 @@ ResultExpr RestrictFcntlCommands() {
uint64_t kOLargeFileFlag = O_LARGEFILE;
- if (IsArchitectureX86_64() || IsArchitectureI386() || IsArchitectureMips())
+ if (IsArchitectureX86_64() || IsArchitectureI386() || IsArchitectureMips() \
+ || IsArchitecturePPC64())
if (IsArchitectureX86_64() || IsArchitectureI386() || IsArchitectureMips())
kOLargeFileFlag = 0100000;
+ else if (IsArchitecturePPC64())
+ kOLargeFileFlag = 0200000;
+
const Arg<int> cmd(1);
const Arg<long> long_arg(2);
@@ -262,14 +279,23 @@ ResultExpr RestrictFcntlCommands() {
F_SETLKW,
F_GETLK,