[PATCH 4.9 87/93] x86/tsc: Fix ART for TSC_KNOWN_FREQ

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 44fee88cea43d3c2cac962e0439cb10a3cabff6d upstream. Subhransu reported that convert_art_to_tsc() isn't working for him. The ART to TSC relation is only set up for systems

[PATCH 4.9 86/93] irqchip/gicv3-its: Add workaround for QDF2400 ITS erratum 0065

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shanker Donthineni commit 90922a2d03d84de36bf8a9979d62580102f31a92 upstream. On Qualcomm Datacenter Technologies QDF2400 SoCs, the ITS hardware implementation uses 16Bytes for Interrupt

[PATCH 4.9 61/93] ibmveth: calculate gso_segs for large packets

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Falcon [ Upstream commit 94acf164dc8f1184e8d0737be7125134c2701dbe ] Include calculations to compute the number of segments that comprise an aggregated large

[PATCH 4.9 84/93] drm/vc4: Fix ->clock_select setting for the VEC encoder

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit ab8df60e3a3b68420d0d4477c5f07c00fbfb078b upstream. PV_CONTROL_CLK_SELECT_VEC is actually 2 and not 0. Fix the definition and rework

[PATCH 4.9 61/93] ibmveth: calculate gso_segs for large packets

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Falcon [ Upstream commit 94acf164dc8f1184e8d0737be7125134c2701dbe ] Include calculations to compute the number of segments that comprise an aggregated large packet. Signed-off-by:

[PATCH 4.9 84/93] drm/vc4: Fix ->clock_select setting for the VEC encoder

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit ab8df60e3a3b68420d0d4477c5f07c00fbfb078b upstream. PV_CONTROL_CLK_SELECT_VEC is actually 2 and not 0. Fix the definition and rework the vc4_set_crtc_possible_masks() to

[PATCH 4.9 59/93] PCI: Ignore BAR updates on virtual functions

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas [ Upstream commit 63880b230a4af502c56dde3d4588634c70c66006 ] VF BARs are read-only zero, so updating VF BARs will not have any effect. See the SR-IOV spec

[PATCH 4.9 59/93] PCI: Ignore BAR updates on virtual functions

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas [ Upstream commit 63880b230a4af502c56dde3d4588634c70c66006 ] VF BARs are read-only zero, so updating VF BARs will not have any effect. See the SR-IOV spec r1.1, sec 3.4.1.11. We

[PATCH 4.9 60/93] PCI: Do any VF BAR updates before enabling the BARs

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Gavin Shan [ Upstream commit f40ec3c748c6912f6266c56a7f7992de61b255ed ] Previously we enabled VFs and enable their memory space before calling

[PATCH 4.9 60/93] PCI: Do any VF BAR updates before enabling the BARs

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Gavin Shan [ Upstream commit f40ec3c748c6912f6266c56a7f7992de61b255ed ] Previously we enabled VFs and enable their memory space before calling pcibios_sriov_enable(). But

[PATCH 4.9 62/93] Drivers: hv: ring_buffer: count on wrap around mappings in get_next_pkt_raw() (v2)

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Kuznetsov [ Upstream commit fa32ff6576623616c1751562edaed8c164ca5199 ] With wrap around mappings in place we can always provide drivers with direct links to packets

[PATCH 4.9 62/93] Drivers: hv: ring_buffer: count on wrap around mappings in get_next_pkt_raw() (v2)

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Kuznetsov [ Upstream commit fa32ff6576623616c1751562edaed8c164ca5199 ] With wrap around mappings in place we can always provide drivers with direct links to packets on the ring buffer,

[PATCH 4.9 78/93] ACPI / blacklist: Make Dell Latitude 3350 ethernet work

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Pobega [ Upstream commit 708f5dcc21ae9b35f395865fc154b0105baf4de4 ] The Dell Latitude 3350's ethernet card attempts to use a reserved IRQ (18), resulting in ACPI

