[PATCH 4.2 063/110] ARM: 8449/1: fix bug in vdsomunge swab32 macro

4.2-stable review patch. If anyone has any objections, please let me know. -- From: "H. Nikolaus Schaller" commit 38850d786a799c3ff2de0dc1980902c3263698dc upstream. Commit 8a603f91cc48 ("ARM: 8445/1: fix vdsomunge not to depend on glibc specific byteswap.h") unfortunately

[PATCH 4.2 062/110] ARM: 8445/1: fix vdsomunge not to depend on glibc specific byteswap.h

4.2-stable review patch. If anyone has any objections, please let me know. -- From: "H. Nikolaus Schaller" commit 8a603f91cc4848ab1a0458bc065aa9f64322e123 upstream. If the host toolchain is not glibc based then the arm kernel build fails with HOSTCC

[PATCH 4.2 061/110] ARM: OMAP1: fix incorrect INT_DMA_LCD

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Aaro Koskinen commit 1bd5dfe41b994a6e793363894befef76626965a9 upstream. Commit 685e2d08c54b ("ARM: OMAP1: Change interrupt numbering for sparse IRQ") turned on SPARSE_IRQ on OMAP1, but forgot

Re: [PATCH v6 1/5] Documentation: tps65912: Add DT bindings for the TPS65912 PMIC

On Fri, Oct 30, 2015 at 05:28:04PM -0500, Andrew F. Davis wrote: > The TPS65912 PMIC contains several regulators and a GPIO controller. > Add bindings for the TPS65912 PMIC. > > Signed-off-by: Andrew F. Davis > --- > .../devicetree/bindings/gpio/gpio-tps65912.txt | 16 +++ >

Re: [PATCH tip/locking/core v9 6/6] locking/pvqspinlock: Queue node adaptive spinning

