{"push_id":1078078525,"size":10,"distinct_size":10,"ref":"refs/heads/cmatest4","head":"1072898091c4a5e2060008c54e2178de1d7127ce","before":"ef80291d7e8813a564a319ac987e7eccfd138e14","commits":[{"sha":"0abf53971732608ff35921aca694475bf0f8519d","author":{"email":"672d2df060548742c9b53de1776a2ea1684fbe5a@gmail.com","name":"voidz777"},"message":"out_of_memory","distinct":true,"url":"https://api.github.com/repos/v0idz777/android_kernel_samsung_tuna_omap4/commits/0abf53971732608ff35921aca694475bf0f8519d"},{"sha":"48f026ec76f2fce4eef2360bec44fe5b731564bc","author":{"email":"d8cd2994e15bc61ddb2b113030bda55eebc3a0fe@google.com","name":"David Rientjes"},"message":"mm, memcg: pass charge order to oom killer\n\nThe oom killer typically displays the allocation order at the time of oom\nas a part of its diangostic messages (for global, cpuset, and mempolicy\nooms).\n\nThe memory controller may also pass the charge order to the oom killer so\nit can emit the same information.  This is useful in determining how large\nthe memory allocation is that triggered the oom killer.\n\nSigned-off-by: David Rientjes <rientjes@google.com>\nCc: Johannes Weiner <hannes@cmpxchg.org>\nCc: Michal Hocko <mhocko@suse.cz>\nCc: Balbir Singh <bsingharora@gmail.com>\nAcked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n\nConflicts:\n\tinclude/linux/memcontrol.h\n\tmm/memcontrol.c","distinct":true,"url":"https://api.github.com/repos/v0idz777/android_kernel_samsung_tuna_omap4/commits/48f026ec76f2fce4eef2360bec44fe5b731564bc"},{"sha":"b251196c6068ab126192326e6753c7b52d1fdb73","author":{"email":"20b70f0af00562e63758b9ee42012ecc96c58590@redhat.com","name":"Oleg Nesterov"},"message":"signal: oom_kill_task: use SEND_SIG_FORCED instead of force_sig()\n\nChange oom_kill_task() to use do_send_sig_info(SEND_SIG_FORCED) instead\nof force_sig(SIGKILL).  With the recent changes we do not need force_ to\nkill the CLONE_NEWPID tasks.\n\nAnd this is more correct.  force_sig() can race with the exiting thread\neven if oom_kill_task() checks p->mm != NULL, while\ndo_send_sig_info(group => true) kille the whole process.\n\nSigned-off-by: Oleg Nesterov <oleg@redhat.com>\nCc: Tejun Heo <tj@kernel.org>\nCc: Anton Vorontsov <anton.vorontsov@linaro.org>\nCc: \"Eric W. Biederman\" <ebiederm@xmission.com>\nCc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>\nCc: David Rientjes <rientjes@google.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/v0idz777/android_kernel_samsung_tuna_omap4/commits/b251196c6068ab126192326e6753c7b52d1fdb73"},{"sha":"026a9f945eeed025423a1f00108443aa253f4f4f","author":{"email":"d8cd2994e15bc61ddb2b113030bda55eebc3a0fe@google.com","name":"David Rientjes"},"message":"mm, oom: normalize oom scores to oom_score_adj scale only for userspace\n\nThe oom_score_adj scale ranges from -1000 to 1000 and represents the\nproportion of memory available to the process at allocation time.  This\nmeans an oom_score_adj value of 300, for example, will bias a process as\nthough it was using an extra 30.0% of available memory and a value of\n-350 will discount 35.0% of available memory from its usage.\n\nThe oom killer badness heuristic also uses this scale to report the oom\nscore for each eligible process in determining the \"best\" process to\nkill.  Thus, it can only differentiate each process's memory usage by\n0.1% of system RAM.\n\nOn large systems, this can end up being a large amount of memory: 256MB\non 256GB systems, for example.\n\nThis can be fixed by having the badness heuristic to use the actual\nmemory usage in scoring threads and then normalizing it to the\noom_score_adj scale for userspace.  This results in better comparison\nbetween eligible threads for kill and no change from the userspace\nperspective.\n\nSuggested-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>\nTested-by: Dave Jones <davej@redhat.com>\nSigned-off-by: David Rientjes <rientjes@google.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n\nConflicts:\n\tmm/oom_kill.c","distinct":true,"url":"https://api.github.com/repos/v0idz777/android_kernel_samsung_tuna_omap4/commits/026a9f945eeed025423a1f00108443aa253f4f4f"},{"sha":"5ff265e6ba98da363046321b09846a1cb060bde1","author":{"email":"d8cd2994e15bc61ddb2b113030bda55eebc3a0fe@google.com","name":"David Rientjes"},"message":"mm, oom: fix badness score underflow\n\nIf the privileges given to root threads (3% of allowable memory) or a\nnegative value of /proc/pid/oom_score_adj happen to exceed the amount of\nrss of a thread, its badness score overflows as a result of commit\na7f638f999ff (\"mm, oom: normalize oom scores to oom_score_adj scale only\nfor userspace\").\n\nFix this by making the type signed and return 1, meaning the thread is\nstill eligible for kill, if the value is negative.\n\nReported-by: Dave Jones <davej@redhat.com>\nAcked-by: Oleg Nesterov <oleg@redhat.com>\nSigned-off-by: David Rientjes <rientjes@google.com>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/v0idz777/android_kernel_samsung_tuna_omap4/commits/5ff265e6ba98da363046321b09846a1cb060bde1"},{"sha":"8f052809de30144e68b84a131549479138890cb1","author":{"email":"d8cd2994e15bc61ddb2b113030bda55eebc3a0fe@google.com","name":"David Rientjes"},"message":"mm, oom: fix and cleanup oom score calculations\n\nThe divide in p->signal->oom_score_adj * totalpages / 1000 within\noom_badness() was causing an overflow of the signed long data type.\n\nThis adds both the root bias and p->signal->oom_score_adj before doing the\nnormalization which fixes the issue and also cleans up the calculation.\n\nTested-by: Dave Jones <davej@redhat.com>\nSigned-off-by: David Rientjes <rientjes@google.com>\nCc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/v0idz777/android_kernel_samsung_tuna_omap4/commits/8f052809de30144e68b84a131549479138890cb1"},{"sha":"726fb040b29df18102d1591e1d7cb3fb276c6fe9","author":{"email":"d65ea3c90af7aca4df42e0739d75ec70ee406024@linux.vnet.ibm.com","name":"Wanpeng Li"},"message":"mm: fix kernel-doc warnings\n\nFix kernel-doc warnings such as\n\n  Warning(../mm/page_cgroup.c:432): No description found for parameter 'id'\n  Warning(../mm/page_cgroup.c:432): Excess function parameter 'mem' description in 'swap_cgroup_record'\n\nSigned-off-by: Wanpeng Li <liwp@linux.vnet.ibm.com>\nCc: Randy Dunlap <randy.dunlap@oracle.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n\nConflicts:\n\tmm/memblock.c","distinct":true,"url":"https://api.github.com/repos/v0idz777/android_kernel_samsung_tuna_omap4/commits/726fb040b29df18102d1591e1d7cb3fb276c6fe9"},{"sha":"9423b83d669855fcd5598a24956cc9c0e80df6ae","author":{"email":"d8cd2994e15bc61ddb2b113030bda55eebc3a0fe@google.com","name":"David Rientjes"},"message":"mm, oom: do not schedule if current has been killed\n\nThe oom killer currently schedules away from current in an uninterruptible\nsleep if it does not have access to memory reserves.  It's possible that\ncurrent was killed because it shares memory with the oom killed thread or\nbecause it was killed by the user in the interim, however.\n\nThis patch only schedules away from current if it does not have a pending\nkill, i.e.  if it does not share memory with the oom killed thread.  It's\npossible that it will immediately retry its memory allocation and fail,\nbut it will immediately be given access to memory reserves if it calls the\noom killer again.\n\nThis prevents the delay of memory freeing when threads that share memory\nwith the oom killed thread get unnecessarily scheduled.\n\nSigned-off-by: David Rientjes <rientjes@google.com>\nCc: Oleg Nesterov <oleg@redhat.com>\nAcked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>\nAcked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/v0idz777/android_kernel_samsung_tuna_omap4/commits/9423b83d669855fcd5598a24956cc9c0e80df6ae"},{"sha":"b132cfffd739e4fe8c8f6869b0bd53ef8926c604","author":{"email":"d8cd2994e15bc61ddb2b113030bda55eebc3a0fe@google.com","name":"David Rientjes"},"message":"mm, oom: fix potential killing of thread that is disabled from oom killing\n\n/proc/sys/vm/oom_kill_allocating_task will immediately kill current when\nthe oom killer is called to avoid a potentially expensive tasklist scan\nfor large systems.\n\nCurrently, however, it is not checking current's oom_score_adj value which\nmay be OOM_SCORE_ADJ_MIN, meaning that it has been disabled from oom\nkilling.\n\nThis patch avoids killing current in such a condition and simply falls\nback to the tasklist scan since memory still needs to be freed.\n\nSigned-off-by: David Rientjes <rientjes@google.com>\nCc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\nAcked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/v0idz777/android_kernel_samsung_tuna_omap4/commits/b132cfffd739e4fe8c8f6869b0bd53ef8926c604"},{"sha":"1072898091c4a5e2060008c54e2178de1d7127ce","author":{"email":"672d2df060548742c9b53de1776a2ea1684fbe5a@gmail.com","name":"voidz777"},"message":"config","distinct":true,"url":"https://api.github.com/repos/v0idz777/android_kernel_samsung_tuna_omap4/commits/1072898091c4a5e2060008c54e2178de1d7127ce"}]}