[PATCH 4.9 78/93] ACPI / blacklist: Make Dell Latitude 3350 ethernet work

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Pobega [ Upstream commit 708f5dcc21ae9b35f395865fc154b0105baf4de4 ] The Dell Latitude 3350's ethernet card attempts to use a reserved IRQ (18), resulting in ACPI being unable to enable

[PATCH 4.9 65/93] powerpc/iommu: Stop using @current in mm_iommu_xxx

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kardashevskiy [ Upstream commit d7baee6901b34c4895eb78efdbf13a49079d7404 ] This changes mm_iommu_xxx helpers to take mm_struct as a parameter instead of getting it from

[PATCH 4.9 65/93] powerpc/iommu: Stop using @current in mm_iommu_xxx

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kardashevskiy [ Upstream commit d7baee6901b34c4895eb78efdbf13a49079d7404 ] This changes mm_iommu_xxx helpers to take mm_struct as a parameter instead of getting it from @current which

[PATCH 4.9 64/93] powerpc/iommu: Pass mm_struct to init/cleanup helpers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kardashevskiy [ Upstream commit 88f54a3581eb9deaa3bd1aade40aef266d782385 ] We are going to get rid of @current references in mmu_context_boos3s64.c and cache mm_struct

[PATCH 4.9 63/93] vfio/spapr: Postpone allocation of userspace version of TCE table

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kardashevskiy [ Upstream commit 39701e56f5f16ea0cf8fc9e8472e645f8de91d23 ] The iommu_table struct manages a hardware TCE table and a vmalloc'd table with corresponding

[PATCH v5 0/7] Xen transport for 9pfs frontend driver

Hi all, This patch series implements a new transport for 9pfs, aimed at Xen systems. The transport is based on a traditional Xen frontend and backend drivers pair. This patch series implements the frontend, which typically runs in a regular unprivileged guest. I also sent a series that

[PATCH 4.9 64/93] powerpc/iommu: Pass mm_struct to init/cleanup helpers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kardashevskiy [ Upstream commit 88f54a3581eb9deaa3bd1aade40aef266d782385 ] We are going to get rid of @current references in mmu_context_boos3s64.c and cache mm_struct in the VFIO

[PATCH 4.9 63/93] vfio/spapr: Postpone allocation of userspace version of TCE table

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kardashevskiy [ Upstream commit 39701e56f5f16ea0cf8fc9e8472e645f8de91d23 ] The iommu_table struct manages a hardware TCE table and a vmalloc'd table with corresponding userspace

[PATCH v5 0/7] Xen transport for 9pfs frontend driver

Hi all, This patch series implements a new transport for 9pfs, aimed at Xen systems. The transport is based on a traditional Xen frontend and backend drivers pair. This patch series implements the frontend, which typically runs in a regular unprivileged guest. I also sent a series that

[PATCH 4.9 56/93] PCI: Decouple IORESOURCE_ROM_ENABLE and PCI_ROM_ADDRESS_ENABLE

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas [ Upstream commit 7a6d312b50e63f598f5b5914c4fd21878ac2b595 ] Remove the assumption that IORESOURCE_ROM_ENABLE == PCI_ROM_ADDRESS_ENABLE.

[PATCH 4.9 56/93] PCI: Decouple IORESOURCE_ROM_ENABLE and PCI_ROM_ADDRESS_ENABLE

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas [ Upstream commit 7a6d312b50e63f598f5b5914c4fd21878ac2b595 ] Remove the assumption that IORESOURCE_ROM_ENABLE == PCI_ROM_ADDRESS_ENABLE. PCI_ROM_ADDRESS_ENABLE is the ROM enable

[PATCH 4.9 93/93] crypto: powerpc - Fix initialisation of crc32c context

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Axtens commit aa2be9b3d6d2d699e9ca7cbfc00867c80e5da213 upstream. Turning on crypto self-tests on a POWER8 shows: alg: hash: Test 1 failed for crc32c-vpmsum

[PATCH 4.9 93/93] crypto: powerpc - Fix initialisation of crc32c context

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Axtens commit aa2be9b3d6d2d699e9ca7cbfc00867c80e5da213 upstream. Turning on crypto self-tests on a POWER8 shows: alg: hash: Test 1 failed for crc32c-vpmsum : ff ff ff