On Fri, Nov 06, 2015 at 12:54:06PM -0500, Waiman Long wrote: > >>+static void pv_wait_node(struct mcs_spinlock *node, struct mcs_spinlock > >>*prev) > >> { > >>struct pv_node *pn = (struct pv_node *)node; > >>+ struct pv_node *pp = (struct pv_node *)prev; > >>int waitcnt = 0; > >>

[PATCH 4.2 074/110] clkdev: fix clk_add_alias() with a NULL alias device name

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Russell King commit 625faa6a720d26fc0db9e20b48dc0dfe4c8d8ddf upstream. clk_add_alias() was not correctly handling the case where alias_dev_name was NULL: rather than producing an entry with a

[PATCH 4.2 065/110] arm64: kernel: fix tcr_el1.t0sz restore on systems with extended idmap

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Lorenzo Pieralisi commit e13d918a19a7b6cba62b32884f5e336e764c2cc6 upstream. Commit dd006da21646 ("arm64: mm: increase VA range of identity map") introduced a mechanism to extend the virtual

[PATCH 4.2 029/110] ASoC: wm8904: Correct number of EQ registers

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Charles Keepax commit 97aff2c03a1e4d343266adadb52313613efb027f upstream. There are 24 EQ registers not 25, I suspect this bug came about because the registers start at EQ1 not zero. The bug is

[PATCH 4.2 037/110] drm/nouveau/gem: return only valid domain when theres only one

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Ilia Mirkin commit 2a6c521bb41ce862e43db46f52e7681d33e8d771 upstream. On nv50+, we restrict the valid domains to just the one where the buffer was originally created. However after the buffer

[PATCH 4.2 038/110] drm/radeon/dpm: dont add pwm attributes if DPM is disabled

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 2a7d44f47f53fa1be677f44c73d78b1bcf9c05d9 upstream. PWM fan control is only available with DPM. If DPM disabled, don't expose the PWM fan controls to avoid a crash. Bug:

[PATCH 4.2 036/110] bus: arm-ccn: Fix irq affinity setting on CPU migration

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Pawel Moll commit a0bcbe969f564d1ec08658170dda72a1b7e9053a upstream. When PMU context is migrating between CPUs, interrupt affinity is set as well. Only this should not happen when the CCN

[PATCH 4.2 035/110] tracing: Have stack tracer force RCU to be watching

4.2-stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (Red Hat)" commit a2d7629048322ae62bff57f34f5f995e25ed234c upstream. The stack tracer was triggering the WARN_ON() in module.c: static void

[PATCH 4.2 076/110] xhci: handle no ping response error properly

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit 3b4739b8951d650becbcd855d7d6f18ac98a9a85 upstream. If a host fails to wake up a isochronous SuperSpeed device from U1/U2 in time for a isoch transfer it will generate a

[PATCH 4.2 080/110] PCI: Prevent out of bounds access in numa_node override

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Sasha Levin commit 1266963170f576d4d08e6310b6963e26d3ff9d1e upstream. 63692df103e9 ("PCI: Allow numa_node override via sysfs") didn't check that the numa node provided by userspace is valid.

[PATCH 4.2 075/110] fbcon: initialize blink interval before calling fb_set_par

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Scot Doyle commit f235f664a8afabccf863a5dee4777d2d7b676fda upstream. Since commit 27a4c827c34ac4256a190cc9d24607f953c1c459 fbcon: use the cursor blink interval provided by vt a PPC64LE

[PATCH 4.2 078/110] xen-blkfront: check for null drvdata in blkback_changed (XenbusStateClosing)

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Cathy Avery commit a54c8f0f2d7df525ff997e2afe71866a1a013064 upstream. xen-blkfront will crash if the check to talk_to_blkback() in blkback_changed()(XenbusStateInitWait) returns an error. The

[PATCH 4.2 079/110] module: Fix locking in symbol_put_addr()

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 275d7d44d802ef271a42dc87ac091a495ba72fc5 upstream. Poma (on the way to another bug) reported an assertion triggering: [] module_assert_mutex_or_preempt+0x49/0x90 []

[PATCH 4.2 077/110] xhci: Add spurious wakeup quirk for LynxPoint-LP controllers

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Laura Abbott commit fd7cd061adcf5f7503515ba52b6a724642a839c8 upstream. We received several reports of systems rebooting and powering on after an attempted shutdown. Testing showed that setting

[PATCH 4.2 108/110] pinctrl: baytrail: Serialize all register access

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Mika Westerberg commit 39ce8150a079e3ae6ed9abf26d7918a558ef7c19 upstream. There is a hardware issue in Intel Baytrail where concurrent GPIO register access might result reads of 0x and

Re: [PATCH 2/6] x86/microcode: Merge early loader

On Fri, Nov 06, 2015 at 02:22:42PM -0500, Josh Boyer wrote: > So this broke dracut. Dracut will look at the config file for the > INTEL or AMD early config options being set. Nothing outside the kernel should depend on Kconfig symbols. > Do we have suggestions on how to work this out going

[PATCH 4.2 106/110] drm/vmwgfx: Fix up user_dmabuf refcounting

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Hellstrom commit 54c12bc374408faddbff75dbf1a6167c19af39c4 upstream. If user space calls unreference on a user_dmabuf it will typically kill the struct ttm_base_object member which is

linux-next network throughput performance regression

I compared the network throughput performance on SLES12 bare metal servers, between SLES12 default kernel and latest linux-next (2015-11-05) kernel, based on the test results, I suspect there is a network regression exists on Linux-Next over the 40G Ethernet network: a) iperf3 reports 50%

[PATCH 4.2 101/110] IB/cm: Fix rb-tree duplicate free and use-after-free

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Doron Tsur commit 0ca81a2840f77855bbad1b9f172c545c4dc9e6a4 upstream. ib_send_cm_sidr_rep could sometimes erase the node from the sidr (depending on errors in the process). Since

Re: [PATCH -next] net: hisilicon: Never build on SPARC

On Friday 06 November 2015 11:16:52 Guenter Roeck wrote: > On Wed, Oct 21, 2015 at 02:53:20PM -0700, Guenter Roeck wrote: > > On Wed, Oct 21, 2015 at 09:11:53PM +0200, Arnd Bergmann wrote: > > > On Wednesday 21 October 2015 10:03:05 Guenter Roeck wrote: > > > > Anyway, if it gets that complicated,

