futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr == uaddr2 in futex_requeue(..., requeue_pi=1)

If uaddr == uaddr2, then we have broken the rule of only requeueing from
a non-pi futex to a pi futex with this call.  If we attempt this, then
dangling pointers may be left for rt_waiter resulting in an exploitable
condition.

This change brings futex_requeue() in line with futex_wait_requeue_pi()
which performs the same check as per commit 6f7b0a2a5c0f ("futex: Forbid
uaddr == uaddr2 in futex_wait_requeue_pi()")

[ tglx: Compare the resulting keys as well, as uaddrs might be
  	different depending on the mapping ]

Fixes CVE-2014-3153.

Change-Id: I5f57f062f735f8a7b29d7a34f4735f9469f671fe
Reported-by: Pinkie Pie
Signed-off-by: Will Drewry <wad@chromium.org>
Signed-off-by: Kees Cook <keescook@chromium.org>
Cc: stable@vger.kernel.org
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Merge "futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr == uaddr2 in futex_requeue(..., requeue_pi=1)"
Update to AU_LINUX_ANDROID_JB_3.2.04.03.00.112.547

Change-Id: Iac9fe761f979088f99d04d331bd64112ff227aab
Signed-off-by: B2G User <b2guser@localhost>
Merge "Update to AU_LINUX_ANDROID_JB_3.2.04.03.00.112.547"
ASoC: msm: fix the hph and lineout concurrency

There was a noise observed during the concurrency of the
hph and the lineout usecase.
This is due to incorrect register value updates in the concurrencies.
Update the register values as per the hw/sw document.

CRs-Fixed: 684412
Change-Id: Ia3f01aec017499d703acc8e170d4444676e50003
Signed-off-by: Aviral Gupta <aviralg@codeaurora.org>
Merge "ASoC: msm: fix the hph and lineout concurrency"