ak_mako_defconfig: disable KALLSYMS
Revert "ak_mako_defconfig: disable DEBUG_KERNEL"

This reverts commit 02ff891c43d2c62e4fd0cc8c4c1a35e4e38ee772.
Revert "bfq-iosched: Set bfq_back_penalty = 1"

This reverts commit 626905b1f9f6497e77f723f7a4f3af4ccf4d7004.
Revert "bfq-iosched: Tuning for SSD"

This reverts commit 37afb6a1ec5028523046328152fba660d26c25e9.
Revert "block, bfq: add Early Queue Merge (EQM) to BFQ-v7r2 for 3.4.0"

This reverts commit 5dbead91af7b40387bda749fdf4286e4942c15c4.
Revert "block: introduce the BFQ-v7r2 I/O sched for 3.4"

This reverts commit bb0b0b364b62f5ba4e01c457d3a2f5aad0c6d73c.
block: introduce the BFQ-v7r3 I/O sched for 3.4
block, bfq: add Early Queue Merge (EQM) to BFQ-v7r3 for 3.4.0
bfq-iosched: Tuning for SSD
bfq-iosched: Set bfq_back_penalty = 1
cpufreq: interactive: Optimize sync_freq implementation

Don't let frequency drop below sync_freq if either load or
frequency among other cpus is above a certain threshold,
not necessarily both.
cpufreq: conservative: introduced micro frequencies sync
makefile: tweak and align flags
msm: thermal: relax temps and throttling
ak_mako_defconfig: revert max to 1512Mhz
Revert "msm: thermal: relax temps and throttling"

This reverts commit 83614146a4ce5b375b4f785e86fb1ab2a6f6a1f2.
msm: cpu: overclock: modded for cpu ultra overclock and normal
ak_mako_defconfig: Disable CONFIG_STRICT_MEMORY_RWX

Its intention is to protect against theoretical vulnerabilities, but
in reality it opens the door for an already actively used exploit.
https://www.codeaurora.org/projects/security-advisories/configstrictmemoryrwx-not-strictly-enforced-cve-2013-4737
The security patch that fixes CONFIG_STRICT_MEMORY_RWX is expensive.
Better conserve the resources and protect us by simple disable of it.
nf: xt_qtaguid: fix handling for cases where tunnels are used.

* fix skb->dev vs par->in/out
When there is some forwarding going on, it introduces extra state
around devs associated with xt_action_param->in/out and sk_buff->dev.
E.g.
   par->in and par->out are both set, or
   skb->dev and par->out are both set (and different)
This would lead qtaguid to make the wrong assumption about the
direction and update the wrong device stats.
Now we rely more on par->in/out.

* Fix handling when qtaguid is used as "owner"
When qtaguid is used as an owner module, and sk_socket->file is
not there (happens when tunnels are involved), it would
incorrectly do a tag stats update.

* Correct debug messages.

Bug: 11687690
Change-Id: I2b1ff8bd7131969ce9e25f8291d83a6280b3ba7f
Signed-off-by: JP Abgrall <jpa@google.com>
(cherry picked from commit 2b71479d6f5fe8f33b335f713380f72037244395)
fix false disconnect due to a signal sent to the reading process

- In the current implementation, when a signal is sent to the reading process,
  read is cancelled by calling usb_ep_dequeue, which lead into calling
  acc_complete_out with ECONNRESET, but the current logic treats it as
  disconnection, which makes the device inaccessible until cable is actually
  disconnected.
- The fix calls disconnect only when ESHUTDOWN error is passed.
- If data has already arrived while trying cancelling, the data is marked
  as available, and it will be read out on the next read. This is necessary
  as USB bulk is assumed to guarantee no data loss.

Signed-off-by: keunyoung <keunyoung@google.com>