Re: [RFC 3/3] ARM: e3xx: Add header file for pinctrl constants

On Friday 06 November 2015 09:55:28 Moritz Fischer wrote: > On Fri, Nov 6, 2015 at 8:42 AM, Arnd Bergmann wrote: > > On Friday 06 November 2015 08:01:25 Moritz Fischer wrote: > >> pins = E31X_TX_BANDSEL_2; > >> output-low; > >> > >> in one .dts, while having something like > >> > >> pins =

[PATCH 4.2 107/110] thp: use is_zero_pfn() only after pte_present() check

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Minchan Kim commit 47aee4d8e314384807e98b67ade07f6da476aa75 upstream. Use is_zero_pfn() on pteval only after pte_present() check on pteval (It might be better idea to introduce is_zero_pte()

[GIT PULL] power supply fix for 4.4

Hi Linus, The following changes since commit 3e069adabc9487b5e28065a17e6a228da3412dfd: Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input (2015-11-06 11:57:41 -0800) are available in the git repository at:

[PATCH 4.2 099/110] um: Fix kernel mode fault condition

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit 56b88a3bf97a39d3f4f010509917b76a865a6dc8 upstream. We have to exclude memory locations <= PAGE_SIZE from the condition and let the kernel mode fault path catch it.

Re: [PATCH] arm: Use kernel mm when updating section permissions

On Fri, Nov 6, 2015 at 12:11 PM, Kevin Hilman wrote: > On Fri, Nov 6, 2015 at 11:12 AM, Kees Cook wrote: > > [...] > >> Hi Kevin and Kernel CI folks, >> >> Could lkdtm get added to the kernel-CI workflows? Extracting and >> validating Oops details when poking lkdtm would be extremely valuable >>

[PATCH 4.1 01/86] ath9k: declare required extra tx headroom

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau commit 029cd0370241641eb70235d205aa0b90c84dce44 upstream. ath9k inserts padding between the 802.11 header and the data area (to align it). Since it didn't declare this extra

[PATCH 4.1 10/86] iommu/vt-d: fix range computation when making room for large pages

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Christian Zander commit ba2374fd2bf379f933773811fdb06cb6a5445f41 upstream. In preparation for the installation of a large page, any small page tables that may still exist in the target IOV

Re: [dm-devel] [PATCH 0/4] dm verity: add support for error correction

On Fri, Nov 06, 2015 at 08:20:15PM +0100, Zdenek Kabelac wrote: > i.e. you have 1G of space - you want to give 250MB as 'redundancy' - > so create 4 partition We cannot afford to set aside 25% of read-only partition space for redundancy on mobile devices, and would rather not impact

[PATCH 4.1 12/86] iommu/amd: Dont clear DTE flags when modifying it

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Joerg Roedel commit cbf3ccd09d683abf1cacd36e3640872ee912d99b upstream. During device assignment/deassignment the flags in the DTE get lost, which might cause spurious faults, for example when

[PATCH 4.1 13/86] powerpc/rtas: Validate rtas.entry before calling enter_rtas()

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Vasant Hegde commit 8832317f662c06f5c06e638f57bfe89a71c9b266 upstream. Currently we do not validate rtas.entry before calling enter_rtas(). This leads to a kernel oops when user space calls

[PATCH 4.1 11/86] iommu/amd: Fix BUG when faulting a PROT_NONE VMA

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Jay Cornwall commit d14f6fced5f9360edca5a1325ddb7077aab1203b upstream. handle_mm_fault indirectly triggers a BUG in do_numa_page when given a VMA without read/write/execute access. Check this

[PATCH 4.2 104/110] arm64: compat: fix stxr failure case in SWP emulation

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit 589cb22bbedacf325951014c07a35a2b01ca57f6 upstream. If the STXR instruction fails in the SWP emulation code, we leave *data overwritten with the loaded value, therefore

[PATCH 4.1 17/86] [media] rtl28xxu: fix control message flaws

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Antti Palosaari commit d18ca5b7ceca0e9674cb4bb2ed476b0fcbb23ba2 upstream. Add lock to prevent concurrent access for control message as control message function uses shared buffer. Without the

[PATCH 4.1 14/86] drm: fix mutex leak in drm_dp_get_mst_branch_device

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Adam Richter commit 30730c7f5943b3beace1e29f7f1476e05de3da14 upstream. In Linux 4.3-rc5, there is an error case in drm_dp_get_branch_device that returns without releasing mgr->lock, resulting

[PATCH 4.1 16/86] [media] si2168: Bounds check firmware

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Laura Abbott commit 47810b4341ac9d2f558894bc5995e6fa2a1298f9 upstream. When reading the firmware and sending commands, the length must be bounds checked to avoid overrunning the size of the

Re: [PATCH 0/2] "big hammer" for DAX msync/fsync correctness

On November 5, 2015 3:59:46 PM PST, Dan Williams wrote: >On Wed, Oct 28, 2015 at 3:51 PM, Ross Zwisler > wrote: >> On Wed, Oct 28, 2015 at 06:24:29PM -0400, Jeff Moyer wrote: >>> Ross Zwisler writes: >>> >>> > This series implements the very slow but correct handling for >>> >

[PATCH 4.1 19/86] ALSA: hda - Fix inverted internal mic on Lenovo G50-80

4.1-stable review patch. If anyone has any objections, please let me know. -- From: David Henningsson commit e8d65a8d985271a102f07c7456da5b86c19ffe16 upstream. Add the appropriate quirk to indicate the Lenovo G50-80 has a stereo mic input where one channel has reverse

[PATCH 4.1 15/86] [media] si2157: Bounds check firmware

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Laura Abbott commit a828d72df216c36e9c40b6c24dc4b17b6f7b5a76 upstream. When reading the firmware and sending commands, the length must be bounds checked to avoid overrunning the size of the

[PATCH 4.1 18/86] KVM: arm: use GIC support unconditionally

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 4a5d69b73948d0e03cd38d77dc11edb2e707165f upstream. The vgic code on ARM is built for all configurations that enable KVM, but the parent_data field that it references is

[PATCH 4.1 20/86] ALSA: hda - Fix deadlock at error in building PCM

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit d289619a219dd01e255d7b5e30f9171b25efea48 upstream. The HDA codec driver issues snd_hda_codec_reset() at the error path of PCM build. This was needed in the earlier code

[PATCH 4.1 02/86] iwlwifi: dvm: fix D3 firmware PN programming

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit 5bd166872d8f99f156fac191299d24f828bb2348 upstream. The code to send the RX PN data (for each TID) to the firmware has a devastating bug: it overwrites the data for TID 0

[PATCH 4.1 21/86] ASoC: Add info callback for SX_TLV controls

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Charles Keepax commit 34198710f55b5f359f43e67d9a08fe5aadfbca1b upstream. SX_TLV controls are intended for situations where the register behind the control has some non-zero value indicating

[PATCH 4.2 105/110] NVMe: Fix memory leak on retried commands

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Keith Busch commit 0dfc70c33409afc232ef0b9ec210535dfbf9bc61 upstream. Resources are reallocated for requeued commands, so unmap and release the iod for the failed command. It's a pretty bad

[PATCH 4.1 24/86] x86/setup: Extend low identity map to cover whole kernel range

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit f5f3497cad8c8416a74b9aaceb127908755d020a upstream. On 32-bit systems, the initial_page_table is reused by efi_call_phys_prolog as an identity map to call

[PATCH 4.1 25/86] mm: make sendfile(2) killable

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 296291cdd1629c308114504b850dc343eabc2782 upstream. Currently a simple program below issues a sendfile(2) system call which takes about 62 days to complete in my test KVM

[PATCH 4.1 22/86] ASoC: wm8904: Correct number of EQ registers

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Charles Keepax commit 97aff2c03a1e4d343266adadb52313613efb027f upstream. There are 24 EQ registers not 25, I suspect this bug came about because the registers start at EQ1 not zero. The bug is

Re: [PATCH 4/7] mfd: hi655x: Add hi665x pmic driver

On Thu, Nov 5, 2015 at 3:34 PM, Chen Feng wrote: > Add pmic driver to support hisilicon hi665x pmic. > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include > +#include

Re: [PATCH 3/3] comedi: driver: Fix - BIT macro used coding style issue

On Thu, Nov 05, 2015 at 09:27:45PM +0530, Ranjith wrote: > BIT macro is used for defining bit location instead of shifting > operator - coding style issue > > Signed-off-by: Ranjith T You're From line and your signed-off line need to match and they both need to be your legal name that you use

[PATCH 4.1 27/86] drm/nouveau/gem: return only valid domain when theres only one

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Ilia Mirkin commit 2a6c521bb41ce862e43db46f52e7681d33e8d771 upstream. On nv50+, we restrict the valid domains to just the one where the buffer was originally created. However after the buffer

[PATCH 4.2 103/110] cpufreq: intel_pstate: Fix divide by zero on Knights Landing (KNL)

4.2-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Pandruvada commit 8e601a9f97a00bab031980de34f9a81891c1f82f upstream. This is a workaround for KNL platform, where in some cases MPERF counter will not have updated value before next

[PATCH 4.1 26/86] fault-inject: fix inverted interval/probability values in printk

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit bb387002693ed28b2bb0408c5dec65521b71e5f1 upstream. interval displays the probability and vice versa. Fixes: 6adc4a22f20bb ("fault-inject: add ratelimit option")

[PATCH 4.1 03/86] iwlwifi: fix firmware filename for 3160

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit b5a48134f8af08f5243328f8a0b05fc5ae7cf343 upstream. The MODULE_FIRMWARE() for 3160 should be using the 7260 version as it's done in the device configuration struct instead

[PATCH 4.1 28/86] drm/radeon/dpm: dont add pwm attributes if DPM is disabled

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 2a7d44f47f53fa1be677f44c73d78b1bcf9c05d9 upstream. PWM fan control is only available with DPM. If DPM disabled, don't expose the PWM fan controls to avoid a crash. Bug:

Re: [PATCH 1/2] HID: hid-logitech: Simplify wheel detection scheme

On Mon, 2 Nov 2015, Simon Wood wrote: > Simplfy how hid-logitech driver detects the native mode of the wheel, > done by looking at the USB-ID revision and comparing bit mask. > > Signed-off-by: Simon Wood I've applied both patches to for-4.4/logitech. Thanks, -- Jiri Kosina SUSE Labs -- To

[PATCH 4.1 00/86] 4.1.13-stable review

This is the start of the stable review cycle for the 4.1.13 release. There are 86 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 Nov 8 19:21:32 UTC 2015. Anything

[PATCH 4.1 43/86] ARM: dts: Fix audio card detection on Peach boards

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Alim Akhtar commit b8bb9baad27e455c467e8fac47eebadbe765c18f upstream. Since commit 2fad972d45c4 ("ARM: dts: Add mclk entry for Peach boards"), sound card detection is broken on peach boards

[PATCH 4.1 08/86] iwlwifi: mvm: flush fw_dump_wk when mvm fails to start

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Andrei Otcheretianski commit dbf73d4a8bb8f4e1d1f3edd3be825692279e2ef3 upstream. FW dump may be triggered when running init ucode, for example due to a sysassert. In this case fw_dump_wk may

[PATCH 4.1 09/86] iwlwifi: pci: add a few more PCI subvendor IDs for the 7265 series

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Luca Coelho commit f08f625876476b6c4a87834dc86e3b927f4697d2 upstream. Add 3 new subdevice IDs for the 0x095A device ID and 2 for the 0x095B device ID. Reported-by: Jeremy Signed-off-by: Luca

[PATCH 4.1 32/86] drm/radeon: dont try to recreate sysfs entries on resume

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 49abb26651167c892393cd9f2ad23df429645ed9 upstream. Fixes a harmless error message caused by: 51a4726b04e880fdd9b4e0e58b13f70b0a68a7f5 Signed-off-by: Alex Deucher

[PATCH 4.1 45/86] ARM: dts: sunxi: Raise minimum CPU voltage for sun7i-a20 to meet SoC specifications

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Timo Sigurdsson commit eaeef1ad9b6ea6df1d1220c254d9563da60cb9d1 upstream. sun7i-a20.dtsi contains a cpufreq operating point at 0.9 volts. The minimum CPU voltage for the Allwinner A20 SoC,

[PATCH 4.1 46/86] ARM: 8445/1: fix vdsomunge not to depend on glibc specific byteswap.h

4.1-stable review patch. If anyone has any objections, please let me know. -- From: "H. Nikolaus Schaller" commit 8a603f91cc4848ab1a0458bc065aa9f64322e123 upstream. If the host toolchain is not glibc based then the arm kernel build fails with HOSTCC

[PATCH 4.1 48/86] Revert "ARM64: unwind: Fix PC calculation"

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit 9702970c7bd3e2d6fecb642a190269131d4ac16c upstream. This reverts commit e306dfd06fcb44d21c80acb8e5a88d55f3d1cf63. With this patch applied, we were the only architecture

[PATCH 4.1 44/86] ARM: dts: am57xx-beagle-x15: set VDD_SD to always-on

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Tomi Valkeinen commit 7e381ec6a36aa44f15fc1a76e6efb9e2cd942e61 upstream. LDO1 regulator (VDD_SD) is connected to SoC's vddshv8. vddshv8 needs to be kept always powered (see commit 5a0f93c6576a

[PATCH 4.1 54/86] xhci: handle no ping response error properly

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit 3b4739b8951d650becbcd855d7d6f18ac98a9a85 upstream. If a host fails to wake up a isochronous SuperSpeed device from U1/U2 in time for a isoch transfer it will generate a

[PATCH 4.1 53/86] i2c: mv64xxx: really allow I2C offloading

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Hezi Shahmoon commit 0729a04977d497cf66234fd7f900ddcec3ef1c52 upstream. Commit 00d8689b85a7 ("i2c: mv64xxx: rework offload support to fix several problems") completely reworked the offload

[PATCH 4.1 50/86] dm btree: fix leak of bufio-backed block in btree_split_beneath error path

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit 4dcb8b57df3593dcb20481d9d6cf79d1dc1534be upstream. btree_split_beneath()'s error path had an outstanding FIXME that speaks directly to the potential for _not_ cleaning up a

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: > Some qcom based bootloaders identify the dtb blob based on a set > of device properties like SoC, platform, PMIC, and revisions of > those components. In downstream kernels, these values are added > to the different component dtsi

[PATCH 4.1 51/86] Revert "serial: 8250_dma: dont bother DMA with small transfers"

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Frederic Danis commit f967fc8f165fadb72166f2bd4785094b3ca21307 upstream. This reverts commit 9119fba0cfeda6d415c9f068df66838a104b87cb. This commit prevents from sending "big" file using

[PATCH 4.1 47/86] ARM: 8449/1: fix bug in vdsomunge swab32 macro

4.1-stable review patch. If anyone has any objections, please let me know. -- From: "H. Nikolaus Schaller" commit 38850d786a799c3ff2de0dc1980902c3263698dc upstream. Commit 8a603f91cc48 ("ARM: 8445/1: fix vdsomunge not to depend on glibc specific byteswap.h") unfortunately

[PATCH 4.1 49/86] dm btree remove: fix a bug when rebalancing nodes after removal

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Joe Thornber commit 2871c69e025e8bc507651d5a9cf81a8a7da9d24b upstream. Commit 4c7e309340ff ("dm btree remove: fix bug in redistribute3") wasn't a complete fix for redistribute3(). The

Re: [PATCH] arm: Use kernel mm when updating section permissions

On Fri, Nov 6, 2015 at 11:12 AM, Kees Cook wrote: [...] > Hi Kevin and Kernel CI folks, > > Could lkdtm get added to the kernel-CI workflows? Extracting and > validating Oops details when poking lkdtm would be extremely valuable > for these cases. :) Yeah, we can add that. What arches should

