{"push_id":1132457019,"size":745,"distinct_size":3,"ref":"refs/heads/nextthing/4.4/next","head":"9fd3f72cb394246d802a86af4136669062ee8c33","before":"f19d39566e65b82281cdd251325f9c06c37523a7","commits":[{"sha":"84cf91ad330f5c9ba51f761a37e58b9aa99bf470","author":{"name":"Christian Borntraeger","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"s390/cpumf: Fix lpp detection\n\ncommit 7a76aa95f6f6682db5629449d763251d1c9f8c4e upstream.\n\nwe have to check bit 40 of the facility list before issuing LPP\nand not bit 48. Otherwise a guest running on a system with\n\"The decimal-floating-point zoned-conversion facility\" and without\nthe \"The set-program-parameters facility\" might crash on an lpp\ninstruction.\n\nSigned-off-by: Christian Borntraeger <borntraeger@de.ibm.com>\nFixes: e22cf8ca6f75 (\"s390/cpumf: rework program parameter setting to detect guest samples\")\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/NextThingCo/CHIP-linux/commits/84cf91ad330f5c9ba51f761a37e58b9aa99bf470"},{"sha":"4c8fe4f52755d4690a745f4e56b543c51add86fe","author":{"name":"Arnd Bergmann","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"regulator: core: avoid unused variable warning\n\ncommit fa731ac7ea04a7d3a5c6d2f568132478c02a83b3 upstream.\n\nThe second argument of the mutex_lock_nested() helper is only\nevaluated if CONFIG_DEBUG_LOCK_ALLOC is set. Otherwise we\nget this build warning for the new regulator_lock_supply\nfunction:\n\ndrivers/regulator/core.c: In function 'regulator_lock_supply':\ndrivers/regulator/core.c:142:6: warning: unused variable 'i' [-Wunused-variable]\n\nTo avoid the warning, this restructures the code to make it\nboth simpler and to move the 'i++' outside of the mutex_lock_nested\ncall, where it is now always used and the variable is not\nflagged as unused.\n\nWe had some discussion about changing mutex_lock_nested to an\ninline function, which would make the code do the right thing here,\nbut in the end decided against it, in order to guarantee that\nmutex_lock_nested() does not introduced overhead without\nCONFIG_DEBUG_LOCK_ALLOC.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nFixes: 9f01cd4a915 (\"regulator: core: introduce function to lock regulators and its supplies\")\nLink: http://permalink.gmane.org/gmane.linux.kernel/2068900\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/4c8fe4f52755d4690a745f4e56b543c51add86fe"},{"sha":"b1999fa6e8145305a6c8bda30ea20783717708e6","author":{"name":"Thierry Reding","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"regulator: core: Fix nested locking of supplies\n\ncommit 70a7fb80e85ae7f78f8e90cec3fbd862ea6a4d4b upstream.\n\nCommit fa731ac7ea04 (\"regulator: core: avoid unused variable warning\")\nintroduced a subtle change in how supplies are locked. Where previously\ncode was always locking the regulator of the current iteration, the new\nimplementation only locks the regulator if it has a supply. For any\ngiven power tree that means that the root will never get locked.\n\nOn the other hand the regulator_unlock_supply() will still release all\nthe locks, which in turn causes the lock debugging code to warn about a\nmutex being unlocked which wasn't locked.\n\nCc: Mark Brown <broonie@kernel.org>\nCc: Arnd Bergmann <arnd@arndb.de>\nFixes: Fixes: fa731ac7ea04 (\"regulator: core: avoid unused variable warning\")\nSigned-off-by: Thierry Reding <treding@nvidia.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/b1999fa6e8145305a6c8bda30ea20783717708e6"},{"sha":"e08f9a7c0e0242c2fae664d252e25c9bf93db522","author":{"name":"Arnd Bergmann","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"ASoC: samsung: pass DMA channels as pointers\n\ncommit b9a1a743818ea3265abf98f9431623afa8c50c86 upstream.\n\nARM64 allmodconfig produces a bunch of warnings when building the\nsamsung ASoC code:\n\nsound/soc/samsung/dmaengine.c: In function 'samsung_asoc_init_dma_data':\nsound/soc/samsung/dmaengine.c:53:32: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]\n   playback_data->filter_data = (void *)playback->channel;\nsound/soc/samsung/dmaengine.c:60:31: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]\n   capture_data->filter_data = (void *)capture->channel;\n\nWe could easily shut up the warning by adding an intermediate cast,\nbut there is a bigger underlying problem: The use of IORESOURCE_DMA\nto pass data from platform code to device drivers is dubious to start\nwith, as what we really want is a pointer that can be passed into\na filter function.\n\nNote that on s3c64xx, the pl08x DMA data is already a pointer, but\ngets cast to resource_size_t so we can pass it as a resource, and it\nthen gets converted back to a pointer. In contrast, the data we pass\nfor s3c24xx is an index into a device specific table, and we artificially\nconvert that into a pointer for the filter function.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nReviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/e08f9a7c0e0242c2fae664d252e25c9bf93db522"},{"sha":"c045105c641ccbeb6e94e87980cc8db870aa3961","author":{"name":"Arnd Bergmann","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"mmc: sh_mmcif: rework dma channel handling\n\ncommit 27cbd7e815a8e223ff7c4fe56daca724101288ac upstream.\n\nWhen compiling the sh_mmcif driver for ARM64, we currently\nget a harmless build warning:\n\n../drivers/mmc/host/sh_mmcif.c: In function 'sh_mmcif_request_dma_one':\n../drivers/mmc/host/sh_mmcif.c:417:4: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]\n    (void *)pdata->slave_id_tx :\n    ^\n../drivers/mmc/host/sh_mmcif.c:418:4: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]\n    (void *)pdata->slave_id_rx;\n\nThis could be worked around by adding another cast to uintptr_t, but\nI decided to simplify the code a little more to avoid that. This\nsplits out the platform data using code into a separate function\nand builds that only for CONFIG_SUPERH. This part still has a typecast\nbut does not need a second one. The SH platform code could be further\nmodified to pass a pointer directly as we do on other architectures\nwhen we have a filter function.\n\nThe normal case is simplified further and now just calls\ndma_request_slave_channel() directly without going through the\ncompat handling.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/c045105c641ccbeb6e94e87980cc8db870aa3961"},{"sha":"19e0783ae96837e30e94acdb0cc4ae935338a969","author":{"name":"Chris Paterson","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"mmc: sh_mmcif: Correct TX DMA channel allocation\n\ncommit a32ef81c9889c9554a3c4b465c4ee7b2d26c6b10 upstream.\n\nCommit 27cbd7e815a8 (\"mmc: sh_mmcif: rework dma channel handling\")\nintroduced a typo causing the TX DMA channel allocation to be overwritten\nby the requested RX DMA channel.\n\nFixes: 27cbd7e815a8 (\"mmc: sh_mmcif: rework dma channel handling\")\nSigned-off-by: Chris Paterson <chris.paterson2@renesas.com>\nAcked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nAcked-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/19e0783ae96837e30e94acdb0cc4ae935338a969"},{"sha":"e8c28e096a07b7bdf6fae534c8ff5f372b25ea82","author":{"name":"Borislav Petkov","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"x86/microcode/intel: Make early loader look for builtin microcode too\n\ncommit 264285ac01673e70557c43ecee338ce97c4c0672 upstream.\n\nSet the initrd @start depending on the presence of an initrd. Otherwise,\nbuiltin microcode loading doesn't work as the start is wrong and we're\nusing it to compute offset to the microcode blobs.\n\nTested-by: Thomas Voegtle <tv@lio96.de>\nSigned-off-by: Borislav Petkov <bp@suse.de>\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/1454499225-21544-3-git-send-email-bp@alien8.de\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/NextThingCo/CHIP-linux/commits/e8c28e096a07b7bdf6fae534c8ff5f372b25ea82"},{"sha":"5aeaf8bd6c6a3f29a1ab55987c10741ef984ea52","author":{"name":"Borislav Petkov","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"x86/microcode: Untangle from BLK_DEV_INITRD\n\ncommit 5f9c01aa7c49a2d74474d6d879a797b8badf29e6 upstream.\n\nThomas Voegtle reported that doing oldconfig with a .config which has\nCONFIG_MICROCODE enabled but BLK_DEV_INITRD disabled prevents the\nmicrocode loading mechanism from being built.\n\nSo untangle it from the BLK_DEV_INITRD dependency so that oldconfig\ndoesn't turn it off and add an explanatory text to its Kconfig help what\nthe supported methods for supplying microcode are.\n\nReported-by: Thomas Voegtle <tv@lio96.de>\nTested-by: Thomas Voegtle <tv@lio96.de>\nSigned-off-by: Borislav Petkov <bp@suse.de>\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/1454499225-21544-2-git-send-email-bp@alien8.de\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/NextThingCo/CHIP-linux/commits/5aeaf8bd6c6a3f29a1ab55987c10741ef984ea52"},{"sha":"7657a398c105500d1614444a26c1fc9166813fb8","author":{"name":"Andy Lutomirski","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"x86/entry/compat: Keep TS_COMPAT set during signal delivery\n\ncommit 4e79e182b419172e35936a47f098509092d69817 upstream.\n\nSignal delivery needs to know the sign of an interrupted syscall's\nreturn value in order to detect -ERESTART variants.  Normally this\nworks independently of bitness because syscalls internally return\nlong.  Under ptrace, however, this can break, and syscall_get_error\nis supposed to sign-extend regs->ax if needed.\n\nWe were clearing TS_COMPAT too early, though, and this prevented\nsign extension, which subtly broke syscall restart under ptrace.\n\nReported-by: Robert O'Callahan <robert@ocallahan.org>\nSigned-off-by: Andy Lutomirski <luto@kernel.org>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nCc: Andy Lutomirski <luto@amacapital.net>\nCc: Borislav Petkov <bp@alien8.de>\nCc: Brian Gerst <brgerst@gmail.com>\nCc: Denys Vlasenko <dvlasenk@redhat.com>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Shuah Khan <shuahkh@osg.samsung.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nFixes: c5c46f59e4e7 (\"x86/entry: Add new, comprehensible entry and exit handlers written in C\")\nLink: http://lkml.kernel.org/r/cbce3cf545522f64eb37f5478cb59746230db3b5.1455142412.git.luto@kernel.org\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/NextThingCo/CHIP-linux/commits/7657a398c105500d1614444a26c1fc9166813fb8"},{"sha":"f6724209df88ec1a760d036b71b8f871b1556785","author":{"name":"Stephane Eranian","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"perf/x86/intel: Add definition for PT PMI bit\n\ncommit 5690ae28e472d25e330ad0c637a5cea3fc39fb32 upstream.\n\nThis patch adds a definition for GLOBAL_OVFL_STATUS bit 55\nwhich is used with the Processor Trace (PT) feature.\n\nSigned-off-by: Stephane Eranian <eranian@google.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nCc: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: Jiri Olsa <jolsa@redhat.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Vince Weaver <vincent.weaver@maine.edu>\nCc: adrian.hunter@intel.com\nCc: kan.liang@intel.com\nCc: namhyung@kernel.org\nLink: http://lkml.kernel.org/r/1457034642-21837-2-git-send-email-eranian@google.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/NextThingCo/CHIP-linux/commits/f6724209df88ec1a760d036b71b8f871b1556785"},{"sha":"54fda475686cfb9a90bb558c0fa590e644503432","author":{"name":"Bjorn Helgaas","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"x86/PCI: Mark Broadwell-EP Home Agent & PCU as having non-compliant BARs\n\ncommit b894157145e4ac7598d7062bc93320898a5e059e upstream.\n\nThe Home Agent and PCU PCI devices in Broadwell-EP have a non-BAR register\nwhere a BAR should be.  We don't know what the side effects of sizing the\n\"BAR\" would be, and we don't know what address space the \"BAR\" might appear\nto describe.\n\nMark these devices as having non-compliant BARs so the PCI core doesn't\ntouch them.\n\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nTested-by: Andi Kleen <ak@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/54fda475686cfb9a90bb558c0fa590e644503432"},{"sha":"0f6e5e26e68f1171b7cf8bebb7ce86c95e506639","author":{"name":"Paolo Bonzini","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"KVM: x86: fix missed hardware breakpoints\n\ncommit 4e422bdd2f849d98fffccbc3295c2f0996097fb3 upstream.\n\nSometimes when setting a breakpoint a process doesn't stop on it.\nThis is because the debug registers are not loaded correctly on\nVCPU load.\n\nThe following simple reproducer from Oleg Nesterov tries using debug\nregisters in both the host and the guest, for example by running \"./bp\n0 1\" on the host and \"./bp 14 15\" under QEMU.\n\n    #include <unistd.h>\n    #include <signal.h>\n    #include <stdlib.h>\n    #include <stdio.h>\n    #include <sys/wait.h>\n    #include <sys/ptrace.h>\n    #include <sys/user.h>\n    #include <asm/debugreg.h>\n    #include <assert.h>\n\n    #define offsetof(TYPE, MEMBER) ((size_t) &((TYPE *)0)->MEMBER)\n\n    unsigned long encode_dr7(int drnum, int enable, unsigned int type, unsigned int len)\n    {\n        unsigned long dr7;\n\n        dr7 = ((len | type) & 0xf)\n            << (DR_CONTROL_SHIFT + drnum * DR_CONTROL_SIZE);\n        if (enable)\n            dr7 |= (DR_GLOBAL_ENABLE << (drnum * DR_ENABLE_SIZE));\n\n        return dr7;\n    }\n\n    int write_dr(int pid, int dr, unsigned long val)\n    {\n        return ptrace(PTRACE_POKEUSER, pid,\n                offsetof (struct user, u_debugreg[dr]),\n                val);\n    }\n\n    void set_bp(pid_t pid, void *addr)\n    {\n        unsigned long dr7;\n        assert(write_dr(pid, 0, (long)addr) == 0);\n        dr7 = encode_dr7(0, 1, DR_RW_EXECUTE, DR_LEN_1);\n        assert(write_dr(pid, 7, dr7) == 0);\n    }\n\n    void *get_rip(int pid)\n    {\n        return (void*)ptrace(PTRACE_PEEKUSER, pid,\n                offsetof(struct user, regs.rip), 0);\n    }\n\n    void test(int nr)\n    {\n        void *bp_addr = &&label + nr, *bp_hit;\n        int pid;\n\n        printf(\"test bp %d\\n\", nr);\n        assert(nr < 16); // see 16 asm nops below\n\n        pid = fork();\n        if (!pid) {\n            assert(ptrace(PTRACE_TRACEME, 0,0,0) == 0);\n            kill(getpid(), SIGSTOP);\n            for (;;) {\n                label: asm (\n                    \"nop; nop; nop; nop;\"\n                    \"nop; nop; nop; nop;\"\n                    \"nop; nop; nop; nop;\"\n                    \"nop; nop; nop; nop;\"\n                );\n            }\n        }\n\n        assert(pid == wait(NULL));\n        set_bp(pid, bp_addr);\n\n        for (;;) {\n            assert(ptrace(PTRACE_CONT, pid, 0, 0) == 0);\n            assert(pid == wait(NULL));\n\n            bp_hit = get_rip(pid);\n            if (bp_hit != bp_addr)\n                fprintf(stderr, \"ERR!! hit wrong bp %ld != %d\\n\",\n                    bp_hit - &&label, nr);\n        }\n    }\n\n    int main(int argc, const char *argv[])\n    {\n        while (--argc) {\n            int nr = atoi(*++argv);\n            if (!fork())\n                test(nr);\n        }\n\n        while (wait(NULL) > 0)\n            ;\n        return 0;\n    }\n\nSuggested-by: Nadadv Amit <namit@cs.technion.ac.il>\nReported-by: Andrey Wagin <avagin@gmail.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/0f6e5e26e68f1171b7cf8bebb7ce86c95e506639"},{"sha":"49f0cbfc3e73108c319c3d3cc5fe04587d96b654","author":{"name":"Radim Krčmář","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"KVM: i8254: change PIT discard tick policy\n\ncommit 7dd0fdff145c5be7146d0ac06732ae3613412ac1 upstream.\n\nDiscard policy uses ack_notifiers to prevent injection of PIT interrupts\nbefore EOI from the last one.\n\nThis patch changes the policy to always try to deliver the interrupt,\nwhich makes a difference when its vector is in ISR.\nOld implementation would drop the interrupt, but proposed one injects to\nIRR, like real hardware would.\n\nThe old policy breaks legacy NMI watchdogs, where PIT is used through\nvirtual wire (LVT0): PIT never sends an interrupt before receiving EOI,\nthus a guest deadlock with disabled interrupts will stop NMIs.\n\nNote that NMI doesn't do EOI, so PIT also had to send a normal interrupt\nthrough IOAPIC.  (KVM's PIT is deeply rotten and luckily not used much\nin modern systems.)\n\nEven though there is a chance of regressions, I think we can fix the\nLVT0 NMI bug without introducing a new tick policy.\n\nReported-by: Yuki Shibuya <shibuya.yk@ncos.nec.co.jp>\nReviewed-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Radim Krčmář <rkrcmar@redhat.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/49f0cbfc3e73108c319c3d3cc5fe04587d96b654"},{"sha":"4e2fa4bbbac1c2e198e4c980d451c9ec568ae798","author":{"name":"Paolo Bonzini","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"KVM: fix spin_lock_init order on x86\n\ncommit e9ad4ec8379ad1ba6f68b8ca1c26b50b5ae0a327 upstream.\n\nMoving the initialization earlier is needed in 4.6 because\nkvm_arch_init_vm is now using mmu_lock, causing lockdep to\ncomplain:\n\n[  284.440294] INFO: trying to register non-static key.\n[  284.445259] the code is fine but needs lockdep annotation.\n[  284.450736] turning off the locking correctness validator.\n...\n[  284.528318]  [<ffffffff810aecc3>] lock_acquire+0xd3/0x240\n[  284.533733]  [<ffffffffa0305aa0>] ? kvm_page_track_register_notifier+0x20/0x60 [kvm]\n[  284.541467]  [<ffffffff81715581>] _raw_spin_lock+0x41/0x80\n[  284.546960]  [<ffffffffa0305aa0>] ? kvm_page_track_register_notifier+0x20/0x60 [kvm]\n[  284.554707]  [<ffffffffa0305aa0>] kvm_page_track_register_notifier+0x20/0x60 [kvm]\n[  284.562281]  [<ffffffffa02ece70>] kvm_mmu_init_vm+0x20/0x30 [kvm]\n[  284.568381]  [<ffffffffa02dbf7a>] kvm_arch_init_vm+0x1ea/0x200 [kvm]\n[  284.574740]  [<ffffffffa02bff3f>] kvm_dev_ioctl+0xbf/0x4d0 [kvm]\n\nHowever, it also helps fixing a preexisting problem, which is why this\npatch is also good for stable kernels: kvm_create_vm was incrementing\ncurrent->mm->mm_count but not decrementing it at the out_err label (in\ncase kvm_init_mmu_notifier failed).  The new initialization order makes\nit possible to add the required mmdrop without adding a new error label.\n\nReported-by: Borislav Petkov <bp@alien8.de>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/4e2fa4bbbac1c2e198e4c980d451c9ec568ae798"},{"sha":"c44b175bf03cd74e517f3c98b2cb4896e04202ae","author":{"name":"Paolo Bonzini","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"KVM: VMX: avoid guest hang on invalid invept instruction\n\ncommit 2849eb4f99d54925c543db12917127f88b3c38ff upstream.\n\nA guest executing an invalid invept instruction would hang\nbecause the instruction pointer was not updated.\n\nFixes: bfd0a56b90005f8c8a004baf407ad90045c2b11e\nReviewed-by: David Matlack <dmatlack@google.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/c44b175bf03cd74e517f3c98b2cb4896e04202ae"},{"sha":"f9153f95f2b5a1a90b81c746342bed9d40dc9ae0","author":{"name":"Paolo Bonzini","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"KVM: VMX: avoid guest hang on invalid invvpid instruction\n\ncommit f6870ee9e53430f2a318ccf0dd5e66bb46194e43 upstream.\n\nA guest executing an invalid invvpid instruction would hang\nbecause the instruction pointer was not updated.\n\nReported-by: jmontleo@redhat.com\nTested-by: jmontleo@redhat.com\nFixes: 99b83ac893b84ed1a62ad6d1f2b6cc32026b9e85\nReviewed-by: David Matlack <dmatlack@google.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/f9153f95f2b5a1a90b81c746342bed9d40dc9ae0"},{"sha":"6a84dfcbf56eab7955b607e22696cb145e019f20","author":{"name":"Paolo Bonzini","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"KVM: VMX: fix nested vpid for old KVM guests\n\ncommit ef697a712a6165aea7779c295604b099e8bfae2e upstream.\n\nOld KVM guests invoke single-context invvpid without actually checking\nwhether it is supported.  This was fixed by commit 518c8ae (\"KVM: VMX:\nMake sure single type invvpid is supported before issuing invvpid\ninstruction\", 2010-08-01) and the patch after, but pre-2.6.36\nkernels lack it including RHEL 6.\n\nReported-by: jmontleo@redhat.com\nTested-by: jmontleo@redhat.com\nFixes: 99b83ac893b84ed1a62ad6d1f2b6cc32026b9e85\nReviewed-by: David Matlack <dmatlack@google.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/6a84dfcbf56eab7955b607e22696cb145e019f20"},{"sha":"37014e0c5c90e250892da8aba8533cd43bacb4eb","author":{"name":"Alexander Shishkin","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"perf/core: Fix perf_sched_count derailment\n\ncommit 927a5570855836e5d5859a80ce7e91e963545e8f upstream.\n\nThe error path in perf_event_open() is such that asking for a sampling\nevent on a PMU that doesn't generate interrupts will end up in dropping\nthe perf_sched_count even though it hasn't been incremented for this\nevent yet.\n\nGiven a sufficient amount of these calls, we'll end up disabling\nscheduler's jump label even though we'd still have active events in the\nsystem, thereby facilitating the arrival of the infernal regions upon us.\n\nI'm fixing this by moving account_event() inside perf_event_alloc().\n\nSigned-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Arnaldo Carvalho de Melo <acme@infradead.org>\nCc: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: Jiri Olsa <jolsa@redhat.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Stephane Eranian <eranian@google.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Vince Weaver <vincent.weaver@maine.edu>\nCc: vince@deater.net\nLink: http://lkml.kernel.org/r/1456917854-29427-1-git-send-email-alexander.shishkin@linux.intel.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/NextThingCo/CHIP-linux/commits/37014e0c5c90e250892da8aba8533cd43bacb4eb"},{"sha":"2dfe91df33715503b253563d5e6d9a816758485c","author":{"name":"Andi Kleen","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"perf tools: Dont stop PMU parsing on alias parse error\n\ncommit 940db6dcd3f4659303fdf6befe7416adc4d24118 upstream.\n\nWhen an error happens during alias parsing currently the complete\nparsing of all attributes of the PMU is stopped. This is breaks old perf\non a newer kernel that may have not-yet-know alias attributes (such as\n.scale or .per-pkg).\n\nContinue when some attribute is unparseable.\n\nThis is IMHO a stable candidate and should be backported to older\nversions to avoid problems with newer kernels.\n\nv2: Print warnings when something goes wrong.\nv3: Change warning to debug output\n\nSigned-off-by: Andi Kleen <ak@linux.intel.com>\nCc: Jiri Olsa <jolsa@kernel.org>\nLink: http://lkml.kernel.org/r/1455749095-18358-1-git-send-email-andi@firstfloor.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/2dfe91df33715503b253563d5e6d9a816758485c"},{"sha":"6be7771fe7242d7d4399545e0c9e2f6f3cd76725","author":{"name":"Wang Nan","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"perf tools: Fix checking asprintf return value\n\ncommit 26dee028d365fbc0e3326606a8520260b4462381 upstream.\n\nAccording to man pages, asprintf returns -1 when failure. This patch\nfixes two incorrect return value checker.\n\nSigned-off-by: Wang Nan <wangnan0@huawei.com>\nCc: Adrian Hunter <adrian.hunter@intel.com>\nCc: Alexei Starovoitov <ast@kernel.org>\nCc: Brendan Gregg <brendan.d.gregg@gmail.com>\nCc: Cody P Schafer <dev@codyps.com>\nCc: He Kuang <hekuang@huawei.com>\nCc: Jeremie Galarneau <jeremie.galarneau@efficios.com>\nCc: Jiri Olsa <jolsa@kernel.org>\nCc: Kirill Smelkov <kirr@nexedi.com>\nCc: Li Zefan <lizefan@huawei.com>\nCc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Zefan Li <lizefan@huawei.com>\nCc: pi3orama@163.com\nFixes: ffeb883e5662 (\"perf tools: Show proper error message for wrong terms of hw/sw events\")\nLink: http://lkml.kernel.org/r/1455882283-79592-5-git-send-email-wangnan0@huawei.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NextThingCo/CHIP-linux/commits/6be7771fe7242d7d4399545e0c9e2f6f3cd76725"}]}
{"actor":{"display_login":"mripard"}}