{"push_id":2638227041,"size":100,"distinct_size":100,"ref":"refs/heads/orange-pi-4.16","head":"b43238f62434cd8c335fe2f04bf7cdcdf56c1e28","before":"3b786d8a4c8ef2d772b4b189b6b94171894199a1","commits":[{"sha":"c6f589eed3b5a9b73b3be76a719917cc905bab0e","author":{"name":"Josh Poimboeuf","email":"4e2e91f15355af385c021c68a9357f2fd253fb9d@redhat.com"},"message":"objtool: Support GCC 8's cold subfunctions\n\ncommit 13810435b9a7014fb92eb715f77da488f3b65b99 upstream.\n\nGCC 8 moves a lot of unlikely code out of line to \"cold\" subfunctions in\n.text.unlikely.  Properly detect the new subfunctions and treat them as\nextensions of the original functions.\n\nThis fixes a bunch of warnings like:\n\n  kernel/cgroup/cgroup.o: warning: objtool: parse_cgroup_root_flags()+0x33: sibling call from callable instruction with modified stack frame\n  kernel/cgroup/cgroup.o: warning: objtool: cgroup_addrm_files()+0x290: sibling call from callable instruction with modified stack frame\n  kernel/cgroup/cgroup.o: warning: objtool: cgroup_apply_control_enable()+0x25b: sibling call from callable instruction with modified stack frame\n  kernel/cgroup/cgroup.o: warning: objtool: rebind_subsystems()+0x325: sibling call from callable instruction with modified stack frame\n\nReported-and-tested-by: damian <damian.tometzki@icloud.com>\nReported-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Josh Poimboeuf <jpoimboe@redhat.com>\nAcked-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: David Laight <David.Laight@ACULAB.COM>\nCc: Greg KH <gregkh@linuxfoundation.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Randy Dunlap <rdunlap@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nLink: http://lkml.kernel.org/r/0965e7fcfc5f31a276f0c7f298ff770c19b68706.1525923412.git.jpoimboe@redhat.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/c6f589eed3b5a9b73b3be76a719917cc905bab0e"},{"sha":"662b404b5082b34a916f4901028b02749aeaab16","author":{"name":"Josh Poimboeuf","email":"4e2e91f15355af385c021c68a9357f2fd253fb9d@redhat.com"},"message":"objtool: Support GCC 8 switch tables\n\ncommit fd35c88b74170d9335530d9abf271d5d73eb5401 upstream.\n\nWith GCC 8, some issues were found with the objtool switch table\ndetection.\n\n1) In the .rodata section, immediately after the switch table, there can\n   be another object which contains a pointer to the function which had\n   the switch statement.  In this case objtool wrongly considers the\n   function pointer to be part of the switch table.  Fix it by:\n\n   a) making sure there are no pointers to the beginning of the\n      function; and\n\n   b) making sure there are no gaps in the switch table.\n\n   Only the former was needed, the latter adds additional protection for\n   future optimizations.\n\n2) In find_switch_table(), case 1 and case 2 are missing the check to\n   ensure that the .rodata switch table data is anonymous, i.e. that it\n   isn't already associated with an ELF symbol.  Fix it by adding the\n   same find_symbol_containing() check which is used for case 3.\n\nThis fixes the following warnings with GCC 8:\n\n  drivers/block/virtio_blk.o: warning: objtool: virtio_queue_rq()+0x0: stack state mismatch: cfa1=7+8 cfa2=7+72\n  net/ipv6/icmp.o: warning: objtool: icmpv6_rcv()+0x0: stack state mismatch: cfa1=7+8 cfa2=7+64\n  drivers/usb/core/quirks.o: warning: objtool: quirks_param_set()+0x0: stack state mismatch: cfa1=7+8 cfa2=7+48\n  drivers/mtd/nand/raw/nand_hynix.o: warning: objtool: hynix_nand_decode_id()+0x0: stack state mismatch: cfa1=7+8 cfa2=7+24\n  drivers/mtd/nand/raw/nand_samsung.o: warning: objtool: samsung_nand_decode_id()+0x0: stack state mismatch: cfa1=7+8 cfa2=7+32\n  drivers/gpu/drm/nouveau/nvkm/subdev/top/gk104.o: warning: objtool: gk104_top_oneinit()+0x0: stack state mismatch: cfa1=7+8 cfa2=7+64\n\nReported-by: Arnd Bergmann <arnd@arndb.de>\nReported-by: kbuild test robot <lkp@intel.com>\nSigned-off-by: Josh Poimboeuf <jpoimboe@redhat.com>\nAcked-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: David Laight <David.Laight@ACULAB.COM>\nCc: Greg KH <gregkh@linuxfoundation.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Randy Dunlap <rdunlap@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: damian <damian.tometzki@icloud.com>\nLink: http://lkml.kernel.org/r/20180510224849.xwi34d6tzheb5wgw@treble\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/662b404b5082b34a916f4901028b02749aeaab16"},{"sha":"954714d8cfcb0a7053c6ef166ac204171fb6f794","author":{"name":"Josh Poimboeuf","email":"4e2e91f15355af385c021c68a9357f2fd253fb9d@redhat.com"},"message":"objtool: Detect RIP-relative switch table references\n\ncommit 6f5ec2993b1f39aed12fa6fd56e8dc2272ee8a33 upstream.\n\nTypically a switch table can be found by detecting a .rodata access\nfollowed an indirect jump:\n\n    1969:\t4a 8b 0c e5 00 00 00 \tmov    0x0(,%r12,8),%rcx\n    1970:\t00\n\t\t\t196d: R_X86_64_32S\t.rodata+0x438\n    1971:\te9 00 00 00 00       \tjmpq   1976 <dispc_runtime_suspend+0xb6a>\n\t\t\t1972: R_X86_64_PC32\t__x86_indirect_thunk_rcx-0x4\n\nRandy Dunlap reported a case (seen with GCC 4.8) where the .rodata\naccess uses RIP-relative addressing:\n\n    19bd:\t48 8b 3d 00 00 00 00 \tmov    0x0(%rip),%rdi        # 19c4 <dispc_runtime_suspend+0xbb8>\n\t\t\t19c0: R_X86_64_PC32\t.rodata+0x45c\n    19c4:\te9 00 00 00 00       \tjmpq   19c9 <dispc_runtime_suspend+0xbbd>\n\t\t\t19c5: R_X86_64_PC32\t__x86_indirect_thunk_rdi-0x4\n\nIn this case the relocation addend needs to be adjusted accordingly in\norder to find the location of the switch table.\n\nThe fix is for case 3 (as described in the comments), but also make the\nexisting case 1 & 2 checks more precise by only adjusting the addend for\nR_X86_64_PC32 relocations.\n\nThis fixes the following warnings:\n\n  drivers/video/fbdev/omap2/omapfb/dss/dispc.o: warning: objtool: dispc_runtime_suspend()+0xbb8: sibling call from callable instruction with modified stack frame\n  drivers/video/fbdev/omap2/omapfb/dss/dispc.o: warning: objtool: dispc_runtime_resume()+0xcc5: sibling call from callable instruction with modified stack frame\n\nReported-by: Randy Dunlap <rdunlap@infradead.org>\nSigned-off-by: Josh Poimboeuf <jpoimboe@redhat.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nLink: http://lkml.kernel.org/r/b6098294fd67afb69af8c47c9883d7a68bf0f8ea.1526305958.git.jpoimboe@redhat.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/954714d8cfcb0a7053c6ef166ac204171fb6f794"},{"sha":"c3752344435b2657aebd54b1eb47612faf473229","author":{"name":"Josh Poimboeuf","email":"4e2e91f15355af385c021c68a9357f2fd253fb9d@redhat.com"},"message":"objtool: Detect RIP-relative switch table references, part 2\n\ncommit 7dec80ccbe310fb7e225bf21c48c672bb780ce7b upstream.\n\nWith the following commit:\n\n  fd35c88b7417 (\"objtool: Support GCC 8 switch tables\")\n\nI added a \"can't find switch jump table\" warning, to stop covering up\nsilent failures if add_switch_table() can't find anything.\n\nThat warning found yet another bug in the objtool switch table detection\nlogic.  For cases 1 and 2 (as described in the comments of\nfind_switch_table()), the find_symbol_containing() check doesn't adjust\nthe offset for RIP-relative switch jumps.\n\nIncidentally, this bug was already fixed for case 3 with:\n\n  6f5ec2993b1f (\"objtool: Detect RIP-relative switch table references\")\n\nHowever, that commit missed the fix for cases 1 and 2.\n\nThe different cases are now starting to look more and more alike.  So\nfix the bug by consolidating them into a single case, by checking the\noriginal dynamic jump instruction in the case 3 loop.\n\nThis also simplifies the code and makes it more robust against future\nswitch table detection issues -- of which I'm sure there will be many...\n\nSwitch table detection has been the most fragile area of objtool, by\nfar.  I long for the day when we'll have a GCC plugin for annotating\nswitch tables.  Linus asked me to delay such a plugin due to the\nflakiness of the plugin infrastructure in older versions of GCC, so this\nrickety code is what we're stuck with for now.  At least the code is now\na little simpler than it was.\n\nReported-by: kbuild test robot <lkp@intel.com>\nSigned-off-by: Josh Poimboeuf <jpoimboe@redhat.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nLink: http://lkml.kernel.org/r/f400541613d45689086329432f3095119ffbc328.1526674218.git.jpoimboe@redhat.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/c3752344435b2657aebd54b1eb47612faf473229"},{"sha":"b3ab9104f4b7ac41668602bff01a93c753ac5304","author":{"name":"Josh Poimboeuf","email":"4e2e91f15355af385c021c68a9357f2fd253fb9d@redhat.com"},"message":"objtool: Fix \"noreturn\" detection for recursive sibling calls\n\ncommit 0afd0d9e0e7879d666c1df2fa1bea4d8716909fe upstream.\n\nObjtool has some crude logic for detecting static \"noreturn\" functions\n(aka \"dead ends\").  This is necessary for being able to correctly follow\nGCC code flow when such functions are called.\n\nIt's remotely possible for two functions to call each other via sibling\ncalls.  If they don't have RET instructions, objtool's noreturn\ndetection logic goes into a recursive loop:\n\n  drivers/char/ipmi/ipmi_ssif.o: warning: objtool: return_hosed_msg()+0x0: infinite recursion (objtool bug!)\n  drivers/char/ipmi/ipmi_ssif.o: warning: objtool: deliver_recv_msg()+0x0: infinite recursion (objtool bug!)\n\nInstead of reporting an error in this case, consider the functions to be\nnon-dead-ends.\n\nReported-and-tested-by: Randy Dunlap <rdunlap@infradead.org>\nSigned-off-by: Josh Poimboeuf <jpoimboe@redhat.com>\nAcked-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Arnd Bergmann <arnd@arndb.de>\nCc: David Laight <David.Laight@ACULAB.COM>\nCc: Greg KH <gregkh@linuxfoundation.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: damian <damian.tometzki@icloud.com>\nLink: http://lkml.kernel.org/r/7cc156408c5781a1f62085d352ced1fe39fe2f91.1525923412.git.jpoimboe@redhat.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/b3ab9104f4b7ac41668602bff01a93c753ac5304"},{"sha":"75b38053ae030775f94b2a55b044c2aa88f4c642","author":{"name":"Yazen Ghannam","email":"90fbc5f72d145c37c06c9ccf437a088384a94d6d@amd.com"},"message":"x86/mce/AMD: Carve out SMCA get_block_address() code\n\ncommit 8a331f4a0863bea758561c921b94b4d28f7c4029 upstream.\n\nCarve out the SMCA code in get_block_address() into a separate helper\nfunction.\n\nNo functional change.\n\nSigned-off-by: Yazen Ghannam <yazen.ghannam@amd.com>\n[ Save an indentation level. ]\nSigned-off-by: Borislav Petkov <bp@suse.de>\nCc: Borislav Petkov <bp@alien8.de>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Tony Luck <tony.luck@intel.com>\nCc: linux-edac <linux-edac@vger.kernel.org>\nLink: http://lkml.kernel.org/r/20180215210943.11530-4-Yazen.Ghannam@amd.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/75b38053ae030775f94b2a55b044c2aa88f4c642"},{"sha":"1415eea15edcdf86632d762f81511be6df1128f8","author":{"name":"Borislav Petkov","email":"0691a664b24b6f15b20cd5aee64b72271db08be1@suse.de"},"message":"x86/MCE/AMD: Cache SMCA MISC block addresses\n\ncommit 78ce241099bb363b19dbd0245442e66c8de8f567 upstream.\n\n... into a global, two-dimensional array and service subsequent reads from\nthat cache to avoid rdmsr_on_cpu() calls during CPU hotplug (IPIs with IRQs\ndisabled).\n\nIn addition, this fixes a KASAN slab-out-of-bounds read due to wrong usage\nof the bank->blocks pointer.\n\nFixes: 27bd59502702 (\"x86/mce/AMD: Get address from already initialized block\")\nReported-by: Johannes Hirte <johannes.hirte@datenkhaos.de>\nTested-by: Johannes Hirte <johannes.hirte@datenkhaos.de>\nSigned-off-by: Borislav Petkov <bp@suse.de>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Yazen Ghannam <yazen.ghannam@amd.com>\nLink: http://lkml.kernel.org/r/20180414004230.GA2033@probook\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/1415eea15edcdf86632d762f81511be6df1128f8"},{"sha":"01770968181c3c43ce039d1674038cb476729e50","author":{"name":"Himanshu Jha","email":"db39123178a3996d9dafcdcc9af59c3e841de70a@gmail.com"},"message":"drm/vmwgfx: Use kasprintf\n\ncommit 6073a09210e06f39adabd682c282b3ee14c3d33d upstream.\n\nUse kasprintf instead of combination of kmalloc and sprintf. Also,\nremove the local variables used for storing the string length as they\nare not required now.\n\nSigned-off-by: Himanshu Jha <himanshujha199640@gmail.com>\nReviewed-by: Sinclair Yeh <syeh@vmware.com>\nSigned-off-by: Thomas Hellstrom <thellstrom@vmware.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/01770968181c3c43ce039d1674038cb476729e50"},{"sha":"a3dd123a9fc4ae1161c61bf5208be519d0a332bd","author":{"name":"Thomas Hellstrom","email":"a26490dfbee4be3d38287ad6448444504f58193c@vmware.com"},"message":"drm/vmwgfx: Fix host logging / guestinfo reading error paths\n\ncommit f37230c0ad481091bc136788ff8b37dc86300c6d upstream.\n\nThe error paths were leaking opened channels.\nFix by using dedicated error paths.\n\nCc: <stable@vger.kernel.org>\nSigned-off-by: Thomas Hellstrom <thellstrom@vmware.com>\nReviewed-by: Brian Paul <brianp@vmware.com>\nReviewed-by: Sinclair Yeh <syeh@vmware.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/a3dd123a9fc4ae1161c61bf5208be519d0a332bd"},{"sha":"03a4e4ecdfdd95ce1ceb759bffa2681d210d9a8e","author":{"name":"Greg Kroah-Hartman","email":"4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org"},"message":"Revert \"pinctrl: msm: Use dynamic GPIO numbering\"\n\nThis reverts commit 7d8e0341b2b93fb505cd75e8e0d4f1911d0fa0fe which is\ncommit a7aa75a2a7dba32594291a71c3704000a2fd7089 upstream.\n\nThere's been too many complaints about this.  Personally I think it's\ngoing to blow up when people hit this in mainline, but hey, it's not my\nsystems.  At least we don't have to backport the mess to the stable\nkernels to give them some more life to live unscathed :)\n\nReported-by: Timur Tabi <timur@codeaurora.org>\nReported-by: Sebastian Gottschall <s.gottschall@dd-wrt.com>\nCc: Bjorn Andersson <bjorn.andersson@linaro.org>\nCc: Linus Walleij <linus.walleij@linaro.org>\nCc: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/03a4e4ecdfdd95ce1ceb759bffa2681d210d9a8e"},{"sha":"4fb9ed2ecab4f239883176ef95a6a9978f59a4b9","author":{"name":"Dave Chinner","email":"4d9e23a041ac966f5316a7481300d4ae12e806fe@redhat.com"},"message":"xfs: convert XFS_AGFL_SIZE to a helper function\n\ncommit a78ee256c325ecfaec13cafc41b315bd4e1dd518 upstream.\n\nThe AGFL size calculation is about to get more complex, so lets turn\nthe macro into a function first and remove the macro.\n\nSigned-off-by: Dave Chinner <dchinner@redhat.com>\n[darrick: forward port to newer kernel, simplify the helper]\nSigned-off-by: Darrick J. Wong <darrick.wong@oracle.com>\nReviewed-by: Brian Foster <bfoster@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/4fb9ed2ecab4f239883176ef95a6a9978f59a4b9"},{"sha":"60fdebd2f3cefd816bf8a0e58385a134ba8dfaa8","author":{"name":"Brian Foster","email":"335646b5e374a776a6a2caca10969d6e3ec1cd2b@redhat.com"},"message":"xfs: detect agfl count corruption and reset agfl\n\ncommit a27ba2607e60312554cbcd43fc660b2c7f29dc9c upstream.\n\nThe struct xfs_agfl v5 header was originally introduced with\nunexpected padding that caused the AGFL to operate with one less\nslot than intended. The header has since been packed, but the fix\nleft an incompatibility for users who upgrade from an old kernel\nwith the unpacked header to a newer kernel with the packed header\nwhile the AGFL happens to wrap around the end. The newer kernel\nrecognizes one extra slot at the physical end of the AGFL that the\nprevious kernel did not. The new kernel will eventually attempt to\nallocate a block from that slot, which contains invalid data, and\ncause a crash.\n\nThis condition can be detected by comparing the active range of the\nAGFL to the count. While this detects a padding mismatch, it can\nalso trigger false positives for unrelated flcount corruption. Since\nwe cannot distinguish a size mismatch due to padding from unrelated\ncorruption, we can't trust the AGFL enough to simply repopulate the\nempty slot.\n\nInstead, avoid unnecessarily complex detection logic and and use a\nsolution that can handle any form of flcount corruption that slips\nthrough read verifiers: distrust the entire AGFL and reset it to an\nempty state. Any valid blocks within the AGFL are intentionally\nleaked. This requires xfs_repair to rectify (which was already\nnecessary based on the state the AGFL was found in). The reset\nmitigates the side effect of the padding mismatch problem from a\nfilesystem crash to a free space accounting inconsistency. The\ngeneric approach also means that this patch can be safely backported\nto kernels with or without a packed struct xfs_agfl.\n\nCheck the AGF for an invalid freelist count on initial read from\ndisk. If detected, set a flag on the xfs_perag to indicate that a\nreset is required before the AGFL can be used. In the first\ntransaction that attempts to use a flagged AGFL, reset it to empty,\nwarn the user about the inconsistency and allow the freelist fixup\ncode to repopulate the AGFL with new blocks. The xfs_perag flag is\ncleared to eliminate the need for repeated checks on each block\nallocation operation.\n\nThis allows kernels that include the packing fix commit 96f859d52bcb\n(\"libxfs: pack the agfl header structure so XFS_AGFL_SIZE is correct\")\nto handle older unpacked AGFL formats without a filesystem crash.\n\nSuggested-by: Dave Chinner <david@fromorbit.com>\nSigned-off-by: Brian Foster <bfoster@redhat.com>\nReviewed-by: Darrick J. Wong <darrick.wong@oracle.com>\nReviewed-by Dave Chiluk <chiluk+linuxxfs@indeed.com>\nSigned-off-by: Darrick J. Wong <darrick.wong@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/60fdebd2f3cefd816bf8a0e58385a134ba8dfaa8"},{"sha":"9e138ac87d71e31c681d8dbe77a35fd94e41aacb","author":{"name":"Dmitry Torokhov","email":"6b8646d310837fed93a129ed3c979b90c7f2674f@gmail.com"},"message":"Input: synaptics - Lenovo Carbon X1 Gen5 (2017) devices should use RMI\n\ncommit 9b2071028f8def49971a3b213ab6efd02a7e56e8 upstream.\n\nThe touchpad on Lenovo Carbon X1 Gen 5 (2017 - Kabylake) is accessible over\nSMBUS/RMI, so let's activate it by default.\n\nCc: stable@vger.kernel.org\nReviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/9e138ac87d71e31c681d8dbe77a35fd94e41aacb"},{"sha":"59d895f17023e75dcb302934b4ecc5b4686ba080","author":{"name":"Edvard Holst","email":"f952cf33e14f822bff0507050f3547ef7b38530e@gmail.com"},"message":"Input: synaptics - Lenovo Thinkpad X1 Carbon G5 (2017) with Elantech trackpoints should use RMI\n\ncommit 15e2cffec3aa0d47a8d75ae80e1b136bfb5dff30 upstream.\n\nLenovo use two different trackpoints in the fifth generation Thinkpad X1\nCarbon. Both are accessible over SMBUS/RMI but the pnpIDs are missing.\nThis patch is for the Elantech trackpoint specifically which also\nreports SMB version 3 so rmi_smbus needs to be updated in order to\nhandle it.\n\nFor the record, I was not the first one to come up with this patch as it\nhas been floating around the internet for a while now. However, I have\nspent significant time with testing and my efforts to find the original\nauthor of the patch have been unsuccessful.\n\nSigned-off-by: Edvard Holst <edvard.holst@gmail.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/59d895f17023e75dcb302934b4ecc5b4686ba080"},{"sha":"93b9899aabfb1c61e7926186bf5a988c1368c8c6","author":{"name":"Aaron Ma","email":"6d75ab49fa4401d16749457e532362eb5fdb78e3@canonical.com"},"message":"Input: synaptics - add Intertouch support on X1 Carbon 6th and X280\n\ncommit 5717a09aeaf62d197deba1fc7ccd6bc45f3a9dcc upstream.\n\nSynaptics devices reported it has Intertouch support,\nand it fails via PS/2 as following logs:\n\npsmouse serio2: Failed to reset mouse on synaptics-pt/serio0\npsmouse serio2: Failed to enable mouse on synaptics-pt/serio0\n\nSet these new devices to use SMBus to fix this issue, then they report\nSMBus version 3 is using, patch:\nhttps://patchwork.kernel.org/patch/9989547/ enabled SMBus ver 3 and\nmakes synaptics devices work fine on SMBus mode.\n\nSigned-off-by: Aaron Ma <aaron.ma@canonical.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/93b9899aabfb1c61e7926186bf5a988c1368c8c6"},{"sha":"dfc8e3e2dc7118184169efb6fabf934cf6a0d168","author":{"name":"Benjamin Tissoires","email":"7a0e50e3f6a0939db82b6a8a423c08a163896f41@redhat.com"},"message":"Input: synaptics - add Lenovo 80 series ids to SMBus\n\ncommit ad8fb554f04e38f155c9bc34bbf521fc592ceee7 upstream.\n\nThis time, Lenovo decided to go with different pieces in its latest\nseries of Thinkpads.\n\nFor those we have been able to test:\n- the T480 is using Synaptics with an IBM trackpoint\n   -> it behaves properly with or without intertouch, there is no point\n      not using RMI4\n- the X1 Carbon 6th gen is using Synaptics with an IBM trackpoint\n   -> the touchpad doesn't behave properly under PS/2 so we have to\n      switch it to RMI4 if we do not want to have disappointed users\n- the X280 is using Synaptics with an ALPS trackpoint\n   -> the recent fixes in the trackpoint handling fixed it so upstream\n      now works fine with or without RMI4, and there is no point not\n      using RMI4\n- the T480s is using an Elan touchpad, so that's a different story\n\nCc: <stable@vger.kernel.org> # v4.14.x, v4.15.x, v4.16.x\nSigned-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>\nAcked-by: KT Liao <kt.liao@emc.com.tw>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/dfc8e3e2dc7118184169efb6fabf934cf6a0d168"},{"sha":"a81ce0bfa189d1de3d5f239d855b0528d99f78b3","author":{"name":"Benjamin Tissoires","email":"7a0e50e3f6a0939db82b6a8a423c08a163896f41@redhat.com"},"message":"Input: elan_i2c_smbus - fix corrupted stack\n\ncommit 40f7090bb1b4ec327ea1e1402ff5783af5b35195 upstream.\n\nNew ICs (like the one on the Lenovo T480s) answer to\nETP_SMBUS_IAP_VERSION_CMD 4 bytes instead of 3. This corrupts the stack\nas i2c_smbus_read_block_data() uses the values returned by the i2c\ndevice to know how many data it need to return.\n\ni2c_smbus_read_block_data() can read up to 32 bytes (I2C_SMBUS_BLOCK_MAX)\nand there is no safeguard on how many bytes are provided in the return\nvalue. Ensure we always have enough space for any future firmware.\nAlso 0-initialize the values to prevent any access to uninitialized memory.\n\nCc: <stable@vger.kernel.org> # v4.4.x, v4.9.x, v4.14.x, v4.15.x, v4.16.x\nSigned-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>\nAcked-by: KT Liao <kt.liao@emc.com.tw>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/a81ce0bfa189d1de3d5f239d855b0528d99f78b3"},{"sha":"0ea40e76fb392a6926089ddfbbcba3c3a33de924","author":{"name":"Steven Rostedt (VMware)","email":"43232e92d70cc7aa53504ad0397085ee47bad87f@goodmis.org"},"message":"tracing: Fix crash when freeing instances with event triggers\n\ncommit 86b389ff22bd6ad8fd3cb98e41cd271886c6d023 upstream.\n\nIf a instance has an event trigger enabled when it is freed, it could cause\nan access of free memory. Here's the case that crashes:\n\n # cd /sys/kernel/tracing\n # mkdir instances/foo\n # echo snapshot > instances/foo/events/initcall/initcall_start/trigger\n # rmdir instances/foo\n\nWould produce:\n\n general protection fault: 0000 [#1] PREEMPT SMP PTI\n Modules linked in: tun bridge ...\n CPU: 5 PID: 6203 Comm: rmdir Tainted: G        W         4.17.0-rc4-test+ #933\n Hardware name: Hewlett-Packard HP Compaq Pro 6300 SFF/339A, BIOS K01 v03.03 07/14/2016\n RIP: 0010:clear_event_triggers+0x3b/0x70\n RSP: 0018:ffffc90003783de0 EFLAGS: 00010286\n RAX: 0000000000000000 RBX: 6b6b6b6b6b6b6b2b RCX: 0000000000000000\n RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8800c7130ba0\n RBP: ffffc90003783e00 R08: ffff8801131993f8 R09: 0000000100230016\n R10: ffffc90003783d80 R11: 0000000000000000 R12: ffff8800c7130ba0\n R13: ffff8800c7130bd8 R14: ffff8800cc093768 R15: 00000000ffffff9c\n FS:  00007f6f4aa86700(0000) GS:ffff88011eb40000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f6f4a5aed60 CR3: 00000000cd552001 CR4: 00000000001606e0\n Call Trace:\n  event_trace_del_tracer+0x2a/0xc5\n  instance_rmdir+0x15c/0x200\n  tracefs_syscall_rmdir+0x52/0x90\n  vfs_rmdir+0xdb/0x160\n  do_rmdir+0x16d/0x1c0\n  __x64_sys_rmdir+0x17/0x20\n  do_syscall_64+0x55/0x1a0\n  entry_SYSCALL_64_after_hwframe+0x49/0xbe\n\nThis was due to the call the clears out the triggers when an instance is\nbeing deleted not removing the trigger from the link list.\n\nCc: stable@vger.kernel.org\nFixes: 85f2b08268c01 (\"tracing: Add basic event trigger framework\")\nSigned-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/0ea40e76fb392a6926089ddfbbcba3c3a33de924"},{"sha":"cb43adab6f4c66bd01f503d6cbbddabfc8d3daa8","author":{"name":"Steven Rostedt (VMware)","email":"43232e92d70cc7aa53504ad0397085ee47bad87f@goodmis.org"},"message":"tracing: Make the snapshot trigger work with instances\n\ncommit 2824f5033248600673e3e126a4d135363cbfd9ac upstream.\n\nThe snapshot trigger currently only affects the main ring buffer, even when\nit is used by the instances. This can be confusing as the snapshot trigger\nis listed in the instance.\n\n > # cd /sys/kernel/tracing\n > # mkdir instances/foo\n > # echo snapshot > instances/foo/events/syscalls/sys_enter_fchownat/trigger\n > # echo top buffer > trace_marker\n > # echo foo buffer > instances/foo/trace_marker\n > # touch /tmp/bar\n > # chown rostedt /tmp/bar\n > # cat instances/foo/snapshot\n # tracer: nop\n #\n #\n # * Snapshot is freed *\n #\n # Snapshot commands:\n # echo 0 > snapshot : Clears and frees snapshot buffer\n # echo 1 > snapshot : Allocates snapshot buffer, if not already allocated.\n #                      Takes a snapshot of the main buffer.\n # echo 2 > snapshot : Clears snapshot buffer (but does not allocate or free)\n #                      (Doesn't have to be '2' works with any number that\n #                       is not a '0' or '1')\n\n > # cat snapshot\n # tracer: nop\n #\n #                              _-----=> irqs-off\n #                             / _----=> need-resched\n #                            | / _---=> hardirq/softirq\n #                            || / _--=> preempt-depth\n #                            ||| /     delay\n #           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION\n #              | |       |   ||||       |         |\n             bash-1189  [000] ....   111.488323: tracing_mark_write: top buffer\n\nNot only did the snapshot occur in the top level buffer, but the instance\nsnapshot buffer should have been allocated, and it is still free.\n\nCc: stable@vger.kernel.org\nFixes: 85f2b08268c01 (\"tracing: Add basic event trigger framework\")\nSigned-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/cb43adab6f4c66bd01f503d6cbbddabfc8d3daa8"},{"sha":"f230f951e0e7b602a793f31ae37bc6930b87472f","author":{"name":"Max Gurtovoy","email":"2f93054f4993088139f93ad83c8b051f7d225637@mellanox.com"},"message":"nvme: fix extended data LBA supported setting\n\ncommit c97f414c54a255f4f05a50a2625efaeee406e134 upstream.\n\nThis value depands on the metadata support value, so reorder the\ninitialization to fit.\n\nFixes: b5be3b392 (\"nvme: always unregister the integrity profile in __nvme_revalidate_disk\")\nSigned-off-by: Max Gurtovoy <maxg@mellanox.com>\nSigned-off-by: Christoph Hellwig <hch@lst.de>\nCc: stable@vger.kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/megous/linux/commits/f230f951e0e7b602a793f31ae37bc6930b87472f"}]}
{"actor":{"display_login":"megous"}}