[PATCH 4.9 88/93] x86/kasan: Fix boot with KASAN=y and PROFILE_ANNOTATED_BRANCHES=y

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit be3606ff739d1c1be36389f8737c577ad87e1f57 upstream. The kernel doesn't boot with both PROFILE_ANNOTATED_BRANCHES=y and KASAN=y options selected.

[PATCH 4.9 88/93] x86/kasan: Fix boot with KASAN=y and PROFILE_ANNOTATED_BRANCHES=y

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit be3606ff739d1c1be36389f8737c577ad87e1f57 upstream. The kernel doesn't boot with both PROFILE_ANNOTATED_BRANCHES=y and KASAN=y options selected. With branch profiling

[PATCH 4.10 03/63] net/mlx5e: Fix broken CQE compression initialization

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tariq Toukan [ Upstream commit b0d4660b4cc52e6477ca3a43435351d565dfcedc ] Some of RQ type parameters are derived from CQE compression state flag, CQE compression flag

[PATCH 4.10 03/63] net/mlx5e: Fix broken CQE compression initialization

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tariq Toukan [ Upstream commit b0d4660b4cc52e6477ca3a43435351d565dfcedc ] Some of RQ type parameters are derived from CQE compression state flag, CQE compression flag was initialized only

[PATCH 4.9 92/93] locking/rwsem: Fix down_write_killable() for CONFIG_RWSEM_GENERIC_SPINLOCK=y

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Niklas Cassel commit 17fcbd590d0c3e35bd9646e2215f86586378bc42 upstream. We hang if SIGKILL has been sent, but the task is stuck in down_read() (after do_exit()), even

[PATCH 4.9 92/93] locking/rwsem: Fix down_write_killable() for CONFIG_RWSEM_GENERIC_SPINLOCK=y

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Niklas Cassel commit 17fcbd590d0c3e35bd9646e2215f86586378bc42 upstream. We hang if SIGKILL has been sent, but the task is stuck in down_read() (after do_exit()), even though no task is doing

Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU controller

Hello, On Tue, Feb 28, 2017 at 02:38:38PM +, Patrick Bellasi wrote: > This patch extends the CPU controller by adding a couple of new > attributes, capacity_min and capacity_max, which can be used to enforce > bandwidth boosting and capping. More specifically: > > - capacity_min: defines the

Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU controller

Hello, On Tue, Feb 28, 2017 at 02:38:38PM +, Patrick Bellasi wrote: > This patch extends the CPU controller by adding a couple of new > attributes, capacity_min and capacity_max, which can be used to enforce > bandwidth boosting and capping. More specifically: > > - capacity_min: defines the

Re: [PATCH v1 0/3] ioremap() tidy-up

On Fri, Mar 17, 2017 at 11:00:03PM +0100, Arnd Bergmann wrote: > On Fri, Mar 17, 2017 at 6:46 PM, Bjorn Helgaas wrote: > > 1) Fix some comments that say "IOMMU" when they mean "MMU". > > > > 2) Remove the generic __ioremap() definition, which I think is unused and > >

[PATCH 4.10 02/63] net/mlx5e: Do not reduce LRO WQE size when not using build_skb

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tariq Toukan [ Upstream commit 4078e637c12f1e0a74293f1ec9563f42bff14a03 ] When rq_type is Striding RQ, no room of SKB_RESERVE is needed as SKB allocation is not done via

Re: [PATCH v1 0/3] ioremap() tidy-up

On Fri, Mar 17, 2017 at 11:00:03PM +0100, Arnd Bergmann wrote: > On Fri, Mar 17, 2017 at 6:46 PM, Bjorn Helgaas wrote: > > 1) Fix some comments that say "IOMMU" when they mean "MMU". > > > > 2) Remove the generic __ioremap() definition, which I think is unused and > > confusing. > > > > 3)

[PATCH 4.10 02/63] net/mlx5e: Do not reduce LRO WQE size when not using build_skb

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tariq Toukan [ Upstream commit 4078e637c12f1e0a74293f1ec9563f42bff14a03 ] When rq_type is Striding RQ, no room of SKB_RESERVE is needed as SKB allocation is not done via build_skb. Fixes:

