New issue
Advanced search Search tips

Issue 782242 link

Starred by 2 users
Status: Fixed
Owner: ----
Closed: Sep 20
Cc:
vapier@chromium.org
dgreid@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Run audio daemons in namespaces

Project Member Reported by jorgelo@chromium.org, Nov 7 2017 
cras is already running as a non-root user with NNP, but we can probably put it in a namespace. Figure out if this doesn't break anything.
Project Member

Comment 1 by bugdroid1@chromium.org, Dec 2 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/adhd/+/01613ee8b647454150fc0c58c86757d75ccae019

commit 01613ee8b647454150fc0c58c86757d75ccae019
Author: Dylan Reid <dgreid@chromium.org>
Date: Sat Dec 02 23:27:13 2017

init: Run CRAS in new namespaces

There is no reason to leave cras in the init namespaces. This enters a
new mount, uts, and IPC namespace. A minimal set of mounts are
added to the mount namespace. cras must run in the root net namespace so
it is shared with bluez for bluetooth audio.

BUG= 782242 
TEST=play audio on samus through web and android apps.

Change-Id: If3889775d2aabea54ccb25169e795d47b9683585
Signed-off-by: Dylan Reid <dgreid@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/798751
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>

[modify] https://crrev.com/01613ee8b647454150fc0c58c86757d75ccae019/init/cras.sh

Comment 2 by jorgelo@chromium.org, Sep 20 

Do we want to close this?

Comment 3 by dgreid@google.com, Sep 20

Status: Fixed (was: Available)
►

Sign in to add a comment