seccomp: whitelist connect for wl_device

The path to the wayland socket changed, so the previous whitelist based
on the connect() arg2 sockaddr_un size now fails.

BUG=None
TEST=Verify that release build of crosvm starts again on chromebook

Change-Id: I3c30977e7c1487b937d69e1dbce4b7fd87136978
Signed-off-by: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1234827
Reviewed-by: David Riley <davidriley@chromium.org>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Zach Reizner <zachr@chromium.org>
This commit is contained in:
Daniel Verkamp 2018-09-19 15:36:22 -07:00 committed by chrome-bot
parent 713dd60491
commit a0408258e0
2 changed files with 2 additions and 2 deletions

View file

@ -32,7 +32,7 @@ eventfd2: 1
socket: arg0 == 1 && arg1 == 0x80001 && arg2 == 0
# arg1 == FIONBIO || arg1 == DMA_BUF_IOCTL_SYNC
ioctl: arg1 == 0x5421 || arg1 == 0x40086200
connect: arg2 == 13
connect: 1
# Used to communicate with wayland
recvmsg: 1
sendmsg: 1

View file

@ -31,7 +31,7 @@ eventfd2: 1
socket: arg0 == 1 && arg1 == 0x80001 && arg2 == 0
# arg1 == FIONBIO || arg1 == DMA_BUF_IOCTL_SYNC
ioctl: arg1 == 0x5421 || arg1 == 0x40086200
connect: arg2 == 13
connect: 1
# Used to communicate with wayland
recvmsg: 1
sendmsg: 1