[PATCH 4.10 15/63] vxlan: lock RCU on TX path

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Jakub Kicinski [ Upstream commit 56de859e9967c070464a9a9f4f18d73f9447298e ] There is no guarantees that callers of the TX path will hold the RCU lock. Grab it

[PATCH 4.10 17/63] mlxsw: spectrum_router: Avoid potential packets loss

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Ido Schimmel [ Upstream commit f7df4923fa986247e93ec2cdff5ca168fff14dcf ] When the structure of the LPM tree changes (f.e., due to the addition of a new prefix), we

[PATCH 4.10 15/63] vxlan: lock RCU on TX path

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Jakub Kicinski [ Upstream commit 56de859e9967c070464a9a9f4f18d73f9447298e ] There is no guarantees that callers of the TX path will hold the RCU lock. Grab it explicitly. Fixes:

[PATCH 4.10 17/63] mlxsw: spectrum_router: Avoid potential packets loss

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Ido Schimmel [ Upstream commit f7df4923fa986247e93ec2cdff5ca168fff14dcf ] When the structure of the LPM tree changes (f.e., due to the addition of a new prefix), we unbind the old tree and

[PATCH 4.10 05/63] net/mlx5e: Fix wrong CQE decompression

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tariq Toukan [ Upstream commit 36154be40a28e4afaa0416da2681d80b7e2ca319 ] In cqe compression with striding RQ, the decompression of the CQE field wqe_counter was done

[PATCH 4.10 05/63] net/mlx5e: Fix wrong CQE decompression

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tariq Toukan [ Upstream commit 36154be40a28e4afaa0416da2681d80b7e2ca319 ] In cqe compression with striding RQ, the decompression of the CQE field wqe_counter was done with a wrong wraparound

[PATCH 4.10 16/63] geneve: lock RCU on TX path

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Jakub Kicinski [ Upstream commit a717e3f740803cc88bd5c9a70c93504f6a368663 ] There is no guarantees that callers of the TX path will hold the RCU lock. Grab it

[PATCH 4.10 16/63] geneve: lock RCU on TX path

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Jakub Kicinski [ Upstream commit a717e3f740803cc88bd5c9a70c93504f6a368663 ] There is no guarantees that callers of the TX path will hold the RCU lock. Grab it explicitly. Fixes:

[PATCH 4.10 20/63] net: dont call strlen() on the user buffer in packet_bind_spkt()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Potapenko [ Upstream commit 540e2894f7905538740aaf122bd8e0548e1c34a4 ] KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of uninitialized

[PATCH 4.10 20/63] net: dont call strlen() on the user buffer in packet_bind_spkt()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Potapenko [ Upstream commit 540e2894f7905538740aaf122bd8e0548e1c34a4 ] KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of uninitialized memory in

[PATCH 4.10 22/63] ipv6: orphan skbs in reassembly unit

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 48cac18ecf1de82f76259a54402c3adb7839ad01 ] Andrey reported a use-after-free in IPv6 stack. Issue here is that we free the socket while it

[PATCH 4.10 22/63] ipv6: orphan skbs in reassembly unit

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 48cac18ecf1de82f76259a54402c3adb7839ad01 ] Andrey reported a use-after-free in IPv6 stack. Issue here is that we free the socket while it still has skb in TX

[PATCH 4.10 23/63] dccp: Unlock sock before calling sk_free()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnaldo Carvalho de Melo [ Upstream commit d5afb6f9b6bb2c57bd0c05e76e12489dc0d037d9 ] The code where sk_clone() came from created a new socket and locked it, but then, on

[PATCH 4.10 19/63] net: bridge: allow IPv6 when multicast flood is disabled

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Mike Manning [ Upstream commit 8953de2f02ad7b15e4964c82f9afd60f128e4e98 ] Even with multicast flooding turned off, IPv6 ND should still work so that IPv6 connectivity

