[PATCH 4.9 115/116] drm/i915: skip the first 4k of stolen memory on everything >= gen8

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paulo Zanoni commit 6ba0566cf2afcdb17bff882e3a95cbbcb22c4a83 upstream. BSpec got updated and this workaround is now listed as standard required programming for all subsequent projects. This is

[PATCH 07/12] x86/rdt,cqm: Scheduling support update

Introduce a scheduling hook finish_arch_pre_lock_switch which is called just after the perf sched_in during context switch. This method handles both cat and cqm sched in scenarios. The IA32_PQR_ASSOC MSR is used by cat(cache allocation) and cqm and this patch integrates the two msr writes to one.

[PATCH 4.9 071/116] scsi: aacraid: remove wildcard for series 9 controllers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kevin Barnett commit ae2aae2421983f6f68eb7c4692624bc43ea50712 upstream. Controllers with this PCI ID never shipped outside of PMCS/Microsemi. Remove the ID from the aacraid driver. smartpqi is

[PATCH 12/12] perf/stat: revamp read error handling, snapshot and per_pkg events

From: David Carrillo-Cisneros A package wide event can return a valid read even if it has not run in a specific cpu, this does not fit well with the assumption that run == 0 is equivalent to a . To fix the problem, this patch defines special error values for val, run and ena (~0ULL), and use

[PATCH 10/12] perf/core,x86/cqm: Add read for Cgroup events,per pkg reads.

For cqm cgroup events, the events can be read even if the event was not active on the cpu on which the event is being read. This is because the RMIDs are per package and hence if we read the llc_occupancy value on a cpu x, we are really reading the occupancy for the package where cpu x belongs.

[PATCH 4.9 069/116] sc16is7xx: Drop bogus use of IRQF_ONESHOT

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Josh Cartwright commit 04da73803c05dc1150ccc31cbf93e8cd56679c09 upstream. The use of IRQF_ONESHOT when registering an interrupt handler with request_irq() is non-sensical. Not only that, it

Re: [RFC] x86/mm/KASLR: Remap GDTs at fixed location

On Fri, Jan 6, 2017 at 10:03 AM, Thomas Garnier wrote: > On Thu, Jan 5, 2017 at 10:49 PM, Ingo Molnar wrote: >> >> * Thomas Garnier wrote: >> >>> >> Not sure I fully understood and I don't want to miss an important point. >>> >> Do >>> >> you mean making GDT (remapping and per-cpu) read-only

Re: [PATCH net-next] net: dsa: move HWMON support to its own file

On 01/06/2017 01:42 PM, Vivien Didelot wrote: > Isolate the HWMON support in DSA in its own file. Currently only the > legacy DSA code is concerned. > > Signed-off-by: Vivien Didelot Reviewed-by: Florian Fainelli -- Florian

[PATCH 4.4 01/58] ssb: Fix error routine when fallback SPROM fails

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Larry Finger commit 8052d7245b6089992343c80b38b14dbbd8354651 upstream. When there is a CRC error in the SPROM read from the device, the code attempts to handle a

[PATCH 4.9 079/116] x86/smpboot: Make logical package management more robust

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 9d85eb9119f4eeeb48e87adfcd71f752655700e9 upstream. The logical package management has several issues: - The APIC ids provided by ACPI are not

[PATCH 11/12] perf/stat: fix bug in handling events in error state

From: Stephane Eranian When an event is in error state, read() returns 0 instead of sizeof() buffer. In certain modes, such as interval printing, ignoring the 0 return value may cause bogus count deltas to be computed and thus invalid results printed. this patch fixes this

[PATCH 4.4 01/58] ssb: Fix error routine when fallback SPROM fails

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Larry Finger commit 8052d7245b6089992343c80b38b14dbbd8354651 upstream. When there is a CRC error in the SPROM read from the device, the code attempts to handle a fallback SPROM. When this also

