Merge pull request #1 from apascual89/kk4.4

Merge with cm.
Merge branch 'cm-11.0' of https://github.com/CyanogenMod/android_kernel_samsung_hlte into kk4.4
mdss: panel: fix purple "push" at low brightness using temperature

* also fix samsung's sysfs mess with temperature node
mdss: implement panel color control

Adapted and modified work by CM-10.2, morfic and ktoonsez
- what a pain this was to make it work on hlte

    Creates a syfs interface here:
	/sys/class/lcd/panel/panel_colors

    Will accept 0-4 for parameters:
      0 - Cold (more blues)
      1 - Cool
      2 - Normal (stock colors)
      3 - Warm
      4 - Hot (more reds)

Conflicts:

	drivers/video/msm/mdss/mdss_samsung_dsi_panel.c

Conflicts:

	drivers/video/msm/mdss/mdss_samsung_dsi_panel.c
mdss: revert panel temp back to stock - use init.d to adjust
Merge branch 'cm-11.0' of https://github.com/CyanogenMod/android_kernel_samsung_hlte into kk4.4
Bluetooth: Prevent Bluetooth L2CAP Remote Heap Memory Corruption

A remote user can provide a small value for the command size field in
the command header of an l2cap configuration request, resulting in an
integer underflow when subtracting the size of the configuration request
header.  This results in copying a very large amount of data via
memcpy() and destroying the kernel heap.  Check for underflow.

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>
sound control 3.2: Initial GPL release for WCD9320 Audio Codec

This is first official GPL release based on my private implementation.

Signed-off-by: Paul Reioux <reioux@gmail.com>
sound control: kitkat compatibility fix up
sound control: remove taiko_read

taiko_read could sometimes causes a kernel panic, however it is not a necessary function so we simply remove everything associated.
also remove unused poweramp register controls and only retain headphone_pa_gain_show for compatibility.
hlte: power enhancement for wacom hardware.

* always disable digitizer when the pen is inserted

Change-Id: I6c9798682f9f6349b37cb452353bd0c0e6958401
Linux 3.4.0 -> 3.4.71

Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>
Signed-off-by: Wootever <Wootever@users.noreply.github.com>

Conflicts:
	drivers/uio/uio.c
	drivers/video/au1100fb.c
	drivers/video/au1200fb.c
	kernel/events/core.c
	kernel/futex.c
	kernel/kthread.c
Linux 3.4.72 -> 3.4.80

Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>
Signed-off-by: Wootever <Wootever@users.noreply.github.com>
3.4.81
Linux 3.4.82
Merge branch 'cm-11.0' of https://github.com/CyanogenMod/android_kernel_samsung_hlte into kk4.4
Merge branch 'cm-11.0' of https://github.com/CyanogenMod/android_kernel_samsung_hlte into kk4.4
msm: kgsl: Fix Z180 memory leak

Decerement entry refcount, which incremented
in kgsl_sharedmem_find_region.

CRs-Fixed: 635747
Change-Id: I621ba8f8e119a9ab8ba5455b28a565e3cae2f7cd
Signed-off-by: Hareesh Gundu <hareeshg@codeaurora.org>
SELinux: Fix memory leak upon loading policy

commit 8ed814602876bec9bad2649ca17f34b499357a1c upstream.

Hello.

I got below leak with linux-3.10.0-54.0.1.el7.x86_64 .

[  681.903890] kmemleak: 5538 new suspected memory leaks (see /sys/kernel/debug/kmemleak)

Below is a patch, but I don't know whether we need special handing for undoing
ebitmap_set_bit() call.
----------
>>From fe97527a90fe95e2239dfbaa7558f0ed559c0992 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Date: Mon, 6 Jan 2014 16:30:21 +0900
Subject: SELinux: Fix memory leak upon loading policy

Commit 2463c26d "SELinux: put name based create rules in a hashtable" did not
check return value from hashtab_insert() in filename_trans_read(). It leaks
memory if hashtab_insert() returns error.

  unreferenced object 0xffff88005c9160d0 (size 8):
    comm "systemd", pid 1, jiffies 4294688674 (age 235.265s)
    hex dump (first 8 bytes):
      57 0b 00 00 6b 6b 6b a5                          W...kkk.
    backtrace:
      [<ffffffff816604ae>] kmemleak_alloc+0x4e/0xb0
      [<ffffffff811cba5e>] kmem_cache_alloc_trace+0x12e/0x360
      [<ffffffff812aec5d>] policydb_read+0xd1d/0xf70
      [<ffffffff812b345c>] security_load_policy+0x6c/0x500
      [<ffffffff812a623c>] sel_write_load+0xac/0x750
      [<ffffffff811eb680>] vfs_write+0xc0/0x1f0
      [<ffffffff811ec08c>] SyS_write+0x4c/0xa0
      [<ffffffff81690419>] system_call_fastpath+0x16/0x1b
      [<ffffffffffffffff>] 0xffffffffffffffff

However, we should not return EEXIST error to the caller, or the systemd will
show below message and the boot sequence freezes.

  systemd[1]: Failed to load SELinux policy. Freezing.

Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Acked-by: Eric Paris <eparis@redhat.com>
Signed-off-by: Paul Moore <pmoore@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Change-Id: I5204ed79917dc5d0a4a5e7be7dff7a0035ac09b9
Linux 3.4.83