[PATCH 4.10 23/63] dccp: Unlock sock before calling sk_free()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnaldo Carvalho de Melo [ Upstream commit d5afb6f9b6bb2c57bd0c05e76e12489dc0d037d9 ] The code where sk_clone() came from created a new socket and locked it, but then, on the error path

[PATCH 4.10 19/63] net: bridge: allow IPv6 when multicast flood is disabled

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Mike Manning [ Upstream commit 8953de2f02ad7b15e4964c82f9afd60f128e4e98 ] Even with multicast flooding turned off, IPv6 ND should still work so that IPv6 connectivity is provided. Allow this

Re: [PATCH 2/4] perf annotate: Avoid division by zero when calculating percent

Em Mon, Mar 20, 2017 at 11:56:55AM +0900, Taeung Song escreveu: > Currently perf-annotate with --print-line can print > -nan(0x8) because of division by zero > when calculating percent. > > So if a sum of samples is zero, skip calculating percent. Tried to reproduce it here,

[PATCH v4] usb: hub: Fix error loop seen after hub communication errors

While stress testing a usb controller using a bind/unbind looop, the following error loop was observed. usb 7-1.2: new low-speed USB device number 3 using xhci-hcd usb 7-1.2: hub failed to enable device, error -108 usb 7-1-port2: cannot disable (err = -22) usb 7-1-port2: couldn't allocate

[PATCH v4] usb: hub: Fix error loop seen after hub communication errors

While stress testing a usb controller using a bind/unbind looop, the following error loop was observed. usb 7-1.2: new low-speed USB device number 3 using xhci-hcd usb 7-1.2: hub failed to enable device, error -108 usb 7-1-port2: cannot disable (err = -22) usb 7-1-port2: couldn't allocate

Re: [PATCH 2/4] perf annotate: Avoid division by zero when calculating percent

Em Mon, Mar 20, 2017 at 11:56:55AM +0900, Taeung Song escreveu: > Currently perf-annotate with --print-line can print > -nan(0x8) because of division by zero > when calculating percent. > > So if a sum of samples is zero, skip calculating percent. Tried to reproduce it here,

[PATCH 4.10 26/63] amd-xgbe: Dont overwrite SFP PHY mod_absent settings

4.10-stable review patch. If anyone has any objections, please let me know. -- From: "Lendacky, Thomas" [ Upstream commit 2697ea5a859b83ca49511dcfd98daf42584eb3cf ] If an SFP module is not present, xgbe_phy_sfp_phy_settings() should return after

[PATCH 4.10 26/63] amd-xgbe: Dont overwrite SFP PHY mod_absent settings

4.10-stable review patch. If anyone has any objections, please let me know. -- From: "Lendacky, Thomas" [ Upstream commit 2697ea5a859b83ca49511dcfd98daf42584eb3cf ] If an SFP module is not present, xgbe_phy_sfp_phy_settings() should return after applying the default

[PATCH 4.10 10/63] ipv4: add missing initialization for flowi4_uid

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Julian Anastasov [ Upstream commit 8bcfd0925ef15f072ba1e7bee2c25e9e1b5fd6ca ] Avoid matching of random stack value for uid when rules are looked up on input route or when RP

[PATCH 4.10 10/63] ipv4: add missing initialization for flowi4_uid

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Julian Anastasov [ Upstream commit 8bcfd0925ef15f072ba1e7bee2c25e9e1b5fd6ca ] Avoid matching of random stack value for uid when rules are looked up on input route or when RP filter is used.

[PATCH 4.10 12/63] sctp: set sin_port for addr param when checking duplicate address

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit 2e3ce5bc2aa938653c3866aa7f4901a1f199b1c8 ] Commit b8607805dd15 ("sctp: not copying duplicate addrs to the assoc's bind address list") tried

[PATCH 4.10 12/63] sctp: set sin_port for addr param when checking duplicate address

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit 2e3ce5bc2aa938653c3866aa7f4901a1f199b1c8 ] Commit b8607805dd15 ("sctp: not copying duplicate addrs to the assoc's bind address list") tried to check for duplicate

[PATCH 4.10 41/63] mpls: Do not decrement alive counter for unregister events