[PATCH 4.9 079/116] x86/smpboot: Make logical package management more robust

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 9d85eb9119f4eeeb48e87adfcd71f752655700e9 upstream. The logical package management has several issues: - The APIC ids provided by ACPI are not required to be the same

[PATCH 11/12] perf/stat: fix bug in handling events in error state

From: Stephane Eranian When an event is in error state, read() returns 0 instead of sizeof() buffer. In certain modes, such as interval printing, ignoring the 0 return value may cause bogus count deltas to be computed and thus invalid results printed. this patch fixes this problem by modifying

[PATCH net-next 2/2] arm: dts: vf610-zii-dev-rev-b: remove ports label

Now that the "label" property is optional for Ethernet switch ports, remove them in the ZII Dev Rev B board DTS. On a Rev B board, once eth1 is up, this DTS now exposes to userspace: # ip link | grep ': ' | cut -d: -f2 lo eth0 eth1 eth2@eth1 eth3@eth1 eth4@eth1

[PATCH net-next 2/2] arm: dts: vf610-zii-dev-rev-b: remove ports label

Now that the "label" property is optional for Ethernet switch ports, remove them in the ZII Dev Rev B board DTS. On a Rev B board, once eth1 is up, this DTS now exposes to userspace: # ip link | grep ': ' | cut -d: -f2 lo eth0 eth1 eth2@eth1 eth3@eth1 eth4@eth1

[PATCH net-next 0/2] net: dsa: make "label" property optional

Patch 1/2 makes the "label" property in new DSA bindings optional. This doesn't change the current behavior with existing DTS files. As Linux considers the Ethernet switch ports as normal NICs by default, not providing a "label" property for user ports results in using the standard "ethX" network

[PATCH 4.4 18/58] drm/nouveau/i2c/gk110b,gm10x: use the correct implementation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 5b3800a6b763874e4a23702fb9628d3bd3315ce9 upstream. DPAUX registers moved on Kepler, these chipsets were still using the Fermi implementation for some

[PATCH 4.4 27/58] scsi: megaraid_sas: For SRIOV enabled firmware, ensure VF driver waits for 30secs before reset

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kashyap Desai commit 18e1c7f68a5814442abad849abe6eacbf02ffd7c upstream. For SRIOV enabled firmware, if there is a OCR(online controller reset) possibility driver

[PATCH net-next 1/2] net: dsa: make "label" property optional for dsa2

In the new DTS bindings for DSA (dsa2), the "ethernet" and "link" phandles are respectively mandatory and exclusive to CPU port and DSA link device tree nodes. Simplify dsa2.c a bit by checking the presence of such phandle instead of checking the redundant "label" property. Then the Linux

[PATCH 4.4 27/58] scsi: megaraid_sas: For SRIOV enabled firmware, ensure VF driver waits for 30secs before reset

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kashyap Desai commit 18e1c7f68a5814442abad849abe6eacbf02ffd7c upstream. For SRIOV enabled firmware, if there is a OCR(online controller reset) possibility driver set the convert flag to 1,

[PATCH net-next 1/2] net: dsa: make "label" property optional for dsa2

In the new DTS bindings for DSA (dsa2), the "ethernet" and "link" phandles are respectively mandatory and exclusive to CPU port and DSA link device tree nodes. Simplify dsa2.c a bit by checking the presence of such phandle instead of checking the redundant "label" property. Then the Linux

[PATCH net-next 0/2] net: dsa: make "label" property optional

Patch 1/2 makes the "label" property in new DSA bindings optional. This doesn't change the current behavior with existing DTS files. As Linux considers the Ethernet switch ports as normal NICs by default, not providing a "label" property for user ports results in using the standard "ethX" network

[PATCH 4.4 18/58] drm/nouveau/i2c/gk110b,gm10x: use the correct implementation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 5b3800a6b763874e4a23702fb9628d3bd3315ce9 upstream. DPAUX registers moved on Kepler, these chipsets were still using the Fermi implementation for some reason. This fixes

