[PATCH 4.5 006/238] KVM: x86: fix missed hardware breakpoints

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit 4e422bdd2f849d98fffccbc3295c2f0996097fb3 upstream. Sometimes when setting a breakpoint a process doesn't stop on it. This is because the debug

[PATCH 4.5 019/238] sched/preempt, sh: kmap_coherent relies on disabled preemption

4.5-stable review patch. If anyone has any objections, please let me know. -- From: David Hildenbrand commit b15d53d009558d14c4f394a6d1fa2039c7f45c43 upstream. kmap_coherent needs disabled preemption to not schedule in the critical section, just like

[PATCH 4.5 018/238] sched/fair: Avoid using decay_load_missed() with a negative value

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Byungchul Park commit 7400d3bbaa229eb8e7631d28fb34afd7cd2c96ff upstream. decay_load_missed() cannot handle nagative values, so we need to prevent using the function

[PATCH 4.5 006/238] KVM: x86: fix missed hardware breakpoints

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit 4e422bdd2f849d98fffccbc3295c2f0996097fb3 upstream. Sometimes when setting a breakpoint a process doesn't stop on it. This is because the debug registers are not loaded

[PATCH 4.5 019/238] sched/preempt, sh: kmap_coherent relies on disabled preemption

4.5-stable review patch. If anyone has any objections, please let me know. -- From: David Hildenbrand commit b15d53d009558d14c4f394a6d1fa2039c7f45c43 upstream. kmap_coherent needs disabled preemption to not schedule in the critical section, just like kmap_coherent on mips and

[PATCH 4.5 018/238] sched/fair: Avoid using decay_load_missed() with a negative value

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Byungchul Park commit 7400d3bbaa229eb8e7631d28fb34afd7cd2c96ff upstream. decay_load_missed() cannot handle nagative values, so we need to prevent using the function with a negative value.

Re: [PATCH v5 1/6] pwms: pwm-ti*: Get the clock from the PWMSS (parent)

Hi guys On Tue, 5 Apr 2016, Franklin S Cooper Jr. wrote: > On 04/05/2016 01:08 AM, Sekhar Nori wrote: > > On Tuesday 08 March 2016 06:53 AM, Franklin S Cooper Jr wrote: > > > The eCAP and ePWM doesn't have their own separate clocks. They simply > > > utilize the clock provided directly by the

Re: [PATCH v5 1/6] pwms: pwm-ti*: Get the clock from the PWMSS (parent)

Hi guys On Tue, 5 Apr 2016, Franklin S Cooper Jr. wrote: > On 04/05/2016 01:08 AM, Sekhar Nori wrote: > > On Tuesday 08 March 2016 06:53 AM, Franklin S Cooper Jr wrote: > > > The eCAP and ePWM doesn't have their own separate clocks. They simply > > > utilize the clock provided directly by the

[PATCH 4.5 022/238] s390: fix floating pointer register corruption (again)

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Martin Schwidefsky commit e370e4769463a65dcf8806fa26d2874e0542ac41 upstream. There is a tricky interaction between the machine check handler and the critical sections

[PATCH 4.5 023/238] s390/cpumf: add missing lpp magic initialization

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Carstens commit 8f100bb1ff27873dd71f636da670e503b9ade3c6 upstream. Add the missing lpp magic initialization for cpu 0. Without this all samples on cpu 0 do not

[PATCH 4.5 024/238] s390/pci: enforce fmb page boundary rule

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 80c544ded25ac14d7cc3e555abb8ed2c2da99b84 upstream. The function measurement block must not cross a page boundary. Ensure that by raising the

