{"push_id":1164670473,"size":6,"distinct_size":6,"ref":"refs/heads/cm-13.0","head":"50da13e81364aeb1208aa8729922c08a88da0578","before":"d8aca6605383ed814dd724ce05a5950f20107bdc","commits":[{"sha":"d810c4720d2065413dff8175839c121af60e2025","author":{"name":"Se Wang (Patrick) Oh","email":"1601fcf1961c6cf2d9004dabb5cab361cf16ec34@codeaurora.org"},"message":"workqueue: Fix workqueue stall issue after cpu down failure\n\nWhen the hotplug notifier call chain with CPU_DOWN_PREPARE\nis broken before reaching workqueue_cpu_down_callback(),\nrebind_workers() adds WORKER_REBOUND flag for running workers.\nHence, the nr_running of the pool is not increased when scheduler\nwakes up the worker. The fix is skipping adding WORKER_REBOUND\nflag when the worker doesn't have WORKER_UNBOUND flag in\nCPU_DOWN_FAILED path.\n\nChange-Id: I2528e9154f4913d9ec14b63adbcbcd1eaa8a8452\nSigned-off-by: Se Wang (Patrick) Oh <sewango@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/danielpinto8zz6/android_kernel_xiaomi_kenzo/commits/d810c4720d2065413dff8175839c121af60e2025"},{"sha":"da79b01b999781e32336535c2b233dd23a037020","author":{"name":"Saravana Kannan","email":"1af4e9628f955364122a1d7a403db0e5c0d6f70d@codeaurora.org"},"message":"PM / devfreq: governor_cpufreq: Fix incorrect refcounting of OF node\n\nThe of_node_put(of_child) call was put in to balance the of_node_get()\nthat's done inside for_each_child_of_node(). But that's not the right thing\nto do because for_each_child_of_node() already takes care of doing\nof_node_put(). So, delete the unnecessary of_node_put(of_child) call. We\nstill need the of_node_put(of_par) though.\n\nChange-Id: Iff7744839cfcf01d5a472449f74859e9030b7e16\nSigned-off-by: Saravana Kannan <skannan@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/danielpinto8zz6/android_kernel_xiaomi_kenzo/commits/da79b01b999781e32336535c2b233dd23a037020"},{"sha":"3f72c19b8a8b491dfb4f3c3a6df580d2a42c695f","author":{"name":"Thomas Gleixner","email":"352b5f5ba0189d2583768a9bb8247f98115b9038@linutronix.de"},"message":"sched: Queue RT tasks to head when prio drops\n\ncommit 81a44c5441d7f7d2c3dc9105f4d65ad0d5818617 upstream.\n\nThe following scenario does not work correctly:\n\nRunqueue of CPUx contains two runnable and pinned tasks:\n\n T1: SCHED_FIFO, prio 80\n T2: SCHED_FIFO, prio 80\n\nT1 is on the cpu and executes the following syscalls (classic priority\nceiling scenario):\n\n sys_sched_setscheduler(pid(T1), SCHED_FIFO, .prio = 90);\n ...\n sys_sched_setscheduler(pid(T1), SCHED_FIFO, .prio = 80);\n ...\n\nNow T1 gets preempted by T3 (SCHED_FIFO, prio 95). After T3 goes back\nto sleep the scheduler picks T2. Surprise!\n\nThe same happens w/o actual preemption when T1 is forced into the\nscheduler due to a sporadic NEED_RESCHED event. The scheduler invokes\npick_next_task() which returns T2. So T1 gets preempted and scheduled\nout.\n\nThis happens because sched_setscheduler() dequeues T1 from the prio 90\nlist and then enqueues it on the tail of the prio 80 list behind T2.\nThis violates the POSIX spec and surprises user space which relies on\nthe guarantee that SCHED_FIFO tasks are not scheduled out unless they\ngive the CPU up voluntarily or are preempted by a higher priority\ntask. In the latter case the preempted task must get back on the CPU\nafter the preempting task schedules out again.\n\nWe fixed a similar issue already in commit 60db48c (sched: Queue a\ndeboosted task to the head of the RT prio queue). The same treatment\nis necessary for sched_setscheduler(). So enqueue to head of the prio\nbucket list if the priority of the task is lowered.\n\nIt might be possible that existing user space relies on the current\nbehaviour, but it can be considered highly unlikely due to the corner\ncase nature of the application scenario.\n\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/1391803122-4425-6-git-send-email-bigeasy@linutronix.de\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/danielpinto8zz6/android_kernel_xiaomi_kenzo/commits/3f72c19b8a8b491dfb4f3c3a6df580d2a42c695f"},{"sha":"57f6eb67fc427d2d31042b584abd3f2fca6fc9b7","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"sched/core: Fix an SMP ordering race in try_to_wake_up() vs. schedule()\n\nOleg noticed that its possible to falsely observe p->on_cpu == 0 such\nthat we'll prematurely continue with the wakeup and effectively run p on\ntwo CPUs at the same time.\n\nEven though the overlap is very limited; the task is in the middle of\nbeing scheduled out; it could still result in corruption of the\nscheduler data structures.\n\n        CPU0                            CPU1\n\n        set_current_state(...)\n\n        <preempt_schedule>\n          context_switch(X, Y)\n            prepare_lock_switch(Y)\n              Y->on_cpu = 1;\n            finish_lock_switch(X)\n              store_release(X->on_cpu, 0);\n\n                                        try_to_wake_up(X)\n                                          LOCK(p->pi_lock);\n\n                                          t = X->on_cpu; // 0\n\n          context_switch(Y, X)\n            prepare_lock_switch(X)\n              X->on_cpu = 1;\n            finish_lock_switch(Y)\n              store_release(Y->on_cpu, 0);\n        </preempt_schedule>\n\n        schedule();\n          deactivate_task(X);\n          X->on_rq = 0;\n\n                                          if (X->on_rq) // false\n\n                                          if (t) while (X->on_cpu)\n                                            cpu_relax();\n\n          context_switch(X, ..)\n            finish_lock_switch(X)\n              store_release(X->on_cpu, 0);\n\nAvoid the load of X->on_cpu being hoisted over the X->on_rq load.\n\nReported-by: Oleg Nesterov <oleg@redhat.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Mike Galbraith <efault@gmx.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/danielpinto8zz6/android_kernel_xiaomi_kenzo/commits/57f6eb67fc427d2d31042b584abd3f2fca6fc9b7"},{"sha":"85dc7df330e0221b76c795fcc8405f9b8bc337b7","author":{"name":"Frederic Weisbecker","email":"fe7fea42e1cb0b94cea2acd3bec755592d0c9ba0@gmail.com"},"message":"cputime: Fix jiffies based cputime assumption on steal accounting\n\nThe steal guest time accounting code assumes that cputime_t is based on\njiffies. So when CONFIG_NO_HZ_FULL=y, which implies that cputime_t\nis based on nsecs, steal_account_process_tick() passes the delta in\njiffies to account_steal_time() which then accounts it as if it's a\nvalue in nsecs.\n\nAs a result, accounting 1 second of steal time (with HZ=100 that would\nbe 100 jiffies) is spuriously accounted as 100 nsecs.\n\nAs such /proc/stat may report 0 values of steal time even when two\nguests have run concurrently for a few seconds on the same host and\nsame CPU.\n\nIn order to fix this, lets convert the nsecs based steal delta to\ncputime instead of jiffies by using the right conversion API.\n\nGiven that the steal time is stored in cputime_t and this type can have\na smaller granularity than nsecs, we only account the rounded converted\nvalue and leave the remaining nsecs for the next deltas.\n\nReported-by: Huiqingding <huding@redhat.com>\nReported-by: Marcelo Tosatti <mtosatti@redhat.com>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Marcelo Tosatti <mtosatti@redhat.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nAcked-by: Rik van Riel <riel@redhat.com>\nSigned-off-by: Frederic Weisbecker <fweisbec@gmail.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/danielpinto8zz6/android_kernel_xiaomi_kenzo/commits/85dc7df330e0221b76c795fcc8405f9b8bc337b7"},{"sha":"50da13e81364aeb1208aa8729922c08a88da0578","author":{"name":"franciscofranco","email":"0ac3193ff3d7b4e68ae404d59f776924e2be9ac9@gmail.com"},"message":"cpufreq: interactive: remove boost and boostpulse sysfs nodes to prevent 'average joe' mis-usage\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/danielpinto8zz6/android_kernel_xiaomi_kenzo/commits/50da13e81364aeb1208aa8729922c08a88da0578"}]}
{"actor":{"display_login":"danielpinto8zz6"}}