[PATCH 4.9 081/116] IB/mad: Fix an array index check

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 2fe2f378dd45847d2643638c07a7658822087836 upstream. The array ib_mad_mgmt_class_table.method_table has MAX_MGMT_CLASS (80) elements. Hence

[PATCH 4.4 21/58] drm/radeon: add additional pci revision to dpm workaround

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 8729675c00a8d13cb2094d617d70a4a4da7d83c5 upstream. New variant. Signed-off-by: Alex Deucher Signed-off-by: Greg

[PATCH 4.9 081/116] IB/mad: Fix an array index check

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 2fe2f378dd45847d2643638c07a7658822087836 upstream. The array ib_mad_mgmt_class_table.method_table has MAX_MGMT_CLASS (80) elements. Hence compare the array index with

[PATCH 4.4 21/58] drm/radeon: add additional pci revision to dpm workaround

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 8729675c00a8d13cb2094d617d70a4a4da7d83c5 upstream. New variant. Signed-off-by: Alex Deucher Signed-off-by: Greg Kroah-Hartman --- drivers/gpu/drm/radeon/si_dpm.c |

[PATCH 4.4 32/58] scsi: avoid a permanent stop of the scsi devices request queue

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wei Fang commit d2a145252c52792bc59e4767b486b26c430af4bb upstream. A race between scanning and fc_remote_port_delete() may result in a permanent stop if the device gets

Re: [patch] mm, thp: add new background defrag option

On Fri, 6 Jan 2017, Vlastimil Babka wrote: > Deciding between "defer" and "background" is however confusing, and also > doesn't indicate that the difference is related to madvise. > Any suggestions for a better name for "background" are more than welcome. > > The kernel implementation takes

[PATCH 4.4 31/58] scsi: zfcp: fix rport unblock race with LUN recovery

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 6f2ce1c6af37191640ee3ff6e8fc39ea10352f4c upstream. It is unavoidable that zfcp_scsi_queuecommand() has to finish requests with DID_IMM_RETRY

Re: [PATCH net-next 1/2] net: dsa: make "label" property optional for dsa2

> If one wants to rename an interface, udev rules can be used as usual. Hi Vivien Do you have some examples? A quick look at udevadm info suggests we can use ATTR{phys_port_id} and ATTR{phys_switch_id} Humm, it would be nice to know why the second switch has a phys_switch_id of 0100. How

[PATCH 4.4 32/58] scsi: avoid a permanent stop of the scsi devices request queue

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wei Fang commit d2a145252c52792bc59e4767b486b26c430af4bb upstream. A race between scanning and fc_remote_port_delete() may result in a permanent stop if the device gets blocked before

Re: [patch] mm, thp: add new background defrag option

On Fri, 6 Jan 2017, Vlastimil Babka wrote: > Deciding between "defer" and "background" is however confusing, and also > doesn't indicate that the difference is related to madvise. > Any suggestions for a better name for "background" are more than welcome. > > The kernel implementation takes