[PATCH 4.1 55/86] xhci: Add spurious wakeup quirk for LynxPoint-LP controllers

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Laura Abbott commit fd7cd061adcf5f7503515ba52b6a724642a839c8 upstream. We received several reports of systems rebooting and powering on after an attempted shutdown. Testing showed that setting

[PATCH 4.1 56/86] xen-blkfront: check for null drvdata in blkback_changed (XenbusStateClosing)

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Cathy Avery commit a54c8f0f2d7df525ff997e2afe71866a1a013064 upstream. xen-blkfront will crash if the check to talk_to_blkback() in blkback_changed()(XenbusStateInitWait) returns an error. The

[PATCH 4.1 58/86] PCI: Prevent out of bounds access in numa_node override

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Sasha Levin commit 1266963170f576d4d08e6310b6963e26d3ff9d1e upstream. 63692df103e9 ("PCI: Allow numa_node override via sysfs") didn't check that the numa node provided by userspace is valid.

[PATCH 4.1 57/86] module: Fix locking in symbol_put_addr()

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 275d7d44d802ef271a42dc87ac091a495ba72fc5 upstream. Poma (on the way to another bug) reported an assertion triggering: [] module_assert_mutex_or_preempt+0x49/0x90 []

[PATCH 4.1 59/86] ovl: free stack of paths in ovl_fill_super

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Konstantin Khlebnikov commit 0f95502ad84874b3c05fc7cdd9d4d9d5cddf7859 upstream. This fixes small memory leak after mount. Kmemleak report: unreferenced object 0x88003683fe00 (size 16):

