Revert "Backported /drivers/staging/android from 3.4 kernel"

This reverts commit b56734b5fd7a57ea7794467d2f1366847060bf42.
defconfig: staging: 3.0 kernel config entries
staging: logger: hold mutex while removing reader

The readers list is traversed under the log->mutex lock
(for example from fix_up_readers()), but the deletion of
elements from this list is not being done under this lock.

Cc: Brian Swetland <swetland@google.com>
Cc: Dima Zavin <dima@android.com>
Signed-off-by: Rabin Vincent <rabin.vincent@stericsson.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Add permission checking for binder IPC.

Do not apply permission checks to private files.

Fix security_binder_transfer_binder hook.

Drop the owning task argument to security_binder_transfer_binder
since ref->node->proc can be NULL (dead owner?).
Revise the SELinux checking to apply a single transfer check between
the source and destination tasks.  Owning task is no longer relevant.
Drop the receive permission definition as it is no longer used.

This makes the transfer permission similar to the call permission; it is only
useful if you want to allow a binder IPC between two tasks (call permission)
but deny passing of binder references between them (transfer permission).

Change-Id: I51e7a9a6662e826073b35e4f70a57f9ec73e472e
Signed-off-by: William Roberts <w.roberts@sta.samsung.com>
cpufreq: ondemandplus: handle speed up and down in the realtime task

Original commit for interactive governor by Todd Poynor:
https://android.googlesource.com/kernel/common.git/+/f8aa05d96a0d18416d2627c493f7dc9bc5324901
cpufreq: ondemandplus: pin timers to associated CPU

Based on interactive governor commit by Todd Poynor:
https://android.googlesource.com/kernel/common.git/+/430d3d4539a0d441679ca32cc7c3876f97a07da6
cgroup/timer_slack: fix cgroup permission errors

Since the common mounting of cpu and timer_slack into /dev/cpuctl
in commit
https://github.com/boype/kernel_tuna_jb42/commit/f23ab456002c2d3b416260862dbfdb82b031a450
the Android OS cannot move processes across cgoups anymore:

    W/SchedPolicy( 1180): add_tid_to_cgroup failed to write '5949'
    (Permission denied); policy=0

Fix this by implementing an 'allow_attach' handler, according to
this commit:
https://github.com/boype/kernel_tuna_jb42/commit/bb5b603036b99d80527b222dc98eba4ee8341020

Signed-off-by: Boy Petersen <boypetersen@gmail.com>
defconfig: enable 1.5 GHz MPU OPP only for extended version

implement a config variable (CONFIG_TUNA_1_5_GHZ_MPU_OPP) and
disable it for standard version.
Staging: android: binder: Fix memory leak on thread/process exit

If a thread or process exited while a reply, one-way transaction or
death notification was pending, the struct holding the pending work
was leaked.

Change-Id: I2eaafaba1c0ecda3ec0872d449dc16d0721c21e7
Signed-off-by: Arve Hjønnevåg <arve@android.com>
Linux 3.0.85
mm/oom_kill.c (affects lowmemorykiller): prevent changing oom_adj if its value is -17

This should prevent that the Android OS automatically changes
its value when a process has been explicitly set to be unkillable.

To gain control over either oom_adj or oom_score_adj again, set
oom_score_adj to 1000 (OOM_SCORE_MAX).
lowmemorykiller: Use asynchronous compaction when killing processes

Based upon Steve Kondik's commits:
  c9efefe lowmemorykiller: Compact memory when killing processes
  dc952ec lowmemorykiller: Use asynchronous compaction

* Memory compaction is never invoked on Android because we avoid swap
  and don't allocate huge pages. Fix it by invoking compaction from the LMK wh
  a process is killed to reduce memory fragmentation.
defconfig: disable zram
Fancy Kernel r34