4.10-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit 79099aab38c8f5c746748b066ae74ba984fe2cc8 ] Multipath routes can be rendered usesless when a device in one of the paths is deleted. For

[PATCH 4.10 41/63] mpls: Do not decrement alive counter for unregister events

4.10-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit 79099aab38c8f5c746748b066ae74ba984fe2cc8 ] Multipath routes can be rendered usesless when a device in one of the paths is deleted. For example: $ ip -f mpls ro

[PATCH 4.10 09/63] vxlan: dont allow overwrite of config src addr

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Brian Russell [ Upstream commit 1158632b5a2dcce0786c1b1b99654e81cc867981 ] When using IPv6 transport and a default dst, a pointer to the configured source address is

[PATCH 4.10 25/63] amd-xgbe: Be sure to set MDIO modes on device (re)start

4.10-stable review patch. If anyone has any objections, please let me know. -- From: "Lendacky, Thomas" [ Upstream commit b42c6761fd1651f564491b53016046c9ebf0b2a9 ] The MDIO register mode is set when the device is probed. But when the device is

[PATCH 4.10 56/63] x86/kasan: Fix boot with KASAN=y and PROFILE_ANNOTATED_BRANCHES=y

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit be3606ff739d1c1be36389f8737c577ad87e1f57 upstream. The kernel doesn't boot with both PROFILE_ANNOTATED_BRANCHES=y and KASAN=y options selected.

[PATCH 4.10 09/63] vxlan: dont allow overwrite of config src addr

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Brian Russell [ Upstream commit 1158632b5a2dcce0786c1b1b99654e81cc867981 ] When using IPv6 transport and a default dst, a pointer to the configured source address is passed into the route

[PATCH 4.10 25/63] amd-xgbe: Be sure to set MDIO modes on device (re)start

4.10-stable review patch. If anyone has any objections, please let me know. -- From: "Lendacky, Thomas" [ Upstream commit b42c6761fd1651f564491b53016046c9ebf0b2a9 ] The MDIO register mode is set when the device is probed. But when the device is brought down and then back up,

[PATCH 4.10 56/63] x86/kasan: Fix boot with KASAN=y and PROFILE_ANNOTATED_BRANCHES=y

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit be3606ff739d1c1be36389f8737c577ad87e1f57 upstream. The kernel doesn't boot with both PROFILE_ANNOTATED_BRANCHES=y and KASAN=y options selected. With branch profiling

[PATCH] drm/gma500: fix memory leak on edid

From: Colin Ian King edid is allocated on the call to psb_intel_sdvo_get_edid but not kfree'd at all, causing a memory leak. Fix this by kfree'ing the edid. (This may be null, but kfree can handle null frees). Detected by CoverityScan, CID#1090730 ("Resource Leak")

Re: [PATCH] fs/pstore: Perform erase from a worker