[PATCH 4.1 60/86] ovl: free lower_mnt array in ovl_put_super

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Konstantin Khlebnikov commit 5ffdbe8bf1e485026e1c7e4714d2841553cf0b40 upstream. This fixes memory leak after umount. Kmemleak report: unreferenced object 0x8800ba791010 (size 8): comm

[PATCH 4.1 61/86] ovl: use O_LARGEFILE in ovl_copy_up()

4.1-stable review patch. If anyone has any objections, please let me know. -- From: David Howells commit 0480334fa60488d12ae101a02d7d9e1a3d03d7dd upstream. Open the lower file with O_LARGEFILE in ovl_copy_up(). Pass O_LARGEFILE unconditionally in ovl_copy_up_data() as it's

Re: [PATCH 0/3] Remove the need for qcom,{msm-id,board-id,pmic-id}

Hi Stephen, Stephen Boyd writes: > This patchset documents a compatible string format that encodes > all the information that was being encoded in qcom specific DT > properties in downstream msm kernels. The goal being to come > up with a format that will allow us to express the information >

Re: [PATCH RESEND v2 3/4] ARM: BCM: Add SMP support for Broadcom NSP

On 06/11/15 11:57, Florian Fainelli wrote: > On 06/11/15 11:49, Kapil Hali wrote: >> Add SMP support for Broadcom's Northstar Plus SoC >> cpu enable method. This changes also consolidates >> iProc family's - BCM NSP and BCM Kona, platform >> SMP handling in a common file. >> >> Northstar Plus SoC

