{"push_id":2354464831,"size":35,"distinct_size":0,"ref":"refs/heads/caf/3.10/caf/aosp-common/android-4.4-n","head":"3370475604cf98f704f063a13942a7323bbfc3ec","before":"b1d8980bba5ada554ddae6f42f75921853a57b8e","commits":[{"sha":"5b6e767562c12257b47cf702d74788085d3fbe42","author":{"name":"Jack Morgenstein","email":"9199a894d30558f9073fe198ba069ef3e4372dd7@dev.mellanox.co.il"},"message":"IB/mlx4: Fix incorrectly releasing steerable UD QPs when have only ETH ports\n\ncommit 852f6927594d0d3e8632c889b2ab38cbc46476ad upstream.\n\nAllocating steerable UD QPs depends on having at least one IB port,\nwhile releasing those QPs does not.\n\nAs a result, when there are only ETH ports, the IB (RoCE) driver\nrequests releasing a qp range whose base qp is zero, with\nqp count zero.\n\nWhen SR-IOV is enabled, and the VF driver is running on a VM over\na hypervisor which treats such qp release calls as errors\n(rather than NOPs), we see lines in the VM message log like:\n\n mlx4_core 0002:00:02.0: Failed to release qp range base:0 cnt:0\n\nFix this by adding a check for a zero count in mlx4_release_qp_range()\n(which thus treats releasing 0 qps as a nop), and eliminating the\ncheck for device managed flow steering when releasing steerable UD QPs.\n(Freeing ib_uc_qpns_bitmap unconditionally is also OK, since it\nremains NULL when steerable UD QPs are not allocated).\n\nFixes: 4196670be786 (\"IB/mlx4: Don't allocate range of steerable UD QPs for Ethernet-only device\")\nSigned-off-by: Jack Morgenstein <jackm@dev.mellanox.co.il>\nSigned-off-by: Leon Romanovsky <leon@kernel.org>\nSigned-off-by: Jason Gunthorpe <jgg@mellanox.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/5b6e767562c12257b47cf702d74788085d3fbe42"},{"sha":"8bb3fe364f8a77a2cc231e5861fc6b0322651df0","author":{"name":"Bjorn Andersson","email":"823e8bbaa174806583fcc7d851531504068ef2fd@linaro.org"},"message":"PM / devfreq: Propagate error from devfreq_add_device()\n\ncommit d1bf2d30728f310f72296b54f0651ecdb09cbb12 upstream.\n\nPropagate the error of devfreq_add_device() in devm_devfreq_add_device()\nrather than statically returning ENOMEM. This makes it slightly faster\nto pinpoint the cause of a returned error.\n\nFixes: 8cd84092d35e (\"PM / devfreq: Add resource-managed function for devfreq device\")\nCc: stable@vger.kernel.org\nAcked-by: Chanwoo Choi <cw00.choi@samsung.com>\nSigned-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>\nSigned-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/8bb3fe364f8a77a2cc231e5861fc6b0322651df0"},{"sha":"a76abe444968922e8c3743c1c575f7791c0cd8f8","author":{"name":"Eugene Syromiatnikov","email":"0fd753f6c7c05dd1e23aa7f56ee728a20f423dd8@redhat.com"},"message":"s390: fix handling of -1 in set{,fs}[gu]id16 syscalls\n\ncommit 6dd0d2d22aa363fec075cb2577ba273ac8462e94 upstream.\n\nFor some reason, the implementation of some 16-bit ID system calls\n(namely, setuid16/setgid16 and setfsuid16/setfsgid16) used type cast\ninstead of low2highgid/low2highuid macros for converting [GU]IDs, which\nled to incorrect handling of value of -1 (which ought to be considered\ninvalid).\n\nDiscovered by strace test suite.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Eugene Syromiatnikov <esyr@redhat.com>\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/a76abe444968922e8c3743c1c575f7791c0cd8f8"},{"sha":"660728b71a630c59ef17c72ace669bbdd666244f","author":{"name":"Patrice Chotard","email":"ebb4f14edcc10357f6bdfe93214fc704c10d0f18@st.com"},"message":"ARM: dts: STi: Add gpio polarity for \"hdmi,hpd-gpio\" property\n\ncommit 7ac1f59c09a61e6af6622df6809e003b0af07f3d upstream.\n\nThe GPIO polarity is missing in the hdmi,hpd-gpio property, this\nfixes the following DT warnings:\n\narch/arm/boot/dts/stih410-b2120.dtb: Warning (gpios_property): hdmi,hpd-gpio property\nsize (8) too small for cell size 2 in /soc/sti-display-subsystem/sti-hdmi@8d04000\n\narch/arm/boot/dts/stih407-b2120.dtb: Warning (gpios_property): hdmi,hpd-gpio property\nsize (8) too small for cell size 2 in /soc/sti-display-subsystem/sti-hdmi@8d04000\n\narch/arm/boot/dts/stih410-b2260.dtb: Warning (gpios_property): hdmi,hpd-gpio property\nsize (8) too small for cell size 2 in /soc/sti-display-subsystem/sti-hdmi@8d04000\n\n[arnd: marked Cc:stable since this warning shows up with the latest dtc\n       by default, and is more likely to actually cause problems than the\n       other patches from this series]\n\nCc: stable@vger.kernel.org\nSigned-off-by: Patrice Chotard <patrice.chotard@st.com>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/660728b71a630c59ef17c72ace669bbdd666244f"},{"sha":"f8bc000816ef91783a9fba8507da1e998b198d3c","author":{"name":"Viresh Kumar","email":"4ca49bc1dcfdfc376d29da1eb07a3e0b3cd46daa@linaro.org"},"message":"arm: spear600: Add missing interrupt-parent of rtc\n\ncommit 6ffb5b4f248fe53e0361b8cbc2a523b432566442 upstream.\n\nThe interrupt-parent of rtc was missing, add it.\n\nFixes: 8113ba917dfa (\"ARM: SPEAr: DT: Update device nodes\")\nCc: stable@vger.kernel.org # v3.8+\nReported-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Olof Johansson <olof@lixom.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/f8bc000816ef91783a9fba8507da1e998b198d3c"},{"sha":"e2756618e9d124152ef2a89bb8966e6992af43b1","author":{"name":"Viresh Kumar","email":"4ca49bc1dcfdfc376d29da1eb07a3e0b3cd46daa@linaro.org"},"message":"arm: spear13xx: Fix dmas cells\n\ncommit cdd10409914184c7eee5ae3e11beb890c9c16c61 upstream.\n\nThe \"dmas\" cells for the designware DMA controller need to have only 3\nproperties apart from the phandle: request line, src master and\ndestination master. But the commit 6e8887f60f60 updated it incorrectly\nwhile moving from platform code to DT. Fix it.\n\nCc: stable@vger.kernel.org # v3.10+\nFixes: 6e8887f60f60 (\"ARM: SPEAr13xx: Pass generic DW DMAC platform data from DT\")\nReported-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Olof Johansson <olof@lixom.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/e2756618e9d124152ef2a89bb8966e6992af43b1"},{"sha":"7f5cb8e97b42ced7d7c99161825010764aed1946","author":{"name":"Viresh Kumar","email":"4ca49bc1dcfdfc376d29da1eb07a3e0b3cd46daa@linaro.org"},"message":"arm: spear13xx: Fix spics gpio controller's warning\n\ncommit f8975cb1b8a36d0839b6365235778dd9df1d04ca upstream.\n\nThis fixes the following warning by also sending the flags argument for\ngpio controllers:\n\nProperty 'cs-gpios', cell 6 is not a phandle reference in\n/ahb/apb/spi@e0100000\n\nFixes: 8113ba917dfa (\"ARM: SPEAr: DT: Update device nodes\")\nCc: stable@vger.kernel.org # v3.8+\nReported-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Olof Johansson <olof@lixom.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/7f5cb8e97b42ced7d7c99161825010764aed1946"},{"sha":"5ff8af891df048c57462cabc42bb03a55a42196e","author":{"name":"Takashi Iwai","email":"dd0a9a4ae370c51e6d7099900a4bf6656524e055@suse.de"},"message":"ALSA: seq: Fix regression by incorrect ioctl_mutex usages\n\nThis is the revised backport of the upstream commit\nb3defb791b26ea0683a93a4f49c77ec45ec96f10\n\nWe had another backport (e.g. 623e5c8ae32b in 4.4.115), but it applies\nthe new mutex also to the code paths that are invoked via faked\nkernel-to-kernel ioctls.  As reported recently, this leads to a\ndeadlock at suspend (or other scenarios triggering the kernel\nsequencer client).\n\nThis patch addresses the issue by taking the mutex only in the code\npaths invoked by user-space, just like the original fix patch does.\n\nReported-and-tested-by: Andres Bertens <abertensu@yahoo.com>\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/Jackeagle/kernel_msm-3.18/commits/5ff8af891df048c57462cabc42bb03a55a42196e"},{"sha":"c63497edc3aa9b7e22dc2aa012d26ec4770b8f2d","author":{"name":"David Woodhouse","email":"04492b5f5be7e63813236a191d2db929fbf9f04a@amazon.co.uk"},"message":"KVM/x86: Reduce retpoline performance impact in slot_handle_level_range(), by always inlining iterator helper methods\n\ncommit 928a4c39484281f8ca366f53a1db79330d058401 upstream.\n\nWith retpoline, tight loops of \"call this function for every XXX\" are\nvery much pessimised by taking a prediction miss *every* time. This one\nis by far the biggest contributor to the guest launch time with retpoline.\n\nBy marking the iterator slot_handle_…() functions always_inline, we can\nensure that the indirect function call can be optimised away into a\ndirect call and it actually generates slightly smaller code because\nsome of the other conditionals can get optimised away too.\n\nPerformance is now pretty close to what we see with nospectre_v2 on\nthe command line.\n\nSuggested-by: Linus Torvalds <torvalds@linux-foundation.org>\nTested-by: Filippo Sironi <sironi@amazon.de>\nSigned-off-by: David Woodhouse <dwmw@amazon.co.uk>\nReviewed-by: Filippo Sironi <sironi@amazon.de>\nAcked-by: Paolo Bonzini <pbonzini@redhat.com>\nCc: Andy Lutomirski <luto@kernel.org>\nCc: Arjan van de Ven <arjan@linux.intel.com>\nCc: Borislav Petkov <bp@alien8.de>\nCc: Dan Williams <dan.j.williams@intel.com>\nCc: Dave Hansen <dave.hansen@linux.intel.com>\nCc: David Woodhouse <dwmw2@infradead.org>\nCc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nCc: Josh Poimboeuf <jpoimboe@redhat.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: arjan.van.de.ven@intel.com\nCc: dave.hansen@intel.com\nCc: jmattson@google.com\nCc: karahmed@amazon.de\nCc: kvm@vger.kernel.org\nCc: rkrcmar@redhat.com\nLink: http://lkml.kernel.org/r/1518305967-31356-4-git-send-email-dwmw@amazon.co.uk\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/c63497edc3aa9b7e22dc2aa012d26ec4770b8f2d"},{"sha":"ff891875c1a079c55cb5def525c2448c4cbed98c","author":{"name":"Gustavo A. R. Silva","email":"4b411d321e41f8f6965e5524af22579e66e9d999@embeddedor.com"},"message":"x86/cpu: Change type of x86_cache_size variable to unsigned int\n\ncommit 24dbc6000f4b9b0ef5a9daecb161f1907733765a upstream.\n\nCurrently, x86_cache_size is of type int, which makes no sense as we\nwill never have a valid cache size equal or less than 0. So instead of\ninitializing this variable to -1, it can perfectly be initialized to 0\nand use it as an unsigned variable instead.\n\nSuggested-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Gustavo A. R. Silva <garsilva@embeddedor.com>\nCc: Borislav Petkov <bp@alien8.de>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nAddresses-Coverity-ID: 1464429\nLink: http://lkml.kernel.org/r/20180213192208.GA26414@embeddedor.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/ff891875c1a079c55cb5def525c2448c4cbed98c"},{"sha":"0bb10b1679e2b5c817ad11354345c1d73121997b","author":{"name":"Julia Lawall","email":"5f26763d26f96d414e30b3f33734591afe022543@lip6.fr"},"message":"drm/radeon: adjust tested variable\n\ncommit 3a61b527b4e1f285d21b6e9e623dc45cf8bb391f upstream.\n\nCheck the variable that was most recently initialized.\n\nThe semantic match that finds this problem is as follows:\n(http://coccinelle.lip6.fr/)\n\n// <smpl>\n@@\nexpression x, y, f, g, e, m;\nstatement S1,S2,S3,S4;\n@@\n\nx = f(...);\nif (\\(<+...x...+>\\&e\\)) S1 else S2\n(\nx = g(...);\n|\nm = g(...,&x,...);\n|\ny = g(...);\n*if (e)\n S3 else S4\n)\n// </smpl>\n\nSigned-off-by: Julia Lawall <Julia.Lawall@lip6.fr>\nReviewed-by: Christian König <christian.koenig@amd.com>\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/0bb10b1679e2b5c817ad11354345c1d73121997b"},{"sha":"99863c1bfdbf08d9a9001ac2c7c4d4e66fcdab6d","author":{"name":"Stewart Smith","email":"bdb1b341ebfb6d677d83955daa362a2031ee4fdd@linux.vnet.ibm.com"},"message":"rtc-opal: Fix handling of firmware error codes, prevent busy loops\n\ncommit 5b8b58063029f02da573120ef4dc9079822e3cda upstream.\n\nAccording to the OPAL docs:\n  skiboot-5.2.5/doc/opal-api/opal-rtc-read-3.txt\n  skiboot-5.2.5/doc/opal-api/opal-rtc-write-4.txt\n\nOPAL_HARDWARE may be returned from OPAL_RTC_READ or OPAL_RTC_WRITE and\nthis indicates either a transient or permanent error.\n\nPrior to this patch, Linux was not dealing with OPAL_HARDWARE being a\npermanent error particularly well, in that you could end up in a busy\nloop.\n\nThis was not too hard to trigger on an AMI BMC based OpenPOWER machine\ndoing a continuous \"ipmitool mc reset cold\" to the BMC, the result of\nthat being that we'd get stuck in an infinite loop in\nopal_get_rtc_time().\n\nWe now retry a few times before returning the error higher up the\nstack.\n\nFixes: 16b1d26e77b1 (\"rtc/tpo: Driver to support rtc and wakeup on PowerNV platform\")\nCc: stable@vger.kernel.org # v3.19+\nSigned-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/99863c1bfdbf08d9a9001ac2c7c4d4e66fcdab6d"},{"sha":"ab63d810345106d97ec0580598426550a63cf65e","author":{"name":"Zhouyi Zhou","email":"0191e3fcd850b467fd6fa2f018097a5eaffa46ef@gmail.com"},"message":"ext4: save error to disk in __ext4_grp_locked_error()\n\ncommit 06f29cc81f0350261f59643a505010531130eea0 upstream.\n\nIn the function __ext4_grp_locked_error(), __save_error_info()\nis called to save error info in super block block, but does not sync\nthat information to disk to info the subsequence fsck after reboot.\n\nThis patch writes the error information to disk.  After this patch,\nI think there is no obvious EXT4 error handle branches which leads to\n\"Remounting filesystem read-only\" will leave the disk partition miss\nthe subsequence fsck.\n\nSigned-off-by: Zhouyi Zhou <zhouzhouyi@gmail.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/ab63d810345106d97ec0580598426550a63cf65e"},{"sha":"890908b8352e8b565746b691c5f8d809668cca8f","author":{"name":"Ernesto A. Fernández","email":"70e26ba3376e9b8443f01b223165dc25eed48cec@gmail.com"},"message":"ext4: correct documentation for grpid mount option\n\ncommit 9f0372488cc9243018a812e8cfbf27de650b187b upstream.\n\nThe grpid option is currently described as being the same as nogrpid.\n\nSigned-off-by: Ernesto A. Fernández <ernesto.mnd.fernandez@gmail.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/890908b8352e8b565746b691c5f8d809668cca8f"},{"sha":"6d046d9e75af120ce704f8d354d960bd0ad403ad","author":{"name":"Arnd Bergmann","email":"72a0f6d3b182607e6d5c44b93e1abb7b23ee18f3@arndb.de"},"message":"mm: hide a #warning for COMPILE_TEST\n\ncommit af27d9403f5b80685b79c88425086edccecaf711 upstream.\n\nWe get a warning about some slow configurations in randconfig kernels:\n\n  mm/memory.c:83:2: error: #warning Unfortunate NUMA and NUMA Balancing config, growing page-frame for last_cpupid. [-Werror=cpp]\n\nThe warning is reasonable by itself, but gets in the way of randconfig\nbuild testing, so I'm hiding it whenever CONFIG_COMPILE_TEST is set.\n\nThe warning was added in 2013 in commit 75980e97dacc (\"mm: fold\npage->_last_nid into page->flags where possible\").\n\nCc: stable@vger.kernel.org\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/6d046d9e75af120ce704f8d354d960bd0ad403ad"},{"sha":"8cbb6ca49a15cc2538bec4648f1faf844ad125ad","author":{"name":"Johan Hovold","email":"c5aaa0c362db47011b825595d6a432662259e2f1@kernel.org"},"message":"video: fbdev: atmel_lcdfb: fix display-timings lookup\n\ncommit 9cb18db0701f6b74f0c45c23ad767b3ebebe37f6 upstream.\n\nFix child-node lookup during probe, which ended up searching the whole\ndevice tree depth-first starting at the parent rather than just matching\non its children.\n\nTo make things worse, the parent display node was also prematurely\nfreed.\n\nNote that the display and timings node references are never put after a\nsuccessful dt-initialisation so the nodes would leak on later probe\ndeferrals and on driver unbind.\n\nFixes: b985172b328a (\"video: atmel_lcdfb: add device tree suport\")\nCc: stable <stable@vger.kernel.org>     # 3.13\nCc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>\nCc: Nicolas Ferre <nicolas.ferre@microchip.com>\nCc: Alexandre Belloni <alexandre.belloni@free-electrons.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/8cbb6ca49a15cc2538bec4648f1faf844ad125ad"},{"sha":"7f64e1a80640cd97f4767a57796b033d4f47f4db","author":{"name":"Nicolas Pitre","email":"821418b0a29e813296bdaa58f6aecc4445fd1b69@linaro.org"},"message":"console/dummy: leave .con_font_get set to NULL\n\ncommit 724ba8b30b044aa0d94b1cd374fc15806cdd6f18 upstream.\n\nWhen this method is set, the caller expects struct console_font fields\nto be properly initialized when it returns. Leave it unset otherwise\nnonsensical (leaked kernel stack) values are returned to user space.\n\nSigned-off-by: Nicolas Pitre <nico@linaro.org>\nCc: stable@vger.kernel.org\nSigned-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/7f64e1a80640cd97f4767a57796b033d4f47f4db"},{"sha":"4f62fb888d96ddc236aa11015f95d0afe4f3ba8b","author":{"name":"Larry Finger","email":"15b8df22a685ea626b641ec4b41ea74b2ea632fd@lwfinger.net"},"message":"rtlwifi: rtl8821ae: Fix connection lost problem correctly\n\ncommit c713fb071edc0efc01a955f65a006b0e1795d2eb upstream.\n\nThere has been a coding error in rtl8821ae since it was first introduced,\nnamely that an 8-bit register was read using a 16-bit read in\n_rtl8821ae_dbi_read(). This error was fixed with commit 40b368af4b75\n(\"rtlwifi: Fix alignment issues\"); however, this change led to\ninstability in the connection. To restore stability, this change\nwas reverted in commit b8b8b16352cd (\"rtlwifi: rtl8821ae: Fix connection\nlost problem\").\n\nUnfortunately, the unaligned access causes machine checks in ARM\narchitecture, and we were finally forced to find the actual cause of the\nproblem on x86 platforms. Following a suggestion from Pkshih\n<pkshih@realtek.com>, it was found that increasing the ASPM L1\nlatency from 0 to 7 fixed the instability. This parameter was varied to\nsee if a smaller value would work; however, it appears that 7 is the\nsafest value. A new symbol is defined for this quantity, thus it can be\neasily changed if necessary.\n\nFixes: b8b8b16352cd (\"rtlwifi: rtl8821ae: Fix connection lost problem\")\nCc: Stable <stable@vger.kernel.org> # 4.14+\nFix-suggested-by: Pkshih <pkshih@realtek.com>\nSigned-off-by: Larry Finger <Larry.Finger@lwfinger.net>\nTested-by: James Cameron <quozl@laptop.org>  # x86_64 OLPC NL3\nSigned-off-by: Kalle Valo <kvalo@codeaurora.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/4f62fb888d96ddc236aa11015f95d0afe4f3ba8b"},{"sha":"efba91a4c3f465e1b7f10b2454d6406eb217a17e","author":{"name":"Liu Bo","email":"2320f47fd1b0bdd58584dbc8b4d320b2decf8329@oracle.com"},"message":"Btrfs: fix deadlock in run_delalloc_nocow\n\ncommit e89166990f11c3f21e1649d760dd35f9e410321c upstream.\n\n@cur_offset is not set back to what it should be (@cow_start) if\nbtrfs_next_leaf() returns something wrong, and the range [cow_start,\ncur_offset) remains locked forever.\n\ncc: <stable@vger.kernel.org>\nSigned-off-by: Liu Bo <bo.li.liu@oracle.com>\nReviewed-by: Josef Bacik <jbacik@fb.com>\nSigned-off-by: David Sterba <dsterba@suse.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/efba91a4c3f465e1b7f10b2454d6406eb217a17e"},{"sha":"145832a93f28fb80d6cb22b5cd84df5a6e63f47b","author":{"name":"Liu Bo","email":"2320f47fd1b0bdd58584dbc8b4d320b2decf8329@oracle.com"},"message":"Btrfs: fix crash due to not cleaning up tree log block's dirty bits\n\ncommit 1846430c24d66e85cc58286b3319c82cd54debb2 upstream.\n\nIn cases that the whole fs flips into readonly status due to failures in\ncritical sections, then log tree's blocks are still dirty, and this leads\nto a crash during umount time, the crash is about use-after-free,\n\numount\n -> close_ctree\n    -> stop workers\n    -> iput(btree_inode)\n       -> iput_final\n          -> write_inode_now\n\t     -> ...\n\t       -> queue job on stop'd workers\n\ncc: <stable@vger.kernel.org> v3.12+\nFixes: 681ae50917df (\"Btrfs: cleanup reserved space when freeing tree log on error\")\nSigned-off-by: Liu Bo <bo.li.liu@oracle.com>\nReviewed-by: Josef Bacik <jbacik@fb.com>\nSigned-off-by: David Sterba <dsterba@suse.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/145832a93f28fb80d6cb22b5cd84df5a6e63f47b"}]}
{"actor":{"display_login":"Jackeagle"}}