Add security hooks to binder and implement the hooks for SELinux.

Add security hooks to the binder and implement the hooks for SELinux.
The security hooks enable security modules such as SELinux to implement
controls over binder IPC.  The security hooks include support for
controlling what process can become the binder context manager
(binder_set_context_mgr), controlling the ability of a process
to invoke a binder transaction/IPC to another process (binder_transaction),
controlling the ability a process to transfer a binder reference to
another process (binder_transfer_binder), and controlling the ability
of a process to transfer an open file to another process (binder_transfer_file).

This support is used by SE Android, http://selinuxproject.org/page/SEAndroid.

Change-Id: I9a64a87825df2e60b9c51400377af4a9cd1c4049
Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
Do not ratelimit audit messages. We want to see them all.

Change-Id: I19c29788cc33b0f59e0bdfe04fe67c247239c559
Enable SELinux and its dependencies in the mako defconfig.

Change-Id: I2f9b5d040461a3b0af3c22982f3a24cb67cf5048
mako: wifi: Channel blocking when mobile network is no service state.

In case of no service state which means that Wi-Fi framework does not know
country code,  just 1 ~ 11 channels will be active and 12 ~ 14 channels and
5GHz channels will be blocked.

To do this, the followings are changed
1) Change regulatory domain map (nv.bin)
   a) Set N_AMER_EXC_FCC not to use 12 ~ 14 channels and 5GHz channels
   b) Set default regulatory domain to N_AMER_EXC_FCC
2) Change regulatory domain of Vietnam, Israel, and Turkey to others (vos_nvitem.c)
   Vietnam : N_AMER_EXC_FCC -> World
   Turkey  : N_AMER_EXC_FCC -> ETSI

LGE tested all the country codes of which the Mako was released and there was
no regulatory domain problem.

Signed-off-by: Vineeta Srivastava <vsrivastava@google.com>

Change-Id: I588821c2f867e624c7e44c0fefb4b1b5a053501f
Enable setting security contexts on rootfs inodes.

rootfs (ramfs) can support setting of security contexts
by userspace due to the vfs fallback behavior of calling
the security module to set the in-core inode state
for security.* attributes when the filesystem does not
provide an xattr handler.  No xattr handler required
as the inodes are pinned in memory and have no backing
store.

This is useful in allowing early userspace to label individual
files within a rootfs while still providing a policy-defined
default via genfs.

Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
Change-Id: I3436cf9ae27ade445e37376d7b9125746b1e506f
Merge remote-tracking branch 'upstream/cm-10.1' into cm-10.1-untouch