{"push_id":2486300241,"size":134,"distinct_size":134,"ref":"refs/heads/oreo","head":"99283e255b55613f56ad427c92e2871cece32c56","before":"8c3f8271d486c400ca12501e96545bf680c86057","commits":[{"sha":"2b85a2656108c59fadc948462601c82f90bff7c9","author":{"name":"Fenglin Wu","email":"50206e71e59ec2e32aeb984bb9c01d540012d432@codeaurora.org"},"message":"platform: msm: gpio-usbdetect: Report charger types in REAL_TYPE\n\nCommit eca542a92350 (\"power: qpnp-smbcharger: Report charger types in\nREAL_TYPE property\") changes to use POWER_SUPPLY_PROP_REAL_TYPE\nproperty to report charger types between charger driver and USB\ndriver, so change the same in this driver to make sure USB driver\ncould get the correct charger type notification.\n\nChange-Id: Ia70e9a376a494c6c9d8905ff4017996eecc8d503\nSigned-off-by: Fenglin Wu <fenglinw@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/2b85a2656108c59fadc948462601c82f90bff7c9"},{"sha":"df197147c98ea3f0c49d33c366dad8fa83b5e7ef","author":{"name":"Linux Build Service Account","email":"d3c7bae90ce2477533ec852edf38b65198016249@localhost"},"message":"Merge \"platform: msm: gpio-usbdetect: Report charger types in REAL_TYPE\"","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/df197147c98ea3f0c49d33c366dad8fa83b5e7ef"},{"sha":"fbec9856bfa6f428eec3341720c6a366a861d5cb","author":{"name":"Linux Build Service Account","email":"d3c7bae90ce2477533ec852edf38b65198016249@localhost"},"message":"Merge df197147c98ea3f0c49d33c366dad8fa83b5e7ef on remote branch\n\nChange-Id: I032580e6a5f85446f6774c745628635e4240f8b9","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/fbec9856bfa6f428eec3341720c6a366a861d5cb"},{"sha":"663af193e6078fa2a70b13349434dd492487867d","author":{"name":"Sreelakshmi Gownipalli","email":"ca39c2cc03944f28ff9ea61882d0995994b72dbb@codeaurora.org"},"message":"diag: Prevent NULL pointer dereference while closing logging process\n\nPrevent NULL pointer dereference while copying the data to memory device\nprocess by adding mutex protection when closing the process.\n\nChange-Id: Idaad73fb8b2a0bb5a4983d5e255bfdf702cecf71\nSigned-off-by: Sreelakshmi Gownipalli <sgownipa@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/663af193e6078fa2a70b13349434dd492487867d"},{"sha":"cb59c729ef0831f253427a2eb87d984d345854ab","author":{"name":"Siena Richard","email":"ce9435c58b8735725aaefa4986eaeabed15107ac@codeaurora.org"},"message":"msm: qdsp6v2: update CVD version\n\nCVD version is updated to 2.3 on ADSP. Update the mapping\ntable in voice driver to allow CVD version 2.3 to be\nrecognized and used.\n\nChange-Id: Id6d1c960dc720e8013eb9ba1f07af7662b576e37\nCRs-Fixed: 1060201\nSigned-off-by: Siena Richard <sienar@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/cb59c729ef0831f253427a2eb87d984d345854ab"},{"sha":"400bc92595b07fecb7050a03cb7dc8083284fb67","author":{"name":"Maulik Shah","email":"8840d67f3f5aa4f0446868dbb0ab76aea5bd2cdc@codeaurora.org"},"message":"drivers : soc: qcom: mpm: Do not resend GPIO interrupts\n\nInterrupts configured as wakeup capable will be pending at both MPM\nand TLMM during system level LPMs. Since GPIO summary interrupt is\nlevel triggered, do not resend GPIO interrupts when exiting from system\nlevel LPMs.\n\nChange-Id: I63340396cf2764835d628906aa8e7c1278c88cec\nSigned-off-by: Maulik Shah <mkshah@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/400bc92595b07fecb7050a03cb7dc8083284fb67"},{"sha":"c614e8eb8408615a2e7cd1de468c2cbac2096a7a","author":{"name":"Linux Build Service Account","email":"d3c7bae90ce2477533ec852edf38b65198016249@localhost"},"message":"Merge \"msm: qdsp6v2: update CVD version\" into kernel.lnx.3.18.r33-rel","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/c614e8eb8408615a2e7cd1de468c2cbac2096a7a"},{"sha":"062aee898d80c642bf3a537e4a757eaf73bec8b5","author":{"name":"Linux Build Service Account","email":"d3c7bae90ce2477533ec852edf38b65198016249@localhost"},"message":"Merge \"drivers : soc: qcom: mpm: Do not resend GPIO interrupts\" into kernel.lnx.3.18.r33-rel","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/062aee898d80c642bf3a537e4a757eaf73bec8b5"},{"sha":"5a9f55d6d2e3b69944091602949e202c0942e488","author":{"name":"Artem Borisov","email":"f9463d398a2472ef5fe6578acbe4253a3e7c61e9@gmail.com"},"message":"Merge tag 'LA.UM.6.6.r1-07400-89xx.0' of https://source.codeaurora.org/quic/la/kernel/msm-3.18 into HEAD\n\n\"LA.UM.6.6.r1-07400-89xx.0\"","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/5a9f55d6d2e3b69944091602949e202c0942e488"},{"sha":"a5054873ca2d1240fbc66a196142290607eb088c","author":{"name":"Trond Myklebust","email":"cc958843532c615cbd4920e868f78c7985331a5a@primarydata.com"},"message":"NFSv4.1: RECLAIM_COMPLETE must handle NFS4ERR_CONN_NOT_BOUND_TO_SESSION\n\n\n[ Upstream commit 0048fdd06614a4ea088f9fcad11511956b795698 ]\n\nIf the server returns NFS4ERR_CONN_NOT_BOUND_TO_SESSION because we\nare trunking, then RECLAIM_COMPLETE must handle that by calling\nnfs4_schedule_session_recovery() and then retrying.\n\nReported-by: Chuck Lever <chuck.lever@oracle.com>\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>\nTested-by: Chuck Lever <chuck.lever@oracle.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/a5054873ca2d1240fbc66a196142290607eb088c"},{"sha":"51188ac2676d861fb53303a9a394b86f4e7467c6","author":{"name":"Bart Van Assche","email":"28563a2d387a4f8f033bf7abbf80937064dfbe0c@sandisk.com"},"message":"IB/srpt: Fix abort handling\n\n\n[ Upstream commit 55d694275f41a1c0eef4ef49044ff29bc3999490 ]\n\nLet the target core check the CMD_T_ABORTED flag instead of the SRP\ntarget driver. Hence remove the transport_check_aborted_status()\ncall. Since state == SRPT_STATE_CMD_RSP_SENT is something that really\nshould not happen, do not try to recover if srpt_queue_response() is\ncalled for an I/O context that is in that state. This patch is a bug\nfix because the srpt_abort_cmd() call is misplaced - if that function\nis called from srpt_queue_response() it should either be called\nbefore the command state is changed or after the response has been\nsent.\n\nSigned-off-by: Bart Van Assche <bart.vanassche@sandisk.com>\nReviewed-by: Hannes Reinecke <hare@suse.com>\nCc: Doug Ledford <dledford@redhat.com>\nCc: Christoph Hellwig <hch@lst.de>\nCc: Andy Grover <agrover@redhat.com>\nCc: David Disseldorp <ddiss@suse.de>\nSigned-off-by: Nicholas Bellinger <nab@linux-iscsi.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/51188ac2676d861fb53303a9a394b86f4e7467c6"},{"sha":"bc705996bb341187df2bbcbf1b6c2c1cf330ef40","author":{"name":"Steffen Klassert","email":"66deb1d63f85161cc287ce2bac0c65cb5ae958a7@secunet.com"},"message":"af_key: Fix slab-out-of-bounds in pfkey_compile_policy.\n\n\n[ Upstream commit d90c902449a7561f1b1d58ba5a0d11728ce8b0b2 ]\n\nThe sadb_x_sec_len is stored in the unit 'byte divided by eight'.\nSo we have to multiply this value by eight before we can do\nsize checks. Otherwise we may get a slab-out-of-bounds when\nwe memcpy the user sec_ctx.\n\nFixes: df71837d502 (\"[LSM-IPSec]: Security association restriction.\")\nReported-by: Andrey Konovalov <andreyknvl@google.com>\nTested-by: Andrey Konovalov <andreyknvl@google.com>\nSigned-off-by: Steffen Klassert <steffen.klassert@secunet.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/bc705996bb341187df2bbcbf1b6c2c1cf330ef40"},{"sha":"b3b0df34dd5eeab163f696e583ddbb9be5e887d5","author":{"name":"Luca Coelho","email":"48024ebf6407f04843f8b4062a045f41623c6d61@intel.com"},"message":"mac80211: bail out from prep_connection() if a reconfig is ongoing\n\n\n[ Upstream commit f8860ce836f2d502b07ef99559707fe55d90f5bc ]\n\nIf ieee80211_hw_restart() is called during authentication, the\nauthentication process will continue, causing the driver to be called\nin a wrong state.  This ultimately causes an oops in the iwlwifi\ndriver (at least).\n\nThis fixes bugzilla 195299 partly.\n\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=195299\nSigned-off-by: Luca Coelho <luciano.coelho@intel.com>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/b3b0df34dd5eeab163f696e583ddbb9be5e887d5"},{"sha":"f8f828fb92fc92d43b3d48a997fe5466d3d535fa","author":{"name":"Kees Cook","email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org"},"message":"bna: Avoid reading past end of buffer\n\n\n[ Upstream commit 9e4eb1ce472fbf7b007f23c88ec11c37265e401c ]\n\nUsing memcpy() from a string that is shorter than the length copied means\nthe destination buffer is being filled with arbitrary data from the kernel\nrodata segment. Instead, use strncpy() which will fill the trailing bytes\nwith zeros.\n\nThis was found with the future CONFIG_FORTIFY_SOURCE feature.\n\nCc: Daniel Micay <danielmicay@gmail.com>\nSigned-off-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/f8f828fb92fc92d43b3d48a997fe5466d3d535fa"},{"sha":"6b002c74c40dfe77d481a37c7c0a9a972a5c1089","author":{"name":"Kees Cook","email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org"},"message":"qlge: Avoid reading past end of buffer\n\n\n[ Upstream commit df5303a8aa9a0a6934f4cea7427f1edf771f21c2 ]\n\nUsing memcpy() from a string that is shorter than the length copied means\nthe destination buffer is being filled with arbitrary data from the kernel\nrodata segment. Instead, use strncpy() which will fill the trailing bytes\nwith zeros.\n\nThis was found with the future CONFIG_FORTIFY_SOURCE feature.\n\nCc: Daniel Micay <danielmicay@gmail.com>\nSigned-off-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/6b002c74c40dfe77d481a37c7c0a9a972a5c1089"},{"sha":"5a9afaaac6e5353b1643bed44f2dcc476c2f3431","author":{"name":"Grygorii Strashko","email":"bfa0a1520768723a1c60e18250fb841c342eb8d8@ti.com"},"message":"net: ethernet: ti: cpsw: adjust cpsw fifos depth for fullduplex flow control\n\n\n[ Upstream commit 48f5bccc60675f8426a6159935e8636a1fd89f56 ]\n\nWhen users set flow control using ethtool the bits are set properly in the\nCPGMAC_SL MACCONTROL register, but the FIFO depth in the respective Port n\nMaximum FIFO Blocks (Pn_MAX_BLKS) registers remains set to the minimum size\nreset value. When receive flow control is enabled on a port, the port's\nassociated FIFO block allocation must be adjusted. The port RX allocation\nmust increase to accommodate the flow control runout. The TRM recommends\nnumbers of 5 or 6.\n\nHence, apply required Port FIFO configuration to\nPn_MAX_BLKS.Pn_TX_MAX_BLKS=0xF and Pn_MAX_BLKS.Pn_RX_MAX_BLKS=0x5 during\ninterface initialization.\n\nCc: Schuyler Patton <spatton@ti.com>\nSigned-off-by: Grygorii Strashko <grygorii.strashko@ti.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/5a9afaaac6e5353b1643bed44f2dcc476c2f3431"},{"sha":"3bb16f97201a0a9f68573a2223460424f4b8a8e5","author":{"name":"J. Bruce Fields","email":"51738506c1b2ccb0761f23bdc612c93babf738ea@redhat.com"},"message":"lockd: fix lockd shutdown race\n\n\n[ Upstream commit efda760fe95ea15291853c8fa9235c32d319cd98 ]\n\nAs reported by David Jeffery: \"a signal was sent to lockd while lockd\nwas shutting down from a request to stop nfs.  The signal causes lockd\nto call restart_grace() which puts the lockd_net structure on the grace\nlist.  If this signal is received at the wrong time, it will occur after\nlockd_down_net() has called locks_end_grace() but before\nlockd_down_net() stops the lockd thread.  This leads to lockd putting\nthe lockd_net structure back on the grace list, then exiting without\nanything removing it from the list.\"\n\nSo, perform the final locks_end_grace() from the the lockd thread; this\nensures it's serialized with respect to restart_grace().\n\nReported-by: David Jeffery <djeffery@redhat.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/3bb16f97201a0a9f68573a2223460424f4b8a8e5"},{"sha":"1625ef6eba1f95698b675f9120eeca67c5581e00","author":{"name":"Kirill Tkhai","email":"e5b39230c99b4d3ebd6aa54f6d823f95134bc39d@virtuozzo.com"},"message":"pidns: disable pid allocation if pid_ns_prepare_proc() is failed in alloc_pid()\n\n\n[ Upstream commit 8896c23d2ef803f1883fea73117a435925c2b4c4 ]\n\nalloc_pidmap() advances pid_namespace::last_pid.  When first pid\nallocation fails, then next created process will have pid 2 and\npid_ns_prepare_proc() won't be called.  So, pid_namespace::proc_mnt will\nnever be initialized (not to mention that there won't be a child\nreaper).\n\nI saw crash stack of such case on kernel 3.10:\n\n    BUG: unable to handle kernel NULL pointer dereference at (null)\n    IP: proc_flush_task+0x8f/0x1b0\n    Call Trace:\n        release_task+0x3f/0x490\n        wait_consider_task.part.10+0x7ff/0xb00\n        do_wait+0x11f/0x280\n        SyS_wait4+0x7d/0x110\n\nWe may fix this by restore of last_pid in 0 or by prohibiting of futher\nallocations.  Since there was a similar issue in Oleg Nesterov's commit\n314a8ad0f18a (\"pidns: fix free_pid() to handle the first fork failure\").\nand it was fixed via prohibiting allocation, let's follow this way, and\ndo the same.\n\nLink: http://lkml.kernel.org/r/149201021004.4863.6762095011554287922.stgit@localhost.localdomain\nSigned-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>\nAcked-by: Cyrill Gorcunov <gorcunov@openvz.org>\nCc: Andrei Vagin <avagin@virtuozzo.com>\nCc: Andreas Gruenbacher <agruenba@redhat.com>\nCc: Kees Cook <keescook@chromium.org>\nCc: Michael Kerrisk <mtk.manpages@googlemail.com>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nCc: Oleg Nesterov <oleg@redhat.com>\nCc: Paul Moore <paul@paul-moore.com>\nCc: Eric Biederman <ebiederm@xmission.com>\nCc: Andy Lutomirski <luto@amacapital.net>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Serge Hallyn <serge@hallyn.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/1625ef6eba1f95698b675f9120eeca67c5581e00"},{"sha":"66f0db50935d844d9c531484f103f89659374ef4","author":{"name":"Heiko Carstens","email":"8dcf0f69152f32f23184f83357a3731522e56b9c@de.ibm.com"},"message":"s390: move _text symbol to address higher than zero\n\n\n[ Upstream commit d04a4c76f71dd5335f8e499b59617382d84e2b8d ]\n\nThe perf tool assumes that kernel symbols are never present at address\nzero. In fact it assumes if functions that map symbols to addresses\nreturn zero, that the symbol was not found.\n\nGiven that s390's _text symbol historically is located at address zero\nthis yields at least a couple of false errors and warnings in one of\nperf's test cases about not present symbols (\"perf test 1\").\n\nTo fix this simply move the _text symbol to address 0x200, just behind\nthe initial psw and channel program located at the beginning of the\nkernel image. This is now hard coded within the linker script.\n\nI tried a nicer solution which moves the initial psw and channel\nprogram into an own section. However that would move the symbols\nwithin the \"real\" head.text section to different addresses, since the\n\".org\" statements within head.S are relative to the head.text\nsection. If there is a new section in front, everything else will be\nmoved. Alternatively I could have adjusted all \".org\" statements. But\nthis current solution seems to be the easiest one, since nobody really\ncares where the _text symbol is actually located.\n\nReported-by: Zvonko Kosic <zkosic@linux.vnet.ibm.com>\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/66f0db50935d844d9c531484f103f89659374ef4"},{"sha":"7b13441c1d55f6eb2e6bb764b6fccfda495b4a8b","author":{"name":"Talat Batheesh","email":"379516cd0d56f969290cc4bc3774b7586d2e10bf@mellanox.com"},"message":"net/mlx4_en: Avoid adding steering rules with invalid ring\n\n\n[ Upstream commit 89c557687a32c294e9d25670a96e9287c09f2d5f ]\n\nInserting steering rules with illegal ring is an invalid operation,\nblock it.\n\nFixes: 820672812f82 ('net/mlx4_en: Manage flow steering rules with ethtool')\nSigned-off-by: Talat Batheesh <talatb@mellanox.com>\nSigned-off-by: Tariq Toukan <tariqt@mellanox.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/GamingDevilsCC/android_kernel_xiaomi_msm8953/commits/7b13441c1d55f6eb2e6bb764b6fccfda495b4a8b"}]}
{"actor":{"display_login":"GamingDevilsCC"}}