{"push_id":830245803,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"cb098e63f2323c61897813895cf76d623193a79c","before":"c1af3d6f62fe0367dfaa653398fea5e94e2e979c","commits":[{"sha":"f6620c9889908e508e42c289c236c96a0bdfbeea","author":{"email":"69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org","name":"Linus Torvalds"},"message":"Initialize msg/shm IPC objects before doing ipc_addid()\n\nAs reported by Dmitry Vyukov, we really shouldn't do ipc_addid() before\nhaving initialized the IPC object state.  Yes, we initialize the IPC\nobject in a locked state, but with all the lockless RCU lookup work,\nthat IPC object lock no longer means that the state cannot be seen.\n\nWe already did this for the IPC semaphore code (see commit e8577d1f0329:\n\"ipc/sem.c: fully initialize sem_array before making it visible\") but we\nclearly forgot about msg and shm.\n\nReported-by: Dmitry Vyukov <dvyukov@google.com>\nCc: Manfred Spraul <manfred@colorfullife.com>\nCc: Davidlohr Bueso <dbueso@suse.de>\nCc: stable@vger.kernel.org\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/cile381/H815_kernel/commits/f6620c9889908e508e42c289c236c96a0bdfbeea"},{"sha":"d37c165f0266b30d32d416f1cc212168dfc02ef0","author":{"email":"9d4b7fec34444d4f7b5bcba52a53fb47535914f4@motorola.com","name":"Yi-wei Zhao"},"message":"fs: support task's adj rbtree\n\nAdd (or del) a task to (or from) task's adj rbtree\nwhen its oom_score_adj is modified.\n\nChange-Id: I8a9490c6f30f42f6e4ed8f7fa9249f6da6177ae2\nSigned-off-by: Hong-Mei Li <a21834@motorola.com>\nSigned-off-by: Yi-wei Zhao <gbjc64@motorola.com>\nReviewed-on: http://gerrit.mot.com/701206\nSLTApproved: Slta Waiver <sltawvr@motorola.com>\nTested-by: Jira Key <jirakey@motorola.com>\nSubmit-Approved: Jira Key <jirakey@motorola.com>","distinct":true,"url":"https://api.github.com/repos/cile381/H815_kernel/commits/d37c165f0266b30d32d416f1cc212168dfc02ef0"},{"sha":"cb098e63f2323c61897813895cf76d623193a79c","author":{"email":"829500b200af6c2a0eca4dfd5c388e6b8fbe8dc6@suse.cz","name":"Michal Hocko"},"message":"OOM, PM: OOM killed task shouldn't escape PM suspend\n\nPM freezer relies on having all tasks frozen by the time devices are\ngetting frozen so that no task will touch them while they are getting\nfrozen. But OOM killer is allowed to kill an already frozen task in\norder to handle OOM situtation. In order to protect from late wake ups\nOOM killer is disabled after all tasks are frozen. This, however, still\nkeeps a window open when a killed task didn't manage to die by the time\nfreeze_processes finishes.\n\nReduce the race window by checking all tasks after OOM killer has been\ndisabled. This is still not race free completely unfortunately because\noom_killer_disable cannot stop an already ongoing OOM killer so a task\nmight still wake up from the fridge and get killed without\nfreeze_processes noticing. Full synchronization of OOM and freezer is,\nhowever, too heavy weight for this highly unlikely case.\n\nIntroduce and check oom_kills counter which gets incremented early when\nthe allocator enters __alloc_pages_may_oom path and only check all the\ntasks if the counter changes during the freezing attempt. The counter\nis updated so early to reduce the race window since allocator checked\noom_killer_disabled which is set by PM-freezing code. A false positive\nwill push the PM-freezer into a slow path but that is not a big deal.\n\nChanges since v1\n- push the re-check loop out of freeze_processes into\n  check_frozen_processes and invert the condition to make the code more\n  readable as per Rafael\n\nFixes: f660daac474c6f (oom: thaw threads if oom killed thread is frozen before deferring)\nCc: 3.2+ <stable@vger.kernel.org> # 3.2+\nSigned-off-by: Michal Hocko <mhocko@suse.cz>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/cile381/H815_kernel/commits/cb098e63f2323c61897813895cf76d623193a79c"}]}