[PATCH 4.5 026/238] PCI: Disable IO/MEM decoding for devices with non-compliant BARs

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit b84106b4e2290c081cdab521fa832596cdfea246 upstream. The PCI config header (first 64 bytes of each device's config space) is defined by the PCI spec so

[PATCH 4.5 033/238] sg: fix dxferp in from_to case

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Douglas Gilbert commit 5ecee0a3ee8d74b6950cb41e8989b0c2174568d4 upstream. One of the strange things that the original sg driver did was let the user provide both a

[PATCH 4.5 027/238] PCI: ACPI: IA64: fix IO port generic range check

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Lorenzo Pieralisi commit 4a2e7aab4ffce1e0e79b303dc2f9a03aa9f3a332 upstream. The [0 - 64k] ACPI PCI IO port resource boundary check in: acpi_dev_ioresource_flags()

[PATCH 4.5 033/238] sg: fix dxferp in from_to case

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Douglas Gilbert commit 5ecee0a3ee8d74b6950cb41e8989b0c2174568d4 upstream. One of the strange things that the original sg driver did was let the user provide both a data-out buffer (it followed

[PATCH 4.5 027/238] PCI: ACPI: IA64: fix IO port generic range check

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Lorenzo Pieralisi commit 4a2e7aab4ffce1e0e79b303dc2f9a03aa9f3a332 upstream. The [0 - 64k] ACPI PCI IO port resource boundary check in: acpi_dev_ioresource_flags() is currently applied

[PATCH 4.5 022/238] s390: fix floating pointer register corruption (again)

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Martin Schwidefsky commit e370e4769463a65dcf8806fa26d2874e0542ac41 upstream. There is a tricky interaction between the machine check handler and the critical sections of load_fpu_regs and

[PATCH 4.5 023/238] s390/cpumf: add missing lpp magic initialization

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Carstens commit 8f100bb1ff27873dd71f636da670e503b9ade3c6 upstream. Add the missing lpp magic initialization for cpu 0. Without this all samples on cpu 0 do not have the most significant

[PATCH 4.5 024/238] s390/pci: enforce fmb page boundary rule

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 80c544ded25ac14d7cc3e555abb8ed2c2da99b84 upstream. The function measurement block must not cross a page boundary. Ensure that by raising the alignment requirement to the

[PATCH 4.5 026/238] PCI: Disable IO/MEM decoding for devices with non-compliant BARs

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit b84106b4e2290c081cdab521fa832596cdfea246 upstream. The PCI config header (first 64 bytes of each device's config space) is defined by the PCI spec so generic software can

[PATCH 4.5 020/238] EDAC/sb_edac: Fix computation of channel address

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit eb1af3b71f9d83e45f2fd2fd649356e98e1c582c upstream. Large memory Haswell-EX systems with multiple DIMMs per channel were sometimes reporting the wrong

[PATCH 4.5 010/238] KVM: VMX: avoid guest hang on invalid invvpid instruction

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit f6870ee9e53430f2a318ccf0dd5e66bb46194e43 upstream. A guest executing an invalid invvpid instruction would hang because the instruction pointer was not

[PATCH 4.5 025/238] pinctrl-bcm2835: Fix cut-and-paste error in "pull" parsing

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Phil Elwell commit 2c7e3306d23864d49f686f22e56e180ff0fffb7f upstream. The DT bindings for pinctrl-bcm2835 allow both the function and pull to contain either one entry or

[PATCH 4.5 031/238] x86/iopl: Fix iopl capability check on Xen PV

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit c29016cf41fe9fa994a5ecca607cf5f1cd98801e upstream. iopl(3) is supposed to work if iopl is already 3, even if unprivileged. This didn't work right on

[PATCH 4.5 010/238] KVM: VMX: avoid guest hang on invalid invvpid instruction

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit f6870ee9e53430f2a318ccf0dd5e66bb46194e43 upstream. A guest executing an invalid invvpid instruction would hang because the instruction pointer was not updated.

[PATCH 4.5 025/238] pinctrl-bcm2835: Fix cut-and-paste error in "pull" parsing

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Phil Elwell commit 2c7e3306d23864d49f686f22e56e180ff0fffb7f upstream. The DT bindings for pinctrl-bcm2835 allow both the function and pull to contain either one entry or one per pin. However,

[PATCH 4.5 031/238] x86/iopl: Fix iopl capability check on Xen PV

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit c29016cf41fe9fa994a5ecca607cf5f1cd98801e upstream. iopl(3) is supposed to work if iopl is already 3, even if unprivileged. This didn't work right on Xen PV. Fix it.

[PATCH 4.5 020/238] EDAC/sb_edac: Fix computation of channel address

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit eb1af3b71f9d83e45f2fd2fd649356e98e1c582c upstream. Large memory Haswell-EX systems with multiple DIMMs per channel were sometimes reporting the wrong DIMM. Found three

[PATCH 4.5 029/238] x86/apic: Fix suspicious RCU usage in smp_trace_call_function_interrupt()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Dave Jones commit 7834c10313fb823e538f2772be78edcdeed2e6e3 upstream. Since 4.4, I've been able to trigger this occasionally: === [ INFO:

[PATCH 4.5 030/238] x86/iopl/64: Properly context-switch IOPL on Xen PV

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit b7a584598aea7ca73140cb87b40319944dd3393f upstream. On Xen PV, regs->flags doesn't reliably reflect IOPL and the exit-to-userspace code doesn't change

[PATCH 4.5 030/238] x86/iopl/64: Properly context-switch IOPL on Xen PV

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit b7a584598aea7ca73140cb87b40319944dd3393f upstream. On Xen PV, regs->flags doesn't reliably reflect IOPL and the exit-to-userspace code doesn't change IOPL. We need to

[PATCH 4.5 029/238] x86/apic: Fix suspicious RCU usage in smp_trace_call_function_interrupt()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Dave Jones commit 7834c10313fb823e538f2772be78edcdeed2e6e3 upstream. Since 4.4, I've been able to trigger this occasionally: === [ INFO: suspicious RCU usage. ]

[PATCH 4.5 021/238] EDAC, amd64_edac: Shift wrapping issue in f1x_get_norm_dct_addr()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 6f3508f61c814ee852c199988a62bd954c50dfc1 upstream. dct_sel_base_off is declared as a u64 but we're only using the lower 32 bits because of a

Re: [GIT PULL] ext4 bug fixes for 4.6

On Sun, Apr 10, 2016 at 1:48 PM, Linus Torvalds wrote: > > The attached patch is actually tested and seems to fix the issue. Christ. Now really attached. I'll just go back to bed, because today is just not working out. Maybe things will be better tomorrow. Or

Re: [GIT PULL] ext4 bug fixes for 4.6

On Sun, Apr 10, 2016 at 1:29 PM, Linus Torvalds wrote: > > I think the right choice might be to > > (a) revert that patch (or just change the signal_pending() into > fatal_signal_pending()) > > (b) to get the latency advantage, do something like this: The

[PATCH 4.5 011/238] KVM: VMX: fix nested vpid for old KVM guests

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit ef697a712a6165aea7779c295604b099e8bfae2e upstream. Old KVM guests invoke single-context invvpid without actually checking whether it is supported.

[PATCH 4.5 041/238] ncr5380: Forget aborted commands

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit dc183965282d28c82f192e39cbfa91da85505a6f upstream. The list structures and related logic used in the NCR5380 driver mean that a command cannot be

[PATCH 4.5 021/238] EDAC, amd64_edac: Shift wrapping issue in f1x_get_norm_dct_addr()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 6f3508f61c814ee852c199988a62bd954c50dfc1 upstream. dct_sel_base_off is declared as a u64 but we're only using the lower 32 bits because of a shift wrapping bug. This can

Re: [GIT PULL] ext4 bug fixes for 4.6

On Sun, Apr 10, 2016 at 1:48 PM, Linus Torvalds wrote: > > The attached patch is actually tested and seems to fix the issue. Christ. Now really attached. I'll just go back to bed, because today is just not working out. Maybe things will be better tomorrow. Or maybe I should start drinking, and

Re: [GIT PULL] ext4 bug fixes for 4.6

On Sun, Apr 10, 2016 at 1:29 PM, Linus Torvalds wrote: > > I think the right choice might be to > > (a) revert that patch (or just change the signal_pending() into > fatal_signal_pending()) > > (b) to get the latency advantage, do something like this: The attached patch is actually tested and

[PATCH 4.5 011/238] KVM: VMX: fix nested vpid for old KVM guests

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit ef697a712a6165aea7779c295604b099e8bfae2e upstream. Old KVM guests invoke single-context invvpid without actually checking whether it is supported. This was fixed by

[PATCH 4.5 041/238] ncr5380: Forget aborted commands

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit dc183965282d28c82f192e39cbfa91da85505a6f upstream. The list structures and related logic used in the NCR5380 driver mean that a command cannot be queued twice (i.e. can't

[PATCH 4.5 036/238] aacraid: Set correct msix count for EEH recovery

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Raghava Aditya Renukunta commit ecc479e00db8eb110b200afe1effcb3df20ca7ae upstream. During EEH recovery number of online CPU's might change thereby changing

[PATCH 4.5 034/238] aacraid: Fix RRQ overload

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Raghava Aditya Renukunta commit 3f4ce057d51a9c0ed9b01ba693df685d230ffcae upstream. The driver utilizes an array of atomic variables to keep track of IO

[PATCH 4.5 039/238] ncr5380: Dont release lock for PIO transfer

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit 1678847ec93040ae8280d19c42ae0ba8a4233e6d upstream. The calls to NCR5380_transfer_pio() for DATA IN and DATA OUT phases will modify

[PATCH 4.5 037/238] sd: Fix discard granularity when LBPRZ=1

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Martin K. Petersen commit 6540a65da90c09590897310e31993b1f6e28485a upstream. Commit 397737223c59 ("sd: Make discard granularity match logical block size when

[PATCH 4.5 036/238] aacraid: Set correct msix count for EEH recovery

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Raghava Aditya Renukunta commit ecc479e00db8eb110b200afe1effcb3df20ca7ae upstream. During EEH recovery number of online CPU's might change thereby changing the number of MSIx vectors. Since

[PATCH 4.5 034/238] aacraid: Fix RRQ overload

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Raghava Aditya Renukunta commit 3f4ce057d51a9c0ed9b01ba693df685d230ffcae upstream. The driver utilizes an array of atomic variables to keep track of IO submissions to each vector. To submit an

[PATCH 4.5 039/238] ncr5380: Dont release lock for PIO transfer

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit 1678847ec93040ae8280d19c42ae0ba8a4233e6d upstream. The calls to NCR5380_transfer_pio() for DATA IN and DATA OUT phases will modify cmd->SCp.this_residual, cmd->SCp.ptr and

[PATCH 4.5 037/238] sd: Fix discard granularity when LBPRZ=1

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Martin K. Petersen commit 6540a65da90c09590897310e31993b1f6e28485a upstream. Commit 397737223c59 ("sd: Make discard granularity match logical block size when LBPRZ=1") accidentally set the

[PATCH 4.5 045/238] be2iscsi: set the boot_kset pointer to NULL in case of failure

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Maurizio Lombardi commit 84bd64993f916bcf86270c67686ecf4cea7b8933 upstream. In beiscsi_setup_boot_info(), the boot_kset pointer should be set to NULL in case of failure

[PATCH 4.5 035/238] aacraid: Fix memory leak in aac_fib_map_free

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Raghava Aditya Renukunta commit f88fa79a61726ce9434df9b4aede36961f709f17 upstream. aac_fib_map_free() calls pci_free_consistent() without checking that

[PATCH 4.5 043/238] ncr5380: Call scsi_eh_prep_cmnd() and scsi_eh_restore_cmnd() as and when appropriate

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit 8d5dbec3bcb24a7d071962448e0fecaca8c75cc7 upstream. This bug causes the wrong command to have its sense pointer overwritten, which sometimes leads

[PATCH 4.5 054/238] usb: retry reset if a device times out

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 264904ccc33c604d4b3141bbd33808152dfac45b upstream. Some devices I got show an inability to operate right after power on if they are already connected.

[PATCH 4.5 045/238] be2iscsi: set the boot_kset pointer to NULL in case of failure

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Maurizio Lombardi commit 84bd64993f916bcf86270c67686ecf4cea7b8933 upstream. In beiscsi_setup_boot_info(), the boot_kset pointer should be set to NULL in case of failure otherwise an invalid

[PATCH 4.5 035/238] aacraid: Fix memory leak in aac_fib_map_free

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Raghava Aditya Renukunta commit f88fa79a61726ce9434df9b4aede36961f709f17 upstream. aac_fib_map_free() calls pci_free_consistent() without checking that dev->hw_fib_va is not NULL and

[PATCH 4.5 043/238] ncr5380: Call scsi_eh_prep_cmnd() and scsi_eh_restore_cmnd() as and when appropriate

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit 8d5dbec3bcb24a7d071962448e0fecaca8c75cc7 upstream. This bug causes the wrong command to have its sense pointer overwritten, which sometimes leads to a NULL pointer deref. Fix

[PATCH 4.5 054/238] usb: retry reset if a device times out

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 264904ccc33c604d4b3141bbd33808152dfac45b upstream. Some devices I got show an inability to operate right after power on if they are already connected. They are beyond

[PATCH 4.5 053/238] dm: fix rq_end_stats() NULL pointer in dm_requeue_original_request()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Bryn M. Reeves commit 98dbc9c6c61698792e3a66f32f3bf066201d42d7 upstream. An "old" (.request_fn) DM 'struct request' stores a pointer to the associated 'struct dm_rq_target_io'

[PATCH 4.5 053/238] dm: fix rq_end_stats() NULL pointer in dm_requeue_original_request()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Bryn M. Reeves commit 98dbc9c6c61698792e3a66f32f3bf066201d42d7 upstream. An "old" (.request_fn) DM 'struct request' stores a pointer to the associated 'struct dm_rq_target_io' in rq->special.

[PATCH 4.5 044/238] scsi: storvsc: fix SRB_STATUS_ABORTED handling

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Kuznetsov commit ff06c5ffbcb4ffa542fb80c897be977956fafecc upstream. Commit 3209f9d780d1 ("scsi: storvsc: Fix a bug in the handling of SRB status flags") filtered

[PATCH 4.5 042/238] ncr5380: Fix NCR5380_select() EH checks and result handling

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit ccf6efd78317ef6265829c81a3e1a19f628b1a2d upstream. Add missing checks for EH abort during arbitration and selection. Rework the handling of

[PATCH 4.5 052/238] dm cache: make sure every metadata function checks fail_io

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Joe Thornber commit d14fcf3dd79c0b8a8d0ba469c44a6b04f3a1403b upstream. Otherwise operations may be attempted that will only ever go on to crash (since the metadata device is

[PATCH 4.5 040/238] ncr5380: Dont re-enter NCR5380_select()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit 71a00593ec0c2e2c1720e4041cf2926ff1d07826 upstream. Calling NCR5380_select() from the abort handler causes various problems. Firstly, it means

[PATCH 4.5 044/238] scsi: storvsc: fix SRB_STATUS_ABORTED handling

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Kuznetsov commit ff06c5ffbcb4ffa542fb80c897be977956fafecc upstream. Commit 3209f9d780d1 ("scsi: storvsc: Fix a bug in the handling of SRB status flags") filtered

[PATCH 4.5 042/238] ncr5380: Fix NCR5380_select() EH checks and result handling

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit ccf6efd78317ef6265829c81a3e1a19f628b1a2d upstream. Add missing checks for EH abort during arbitration and selection. Rework the handling of NCR5380_select() result to improve

[PATCH 4.5 052/238] dm cache: make sure every metadata function checks fail_io

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Joe Thornber commit d14fcf3dd79c0b8a8d0ba469c44a6b04f3a1403b upstream. Otherwise operations may be attempted that will only ever go on to crash (since the metadata device is either missing or

[PATCH 4.5 040/238] ncr5380: Dont re-enter NCR5380_select()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit 71a00593ec0c2e2c1720e4041cf2926ff1d07826 upstream. Calling NCR5380_select() from the abort handler causes various problems. Firstly, it means potentially re-entering

[PATCH 4.5 050/238] dm: fix excessive dm-mq context switching

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit 6acfe68bac7e6f16dc312157b1fa6e2368985013 upstream. Request-based DM's blk-mq support (dm-mq) was reported to be 50% slower than if an underlying

[PATCH 4.5 050/238] dm: fix excessive dm-mq context switching

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit 6acfe68bac7e6f16dc312157b1fa6e2368985013 upstream. Request-based DM's blk-mq support (dm-mq) was reported to be 50% slower than if an underlying null_blk device were used

[PATCH 4.5 016/238] Thermal: Ignore invalid trip points

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Zhang Rui commit 81ad4276b505e987dd8ebbdf63605f92cd172b52 upstream. In some cases, platform thermal driver may report invalid trip points, thermal core should not take any

[PATCH 4.5 046/238] aic7xxx: Fix queue depth handling

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Alan commit 5a51a7abca133860a6f4429655a9eda3c4afde32 upstream. We were setting the queue depth correctly, then setting it back to two. If you hit this as a

[PATCH 4.5 008/238] KVM: fix spin_lock_init order on x86

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit e9ad4ec8379ad1ba6f68b8ca1c26b50b5ae0a327 upstream. Moving the initialization earlier is needed in 4.6 because kvm_arch_init_vm is now using mmu_lock,

[PATCH 4.5 056/238] USB: uas: Reduce can_queue to MAX_CMNDS

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 55ff8cfbc4e12a7d2187df523938cc671fbebdd1 upstream. The uas driver can never queue more then MAX_CMNDS (- 1) tags and tags are shared between luns, so

[PATCH 4.5 014/238] perf tools: Fix checking asprintf return value

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Wang Nan commit 26dee028d365fbc0e3326606a8520260b4462381 upstream. According to man pages, asprintf returns -1 when failure. This patch fixes two incorrect return value

[PATCH 4.5 046/238] aic7xxx: Fix queue depth handling

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Alan commit 5a51a7abca133860a6f4429655a9eda3c4afde32 upstream. We were setting the queue depth correctly, then setting it back to two. If you hit this as a bisection point then please send me

[PATCH 4.5 008/238] KVM: fix spin_lock_init order on x86

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit e9ad4ec8379ad1ba6f68b8ca1c26b50b5ae0a327 upstream. Moving the initialization earlier is needed in 4.6 because kvm_arch_init_vm is now using mmu_lock, causing lockdep to

[PATCH 4.5 056/238] USB: uas: Reduce can_queue to MAX_CMNDS

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 55ff8cfbc4e12a7d2187df523938cc671fbebdd1 upstream. The uas driver can never queue more then MAX_CMNDS (- 1) tags and tags are shared between luns, so there is no need to

[PATCH 4.5 014/238] perf tools: Fix checking asprintf return value

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Wang Nan commit 26dee028d365fbc0e3326606a8520260b4462381 upstream. According to man pages, asprintf returns -1 when failure. This patch fixes two incorrect return value checker.

[PATCH 4.5 016/238] Thermal: Ignore invalid trip points

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Zhang Rui commit 81ad4276b505e987dd8ebbdf63605f92cd172b52 upstream. In some cases, platform thermal driver may report invalid trip points, thermal core should not take any action for these

[PATCH 4.5 067/238] [media] pwc: Add USB id for Philips Spc880nc webcam

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 7445e45d19a09e5269dc85f17f9635be29d2f76c upstream. SPC 880NC PC camera discussions:

[PATCH 4.5 012/238] perf/core: Fix perf_sched_count derailment

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit 927a5570855836e5d5859a80ce7e91e963545e8f upstream. The error path in perf_event_open() is such that asking for a sampling event on

[PATCH 4.5 013/238] perf tools: Dont stop PMU parsing on alias parse error

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Andi Kleen commit 940db6dcd3f4659303fdf6befe7416adc4d24118 upstream. When an error happens during alias parsing currently the complete parsing of all attributes of the

[PATCH 4.5 067/238] [media] pwc: Add USB id for Philips Spc880nc webcam

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 7445e45d19a09e5269dc85f17f9635be29d2f76c upstream. SPC 880NC PC camera discussions: http://www.pclinuxos.com/forum/index.php/topic,135688.0.html Reported-by:

[PATCH 4.5 012/238] perf/core: Fix perf_sched_count derailment

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit 927a5570855836e5d5859a80ce7e91e963545e8f upstream. The error path in perf_event_open() is such that asking for a sampling event on a PMU that doesn't generate

[PATCH 4.5 013/238] perf tools: Dont stop PMU parsing on alias parse error

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Andi Kleen commit 940db6dcd3f4659303fdf6befe7416adc4d24118 upstream. When an error happens during alias parsing currently the complete parsing of all attributes of the PMU is stopped. This is

[PATCH 4.5 051/238] dm thin metadata: dont issue prefetches if a transaction abort has failed

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Joe Thornber commit 2eae9e4489b4cf83213fa3bd508b5afca3f01780 upstream. If a transaction abort has failed then we can no longer use the metadata device. Typically this happens

[PATCH 4.5 015/238] perf tools: Fix python extension build

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Olsa commit 67d5268908283c187e0a460048a423256c2fb288 upstream. The util/python-ext-sources file contains source files required to build the python extension relative to

[PATCH 4.5 051/238] dm thin metadata: dont issue prefetches if a transaction abort has failed

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Joe Thornber commit 2eae9e4489b4cf83213fa3bd508b5afca3f01780 upstream. If a transaction abort has failed then we can no longer use the metadata device. Typically this happens if the

[PATCH 4.5 015/238] perf tools: Fix python extension build

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Olsa commit 67d5268908283c187e0a460048a423256c2fb288 upstream. The util/python-ext-sources file contains source files required to build the python extension relative to

[PATCH 4.5 072/238] ALSA: usb-audio: Minor code cleanup in create_fixed_stream_quirk()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 902eb7fd1e4af3ac69b9b30f8373f118c92b9729 upstream. Just a minor code cleanup: unify the error paths. Signed-off-by: Takashi Iwai

[PATCH 4.5 206/238] clk: rockchip: rk3368: fix parents of video encoder/decoder

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Stuebner commit 0f28d98463498c61c61a38aacbf9f69e92e85e9d upstream. The vdpu and vepu clocks can also be parented to the npll and current parent list also is wrong as it

[PATCH 4.5 072/238] ALSA: usb-audio: Minor code cleanup in create_fixed_stream_quirk()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 902eb7fd1e4af3ac69b9b30f8373f118c92b9729 upstream. Just a minor code cleanup: unify the error paths. Signed-off-by: Takashi Iwai Signed-off-by: Greg Kroah-Hartman ---

[PATCH 4.5 206/238] clk: rockchip: rk3368: fix parents of video encoder/decoder

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Stuebner commit 0f28d98463498c61c61a38aacbf9f69e92e85e9d upstream. The vdpu and vepu clocks can also be parented to the npll and current parent list also is wrong as it would use the

[PATCH 4.5 068/238] Input: powermate - fix oops with malicious USB descriptors

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Josh Boyer commit 9c6ba456711687b794dcf285856fc14e2c76074f upstream. The powermate driver expects at least one valid USB endpoint in its probe function. If given

[PATCH 4.5 073/238] ALSA: usb-audio: Fix double-free in error paths after snd_usb_add_audio_stream() call

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Vladis Dronov commit 836b34a935abc91e13e63053d0a83b24dfb5ea78 upstream. create_fixed_stream_quirk(), snd_usb_parse_audio_interface() and create_uaxx_quirk() functions

[PATCH 4.5 048/238] libnvdimm, pmem: fix kmap_atomic() leak in error path

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit b5ebc8ec693281c3c1efff7459a069cbd8b9a149 upstream. When we enounter a bad block we need to kunmap_atomic() before returning. Cc: Ross Zwisler

[PATCH 4.5 066/238] rt2x00: add new rt2800usb device Buffalo WLI-UC-G450

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Anthony Wong commit f36f299068794ffc5026f25b6a1b3ed615ea832d upstream. Add USB ID 0411:01fd for Buffalo WLI-UC-G450 wireless adapter, RT chipset 3593 Signed-off-by:

[PATCH 4.5 068/238] Input: powermate - fix oops with malicious USB descriptors

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Josh Boyer commit 9c6ba456711687b794dcf285856fc14e2c76074f upstream. The powermate driver expects at least one valid USB endpoint in its probe function. If given malicious descriptors that

[PATCH 4.5 073/238] ALSA: usb-audio: Fix double-free in error paths after snd_usb_add_audio_stream() call

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Vladis Dronov commit 836b34a935abc91e13e63053d0a83b24dfb5ea78 upstream. create_fixed_stream_quirk(), snd_usb_parse_audio_interface() and create_uaxx_quirk() functions allocate the audioformat

<    1   2   3   4   5   6   7   8   9   10   >