{"push_id":1372955721,"size":5,"distinct_size":5,"ref":"refs/heads/cm-14.0-caf","head":"b4015e45d53cc448a8d81dd82d82b0dd31cae759","before":"554dfc5e169becd0248f3db6f8c6280319d726e4","commits":[{"sha":"a2006a9152726e5949421206621b774e371140cf","author":{"name":"Srinivasarao P","email":"5838be2f68866147a6b98dc0567ce3ec89ebe5fc@codeaurora.org"},"message":"ion: use %pk instead of %p which respects kptr_restrict sysctl\n\nHide kernel pointers from unprivileged users by using %pk format-specifier\ninstead of %p. This respects the kptr_restrict sysctl setting which is by\ndefault on. So by default %pk will print zeroes as address. echo 1 to\nkptr_restrict to print proper kernel address.\n\nChange-Id: Ia300e3e38b8662afac15edda28959564b05c9367\nSigned-off-by: Satyajit Desai <sadesai@codeaurora.org>\nSigned-off-by: Srinivasarao P <spathi@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/morphvale/android_kernel_lge_hammerhead/commits/a2006a9152726e5949421206621b774e371140cf"},{"sha":"396bb0c9eb2ae4ca3964275526d46d565540da4b","author":{"name":"Ravi Kumar Siddojigari","email":"a6954ed8cb4bc79ef2481a88f7c11520d3703eed@codeaurora.org"},"message":"nput: synaptics_dsx: allocate heap memory for temp buf\n\nThere is a possible stack overflow vulnerability in the rmidev_write\nfunction because the stack array size is from user space.\nchanges to allocate heap memory for the temporary buffer instead of\nstack memory to prevent the stack overflow vulnerability.\nAs discussed under  CVE-2016-3865 and ANDROID-28799389.\n\nChange-Id: I20f639e09aaf3c533c98a12a2413570feae3d6d0\nSigned-off-by: Ravi Kumar Siddojigari <rsiddoji@codeaurora.org>\nSigned-off-by: Shantanu Jain <shjain@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/morphvale/android_kernel_lge_hammerhead/commits/396bb0c9eb2ae4ca3964275526d46d565540da4b"},{"sha":"f7919c2746418bd988f45b11ecd113804a9c6e5e","author":{"name":"Suzuki K. Poulose","email":"239e6ad0fed873c6240fa61c5ed99f611cd6b279@arm.com"},"message":"ARM: perf: reject groups spanning multiple hardware PMUs\n\nThe perf core implicitly rejects events spanning multiple HW PMUs, as in\nthese cases the event->ctx will differ. However this validation is\nperformed after pmu::event_init() is called in perf_init_event(), and\nthus pmu::event_init() may be called with a group leader from a\ndifferent HW PMU.\n\nThe ARM PMU driver does not take this fact into account, and when\nvalidating groups assumes that it can call to_arm_pmu(event->pmu) for\nany HW event. When the event in question is from another HW PMU this is\nwrong, and results in dereferencing garbage.\n\nThis patch updates the ARM PMU driver to first test for and reject\nevents from other PMUs, moving the to_arm_pmu and related logic after\nthis test. Fixes a crash triggered by perf_fuzzer on Linux-4.0-rc2, with\na CCI PMU present:\n\n ---\nCPU: 0 PID: 1527 Comm: perf_fuzzer Not tainted 4.0.0-rc2 #57\nHardware name: ARM-Versatile Express\ntask: bd8484c0 ti: be676000 task.ti: be676000\nPC is at 0xbf1bbc90\nLR is at validate_event+0x34/0x5c\npc : [<bf1bbc90>]    lr : [<80016060>]    psr: 00000013\n...\n[<80016060>] (validate_event) from [<80016198>] (validate_group+0x28/0x90)\n[<80016198>] (validate_group) from [<80016398>] (armpmu_event_init+0x150/0x218)\n[<80016398>] (armpmu_event_init) from [<800882e4>] (perf_try_init_event+0x30/0x48)\n[<800882e4>] (perf_try_init_event) from [<8008f544>] (perf_init_event+0x5c/0xf4)\n[<8008f544>] (perf_init_event) from [<8008f8a8>] (perf_event_alloc+0x2cc/0x35c)\n[<8008f8a8>] (perf_event_alloc) from [<8009015c>] (SyS_perf_event_open+0x498/0xa70)\n[<8009015c>] (SyS_perf_event_open) from [<8000e420>] (ret_fast_syscall+0x0/0x34)\nCode: bf1be000 bf1bb380 802a2664 00000000 (00000002)\n---[ end trace 01aff0ff00926a0a ]---\n\nAlso cleans up the code to use the arm_pmu only when we know that\nwe are dealing with an arm pmu event.\n\nCc: Will Deacon <will.deacon@arm.com>\nAcked-by: Mark Rutland <mark.rutland@arm.com>\nAcked-by: Peter Ziljstra (Intel) <peterz@infradead.org>\nSigned-off-by: Suzuki K. Poulose <suzuki.poulose@arm.com>\nSigned-off-by: Will Deacon <will.deacon@arm.com>\nGit-commit: e429817b401f095ac483fcb02524b01faf45dad6\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nChange-Id: I3b9a0078f7a4cd5370ed177c8bd1438c09425eb4\nSigned-off-by: Patrick Fay <pfay@codeaurora.com>\nSigned-off-by: Chetan Ravindranath <cravin@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/morphvale/android_kernel_lge_hammerhead/commits/f7919c2746418bd988f45b11ecd113804a9c6e5e"},{"sha":"3f3860c3d0c2753b6490f8de1b68e289b8b4c90a","author":{"name":"Arve Hjønnevåg","email":"252c00e8bf89f12b2f75a1e0ab87a5ad019cda88@android.com"},"message":"ANDROID: binder: Clear binder and cookie when setting handle in flat binder struct\n\nPrevents leaking pointers between processes\n\nBUG: 30768347\nChange-Id: Id898076926f658a1b8b27a3ccb848756b36de4ca\nSigned-off-by: Arve Hjønnevåg <arve@android.com>\nGit-repo: https://android.googlesource.com/kernel/msm.git\nGit-commit: 11032d745836280574827bb1db5e64a94945180e\nSigned-off-by: Dennis Cagle <d-cagle@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/morphvale/android_kernel_lge_hammerhead/commits/3f3860c3d0c2753b6490f8de1b68e289b8b4c90a"},{"sha":"b4015e45d53cc448a8d81dd82d82b0dd31cae759","author":{"name":"Linus Torvalds","email":"ead7104581934751970e9decb2db5deb20a9e407@linux-foundation.org"},"message":"mm: remove gup_flags FOLL_WRITE games from __get_user_pages()\n\nThis is an ancient bug that was actually attempted to be fixed once\n(badly) by me eleven years ago in commit 4ceb5db9757a (\"Fix\nget_user_pages() race for write access\") but that was then undone due to\nproblems on s390 by commit f33ea7f404e5 (\"fix get_user_pages bug\").\n\nIn the meantime, the s390 situation has long been fixed, and we can now\nfix it by checking the pte_dirty() bit properly (and do it better).  The\ns390 dirty bit was implemented in abf09bed3cce (\"s390/mm: implement\nsoftware dirty bits\") which made it into v3.9.  Earlier kernels will\nhave to look at the page state itself.\n\nAlso, the VM has become more scalable, and what used a purely\ntheoretical race back then has become easier to trigger.\n\nTo fix it, we introduce a new internal FOLL_COW flag to mark the \"yes,\nwe already did a COW\" rather than play racy games with FOLL_WRITE that\nis very fundamental, and then use the pte dirty flag to validate that\nthe FOLL_COW flag is still valid.\n\nChange-Id: If344e2da83dd3d852d265846204c68fd2b30f72e\nReported-and-tested-by: Phil \"not Paul\" Oester <kernel@linuxace.com>\nAcked-by: Hugh Dickins <hughd@google.com>\nReviewed-by: Michal Hocko <mhocko@suse.com>\nCc: Andy Lutomirski <luto@kernel.org>\nCc: Kees Cook <keescook@chromium.org>\nCc: Oleg Nesterov <oleg@redhat.com>\nCc: Willy Tarreau <w@1wt.eu>\nCc: Nick Piggin <npiggin@gmail.com>\nCc: Greg Thelen <gthelen@google.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/morphvale/android_kernel_lge_hammerhead/commits/b4015e45d53cc448a8d81dd82d82b0dd31cae759"}]}
{"actor":{"display_login":"morphvale"}}