{"push_id":1375877271,"size":22,"distinct_size":10,"ref":"refs/heads/cm-13.0","head":"3be8cca38ee58e09b22e0ed217ec0081707a3640","before":"e31262a31d8d176501e8cf499f0d2060b993109f","commits":[{"sha":"fbeeefddeaad029551f7915676b7b12b0f61c7a6","author":{"name":"Srinivasarao P","email":"5838be2f68866147a6b98dc0567ce3ec89ebe5fc@codeaurora.org"},"message":"perf: duplicate deletion of perf event\n\na malicious app can open a perf event with constraint_duplicate\nbit set, disable the event, and close the fd.  On closing the fd,\nthe perf_release() modification causes the kernel to clean up\nthe event as if it still were enabled, leading to the event\nbeing removed from a list twice.\n\nCRs-Fixed: 977563\nChange-Id: I5fbec3722407d2f3d0ff0d9f7097c5889e31fd62\nSigned-off-by: Srinivasarao P <spathi@codeaurora.org>","distinct":false,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/fbeeefddeaad029551f7915676b7b12b0f61c7a6"},{"sha":"354d9ee7441393b3a6ec64363b945b3ff3baf122","author":{"name":"Weiyin Jiang","email":"25745fd6cb0247e11bcb32583c6893d37cc23b30@codeaurora.org"},"message":"ASoC: msm: audio-effects: misc fixes in h/w accelerated effect\n\nAdding memory copy size check and integer overflow check in h/w\naccelerated effect driver.\n\nChange-Id: I17d4cc0a38770f0c5067fa8047cd63e7bf085e48\nCRs-Fixed: 1006609\nSigned-off-by: Weiyin Jiang <wjiang@codeaurora.org>","distinct":false,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/354d9ee7441393b3a6ec64363b945b3ff3baf122"},{"sha":"b1de487865b297b2858c540509672a741a3c9bce","author":{"name":"Vijayavardhan Vennapusa","email":"fd1e89cda16e187a1514e87daf32db280e01223d@qti.qualcomm.com"},"message":"USB: dwc3: debugfs: Add boundary check in dwc3_store_ep_num()\n\nUser can pass arguments as part of write to requests and endpoint number\nwill be calculated based on the arguments. There is a chance that driver\ncan access ep structue that is not allocated due to invalid arguments\npassed by user. Hence fix the issue by having check and return error in\ncase of invalid arguments.\n\nBug: 28172322\n\nChange-Id: I8afd964a7b6d92a5889e1195720d8fe7d32fd357\nSigned-off-by: Vijayavardhan Vennapusa <vvreddy@qti.qualcomm.com>","distinct":false,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/b1de487865b297b2858c540509672a741a3c9bce"},{"sha":"3f482f103d30c0310339e4ea65bfb5d66af3eab0","author":{"name":"Veena Sambasivan","email":"f3dea2712a9835ef757537fe50b353b17bceb98a@codeaurora.org"},"message":"msm: perf: Do not allocate new hw_event if event is duplicate.\n\nDuring a perf_event_enable, kernel/events/core.c calls pmu->add() which\nis platform implementation(arch/arm/kernel/perf_event.c). Due to the\nduplicate constraints, arch/arm/mach-msm/perf_event_msm_krait_l2.c\ndrivers marks the event as OFF but returns TRUE to perf_event.c which\ngoes ahead and allocates the hw_event and enables it.\nSince event is marked OFF, kernel events core will try to enable this event\nagain during next perf_event_enable. Which results in same event enabled\non multiple hw_events. But during the perf_release, event struct is freed\nand only one hw_event is released. This results in dereferencing the\ninvalid pointer and hence the crash.\nFix this by returning error in case of constraint event duplicate. Hence\navoiding the same event programmed on multiple hw event counters.\n\nbug: 28172137\nChange-Id: I20c368bd982f26983465dd5addd88071e1b16231\nSigned-off-by: Arun KS <arunks@codeaurora.org>\nSigned-off-by: Veena Sambasivan <veenas@codeaurora.org>","distinct":false,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/3f482f103d30c0310339e4ea65bfb5d66af3eab0"},{"sha":"29ac661fd908460450dca5f2a4be8b1988f16484","author":{"name":"Arnaldo Carvalho de Melo","email":"7310a59577712e001e6abd523e66592d8f2dc989@redhat.com"},"message":"UPSTREAM: net: Fix use after free in the recvmmsg exit path\n\n(cherry picked from commit 34b88a68f26a75e4fded796f1a49c40f82234b7d)\n\nThe syzkaller fuzzer hit the following use-after-free:\n\n  Call Trace:\n   [<ffffffff8175ea0e>] __asan_report_load8_noabort+0x3e/0x40 mm/kasan/report.c:295\n   [<ffffffff851cc31a>] __sys_recvmmsg+0x6fa/0x7f0 net/socket.c:2261\n   [<     inline     >] SYSC_recvmmsg net/socket.c:2281\n   [<ffffffff851cc57f>] SyS_recvmmsg+0x16f/0x180 net/socket.c:2270\n   [<ffffffff86332bb6>] entry_SYSCALL_64_fastpath+0x16/0x7a\n  arch/x86/entry/entry_64.S:185\n\nAnd, as Dmitry rightly assessed, that is because we can drop the\nreference and then touch it when the underlying recvmsg calls return\nsome packets and then hit an error, which will make recvmmsg to set\nsock->sk->sk_err, oops, fix it.\n\nReported-and-Tested-by: Dmitry Vyukov <dvyukov@google.com>\nCc: Alexander Potapenko <glider@google.com>\nCc: Eric Dumazet <edumazet@google.com>\nCc: Kostya Serebryany <kcc@google.com>\nCc: Sasha Levin <sasha.levin@oracle.com>\nFixes: a2e2725541fa (\"net: Introduce recvmmsg socket syscall\")\nhttp://lkml.kernel.org/r/20160122211644.GC2470@redhat.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nChange-Id: I2adb0faf595b7b634d9b739dfdd1a47109e20ecb\nBug: 30515201","distinct":false,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/29ac661fd908460450dca5f2a4be8b1988f16484"},{"sha":"1f3ebbcc6fb40b21dd19ca22b8a5b584de426f67","author":{"name":"Eric Dumazet","email":"b3d77ad2db30f558882cc0c038be5a3cf96611f9@google.com"},"message":"tcp: fix use after free in tcp_xmit_retransmit_queue()\n\nWhen tcp_sendmsg() allocates a fresh and empty skb, it puts it at the\ntail of the write queue using tcp_add_write_queue_tail()\n\nThen it attempts to copy user data into this fresh skb.\n\nIf the copy fails, we undo the work and remove the fresh skb.\n\nUnfortunately, this undo lacks the change done to tp->highest_sack and\nwe can leave a dangling pointer (to a freed skb)\n\nLater, tcp_xmit_retransmit_queue() can dereference this pointer and\naccess freed memory. For regular kernels where memory is not unmapped,\nthis might cause SACK bugs because tcp_highest_sack_seq() is buggy,\nreturning garbage instead of tp->snd_nxt, but with various debug\nfeatures like CONFIG_DEBUG_PAGEALLOC, this can crash the kernel.\n\nThis bug was found by Marco Grassi thanks to syzkaller.\n\nChange-Id: Ie370d5464d513364ac27a57bf57b3c770703e038\nFixes: 6859d49475d4 (\"[TCP]: Abstract tp->highest_sack accessing & point to next skb\")\nReported-by: Marco Grassi <marco.gra@gmail.com>\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nCc: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>\nCc: Yuchung Cheng <ycheng@google.com>\nCc: Neal Cardwell <ncardwell@google.com>\nAcked-by: Neal Cardwell <ncardwell@google.com>\nReviewed-by: Cong Wang <xiyou.wangcong@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/1f3ebbcc6fb40b21dd19ca22b8a5b584de426f67"},{"sha":"60dfece72437c3fe686fb2a3786ae1a2a12f3bfd","author":{"name":"Nick Desaulniers","email":"b951273a67bf33267cd4dff69171cdef4e5efbe7@google.com"},"message":"binder: prevent kptr leak by using %pK format specifier\n\nWorks in conjunction with kptr_restrict.\nBug: 30143283\n\nChange-Id: I2b3ce22f4e206e74614d51453a1d59b7080ab05a","distinct":false,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/60dfece72437c3fe686fb2a3786ae1a2a12f3bfd"},{"sha":"17c289e73e5ab2331ab577dd34ebc885a55b4fb6","author":{"name":"Nick Desaulniers","email":"b951273a67bf33267cd4dff69171cdef4e5efbe7@google.com"},"message":"fs: ext4: disable support for fallocate FALLOC_FL_PUNCH_HOLE\n\nBug: 28760453\nChange-Id: I019c2de559db9e4b95860ab852211b456d78c4ca\nSigned-off-by: Nick Desaulniers <ndesaulniers@google.com>","distinct":false,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/17c289e73e5ab2331ab577dd34ebc885a55b4fb6"},{"sha":"3cde896260d2e1363c4038ab65a5cbee06c925d3","author":{"name":"Lars-Peter Clausen","email":"7f698333860e9f21dcc513102ebee3bcaf8d683e@metafoo.de"},"message":"ALSA: control: Fix replacing user controls\n\ncommit 82262a46627bebb0febcc26664746c25cef08563 upstream.\n\nThere are two issues with the current implementation for replacing user\ncontrols. The first is that the code does not check if the control is actually a\nuser control and neither does it check if the control is owned by the process\nthat tries to remove it. That allows userspace applications to remove arbitrary\ncontrols, which can cause a user after free if a for example a driver does not\nexpect a control to be removed from under its feed.\n\nThe second issue is that on one hand when a control is replaced the\nuser_ctl_count limit is not checked and on the other hand the user_ctl_count is\nincreased (even though the number of user controls does not change). This allows\nuserspace, once the user_ctl_count limit as been reached, to repeatedly replace\na control until user_ctl_count overflows. Once that happens new controls can be\nadded effectively bypassing the user_ctl_count limit.\n\nBoth issues can be fixed by instead of open-coding the removal of the control\nthat is to be replaced to use snd_ctl_remove_user_ctl(). This function does\nproper permission checks as well as decrements user_ctl_count after the control\nhas been removed.\n\nNote that by using snd_ctl_remove_user_ctl() the check which returns -EBUSY at\nbeginning of the function if the control already exists is removed. This is not\na problem though since the check is quite useless, because the lock that is\nprotecting the control list is released between the check and before adding the\nnew control to the list, which means that it is possible that a different\ncontrol with the same settings is added to the list after the check. Luckily\nthere is another check that is done while holding the lock in snd_ctl_add(), so\nwe'll rely on that to make sure that the same control is not added twice.\n\nChange-Id: Ia77569e4ab4427579d29ea9b73f1dfad5a037eb6\nSigned-off-by: Lars-Peter Clausen <lars@metafoo.de>\nAcked-by: Jaroslav Kysela <perex@perex.cz>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/3cde896260d2e1363c4038ab65a5cbee06c925d3"},{"sha":"7e0456747cb4ef25a1f44a59496f047d05cb6f69","author":{"name":"Mohamad Ayyash","email":"a63011e6db47c5624401b2ef01e42a84436c0cfe@google.com"},"message":"Replace %p with %pK to prevent leaking kernel address\n\nBUG: 27532522\nChange-Id: Ic0710a9a8cfc682acd88ecf3bbfeece2d798c4a4\nSigned-off-by: Mohamad Ayyash <mkayyash@google.com>","distinct":false,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/7e0456747cb4ef25a1f44a59496f047d05cb6f69"},{"sha":"624eea59e43eb34b813011aa4822e30651996fec","author":{"name":"kangjie","email":"c6dbead15f805a0881e9469feef97d17b99af2f6@gmail.com"},"message":"fix infoleak in rtnetlink\n\nthe stack object “map” has a total size of 32 bytes. Its last 4\nbytes are padding generated by compiler. These padding bytes are\nnot initialized and sent out via “nla_put”\n\nBug: 28620102\n\nChange-Id: I13da380c6fe8abca49e3cf9f05293c02b44d2e5e\nSigned-off-by: kangjie <kangjielu@gmail.com>","distinct":false,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/624eea59e43eb34b813011aa4822e30651996fec"},{"sha":"39749499da00f3b12137c3d1cafb852b91d6c091","author":{"name":"David Howells","email":"358fdf7bce8223edb2a0d846104bf62a286894d5@redhat.com"},"message":"KEYS: Fix short sprintf buffer in /proc/keys show function\n\nFix a short sprintf buffer in proc_keys_show().  If the gcc stack protector\nis turned on, this can cause a panic due to stack corruption.\n\nThe problem is that xbuf[] is not big enough to hold a 64-bit timeout\nrendered as weeks:\n\n\t(gdb) p 0xffffffffffffffffULL/(60*60*24*7)\n\t$2 = 30500568904943\n\nThat's 14 chars plus NUL, not 11 chars plus NUL.\n\nExpand the buffer to 16 chars.\n\nI think the unpatched code apparently works if the stack-protector is not\nenabled because on a 32-bit machine the buffer won't be overflowed and on a\n64-bit machine there's a 64-bit aligned pointer at one side and an int that\nisn't checked again on the other side.\n\nThe panic incurred looks something like:\n\nKernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ffffffff81352ebe\nCPU: 0 PID: 1692 Comm: reproducer Not tainted 4.7.2-201.fc24.x86_64 #1\nHardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011\n 0000000000000086 00000000fbbd2679 ffff8800a044bc00 ffffffff813d941f\n ffffffff81a28d58 ffff8800a044bc98 ffff8800a044bc88 ffffffff811b2cb6\n ffff880000000010 ffff8800a044bc98 ffff8800a044bc30 00000000fbbd2679\nCall Trace:\n [<ffffffff813d941f>] dump_stack+0x63/0x84\n [<ffffffff811b2cb6>] panic+0xde/0x22a\n [<ffffffff81352ebe>] ? proc_keys_show+0x3ce/0x3d0\n [<ffffffff8109f7f9>] __stack_chk_fail+0x19/0x30\n [<ffffffff81352ebe>] proc_keys_show+0x3ce/0x3d0\n [<ffffffff81350410>] ? key_validate+0x50/0x50\n [<ffffffff8134db30>] ? key_default_cmp+0x20/0x20\n [<ffffffff8126b31c>] seq_read+0x2cc/0x390\n [<ffffffff812b6b12>] proc_reg_read+0x42/0x70\n [<ffffffff81244fc7>] __vfs_read+0x37/0x150\n [<ffffffff81357020>] ? security_file_permission+0xa0/0xc0\n [<ffffffff81246156>] vfs_read+0x96/0x130\n [<ffffffff81247635>] SyS_read+0x55/0xc0\n [<ffffffff817eb872>] entry_SYSCALL_64_fastpath+0x1a/0xa4\n\nChange-Id: I0787d5a38c730ecb75d3c08f28f0ab36295d59e7\nReported-by: Ondrej Kozina <okozina@redhat.com>\nSigned-off-by: David Howells <dhowells@redhat.com>\nTested-by: Ondrej Kozina <okozina@redhat.com>","distinct":false,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/39749499da00f3b12137c3d1cafb852b91d6c091"},{"sha":"b149a0882aeea5403dfea719ac4a329eedbcb299","author":{"name":"Linus Torvalds","email":"ead7104581934751970e9decb2db5deb20a9e407@linux-foundation.org"},"message":"mm: remove gup_flags FOLL_WRITE games from __get_user_pages()\n\ncommit 19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619 upstream.\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: I83a08fd1f9c8928c0ed95286f737c27cc7811576\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>\n[wt: s/gup.c/memory.c; s/follow_page_pte/follow_page_mask;\n     s/faultin_page/__get_user_page]\nSigned-off-by: Willy Tarreau <w@1wt.eu>\nSigned-off-by: Paul Keith <javelinanddart@gmail.com>","distinct":true,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/b149a0882aeea5403dfea719ac4a329eedbcb299"},{"sha":"fe577665479aad12b93ce067b7089e12da276e0b","author":{"name":"Ethan Chen","email":"a4be59b0060802f8152b97d5dee17f7985566e1e@gmail.com"},"message":"platform: msm: Fix compile when CONFIG_PFT is not set\n\nChange-Id: I29eb3b7d55162b80aab722a0d53621a98ed5703d\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/fe577665479aad12b93ce067b7089e12da276e0b"},{"sha":"b3c653f9fca56a0d8d22d69ade77484407b3d62f","author":{"name":"Greg Wallace","email":"8952803a140aef085feef90060e9454201c5d910@gregtwallace.com"},"message":"Disable L1/L2 Cache Error Kernel Panic\n\nThe following can occur during normal phone use:\n\n[ 8971.294545 / 10-20 18:41:38.815] L2 Error detected!\n[ 8971.294554 / 10-20 18:41:38.815] L2ESR    = 0x00010001\n[ 8971.294561 / 10-20 18:41:38.815] L2ESYNR0 = 0x20006000\n[ 8971.294567 / 10-20 18:41:38.815] L2ESYNR1 = 0x00205401\n[ 8971.294573 / 10-20 18:41:38.815] L2EAR0   = 0x20800028\n[ 8971.294579 / 10-20 18:41:38.815] L2EAR1   = 0x00000008\n[ 8971.294585 / 10-20 18:41:38.815] CPU bitmap = 0x1\n[ 8971.294591 / 10-20 18:41:38.815] L2 master port decode error\n[ 8971.294599 / 10-20 18:41:38.815] Kernel panic - not syncing: L2 master port error detected\n\nKernel should not panic in production environment for this type of\nerror.\n\nAlso disable causing kernel panic on a couple of other errors that\nshould not cause panic.\n\nChange-Id: Id45cd67b35037999382ec1e0036c07b26dd2954d","distinct":true,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/b3c653f9fca56a0d8d22d69ade77484407b3d62f"},{"sha":"4a9a381c681f23ef7d41d598169e5c50e9889eec","author":{"name":"Aarushi Girdhar","email":"d0b11fae8e44422fa8538a9a962368b62f82e017@codeaurora.org"},"message":"g2: dts: msm: Update DSI PHY lane configuration settings for LGE dts\n\nWe initially picked 989ae9b76e727f05c05e2b204de3d4ef04798b70, however,\nLG uses a custom DSI PHY lane in the g2 dts, which overrides the MSM\nconfiguration. This applies the same fix to the custom DTS used.\n\nThis should fix a graphical glitch that occurs sometimes while switching\napps, as the intial commit aims to fix.\n\nChange-Id: I9184b476111cbb8aa9335c1c9e4c3e804b124b41","distinct":true,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/4a9a381c681f23ef7d41d598169e5c50e9889eec"},{"sha":"c35d2db4dd56b6b879cbb66af8a64a85604f4747","author":{"name":"Jaganath Kanakkassery","email":"b1803504bdc91c6b87292801bbc34df5d0b85920@samsung.com"},"message":"BACKPORT: Bluetooth: Fix potential NULL dereference in RFCOMM bind callback\n\n(cherry picked from 951b6a0717db97ce420547222647bcc40bf1eacd)\n\naddr can be NULL and it should not be dereferenced before NULL checking.\n\nSigned-off-by: Jaganath Kanakkassery <jaganath.k@samsung.com>\nSigned-off-by: Marcel Holtmann <marcel@holtmann.org>\nChange-Id: I18bda54bb1427d9443a39a04a5c551720118dc26\nBug: 30149612","distinct":true,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/c35d2db4dd56b6b879cbb66af8a64a85604f4747"},{"sha":"7d2b1d367dc8e17e47c191f2cac0ae2975269a07","author":{"name":"Biswajit Paul","email":"7ee5649c8de55a61a3bbcbc7dcde16c04b2f65da@codeaurora.org"},"message":"msm: ipa: fix potential race condition ioctls\n\nThere are numerous potential race condition\nioctls in the IPA driver. The fix is to add\ncheck wherever it copies arguments from\nuser-space memory and process.\n\nBug: 28919863\nCRs-Fixed: 1037897\nChange-Id: I5a440f89153518507acdf5dad42625503732e59a\nSigned-off-by: Skylar Chang <chiaweic@codeaurora.org>\nSigned-off-by: Biswajit Paul <biswajitpaul@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/7d2b1d367dc8e17e47c191f2cac0ae2975269a07"},{"sha":"1b82ee16d3e0e049f31381a97dfa080abc98d6a5","author":{"name":"Biswajit Paul","email":"7ee5649c8de55a61a3bbcbc7dcde16c04b2f65da@codeaurora.org"},"message":"spmi: prevent showing the address of spmidev\n\nCreating devices with the address of the container spmidev is not\nindicative of the actual hardware device it represents.\n\nInstead use an unique id to indicate the device it represents.\n\nBug: 28760543\nCRs-Fixed: 1024197\nChange-Id: Id18e2a19f4fa1249901a3f275defa8f589270d69\nSigned-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>\nSigned-off-by: Biswajit Paul <biswajitpaul@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/blastagator/LGG2_Kernel/commits/1b82ee16d3e0e049f31381a97dfa080abc98d6a5"},{"sha":"dd0440023f94ad4d8d3ac0fb1a71c8024fd050d4","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/blastagator/LGG2_Kernel/commits/dd0440023f94ad4d8d3ac0fb1a71c8024fd050d4"}]}
{"actor":{"display_login":"blastagator"}}