{"push_id":673749506,"size":28,"distinct_size":0,"ref":"refs/heads/cm-12.1-franco","head":"5a215a64f8ad571107716a8ad4edc4fb27a65e79","before":"cbfb6e2982b0004374a87601902001e796b8732f","commits":[{"sha":"a96ac3de6d6350e1e8345764202db977b1a0d140","author":{"email":"9ae5c07c97a9b7156a654b92d02148f372178dd2@gmail.com","name":"Eduard Alfonso"},"message":"Revert \"soundcontrol: add speaker boost control.\"\n\nThis reverts commit 01d88ce1934d046662568c8d949a6ae6acc7821b.","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/a96ac3de6d6350e1e8345764202db977b1a0d140"},{"sha":"2f07c5c258ec85d028bbf9799f58cafedd6b12ad","author":{"email":"9ae5c07c97a9b7156a654b92d02148f372178dd2@gmail.com","name":"Eduard Alfonso"},"message":"Revert \"sound_control: add workaround for sound boost resets. Based on https://github.com/faux123/Nexus_5/commit/33407fd2d63290540eb0054bc7c6611f2080ea8b\"\n\nThis reverts commit 8a028d064ec8ab3d9b41acf6c0065d4933816532.","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/2f07c5c258ec85d028bbf9799f58cafedd6b12ad"},{"sha":"ad67c75111e0434699e3f408261082169d7f1e46","author":{"email":"9ae5c07c97a9b7156a654b92d02148f372178dd2@gmail.com","name":"Eduard Alfonso"},"message":"Revert \"sound_control: just some cosmetic changes.\"\n\nThis reverts commit 2550b6badcc9714becbff2a92d984b1576a729b0.","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/ad67c75111e0434699e3f408261082169d7f1e46"},{"sha":"83faa5b93dda03a754697358c0dcc5e6ffcc7903","author":{"email":"9ae5c07c97a9b7156a654b92d02148f372178dd2@gmail.com","name":"Eduard Alfonso"},"message":"Revert \"sound_control: update how the new values get applied writing and reading them directly from the tabla registries. This will fix the breakage caused by 4.3.\"\n\nThis reverts commit cd3e8c1360230b19597eb3685b2a09c333125b8b.","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/83faa5b93dda03a754697358c0dcc5e6ffcc7903"},{"sha":"732283a4f18af1ef76a27373380d6223dace2f18","author":{"email":"9ae5c07c97a9b7156a654b92d02148f372178dd2@gmail.com","name":"Eduard Alfonso"},"message":"Revert \"sound_control: add basic sound control.\"\n\nThis reverts commit f48b117041386f622a32b63e0e6ebc674cfe17d6.\n\nConflicts:\n\tdrivers/misc/Makefile","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/732283a4f18af1ef76a27373380d6223dace2f18"},{"sha":"103ac7a7210d7e89f778407e3ee88625a4db6451","author":{"email":"f2a4cf793007be8f81a774dc7806c1ffea7b4a2c@intel.com","name":"Zhang Rui"},"message":"PM: Introduce suspend state PM_SUSPEND_FREEZE\n\nPM_SUSPEND_FREEZE state is a general state that\ndoes not need any platform specific support, it equals\nfrozen processes + suspended devices + idle processors.\n\nCompared with PM_SUSPEND_MEMORY,\nPM_SUSPEND_FREEZE saves less power\nbecause the system is still in a running state.\nPM_SUSPEND_FREEZE has less resume latency because it does not\ntouch BIOS, and the processors are in idle state.\n\nCompared with RTPM/idle,\nPM_SUSPEND_FREEZE saves more power as\n1. the processor has longer sleep time because processes are frozen.\n   The deeper c-state the processor supports, more power saving we can get.\n2. PM_SUSPEND_FREEZE uses system suspend code path, thus we can get\n   more power saving from the devices that does not have good RTPM support.\n\nThis state is useful for\n1) platforms that do not have STR, or have a broken STR.\n2) platforms that have an extremely low power idle state,\n   which can be used to replace STR.\n\nThe following describes how PM_SUSPEND_FREEZE state works.\n1. echo freeze > /sys/power/state\n2. the processes are frozen.\n3. all the devices are suspended.\n4. all the processors are blocked by a wait queue\n5. all the processors idles and enters (Deep) c-state.\n6. an interrupt fires.\n7. a processor is woken up and handles the irq.\n8. if it is a general event,\n   a) the irq handler runs and quites.\n   b) goto step 4.\n9. if it is a real wake event, say, power button pressing, keyboard touch, mouse moving,\n   a) the irq handler runs and activate the wakeup source\n   b) wakeup_source_activate() notifies the wait queue.\n   c) system starts resuming from PM_SUSPEND_FREEZE\n10. all the devices are resumed.\n11. all the processes are unfrozen.\n12. system is back to working.\n\nKnown Issue:\nThe wakeup of this new PM_SUSPEND_FREEZE state may behave differently\nfrom the previous suspend state.\nTake ACPI platform for example, there are some GPEs that only enabled\nwhen the system is in sleep state, to wake the system backk from S3/S4.\nBut we are not touching these GPEs during transition to PM_SUSPEND_FREEZE.\nThis means we may lose some wake event.\nBut on the other hand, as we do not disable all the Interrupts during\nPM_SUSPEND_FREEZE, we may get some extra \"wakeup\" Interrupts, that are\nnot available for S3/S4.\n\nThe patches has been tested on an old Sony laptop, and here are the results:\n\nAverage Power:\n1. RPTM/idle for half an hour:\n   14.8W, 12.6W, 14.1W, 12.5W, 14.4W, 13.2W, 12.9W\n2. Freeze for half an hour:\n   11W, 10.4W, 9.4W, 11.3W 10.5W\n3. RTPM/idle for three hours:\n   11.6W\n4. Freeze for three hours:\n   10W\n5. Suspend to Memory:\n   0.5~0.9W\n\nAverage Resume Latency:\n1. RTPM/idle with a black screen: (From pressing keyboard to screen back)\n   Less than 0.2s\n2. Freeze: (From pressing power button to screen back)\n   2.50s\n3. Suspend to Memory: (From pressing power button to screen back)\n   4.33s\n\n>From the results, we can see that all the platforms should benefit from\nthis patch, even if it does not have Low Power S0.\n\nSigned-off-by: Zhang Rui <rui.zhang@intel.com>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tkernel/power/main.c\n\tkernel/power/suspend.c\n\nConflicts:\n\tdrivers/base/power/wakeup.c\n\tkernel/power/suspend.c","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/103ac7a7210d7e89f778407e3ee88625a4db6451"},{"sha":"cf5cc03832397046163e115038d46ae05856221d","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire. From http://ripke.com/loadavg/moire\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/cf5cc03832397046163e115038d46ae05856221d"},{"sha":"f98186e779b2cfe9599503864e6cf6ba5badc96d","author":{"email":"7d26b35203412f18a7dea4f8e1db1a75b1c5b706@semaphore.gr","name":"Stratos Karafotis"},"message":"cpufreq: Break out early if freq equals to target_freq\n\nSigned-off-by: Stratos Karafotis <stratosk@semaphore.gr>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/f98186e779b2cfe9599503864e6cf6ba5badc96d"},{"sha":"4380bfe18842cdcc1969d27fca7f491eb0bc565b","author":{"email":"7d26b35203412f18a7dea4f8e1db1a75b1c5b706@semaphore.gr","name":"Stratos Karafotis"},"message":"cpufreq: Initial CPU utilization should be 0\n\nSigned-off-by: Stratos Karafotis <stratosk@semaphore.gr>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/4380bfe18842cdcc1969d27fca7f491eb0bc565b"},{"sha":"a05fb27b86aa42e23cb3dbf6e2e84926347d9a63","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"wlan: just shut up...\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tdrivers/staging/prima/CORE/MAC/src/pe/lim/limProcessActionFrame.c","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/a05fb27b86aa42e23cb3dbf6e2e84926347d9a63"},{"sha":"81f681de75356c68c7e97e0ec31bfbcf46c48a86","author":{"email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@arm.linux.org.uk","name":"Russell King"},"message":"ARM: make kernel oops easier to read\n\nWe don't need the offset for the first function name in each backtrace\nentry; this needlessly consumes screen space.  This is virtually always\nthe first or second instruction in the called function.\n\nAlso, recognise stmfd instructions which include r10 as a valid stack\nsaving instruction, and when dumping the registers, dump six registers\nper line rather than five, and fix the wrapping.\n\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tarch/arm/kernel/traps.c","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/81f681de75356c68c7e97e0ec31bfbcf46c48a86"},{"sha":"cffbe3af683a4bbacbaee4b762fb3bf0296b06af","author":{"email":"4c9eb49378914b743bdd32292c04df29b820d73e@cn.fujitsu.com","name":"Lai Jiangshan"},"message":"kthread_work: wake up worker only when the worker is idle\n\nIf the worker is already executing a work item when another is queued,\nwe can safely skip wakeup without worrying about stalling queue thus\navoiding waking up the busy worker spuriously.  Spurious wakeups\nshould be fine but still isn't nice and avoiding it is trivial here.\n\ntj: Updated description.\n\nSigned-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>\nSigned-off-by: Tejun Heo <tj@kernel.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/cffbe3af683a4bbacbaee4b762fb3bf0296b06af"},{"sha":"49375908209e60e60665e30ea13107b3b4b5a413","author":{"email":"de609eb4d5d70b1d38ec6642adbfc33a2781f63c@zeniv.linux.org.uk","name":"Al Viro"},"message":"nick kvfree() from apparmor\n\ntoo many places open-code it\n\nConflicts:\n\tmm/util.c\n\nBug: 17871993\nChange-Id: I007f4b663d7af564b2ce4009f5e13eeeeb82929a\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>\nGit-commit: 39f1f78d53b9bcbca91967380c5f0f2305a5c55f\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\n[jgebben@codeaurora.org: Remove redundant apparmor code not present upstream]\nSigned-off-by: Jeremy Gebben <jgebben@codeaurora.org>\nSigned-off-by: Naveen Ramaraj <nramaraj@codeaurora.org>\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/49375908209e60e60665e30ea13107b3b4b5a413"},{"sha":"e4ca4e155ff5632c5d09d9918547082e695af30f","author":{"email":"331be22c6b63ca3e0a03d408c2d906b1b02cd5f2@cmpxchg.org","name":"Johannes Weiner"},"message":"mm/page-writeback.c: fix dirty_balance_reserve subtraction from dirtyable memory\n\nTejun reported stuttering and latency spikes on a system where random\ntasks would enter direct reclaim and get stuck on dirty pages.  Around\n50% of memory was occupied by tmpfs backed by an SSD, and another disk\n(rotating) was reading and writing at max speed to shrink a partition.\n\n: The problem was pretty ridiculous.  It's a 8gig machine w/ one ssd and 10k\n: rpm harddrive and I could reliably reproduce constant stuttering every\n: several seconds for as long as buffered IO was going on on the hard drive\n: either with tmpfs occupying somewhere above 4gig or a test program which\n: allocates about the same amount of anon memory.  Although swap usage was\n: zero, turning off swap also made the problem go away too.\n:\n: The trigger conditions seem quite plausible - high anon memory usage w/\n: heavy buffered IO and swap configured - and it's highly likely that this\n: is happening in the wild too.  (this can happen with copying large files\n: to usb sticks too, right?)\n\nThis patch (of 2):\n\nThe dirty_balance_reserve is an approximation of the fraction of free\npages that the page allocator does not make available for page cache\nallocations.  As a result, it has to be taken into account when\ncalculating the amount of \"dirtyable memory\", the baseline to which\ndirty_background_ratio and dirty_ratio are applied.\n\nHowever, currently the reserve is subtracted from the sum of free and\nreclaimable pages, which is non-sensical and leads to erroneous results\nwhen the system is dominated by unreclaimable pages and the\ndirty_balance_reserve is bigger than free+reclaimable.  In that case, at\nleast the already allocated cache should be considered dirtyable.\n\nFix the calculation by subtracting the reserve from the amount of free\npages, then adding the reclaimable pages on top.\n\n[akpm@linux-foundation.org: fix CONFIG_HIGHMEM build]\nSigned-off-by: Johannes Weiner <hannes@cmpxchg.org>\nReported-by: Tejun Heo <tj@kernel.org>\nTested-by: Tejun Heo <tj@kernel.org>\nReviewed-by: Rik van Riel <riel@redhat.com>\nCc: Mel Gorman <mgorman@suse.de>\nCc: Wu Fengguang <fengguang.wu@intel.com>\nReviewed-by: Michal Hocko <mhocko@suse.cz>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tmm/page-writeback.c","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/e4ca4e155ff5632c5d09d9918547082e695af30f"},{"sha":"7a4b16591d1d104cd50671d2981164d512545ac4","author":{"email":"5c915a589b3ddf58cebf14bec41bcc143b37ac3c@kernel.org","name":"Namhyung Kim"},"message":"selinux: simple cleanup for cond_read_node()\n\nThe node->cur_state and len can be read in a single call of next_entry().\nAnd setting len before reading is a dead write so can be eliminated.\n\nSigned-off-by: Namhyung Kim <namhyung@kernel.org>\n(Minor tweak to the length parameter in the call to next_entry())\nSigned-off-by: Paul Moore <pmoore@redhat.com>\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/7a4b16591d1d104cd50671d2981164d512545ac4"},{"sha":"3092d6ee116f6b577eee277e8b17daf6fd221b80","author":{"email":"5c915a589b3ddf58cebf14bec41bcc143b37ac3c@kernel.org","name":"Namhyung Kim"},"message":"selinux: fix a possible memory leak in cond_read_node()\n\nThe cond_read_node() should free the given node on error path as it's\nnot linked to p->cond_list yet.  This is done via cond_node_destroy()\nbut it's not called when next_entry() fails before the expr loop.\n\nSigned-off-by: Namhyung Kim <namhyung@kernel.org>\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/3092d6ee116f6b577eee277e8b17daf6fd221b80"},{"sha":"0b3866874d9f16de0dc2f78d4e47ba0586bcb8ac","author":{"email":"a123fdd9fb50e93f03393cfddab9c182b4164439@hp.com","name":"Waiman Long"},"message":"selinux: no recursive read_lock of policy_rwlock in security_genfs_sid()\n\nWith the introduction of fair queued rwlock, recursive read_lock()\nmay hang the offending process if there is a write_lock() somewhere\nin between.\n\nWith recursive read_lock checking enabled, the following error was\nreported:\n\n=============================================\n[ INFO: possible recursive locking detected ]\n3.16.0-rc1 #2 Tainted: G            E\n---------------------------------------------\nload_policy/708 is trying to acquire lock:\n (policy_rwlock){.+.+..}, at: [<ffffffff8125b32a>]\nsecurity_genfs_sid+0x3a/0x170\n\nbut task is already holding lock:\n (policy_rwlock){.+.+..}, at: [<ffffffff8125b48c>]\nsecurity_fs_use+0x2c/0x110\n\nother info that might help us debug this:\n Possible unsafe locking scenario:\n\n       CPU0\n       ----\n  lock(policy_rwlock);\n  lock(policy_rwlock);\n\nThis patch fixes the occurrence of recursive read_lock() of\npolicy_rwlock by adding a helper function __security_genfs_sid()\nwhich requires caller to take the lock before calling it. The\nsecurity_fs_use() was then modified to call the new helper function.\n\nSigned-off-by: Waiman Long <Waiman.Long@hp.com>\nAcked-by:  Stephen Smalley <sds@tycho.nsa.gov>\nSigned-off-by: Paul Moore <pmoore@redhat.com>\n\nConflicts:\n\n\tsecurity/selinux/ss/services.c\n\n(Adapted for Shamu 3.10 Kernel)\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/0b3866874d9f16de0dc2f78d4e47ba0586bcb8ac"},{"sha":"55871e2a9891a16947726463f22dadf51eda7133","author":{"email":"d5ec0d24602845f6f4b6a35ef729998d1fba5507@redhat.com","name":"Dave Jones"},"message":"selinux: conditionally reschedule in mls_convert_context while loading selinux policy\n\nOn a slow machine (with debugging enabled), upgrading selinux policy may take\na considerable amount of time. Long enough that the softlockup detector\ngets triggered.\n\nThe backtrace looks like this..\n\n > BUG: soft lockup - CPU#2 stuck for 23s! [load_policy:19045]\n > Call Trace:\n >  [<ffffffff81221ddf>] symcmp+0xf/0x20\n >  [<ffffffff81221c27>] hashtab_search+0x47/0x80\n >  [<ffffffff8122e96c>] mls_convert_context+0xdc/0x1c0\n >  [<ffffffff812294e8>] convert_context+0x378/0x460\n >  [<ffffffff81229170>] ? security_context_to_sid_core+0x240/0x240\n >  [<ffffffff812221b5>] sidtab_map+0x45/0x80\n >  [<ffffffff8122bb9f>] security_load_policy+0x3ff/0x580\n >  [<ffffffff810788a8>] ? sched_clock_cpu+0xa8/0x100\n >  [<ffffffff810786dd>] ? sched_clock_local+0x1d/0x80\n >  [<ffffffff810788a8>] ? sched_clock_cpu+0xa8/0x100\n >  [<ffffffff8103096a>] ? __change_page_attr_set_clr+0x82a/0xa50\n >  [<ffffffff810786dd>] ? sched_clock_local+0x1d/0x80\n >  [<ffffffff810788a8>] ? sched_clock_cpu+0xa8/0x100\n >  [<ffffffff8103096a>] ? __change_page_attr_set_clr+0x82a/0xa50\n >  [<ffffffff810788a8>] ? sched_clock_cpu+0xa8/0x100\n >  [<ffffffff81534ddc>] ? retint_restore_args+0xe/0xe\n >  [<ffffffff8109c82d>] ? trace_hardirqs_on_caller+0xfd/0x1c0\n >  [<ffffffff81279a2e>] ? trace_hardirqs_on_thunk+0x3a/0x3f\n >  [<ffffffff810d28a8>] ? rcu_irq_exit+0x68/0xb0\n >  [<ffffffff81534ddc>] ? retint_restore_args+0xe/0xe\n >  [<ffffffff8121e947>] sel_write_load+0xa7/0x770\n >  [<ffffffff81139633>] ? vfs_write+0x1c3/0x200\n >  [<ffffffff81210e8e>] ? security_file_permission+0x1e/0xa0\n >  [<ffffffff8113952b>] vfs_write+0xbb/0x200\n >  [<ffffffff811581c7>] ? fget_light+0x397/0x4b0\n >  [<ffffffff81139c27>] SyS_write+0x47/0xa0\n >  [<ffffffff8153bde4>] tracesys+0xdd/0xe2\n\nStephen Smalley suggested:\n\n > Maybe put a cond_resched() within the ebitmap_for_each_positive_bit()\n > loop in mls_convert_context()?\n\nThat seems to do the trick. Tested by downgrading and re-upgrading selinux-policy-targeted.\n\nSigned-off-by: Dave Jones <davej@redhat.com>\nAcked-by: Stephen Smalley <sds@tycho.nsa.gov>\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/55871e2a9891a16947726463f22dadf51eda7133"},{"sha":"244265bf92c6297e8746c77b950d01feb4362ce9","author":{"email":"d5ec0d24602845f6f4b6a35ef729998d1fba5507@redhat.com","name":"Dave Jones"},"message":"selinux: conditionally reschedule in hashtab_insert while loading selinux policy\n\nAfter silencing the sleeping warning in mls_convert_context() I started\nseeing similar traces from hashtab_insert. Do a cond_resched there too.\n\nSigned-off-by: Dave Jones <davej@redhat.com>\nAcked-by: Stephen Smalley <sds@tycho.nsa.gov>\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/244265bf92c6297e8746c77b950d01feb4362ce9"},{"sha":"91b81da15bd6d6ac7b9afc4351f0ff660580d231","author":{"email":"45d857216ef082c1ddfd5d3991b4f3d23f51761f@arcor.de","name":"myfluxi"},"message":"msm: kgsl: Report correct GPU frequency in sysfs\n\nChange-Id: I1aac90d0554b9de0511ffb78042177a5a23855ce\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tdrivers/gpu/msm/kgsl_pwrctrl.c","distinct":false,"url":"https://api.github.com/repos/xsynergy510x/android_kernel_samsung_jf/commits/91b81da15bd6d6ac7b9afc4351f0ff660580d231"}]}