{"push_id":933703086,"size":4,"distinct_size":4,"ref":"refs/heads/unity","head":"78910ef98ec423b02117f0ba09c14ce26f1ffc79","before":"893cf6489c3194f33a2c163e98b1a3855fdcf3c7","commits":[{"sha":"8bdd9ced9d92b80037d90bf487dc6fdc9ad77095","author":{"email":"577f74ec3f2c8a155237d5ad42a70103d17f8313@codeaurora.org","name":"Vikram Mulukutla"},"message":"soc: qcom: smem: Zero out ramdump segment memory\n\nThe ramdump API uses fields other than those used by\nthe smem driver. Ensure that the ramdump segment structure\nfields are zeroed out by using kcalloc instead of kmalloc_array.\n\nChange-Id: I3e7139024d25d99e9fde89a54a18b131d418b1bc\nSigned-off-by: Vikram Mulukutla <markivx@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/maxice8/android_kernel_oneplus_msm8974/commits/8bdd9ced9d92b80037d90bf487dc6fdc9ad77095"},{"sha":"ae05ad50ea90c7e9f522286db4dd270162bfa005","author":{"email":"e36519ed998e577ca4306dc3c35b89f0bef834f3@codeaurora.org","name":"Arun Kumar Neelakantam"},"message":"soc: qcom: smem: use remote spinlock try lock\n\nIf a remote subsystem resets while holding the remote spinlock and APPs\nis trying to acquire the same remote spinlock, then SSR does not get\nhandled and the system eventually crashes due to a deadlock.\n\nUse remote_spinlock_trylock_irqsave() instead of remote_spinlock_irqsave()\nwhich allows the CPU to handle the pending interrupts if remote spinlock\nis not available.\n\nCRs-Fixed: 932028\nChange-Id: I88716abf5bfd9a85495733cffe6df9e8e827c1b5\nSigned-off-by: Arun Kumar Neelakantam <aneela@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/maxice8/android_kernel_oneplus_msm8974/commits/ae05ad50ea90c7e9f522286db4dd270162bfa005"},{"sha":"8a902a971dbe066ba8729c322d529f2acbab64b3","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>","distinct":true,"url":"https://api.github.com/repos/maxice8/android_kernel_oneplus_msm8974/commits/8a902a971dbe066ba8729c322d529f2acbab64b3"},{"sha":"78910ef98ec423b02117f0ba09c14ce26f1ffc79","author":{"email":"de609eb4d5d70b1d38ec6642adbfc33a2781f63c@zeniv.linux.org.uk","name":"Al Viro"},"message":"stop passing nameidata * to ->d_revalidate()\n\nJust the lookup flags.  Die, bastard, die...\n\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>\n\nConflicts:\n\tfs/nfs/dir.c","distinct":true,"url":"https://api.github.com/repos/maxice8/android_kernel_oneplus_msm8974/commits/78910ef98ec423b02117f0ba09c14ce26f1ffc79"}]}