Fix ARM Chrome not starting up.

Fix ARM Chrome not starting up.

The seccomp bpf filter was complaining because getsockopt and setsockopt were being called but they're not allowed. I had fixed this for x86-64 in r360114 but the change should have also allowed ARM. Really, it's anything other than 32 bit Linux (which doesn't have a specific id for these methods).

BUG=572795, 561803
Committed: https://crrev.com/93af6debfce796660a58a8681c9da97c5d43638e
Cr-Commit-Position: refs/heads/master@{#367102}

[jam, 2015-12-29 20:05:34]

jam@chromium.org changed reviewers:
+ jhorwich@chromium.org

[jam, 2015-12-29 20:06:20]

Description was changed from

==========
Fix ARM Chrome not starting up.

The seccomp bpf filter was complaining because getsockopt and setsockopt were
being called but they're not allowed. I had fixed this for x86 in r360114 but
the change should have also allowed ARM. Really, it's anything other than 32 bit
Linux (which doesn't have a specific id for these methods).

BUG=572795,561803
==========

to

==========
Fix ARM Chrome not starting up.

The seccomp bpf filter was complaining because getsockopt and setsockopt were
being called but they're not allowed. I had fixed this for x86-64 in r360114 but
the change should have also allowed ARM. Really, it's anything other than 32 bit
Linux (which doesn't have a specific id for these methods).

BUG=572795,561803
==========

[Josh Horwich, 2015-12-29 20:59:46]

On 2015/12/29 20:05:34, jam wrote:

lgtm - thank you for the fix.

I expect we'll need/want an OWNER review too, right?

[jam, 2015-12-29 21:06:21]

On 2015/12/29 20:59:46, Josh Horwich wrote:
> On 2015/12/29 20:05:34, jam wrote:
> 
> lgtm - thank you for the fix.
> 
> I expect we'll need/want an OWNER review too, right?

I pinged the security reviewers but all were ooo. since i'm toplevel, i'm gonna
commit and I'll forward it to others to have a look later, so that arm cros
isn't broken in the meantime.

[jam, 2015-12-29 21:06:29]

The CQ bit was checked by jam@chromium.org

[commit-bot: I haz the power, 2015-12-29 21:06:39]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1553543002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1553543002/1

[commit-bot: I haz the power, 2015-12-29 21:10:58]

Description was changed from

==========
Fix ARM Chrome not starting up.

The seccomp bpf filter was complaining because getsockopt and setsockopt were
being called but they're not allowed. I had fixed this for x86-64 in r360114 but
the change should have also allowed ARM. Really, it's anything other than 32 bit
Linux (which doesn't have a specific id for these methods).

BUG=572795,561803
==========

to

==========
Fix ARM Chrome not starting up.

The seccomp bpf filter was complaining because getsockopt and setsockopt were
being called but they're not allowed. I had fixed this for x86-64 in r360114 but
the change should have also allowed ARM. Really, it's anything other than 32 bit
Linux (which doesn't have a specific id for these methods).

BUG=572795,561803
==========

[commit-bot: I haz the power, 2015-12-29 21:10:59]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-12-29 21:12:08]

Description was changed from

==========
Fix ARM Chrome not starting up.

The seccomp bpf filter was complaining because getsockopt and setsockopt were
being called but they're not allowed. I had fixed this for x86-64 in r360114 but
the change should have also allowed ARM. Really, it's anything other than 32 bit
Linux (which doesn't have a specific id for these methods).

BUG=572795,561803
==========

to

==========
Fix ARM Chrome not starting up.

The seccomp bpf filter was complaining because getsockopt and setsockopt were
being called but they're not allowed. I had fixed this for x86-64 in r360114 but
the change should have also allowed ARM. Really, it's anything other than 32 bit
Linux (which doesn't have a specific id for these methods).

BUG=572795,561803

Committed: https://crrev.com/93af6debfce796660a58a8681c9da97c5d43638e
Cr-Commit-Position: refs/heads/master@{#367102}
==========

[commit-bot: I haz the power, 2015-12-29 21:12:09]

Patchset 1 (id:??) landed as
https://crrev.com/93af6debfce796660a58a8681c9da97c5d43638e
Cr-Commit-Position: refs/heads/master@{#367102}

[rickyz (no longer on Chrome), 2015-12-29 23:08:31]

On 2015/12/29 at 21:12:09, commit-bot wrote:
> Patchset 1 (id:??) landed as
https://crrev.com/93af6debfce796660a58a8681c9da97c5d43638e
> Cr-Commit-Position: refs/heads/master@{#367102}

post lgtm - sorry for the delay!