Forked from  bug #755697 ...

---

We have some local CHROMIUM changes in kernel 4.4:

CHROMIUM: android: binder: another use of binder_lock_interruptible
android: binder: Turn off warning for NO_WAIT allocation
CHROMIUM: android: binder: do not create thread when trying to kill it
CHROMIUM: android: binder: introduce binder_lock_interruptible
CHROMIUM: android: binder: do not take binder lock when thread forcibly woken up
CHROMIUM: android: binder: push binder_lock down into ioctl ops
CHROMIUM: android: binder: reset BINDER_LOOPER_STATE_NEED_RETURN earlier
FROMLIST: android: binder: check result of binder_get_thread() in binder_poll()
CHROMIUM: android: binder: Fix potential scheduling-while-atomic
android: binder: Disable preemption while holding the global binder lock.
android: binder: Use wake up hint for synchronous transactions.
CHROMIUM: android: binder: get rid of BINDER_LOOPER_STATE_WAITING

---

When we landed some these changes we evaluated the upstream "remove the big binder lock" patches, but Dmitry found some things there that he objected to.

This bug tracks the effort to submit patches upstream to cleanup the things that were not liked.  Possibly for inspiration we might want to apply some of the CHROMIUM patches above to upstream.

---

For now newer kernels (like 4.12) will use the pure upstream solution for binder.  Again, see  bug #755697