On Fri, Mar 17, 2017 at 2:52 AM, Chris Wilson wrote: > In order to prevent a cyclic recursion between psi->read_mutex and the > inode_lock, we need to move the pse->erase to a worker. > > [ 605.374955] == > [

[PATCH] drm/gma500: fix memory leak on edid

From: Colin Ian King edid is allocated on the call to psb_intel_sdvo_get_edid but not kfree'd at all, causing a memory leak. Fix this by kfree'ing the edid. (This may be null, but kfree can handle null frees). Detected by CoverityScan, CID#1090730 ("Resource Leak") Fixes: 5736995b473b

Re: [PATCH] fs/pstore: Perform erase from a worker

On Fri, Mar 17, 2017 at 2:52 AM, Chris Wilson wrote: > In order to prevent a cyclic recursion between psi->read_mutex and the > inode_lock, we need to move the pse->erase to a worker. > > [ 605.374955] == > [ 605.381281] [ INFO: possible

[PATCH 4.10 61/63] locking/rwsem: Fix down_write_killable() for CONFIG_RWSEM_GENERIC_SPINLOCK=y

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Niklas Cassel commit 17fcbd590d0c3e35bd9646e2215f86586378bc42 upstream. We hang if SIGKILL has been sent, but the task is stuck in down_read() (after do_exit()), even

[PATCH 4.10 61/63] locking/rwsem: Fix down_write_killable() for CONFIG_RWSEM_GENERIC_SPINLOCK=y

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Niklas Cassel commit 17fcbd590d0c3e35bd9646e2215f86586378bc42 upstream. We hang if SIGKILL has been sent, but the task is stuck in down_read() (after do_exit()), even though no task is doing

[PATCH 4.10 60/63] futex: Add missing error handling to FUTEX_REQUEUE_PI

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 9bbb25afeb182502ca4f2c4f3f88af0681b34cae upstream. Thomas spotted that fixup_pi_state_owner() can return errors and we fail to unlock the rt_mutex

[PATCH 4.10 59/63] futex: Fix potential use-after-free in FUTEX_REQUEUE_PI

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit c236c8e95a3d395b0494e7108f0d41cf36ec107c upstream. While working on the futex code, I stumbled over this potential use-after-free scenario. Dmitry

[PATCH 4.10 60/63] futex: Add missing error handling to FUTEX_REQUEUE_PI

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 9bbb25afeb182502ca4f2c4f3f88af0681b34cae upstream. Thomas spotted that fixup_pi_state_owner() can return errors and we fail to unlock the rt_mutex in that case.

[PATCH 4.10 59/63] futex: Fix potential use-after-free in FUTEX_REQUEUE_PI

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit c236c8e95a3d395b0494e7108f0d41cf36ec107c upstream. While working on the futex code, I stumbled over this potential use-after-free scenario. Dmitry triggered it later

[PATCH 4.10 49/63] arm64: KVM: VHE: Clear HCR_TGE when invalidating guest TLBs

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 68925176296a8b995e503349200e256674bfe5ac upstream. When invalidating guest TLBs, special care must be taken to actually shoot the guest TLBs and not

[PATCH 4.10 49/63] arm64: KVM: VHE: Clear HCR_TGE when invalidating guest TLBs

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 68925176296a8b995e503349200e256674bfe5ac upstream. When invalidating guest TLBs, special care must be taken to actually shoot the guest TLBs and not the host ones if we're

[PATCH 4.10 50/63] irqchip/gicv3-its: Add workaround for QDF2400 ITS erratum 0065

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Shanker Donthineni commit 90922a2d03d84de36bf8a9979d62580102f31a92 upstream. On Qualcomm Datacenter Technologies QDF2400 SoCs, the ITS hardware implementation uses

[PATCH 4.10 62/63] crypto: powerpc - Fix initialisation of crc32c context

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Axtens commit aa2be9b3d6d2d699e9ca7cbfc00867c80e5da213 upstream. Turning on crypto self-tests on a POWER8 shows: alg: hash: Test 1 failed for crc32c-vpmsum

[PATCH 4.10 04/63] net/mlx5e: Update MPWQE stride size when modifying CQE compress state

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Saeed Mahameed [ Upstream commit 6dc4b54e77282caf17f0ff72aa32dd296037fbc0 ] When the admin enables/disables cqe compression, updating mpwqe stride size is required:

[PATCH 4.10 50/63] irqchip/gicv3-its: Add workaround for QDF2400 ITS erratum 0065

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Shanker Donthineni commit 90922a2d03d84de36bf8a9979d62580102f31a92 upstream. On Qualcomm Datacenter Technologies QDF2400 SoCs, the ITS hardware implementation uses 16Bytes for Interrupt

[PATCH 4.10 62/63] crypto: powerpc - Fix initialisation of crc32c context

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Axtens commit aa2be9b3d6d2d699e9ca7cbfc00867c80e5da213 upstream. Turning on crypto self-tests on a POWER8 shows: alg: hash: Test 1 failed for crc32c-vpmsum : ff ff ff

[PATCH 4.10 04/63] net/mlx5e: Update MPWQE stride size when modifying CQE compress state

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Saeed Mahameed [ Upstream commit 6dc4b54e77282caf17f0ff72aa32dd296037fbc0 ] When the admin enables/disables cqe compression, updating mpwqe stride size is required: CQE compress ON ==>

[PATCH 4.9 18/93] ipv6: orphan skbs in reassembly unit

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 48cac18ecf1de82f76259a54402c3adb7839ad01 ] Andrey reported a use-after-free in IPv6 stack. Issue here is that we free the socket while it

[PATCH 4.9 18/93] ipv6: orphan skbs in reassembly unit

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 48cac18ecf1de82f76259a54402c3adb7839ad01 ] Andrey reported a use-after-free in IPv6 stack. Issue here is that we free the socket while it still has skb in TX