[PATCH 4.1 36/86] iio: st_accel: fix interrupt handling on LIS3LV02

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 61fd56309165d4790f99462d893b099f0b07312a upstream. This accelerometer accidentally either emits a DRDY signal or an IRQ signal. Accidentally I activated the IRQ signal as

[PATCH 4.1 64/86] crypto: api - Only abort operations on fatal signal

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit 3fc89adb9fa4beff31374a4bf50b3d099d88ae83 upstream. Currently a number of Crypto API operations may fail when a signal occurs. This causes nasty problems as the caller of

[PATCH 4.1 62/86] ovl: fix dentry reference leak

4.1-stable review patch. If anyone has any objections, please let me know. -- From: David Howells commit ab79efab0a0ba01a74df782eb7fa44b044dae8b5 upstream. In ovl_copy_up_locked(), newdentry is leaked if the function exits through out_cleanup as this just to out after calling

[PATCH 4.1 05/86] iwlwifi: mvm: clear csa countdown when AP is stopped

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Avraham Stern commit e9cb0327b26dd7ba43a3b7a05b4b62219decf42d upstream. The csa_countdown flag was not cleared when the AP is stopped. As a result, if the AP was stopped after csa_countdown

[PATCH 4.1 67/86] md/raid5: fix locking in handle_stripe_clean_event()

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Roman Gushchin commit b8a9d66d043ffac116100775a469f05f5158c16f upstream. After commit 566c09c53455 ("raid5: relieve lock contention in get_active_stripe()") __find_stripe() is called under

