Description of problem:

The latest chromium-browser releases fail to start when home directories are on NFS. It seems an updated SELinux policy is needed to allow chrome_sandbox_t access to nfs_t (and autofs_t) when the use_nfs_home_dirs SELinux boolean is set.

Version-Release number of selected component (if applicable):
chromium-browser-39.0.2171.99-1.el6_6.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Start chromium-browser as a user with an NFS mounted home directory
2.
3.

Actual results:
The following error is thrown and no windows is opened.
$ chromium-browser 
[0122/113309:ERROR:nss_util.cc(94)] Failed to create /users/system/rtheys/.pki/nssdb directory.
[0122/113309:FATAL:chrome_main_delegate.cc(359)] Check failed: process_type.empty(). Unable to get the user data directory for process type: zygote


Expected results:
Chromium opens.

Additional info:

The following SELinux module fixes this for me:

module esat_chromium 1.0;

require {
        type autofs_t;
        type chrome_sandbox_t;
        type nfs_t;
        class dir { getattr search };
        class filesystem getattr;
}

#============= chrome_sandbox_t ==============


allow chrome_sandbox_t autofs_t:dir { getattr search };
allow chrome_sandbox_t nfs_t:filesystem getattr;