[PATCH 4.4 31/58] scsi: zfcp: fix rport unblock race with LUN recovery

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 6f2ce1c6af37191640ee3ff6e8fc39ea10352f4c upstream. It is unavoidable that zfcp_scsi_queuecommand() has to finish requests with DID_IMM_RETRY (like

Re: [PATCH net-next 1/2] net: dsa: make "label" property optional for dsa2

> If one wants to rename an interface, udev rules can be used as usual. Hi Vivien Do you have some examples? A quick look at udevadm info suggests we can use ATTR{phys_port_id} and ATTR{phys_switch_id} Humm, it would be nice to know why the second switch has a phys_switch_id of 0100. How

[PATCH 4.4 33/58] ARC: mm: arc700: Dont assume 2 colours for aliasing VIPT dcache

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vineet Gupta commit 08fe007968b2b45e831daf74899f79a54d73f773 upstream. An ARC700 customer reported linux boot crashes when upgrading to bigger L1 dcache (64K from 32K).

[PATCH 4.4 33/58] ARC: mm: arc700: Dont assume 2 colours for aliasing VIPT dcache

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vineet Gupta commit 08fe007968b2b45e831daf74899f79a54d73f773 upstream. An ARC700 customer reported linux boot crashes when upgrading to bigger L1 dcache (64K from 32K). Turns out they had an

[PATCH 4.4 34/58] firmware: fix usermode helper fallback loading

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yves-Alexis Perez commit 2e700f8d85975f516ccaad821278c1fe66b2cc98 upstream. When you use the firmware usermode helper fallback with a timeout value set to a value greater

[PATCH 4.4 34/58] firmware: fix usermode helper fallback loading

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yves-Alexis Perez commit 2e700f8d85975f516ccaad821278c1fe66b2cc98 upstream. When you use the firmware usermode helper fallback with a timeout value set to a value greater than INT_MAX

[PATCH 4.4 07/58] timekeeping_Force_unsigned_clocksource_to_nanoseconds_conversion

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 9c1645727b8fa90d07256fdfcc45bf831242a3ab upstream. The clocksource delta to nanoseconds conversion is using signed math, but the delta is unsigned.

[PATCH 4.4 04/58] ath9k: Really fix LED polarity for some Mini PCI AR9220 MB92 cards.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vittorio Gambaletta (VittGam) commit 79e57dd113d307a6c74773b8aaecf5442068988a upstream. The active_high LED of my Wistron DNMA-92 is still being recognized as

Re: [PATCHv3] HID: i2c-hid: Add sleep between POWER ON and RESET

On Jan 07 2017 or thereabouts, Brendan McGrath wrote: > Support for the Asus Touchpad was recently added. It turns out this > device can fail initialisation (and become unusable) when the RESET > command is sent too soon after the POWER ON command. > > Unfortunately the i2c-hid specification does

[PATCH 4.4 06/58] regulator: stw481x-vmmc: fix ages old enable error

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 295070e9aa015abb9b92cccfbb1e43954e938133 upstream. The regulator has never been properly enabled, it has been dormant all the time. It's strange

[PATCH 4.4 08/58] clk: bcm2835: Avoid overwriting the div info when disabling a pll_div clk

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit 68af4fa8f39b542a6cde7ac19518d88e9b3099dc upstream. bcm2835_pll_divider_off() is resetting the divider field in the A2W reg to zero

[PATCH 4.4 07/58] timekeeping_Force_unsigned_clocksource_to_nanoseconds_conversion

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 9c1645727b8fa90d07256fdfcc45bf831242a3ab upstream. The clocksource delta to nanoseconds conversion is using signed math, but the delta is unsigned. This makes the

[PATCH 4.4 04/58] ath9k: Really fix LED polarity for some Mini PCI AR9220 MB92 cards.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vittorio Gambaletta (VittGam) commit 79e57dd113d307a6c74773b8aaecf5442068988a upstream. The active_high LED of my Wistron DNMA-92 is still being recognized as active_low on 4.7.6 mainline.

Re: [PATCHv3] HID: i2c-hid: Add sleep between POWER ON and RESET

On Jan 07 2017 or thereabouts, Brendan McGrath wrote: > Support for the Asus Touchpad was recently added. It turns out this > device can fail initialisation (and become unusable) when the RESET > command is sent too soon after the POWER ON command. > > Unfortunately the i2c-hid specification does

[PATCH 4.4 06/58] regulator: stw481x-vmmc: fix ages old enable error

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 295070e9aa015abb9b92cccfbb1e43954e938133 upstream. The regulator has never been properly enabled, it has been dormant all the time. It's strange that MMC was working at

[PATCH 4.4 08/58] clk: bcm2835: Avoid overwriting the div info when disabling a pll_div clk

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit 68af4fa8f39b542a6cde7ac19518d88e9b3099dc upstream. bcm2835_pll_divider_off() is resetting the divider field in the A2W reg to zero when disabling the clock. Make sure

[PATCH 4.9 098/116] pNFS: Dont clear the layout stateid if a layout return is outstanding

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 7b650994ab07434ae58a247dc9ac87d2488ca75c upstream. If we no longer hold any layout segments, we're normally expected to consider the

[PATCH] perf tools: Create libdir directory before installing libperf-jvmti.so

The install command for libperf-jvmti.so does not check if libdir exists before installing. This means that when the install command is run: install libperf-jvmti.so '/tmp/test_root/usr/lib64'; libperf-jvmti.so will get installed to /usr/lib64 as a file and break further installation. Fix this

[PATCH 4.4 00/58] 4.4.41-stable review

This is the start of the stable review cycle for the 4.4.41 release. There are 58 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sun Jan 8 21:38:49 UTC 2017. Anything

[PATCH 4.9 098/116] pNFS: Dont clear the layout stateid if a layout return is outstanding

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 7b650994ab07434ae58a247dc9ac87d2488ca75c upstream. If we no longer hold any layout segments, we're normally expected to consider the layout stateid to be invalid.

[PATCH] perf tools: Create libdir directory before installing libperf-jvmti.so

The install command for libperf-jvmti.so does not check if libdir exists before installing. This means that when the install command is run: install libperf-jvmti.so '/tmp/test_root/usr/lib64'; libperf-jvmti.so will get installed to /usr/lib64 as a file and break further installation. Fix this

[PATCH 4.4 00/58] 4.4.41-stable review

This is the start of the stable review cycle for the 4.4.41 release. There are 58 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sun Jan 8 21:38:49 UTC 2017. Anything

[PATCH 4.4 54/58] powerpc: Convert cmp to cmpd in idle enter sequence

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Segher Boessenkool commit 80f23935cadb1c654e81951f5a8b7ceae0acc1b4 upstream. PowerPC's "cmp" instruction has four operands. Normally people write "cmpw" or "cmpd"

Re: [PATCH v5 5/5] arm64: dts: exynos: Add tm2 touchkey node

Hi, 2017-01-07 7:09 GMT+09:00 Chanwoo Choi : > Hi, > > 2017-01-07 6:31 GMT+09:00 Chanwoo Choi : >> Hi, >> >> 2017-01-06 22:43 GMT+09:00 Andi Shyti : >>> From: Jaechul Lee >>> >>> Add DT node support for TM2

[PATCH 4.4 50/58] PCI: Check for PME in targeted sleep state

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit 6496ebd7edf446fccf8266a1a70ffcb64252593e upstream. One some systems, the firmware does not allow certain PCI devices to be put in deep D-states.

[PATCH 4.4 49/58] Input: drv260x - fix input devices parent assignment

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jingkui Wang commit 5a8a6b89c15766446d845671d574a9243b6d8786 upstream. We were assigning I2C bus controller instead of client as parent device. Besides being logically

[PATCH 4.4 54/58] powerpc: Convert cmp to cmpd in idle enter sequence

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Segher Boessenkool commit 80f23935cadb1c654e81951f5a8b7ceae0acc1b4 upstream. PowerPC's "cmp" instruction has four operands. Normally people write "cmpw" or "cmpd" for the second cmp operand 0

Re: [PATCH v5 5/5] arm64: dts: exynos: Add tm2 touchkey node

Hi, 2017-01-07 7:09 GMT+09:00 Chanwoo Choi : > Hi, > > 2017-01-07 6:31 GMT+09:00 Chanwoo Choi : >> Hi, >> >> 2017-01-06 22:43 GMT+09:00 Andi Shyti : >>> From: Jaechul Lee >>> >>> Add DT node support for TM2 touchkey device. >>> >>> Signed-off-by: Beomho Seo >>> Signed-off-by: Jaechul Lee >>>

[PATCH 4.4 50/58] PCI: Check for PME in targeted sleep state

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit 6496ebd7edf446fccf8266a1a70ffcb64252593e upstream. One some systems, the firmware does not allow certain PCI devices to be put in deep D-states. This can cause problems for

[PATCH 4.4 49/58] Input: drv260x - fix input devices parent assignment

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jingkui Wang commit 5a8a6b89c15766446d845671d574a9243b6d8786 upstream. We were assigning I2C bus controller instead of client as parent device. Besides being logically wrong, it messed up with

[PATCH 4.4 48/58] [media] media: solo6x10: fix lockup by avoiding delayed register write

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Utkin commit 5fc4b067ec082c3127e0156f800769b7e0dce078 upstream. This fixes a lockup at device probing which happens on some solo6010 hardware samples.

[PATCH 4.4 39/58] KVM: PPC: Book3S HV: Dont lose hardware R/C bit updates in H_PROTECT

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit f064a0de1579fabded8990bed93971e30deb9ecb upstream. The hashed page table MMU in POWER processors can update the R (reference) and C (change) bits in a

[PATCH 4.4 57/58] sg_write()/bsg_write() is not fit to be called under KERNEL_DS

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 128394eff343fc6d2f32172f03e24829539c5835 upstream. Both damn things interpret userland pointers embedded into the payload; worse, they are actually

[PATCH 4.4 39/58] KVM: PPC: Book3S HV: Dont lose hardware R/C bit updates in H_PROTECT

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit f064a0de1579fabded8990bed93971e30deb9ecb upstream. The hashed page table MMU in POWER processors can update the R (reference) and C (change) bits in a HPTE at any time

[PATCH 4.4 57/58] sg_write()/bsg_write() is not fit to be called under KERNEL_DS

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 128394eff343fc6d2f32172f03e24829539c5835 upstream. Both damn things interpret userland pointers embedded into the payload; worse, they are actually traversing those. Leaving

[PATCH 4.4 48/58] [media] media: solo6x10: fix lockup by avoiding delayed register write

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Utkin commit 5fc4b067ec082c3127e0156f800769b7e0dce078 upstream. This fixes a lockup at device probing which happens on some solo6010 hardware samples. This is a regression introduced by

[PATCH 4.4 45/58] IPoIB: Avoid reading an uninitialized member variable

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 11b642b84e8c43e8597de031678d15c08dd057bc upstream. This patch avoids that Coverity reports the following: Using uninitialized value

[PATCH 4.4 45/58] IPoIB: Avoid reading an uninitialized member variable

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 11b642b84e8c43e8597de031678d15c08dd057bc upstream. This patch avoids that Coverity reports the following: Using uninitialized value port_attr.state when calling

[PATCH 4.4 47/58] IB/cma: Fix a race condition in iboe_addr_get_sgid()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit fba332b079029c2f4f7e84c1c1cd8e3867310c90 upstream. Code that dereferences the struct net_device ip_ptr member must be protected with an

Re: weird allocation pattern in alloc_ila_locks

On Fri, 2017-01-06 at 13:16 +0100, Michal Hocko wrote: > I was thinking about the rhashtable which was the source of the c and > it can be simplified as well. > --- > From 43604f5f020284ea85d928d52f6a55fde7ca Mon Sep 17 00:00:00 2001 > From: Michal Hocko > Date: Fri, 6 Jan

[PATCH 4.4 38/58] KVM: PPC: Book3S HV: Save/restore XER in checkpointed register state

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 0d808df06a44200f52262b6eb72bcb6042f5a7c5 upstream. When switching from/to a guest that has a transaction in progress, we need to save/restore the

[PATCH 4.4 47/58] IB/cma: Fix a race condition in iboe_addr_get_sgid()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit fba332b079029c2f4f7e84c1c1cd8e3867310c90 upstream. Code that dereferences the struct net_device ip_ptr member must be protected with an in_dev_get() / in_dev_put() pair.

Re: weird allocation pattern in alloc_ila_locks

On Fri, 2017-01-06 at 13:16 +0100, Michal Hocko wrote: > I was thinking about the rhashtable which was the source of the c and > it can be simplified as well. > --- > From 43604f5f020284ea85d928d52f6a55fde7ca Mon Sep 17 00:00:00 2001 > From: Michal Hocko > Date: Fri, 6 Jan 2017 13:12:31 +0100

[PATCH 4.4 38/58] KVM: PPC: Book3S HV: Save/restore XER in checkpointed register state

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 0d808df06a44200f52262b6eb72bcb6042f5a7c5 upstream. When switching from/to a guest that has a transaction in progress, we need to save/restore the checkpointed register

[PATCH 4.4 41/58] ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short jumps to it

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (Red Hat) commit 847fa1a6d3d00f3bdf68ef5fa4a786f644a0dd67 upstream. With new binutils, gcc may get smart with its optimization and change a jmp from a 5

[PATCH 4.4 58/58] net: mvpp2: fix dma unmapping of TX buffers for fragments

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit 8354491c9d5b06709384cea91d13019bf5e61449 upstream. Since commit 71ce391dfb784 ("net: mvpp2: enable proper per-CPU TX buffers

[PATCH 4.4 41/58] ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short jumps to it

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (Red Hat) commit 847fa1a6d3d00f3bdf68ef5fa4a786f644a0dd67 upstream. With new binutils, gcc may get smart with its optimization and change a jmp from a 5 byte jump to a 2 byte

[PATCH 4.4 58/58] net: mvpp2: fix dma unmapping of TX buffers for fragments

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit 8354491c9d5b06709384cea91d13019bf5e61449 upstream. Since commit 71ce391dfb784 ("net: mvpp2: enable proper per-CPU TX buffers unmapping"), we are not correctly DMA

[PATCH 4.4 22/58] drm/gma500: Add compat ioctl

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Patrik Jakobsson commit 0a97c81a9717431e6c57ea845b59c3c345edce67 upstream. Hook up drm_compat_ioctl to support 32-bit userspace on 64-bit kernels. It turns out

[PATCH 4.4 22/58] drm/gma500: Add compat ioctl

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Patrik Jakobsson commit 0a97c81a9717431e6c57ea845b59c3c345edce67 upstream. Hook up drm_compat_ioctl to support 32-bit userspace on 64-bit kernels. It turns out that N2600 and N2800 comes with

Re: [PATCH v5 4/5] input: tm2-touchkey: Add touchkey driver support for TM2

Hi, I have a question. In this patch, the compatible name includes the specific h/w board name(TM2). Usually, when developing the device driver, we prefer to use the original h/w name of each device. - "samsung,tm2-touchkey" If this touchkey device is used on other h/w board, you should add new

Re: [PATCH v5 4/5] input: tm2-touchkey: Add touchkey driver support for TM2

Hi, I have a question. In this patch, the compatible name includes the specific h/w board name(TM2). Usually, when developing the device driver, we prefer to use the original h/w name of each device. - "samsung,tm2-touchkey" If this touchkey device is used on other h/w board, you should add new

[PATCH 4.4 17/58] drm/nouveau/fifo/gf100-: protect channel preempt with subdev mutex

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit b27add13f500469127afdf011dbcc9c649e16e54 upstream. This avoids an issue that occurs when we're attempting to preempt multiple channels simultaneously. HW

[PATCH 4.4 17/58] drm/nouveau/fifo/gf100-: protect channel preempt with subdev mutex

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit b27add13f500469127afdf011dbcc9c649e16e54 upstream. This avoids an issue that occurs when we're attempting to preempt multiple channels simultaneously. HW seems to ignore

[PATCH 4.4 35/58] s390/vmlogrdr: fix IUCV buffer allocation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gerald Schaefer commit 5457e03de918f7a3e294eb9d26a608ab8a579976 upstream. The buffer for iucv_message_receive() needs to be below 2 GB. In __iucv_message_receive(),

[PATCH 4.4 36/58] sc16is7xx: Drop bogus use of IRQF_ONESHOT

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Josh Cartwright commit 04da73803c05dc1150ccc31cbf93e8cd56679c09 upstream. The use of IRQF_ONESHOT when registering an interrupt handler with request_irq() is non-sensical. Not

[PATCH 4.4 37/58] md/raid5: limit request size according to implementation limits

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Konstantin Khlebnikov commit e8d7c33232e5fdfa761c3416539bc5b4acd12db5 upstream. Current implementation employ 16bit counter of active stripes in lower bits of

[PATCH 4.4 03/58] cfg80211/mac80211: fix BSS leaks when abandoning assoc attempts

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit e6f462df9acd2a3295e5d34eb29e2823220cf129 upstream. When mac80211 abandons an association attempt, it may free all the data structures, but inform

[PATCH 4.4 35/58] s390/vmlogrdr: fix IUCV buffer allocation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gerald Schaefer commit 5457e03de918f7a3e294eb9d26a608ab8a579976 upstream. The buffer for iucv_message_receive() needs to be below 2 GB. In __iucv_message_receive(), the buffer address is

[PATCH 4.4 36/58] sc16is7xx: Drop bogus use of IRQF_ONESHOT

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Josh Cartwright commit 04da73803c05dc1150ccc31cbf93e8cd56679c09 upstream. The use of IRQF_ONESHOT when registering an interrupt handler with request_irq() is non-sensical. Not only that, it

[PATCH 4.4 37/58] md/raid5: limit request size according to implementation limits

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Konstantin Khlebnikov commit e8d7c33232e5fdfa761c3416539bc5b4acd12db5 upstream. Current implementation employ 16bit counter of active stripes in lower bits of bio->bi_phys_segments. If request

[PATCH 4.4 03/58] cfg80211/mac80211: fix BSS leaks when abandoning assoc attempts

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit e6f462df9acd2a3295e5d34eb29e2823220cf129 upstream. When mac80211 abandons an association attempt, it may free all the data structures, but inform cfg80211 and userspace

[PATCH v2] PCI: lock each enable/disable num_vfs operation in sysfs

Enabling/disabling SRIOV via sysfs by echo-ing multiple values simultaneously: echo 63 > /sys/class/net/ethX/device/sriov_numvfs& echo 63 > /sys/class/net/ethX/device/sriov_numvfs sleep 5 echo 0 > /sys/class/net/ethX/device/sriov_numvfs& echo 0 > /sys/class/net/ethX/device/sriov_numvfs Results

[PATCH v2] PCI: lock each enable/disable num_vfs operation in sysfs

Enabling/disabling SRIOV via sysfs by echo-ing multiple values simultaneously: echo 63 > /sys/class/net/ethX/device/sriov_numvfs& echo 63 > /sys/class/net/ethX/device/sriov_numvfs sleep 5 echo 0 > /sys/class/net/ethX/device/sriov_numvfs& echo 0 > /sys/class/net/ethX/device/sriov_numvfs Results

[PATCH 4.4 55/58] target/user: Fix use-after-free of tcmu_cmds if they are expired

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andy Grover commit d0905ca757bc40bd1ebc261a448a521b064777d7 upstream. Don't free the cmd in tcmu_check_expired_cmd, it's still referenced by an entry in our cmd_id->cmd

[PATCH 4.4 40/58] kvm: nVMX: Allow L1 to intercept software exceptions (#BP and #OF)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jim Mattson commit ef85b67385436ddc1998f45f1d6a210f935b3388 upstream. When L2 exits to L0 due to "exception or NMI", software exceptions (#BP and #OF) for which L1 has

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