[PATCH 4.1 66/86] md/raid10: submit_bio_wait() returns 0 on success

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Jes Sorensen commit 681ab4696062f5aa939c9e04d058732306a97176 upstream. This was introduced with 9e882242c6193ae6f416f2d8d8db0d9126bd996b which changed the return value of submit_bio_wait() to

[PATCH 4.1 65/86] md/raid1: submit_bio_wait() returns 0 on success

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Jes Sorensen commit 203d27b0226a05202438ddb39ef0ef1acb14a759 upstream. This was introduced with 9e882242c6193ae6f416f2d8d8db0d9126bd996b which changed the return value of submit_bio_wait() to

[PATCH 4.1 06/86] iwlwifi: mvm: fix D3 firmware PN programming

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit 2cf5eb3ab7bb7f2e3a70edcef236cd62c87db030 upstream. The code to send the RX PN data (for each TID) to the firmware has a devastating bug: it overwrites the data for TID 0

[PATCH 4.1 37/86] iio: accel: sca3000: memory corruption in sca3000_read_first_n_hw_rb()

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit eda7d0f38aaf50dbb2a2de15e8db386c4f6f65fc upstream. "num_read" is in byte units but we are write u16s so we end up write twice as much as intended. Signed-off-by: Dan

[PATCH 4.1 68/86] Revert "md: allow a partially recovered device to be hot-added to an array."