Re: [PATCH v3] usb: hub: Fix error loop seen after hub communication errors

Hi, On Thu, Mar 16, 2017 at 12:24 PM, Guenter Roeck wrote: > @@ -1198,7 +1201,7 @@ static void hub_activate(struct usb_hub *hub, enum > hub_activation_type type) > > /* Scan all ports that need attention */ > kick_hub_wq(hub); > - > +abort: One tiny nit that

[PATCH 4.10 37/63] uapi: fix linux/packet_diag.h userspace compilation error

4.10-stable review patch. If anyone has any objections, please let me know. -- From: "Dmitry V. Levin" [ Upstream commit 745cb7f8a5de0805cade3de3991b7a95317c7c73 ] Replace MAX_ADDR_LEN with its numeric value to fix the following linux/packet_diag.h

Re: [PATCH v3] usb: hub: Fix error loop seen after hub communication errors

Hi, On Thu, Mar 16, 2017 at 12:24 PM, Guenter Roeck wrote: > @@ -1198,7 +1201,7 @@ static void hub_activate(struct usb_hub *hub, enum > hub_activation_type type) > > /* Scan all ports that need attention */ > kick_hub_wq(hub); > - > +abort: One tiny nit that could be done when

[PATCH 4.10 37/63] uapi: fix linux/packet_diag.h userspace compilation error

4.10-stable review patch. If anyone has any objections, please let me know. -- From: "Dmitry V. Levin" [ Upstream commit 745cb7f8a5de0805cade3de3991b7a95317c7c73 ] Replace MAX_ADDR_LEN with its numeric value to fix the following linux/packet_diag.h userspace compilation

Re: [PATCH v2 06/14] mmc: dw_mmc: simplify optional reset handling

On 20 March 2017 at 12:00, Philipp Zabel wrote: > On Mon, 2017-03-20 at 11:49 +0100, Andrzej Hajda wrote: >> On 20.03.2017 11:27, Philipp Zabel wrote: > [...] >> > diff --git a/include/linux/reset.h b/include/linux/reset.h >> > index 86b4ed75359e8..c905ff1c21ec6 100644 >>

Re: [PATCH v2 06/14] mmc: dw_mmc: simplify optional reset handling

On 20 March 2017 at 12:00, Philipp Zabel wrote: > On Mon, 2017-03-20 at 11:49 +0100, Andrzej Hajda wrote: >> On 20.03.2017 11:27, Philipp Zabel wrote: > [...] >> > diff --git a/include/linux/reset.h b/include/linux/reset.h >> > index 86b4ed75359e8..c905ff1c21ec6 100644 >> > ---

Re: [PATCH v5 38/39] media: imx: csi: fix crop rectangle reset in sink set_fmt

On Mon, Mar 20, 2017 at 06:40:21PM +0100, Philipp Zabel wrote: > On Mon, 2017-03-20 at 14:17 +, Russell King - ARM Linux wrote: > > I have tripped over a bug in media-ctl when specifying both a crop and > > compose rectangle - the --help output suggests that "," should be used > > to separate

Re: [PATCH v21 13/13] acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver

On Tue, Mar 21, 2017 at 01:57:58AM +0800, Fu Wei wrote: > On 18 March 2017 at 04:01, Mark Rutland wrote: > > On Tue, Feb 07, 2017 at 02:50:15AM +0800, fu@linaro.org wrote: > > I've not been able to find where the ACPI spec says that zero is not a > > valid GSIV. This

<    3   4   5   6   7   8   9   10   11   12   >