4.1-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit d01552a76d71f9879af448e9142389ee9be6e95b upstream. This reverts commit 7eb418851f3278de67126ea0c427641ab4792c57. This commit is poorly justified, I can find not discusison in

[PATCH] ARM: orion: Fix DSA platform device after mvmdio conversion

DSA expects the mii_bus pointer to be the device structure associated with the MDIO bus controller driver. First commit breaking that was c3a07134e6aa ("mv643xx_eth: convert to use the Marvell Orion MDIO driver"), and then, it got completely under the radar for a while. Reported-by: Frans van de

[PATCH 4.1 41/86] ARM: orion: Fix DSA platform device after mvmdio conversion

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli commit d836ace65ee98d7079bc3c5afdbcc0e27dca20a3 upstream. DSA expects the host_dev pointer to be the device structure associated with the MDIO bus controller driver. First

Re: [PATCH] PCI: dra7xx: mark dra7xx_pcie_msi irq as IRQF_NO_THREAD

Hi Sebastian, On 11/06/2015 10:53 AM, Sebastian Andrzej Siewior wrote: > On 11/05/2015 07:43 PM, Grygorii Strashko wrote: >> diff --git a/drivers/pci/host/pci-dra7xx.c b/drivers/pci/host/pci-dra7xx.c >> index 6589e7e..31460f4 100644 >> --- a/drivers/pci/host/pci-dra7xx.c >> +++

[PATCH 4.1 42/86] ARM: mvebu: correct a385-db-ap compatible string

4.1-stable review patch. If anyone has any objections, please let me know. -- From: Marcin Wojtas commit db347f1a5304d68c68c52f19971924b1e5842f3c upstream. This commit enables standby support on Armada 385 DB-AP board, because the PM initalization routine requires

[PATCH 3.14 00/37] 3.14.57-stable review

This is the start of the stable review cycle for the 3.14.57 release. There are 37 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 Nov 8 19:23:35 UTC 2015. Anything

[PATCH 3.14 21/37] Revert "ARM64: unwind: Fix PC calculation"

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit 9702970c7bd3e2d6fecb642a190269131d4ac16c upstream. This reverts commit e306dfd06fcb44d21c80acb8e5a88d55f3d1cf63. With this patch applied, we were the only architecture

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