[PATCH 4.5 010/200] ARM: mvebu: Correct unit address for linksys

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Patrick Uiterwijk commit 199831c77c50e6913e893b6bc268ba9f4a9a2bf8 upstream. The USB2 port for Armada 38x is defined to be at 58000, not at 5. Fixes: 2d0a7addbd10

[PATCH 4.4 087/163] EDAC: i7core, sb_edac: Dont return NOTIFY_BAD from mce_decoder callback

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit c4fc1956fa31003bfbe4f597e359d751568e2954 upstream. Both of these drivers can return NOTIFY_BAD, but this terminates processing other callbacks that were

[PATCH 4.5 010/200] ARM: mvebu: Correct unit address for linksys

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Patrick Uiterwijk commit 199831c77c50e6913e893b6bc268ba9f4a9a2bf8 upstream. The USB2 port for Armada 38x is defined to be at 58000, not at 5. Fixes: 2d0a7addbd10 ("ARM: Kirkwood: Add

[PATCH 4.4 087/163] EDAC: i7core, sb_edac: Dont return NOTIFY_BAD from mce_decoder callback

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit c4fc1956fa31003bfbe4f597e359d751568e2954 upstream. Both of these drivers can return NOTIFY_BAD, but this terminates processing other callbacks that were registered later on

[PATCH 4.4 148/163] ext4: fix races between buffered IO and collapse / insert range

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 32ebffd3bbb4162da5ff88f9a35dd32d0a28ea70 upstream. Current code implementing FALLOC_FL_COLLAPSE_RANGE and FALLOC_FL_INSERT_RANGE is prone to races with buffered

[PATCH 4.4 135/163] perf evlist: Reference count the cpu and thread maps at set_maps()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnaldo Carvalho de Melo commit a55e5663761366fb883f6f25375dd68bc958b9db upstream. We were dropping the reference we possibly held but not obtaining one for the new maps,

[PATCH 4.4 148/163] ext4: fix races between buffered IO and collapse / insert range

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 32ebffd3bbb4162da5ff88f9a35dd32d0a28ea70 upstream. Current code implementing FALLOC_FL_COLLAPSE_RANGE and FALLOC_FL_INSERT_RANGE is prone to races with buffered writes and page

[PATCH 4.4 135/163] perf evlist: Reference count the cpu and thread maps at set_maps()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnaldo Carvalho de Melo commit a55e5663761366fb883f6f25375dd68bc958b9db upstream. We were dropping the reference we possibly held but not obtaining one for the new maps, which we will drop at

[PATCH 4.5 014/200] usb: xhci: applying XHCI_PME_STUCK_QUIRK to Intel BXT B0 host

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Rafal Redzimski commit 0d46faca6f887a849efb07c1655b5a9f7c288b45 upstream. Broxton B0 also requires XHCI_PME_STUCK_QUIRK. Adding PCI device ID for Broxton B and

Re: [PATCH v2 0/6] Introduce ZONE_CMA

On Mon, May 02, 2016 at 09:49:47AM +0200, Vlastimil Babka wrote: > On 05/02/2016 08:14 AM, Joonsoo Kim wrote: > >Although it's separate issue, I should mentioned one thing. Related to > >I/O pinning issue, ZONE_CMA don't get blockdev allocation request so > >I/O pinning problem is

[PATCH 4.5 001/200] mmc: block: Use the mmc host device index as the mmcblk device index

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Ulf Hansson commit 9aaf3437aa72ed5370bf32c99580a3fa2c330e3d upstream. Commit 520bd7a8b415 ("mmc: core: Optimize boot time by detecting cards simultaneously") causes

[PATCH 4.5 011/200] ARM: OMAP2: Fix up interconnect barrier initialization for DRA7

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Nishanth Menon commit 456e8d53482537616899a146b706eccd095404e6 upstream. The following commits: commit 3fa609755c11 ("ARM: omap2: restore OMAP4 barrier behaviour") commit

[PATCH 4.5 014/200] usb: xhci: applying XHCI_PME_STUCK_QUIRK to Intel BXT B0 host

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Rafal Redzimski commit 0d46faca6f887a849efb07c1655b5a9f7c288b45 upstream. Broxton B0 also requires XHCI_PME_STUCK_QUIRK. Adding PCI device ID for Broxton B and adding to quirk. Signed-off-by:

Re: [PATCH v2 0/6] Introduce ZONE_CMA

On Mon, May 02, 2016 at 09:49:47AM +0200, Vlastimil Babka wrote: > On 05/02/2016 08:14 AM, Joonsoo Kim wrote: > >Although it's separate issue, I should mentioned one thing. Related to > >I/O pinning issue, ZONE_CMA don't get blockdev allocation request so > >I/O pinning problem is

[PATCH 4.5 001/200] mmc: block: Use the mmc host device index as the mmcblk device index

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Ulf Hansson commit 9aaf3437aa72ed5370bf32c99580a3fa2c330e3d upstream. Commit 520bd7a8b415 ("mmc: core: Optimize boot time by detecting cards simultaneously") causes regressions for some

[PATCH 4.5 011/200] ARM: OMAP2: Fix up interconnect barrier initialization for DRA7

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Nishanth Menon commit 456e8d53482537616899a146b706eccd095404e6 upstream. The following commits: commit 3fa609755c11 ("ARM: omap2: restore OMAP4 barrier behaviour") commit f746929ffdc8 ("Revert

[PATCH 4.5 015/200] xhci: resume USB 3 roothub first

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit 671ffdff5b13314b1fc65d62cf7604b873fb5dc4 upstream. Give USB3 devices a better chance to enumerate at USB 3 speeds if they are connected to a

[PATCH 4.5 015/200] xhci: resume USB 3 roothub first

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit 671ffdff5b13314b1fc65d62cf7604b873fb5dc4 upstream. Give USB3 devices a better chance to enumerate at USB 3 speeds if they are connected to a suspended host. Solves an

[PATCH 1/2] Documentation: DT: bindings: Add Broadcom STB PCIe bindings

From: Jim Quinlan This patchs adds the Device Tree bindings for the Broadcom STB PCIe root complex hardware. Signed-off-by: Jim Quinlan Signed-off-by: Florian Fainelli --- .../devicetree/bindings/pci/brcm,brcmstb-pcie.txt |

[PATCH 1/2] Documentation: DT: bindings: Add Broadcom STB PCIe bindings

From: Jim Quinlan This patchs adds the Device Tree bindings for the Broadcom STB PCIe root complex hardware. Signed-off-by: Jim Quinlan Signed-off-by: Florian Fainelli --- .../devicetree/bindings/pci/brcm,brcmstb-pcie.txt | 81 ++ 1 file changed, 81 insertions(+) create

[PATCH 0/2] pci: host: Broadcom STB PCIE RC controller support

Hi all, This patch series adds support for Broadcom STB SoC's PCIe root complex driver. This was primarily tested on BCM7445 (ARM) and BCM7435 (MIPS). Jim is the original author, and I picked up our downstream 4.1 driver and updated it to utilize the non-ARM hw_pci functions as well as made

[PATCH 0/2] pci: host: Broadcom STB PCIE RC controller support

Hi all, This patch series adds support for Broadcom STB SoC's PCIe root complex driver. This was primarily tested on BCM7445 (ARM) and BCM7435 (MIPS). Jim is the original author, and I picked up our downstream 4.1 driver and updated it to utilize the non-ARM hw_pci functions as well as made

[PATCH 4.5 018/200] usb: xhci: fix wild pointers in xhci_mem_cleanup

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Lu Baolu commit 71504062a7c34838c3fccd92c447f399d3cb5797 upstream. This patch fixes some wild pointers produced by xhci_mem_cleanup. These wild pointers will cause

[PATCH 4.5 018/200] usb: xhci: fix wild pointers in xhci_mem_cleanup

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Lu Baolu commit 71504062a7c34838c3fccd92c447f399d3cb5797 upstream. This patch fixes some wild pointers produced by xhci_mem_cleanup. These wild pointers will cause system crash if

Re: [PATCH v3 2/3] fs: direct-io: call .bi_end_io via bio_endio()

On Mon, May 2, 2016 at 10:50 PM, Christoph Hellwig wrote: > On Thu, Apr 28, 2016 at 09:09:48AM +0800, Ming Lei wrote: >> bio_endio() is the graceful way to complete one bio. > > > >> >> Signed-off-by: Ming Lei >> --- >> fs/direct-io.c | 7 +-- >>

[PATCH 4.5 016/200] usb: host: xhci: add a new quirk XHCI_NO_64BIT_SUPPORT

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 0a380be8233dbf8dd20795b801c5d5d5ef3992f7 upstream. On some xHCI controllers (e.g. R-Car SoCs), the AC64 bit (bit 0) of HCCPARAMS1 is

Re: [PATCH v3 2/3] fs: direct-io: call .bi_end_io via bio_endio()

On Mon, May 2, 2016 at 10:50 PM, Christoph Hellwig wrote: > On Thu, Apr 28, 2016 at 09:09:48AM +0800, Ming Lei wrote: >> bio_endio() is the graceful way to complete one bio. > > > >> >> Signed-off-by: Ming Lei >> --- >> fs/direct-io.c | 7 +-- >> 1 file changed, 1 insertion(+), 6

[PATCH 4.5 016/200] usb: host: xhci: add a new quirk XHCI_NO_64BIT_SUPPORT

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 0a380be8233dbf8dd20795b801c5d5d5ef3992f7 upstream. On some xHCI controllers (e.g. R-Car SoCs), the AC64 bit (bit 0) of HCCPARAMS1 is set to 1. However, the xHCs don't

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

>> The takeaway is that msync() is 9-10x slower than userspace cache management. > >An alternative viewpoint: that flushing clean cachelines is >extremely expensive on Intel CPUs. ;) > >i.e. Same numbers, different analysis from a different PoV, and >that gives a *completely different

[PATCH 2/2] pci: host: Add Broadcom STB PCIE RC controller

From: Jim Quinlan This patch adds support for Broadcom's STB SoC PCIE root complex controller. This controller can be found in MIPS-based chips such as BCM7425, 7429 and 7435 and ARM-based SoCs such as BCM7445. This driver enables support for MSI, regulators that need to

[PATCH 4.4 141/163] mtd: brcmnand: Fix v7.1 register offsets

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli commit d267aefc54a28efc5bda7f009598dc83b5f98734 upstream. The BRCMNAND controller revision 7.1 is almost 100% compatible with the previous v6.0 register

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

>> The takeaway is that msync() is 9-10x slower than userspace cache management. > >An alternative viewpoint: that flushing clean cachelines is >extremely expensive on Intel CPUs. ;) > >i.e. Same numbers, different analysis from a different PoV, and >that gives a *completely different

[PATCH 2/2] pci: host: Add Broadcom STB PCIE RC controller

From: Jim Quinlan This patch adds support for Broadcom's STB SoC PCIE root complex controller. This controller can be found in MIPS-based chips such as BCM7425, 7429 and 7435 and ARM-based SoCs such as BCM7445. This driver enables support for MSI, regulators that need to be turned on prior to

[PATCH 4.4 141/163] mtd: brcmnand: Fix v7.1 register offsets

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli commit d267aefc54a28efc5bda7f009598dc83b5f98734 upstream. The BRCMNAND controller revision 7.1 is almost 100% compatible with the previous v6.0 register offset layout, except

[PATCH 4.5 002/200] block: partition: initialize percpuref before sending out KOBJ_ADD

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Ming Lei commit b30a337ca27c4f40439e4bfb290cba5f88d73bb7 upstream. The initialization of partition's percpu_ref should have been done before sending out KOBJ_ADD

[PATCH 4.5 025/200] lib: lz4: fixed zram with lz4 on big endian machines

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Rui Salvaterra commit 3e26a691fe3fe1e02a76e5bab0c143ace4b137b4 upstream. Based on Sergey's test patch [1], this fixes zram with lz4 compression on big endian cpus. Note

[PATCH 4.5 002/200] block: partition: initialize percpuref before sending out KOBJ_ADD

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Ming Lei commit b30a337ca27c4f40439e4bfb290cba5f88d73bb7 upstream. The initialization of partition's percpu_ref should have been done before sending out KOBJ_ADD uevent, which may cause

[PATCH 4.5 025/200] lib: lz4: fixed zram with lz4 on big endian machines

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Rui Salvaterra commit 3e26a691fe3fe1e02a76e5bab0c143ace4b137b4 upstream. Based on Sergey's test patch [1], this fixes zram with lz4 compression on big endian cpus. Note that the 64-bit

[PATCH 4.5 024/200] dm cache metadata: fix cmd_read_lock() acquiring write lock

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Ahmed Samy commit 6545b60baaf880b0cd29a5e89dbe745a06027e89 upstream. Commit 9567366fefdd ("dm cache metadata: fix READ_LOCK macros and cleanup WRITE_LOCK macros") uses

[PATCH 4.5 022/200] usb: gadget: f_fs: Fix use-after-free

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen commit 38740a5b87d53ceb89eb2c970150f6e94e00373a upstream. When using asynchronous read or write operations on the USB endpoints the issuer of the IO request

[PATCH 4.5 023/200] dm cache metadata: fix READ_LOCK macros and cleanup WRITE_LOCK macros

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit 9567366fefddeaea4ed1d713270535d93a3b3c76 upstream. The READ_LOCK macro was incorrectly returning -EINVAL if dm_bm_is_read_only() was true -- it will

[PATCH 4.5 024/200] dm cache metadata: fix cmd_read_lock() acquiring write lock

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Ahmed Samy commit 6545b60baaf880b0cd29a5e89dbe745a06027e89 upstream. Commit 9567366fefdd ("dm cache metadata: fix READ_LOCK macros and cleanup WRITE_LOCK macros") uses down_write() instead of

[PATCH 4.5 022/200] usb: gadget: f_fs: Fix use-after-free

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen commit 38740a5b87d53ceb89eb2c970150f6e94e00373a upstream. When using asynchronous read or write operations on the USB endpoints the issuer of the IO request is notified by

[PATCH 4.5 023/200] dm cache metadata: fix READ_LOCK macros and cleanup WRITE_LOCK macros

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit 9567366fefddeaea4ed1d713270535d93a3b3c76 upstream. The READ_LOCK macro was incorrectly returning -EINVAL if dm_bm_is_read_only() was true -- it will always be true once the

[PATCH 4.5 026/200] debugfs: Make automount point inodes permanently empty

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Seth Forshee commit 87243deb88671f70def4c52dfa7ca7830707bd31 upstream. Starting with 4.1 the tracing subsystem has its own filesystem which is automounted in the

[GIT PULL] drm-vc4-next-2016-05-02

This is my current series for vc4 for -next, replacing drm-vc4-next-2016-04-14 which I'd previously sent. This one has gamma ramp and render node support. The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca: Linux 4.6-rc1 (2016-03-26 16:03:24 -0700) are available in

[PATCH 4.5 026/200] debugfs: Make automount point inodes permanently empty

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Seth Forshee commit 87243deb88671f70def4c52dfa7ca7830707bd31 upstream. Starting with 4.1 the tracing subsystem has its own filesystem which is automounted in the tracing subdirectory of

[GIT PULL] drm-vc4-next-2016-05-02

This is my current series for vc4 for -next, replacing drm-vc4-next-2016-04-14 which I'd previously sent. This one has gamma ramp and render node support. The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca: Linux 4.6-rc1 (2016-03-26 16:03:24 -0700) are available in

[PATCH 4.5 029/200] dmaengine: hsu: correct residue calculation of active descriptor

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit a197f3c7d48c0c1f45076ea47533a76ba9b1a959 upstream. The commit f0579c8ceaf1 ("dmaengine: hsu: speed up residue calculation") speeded up

[PATCH 4.4 143/163] perf hists browser: Only offer symbol scripting when a symbol is under the cursor

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Namhyung Kim commit c221acb0f970d3b80d72c812cda19c121acf5d52 upstream. When this feature was introduced a check was made if there was a resolved symbol under the cursor,

[PATCH 4.5 027/200] dmaengine: dw: fix master selection

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit 3fe6409c23e2bee4b2b1b6d671d2da8daa15271c upstream. The commit 895005202987 ("dmaengine: dw: apply both HS interfaces and remove

[PATCH 4.5 029/200] dmaengine: hsu: correct residue calculation of active descriptor

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit a197f3c7d48c0c1f45076ea47533a76ba9b1a959 upstream. The commit f0579c8ceaf1 ("dmaengine: hsu: speed up residue calculation") speeded up calculation of the queued

[PATCH 4.4 143/163] perf hists browser: Only offer symbol scripting when a symbol is under the cursor

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Namhyung Kim commit c221acb0f970d3b80d72c812cda19c121acf5d52 upstream. When this feature was introduced a check was made if there was a resolved symbol under the cursor, it got lost in commit

[PATCH 4.5 027/200] dmaengine: dw: fix master selection

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit 3fe6409c23e2bee4b2b1b6d671d2da8daa15271c upstream. The commit 895005202987 ("dmaengine: dw: apply both HS interfaces and remove slave_id usage") cleaned up the code to

[PATCH 4.5 031/200] dmaengine: edma: Remove dynamic TPTC power management feature

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi commit 23f49fd2ea9bc8e1c8cff0126cd71b071ea9e91f upstream. The dynamic or on demand pm_runtime does not work correctly on am335x and am437x due to

[PATCH 4.5 031/200] dmaengine: edma: Remove dynamic TPTC power management feature

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi commit 23f49fd2ea9bc8e1c8cff0126cd71b071ea9e91f upstream. The dynamic or on demand pm_runtime does not work correctly on am335x and am437x due to interference with hwmod. Fall

[PATCH 4.5 028/200] dmaengine: hsu: correct use of channel status register

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit 4f4bc0abff79dc9d7ccbd3143adbf8ad1f4fe6ab upstream. There is a typo in documentation regarding to descriptor empty bit (DESCE) which is

[PATCH 4.5 033/200] mtd: nand: pxa3xx_nand: fix dmaengine initialization

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Robert Jarzmik commit 9097103f06332d099c5ab06d1e7f22f4bcaca6e2 upstream. When the driver is initialized in a pure device-tree platform, the driver's probe fails

[PATCH 4.5 032/200] dmaengine: pxa_dma: fix the maximum requestor line

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Robert Jarzmik commit 6bab1c6afdca0371cfa957079b36b78d12dd2cf5 upstream. The current number of requestor lines is limited to 31. This was an error of a previous commit,

[PATCH 4.5 028/200] dmaengine: hsu: correct use of channel status register

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit 4f4bc0abff79dc9d7ccbd3143adbf8ad1f4fe6ab upstream. There is a typo in documentation regarding to descriptor empty bit (DESCE) which is set to 1 when descriptor is empty.

[PATCH 4.5 033/200] mtd: nand: pxa3xx_nand: fix dmaengine initialization

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Robert Jarzmik commit 9097103f06332d099c5ab06d1e7f22f4bcaca6e2 upstream. When the driver is initialized in a pure device-tree platform, the driver's probe fails allocating the dma channel : [

[PATCH 4.5 032/200] dmaengine: pxa_dma: fix the maximum requestor line

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Robert Jarzmik commit 6bab1c6afdca0371cfa957079b36b78d12dd2cf5 upstream. The current number of requestor lines is limited to 31. This was an error of a previous commit, as this number is

[PATCH 4.5 030/200] dmaengine: omap-dma: Fix polled channel completion detection and handling

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi commit 689d3c5ecc9e2eac714d32ca152b72988bc2a67b upstream. When based on the CCR_ENABLE bit the channel is stopped we should not call omap_dma_callback(),

[PATCH 4.5 030/200] dmaengine: omap-dma: Fix polled channel completion detection and handling

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi commit 689d3c5ecc9e2eac714d32ca152b72988bc2a67b upstream. When based on the CCR_ENABLE bit the channel is stopped we should not call omap_dma_callback(), only change the return

[PATCH 4.5 040/200] ALSA: hda - Keep powering up ADCs on Cirrus codecs

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit de3df8a986b635082a1d94bae2c361d043c57106 upstream. Although one weird behavior about the input path (inconsistent D0/D3 switch) on Cirrus CS420x codecs was

[PATCH 4.5 040/200] ALSA: hda - Keep powering up ADCs on Cirrus codecs

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit de3df8a986b635082a1d94bae2c361d043c57106 upstream. Although one weird behavior about the input path (inconsistent D0/D3 switch) on Cirrus CS420x codecs was fixed in the

[PATCH 4.5 042/200] ALSA: pcxhr: Fix missing mutex unlock

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 67f3754b51f22b18c4820fb84062f658c30e8644 upstream. The commit [9bef72bdb26e: ALSA: pcxhr: Use nonatomic PCM ops] converted to non-atomic PCM ops, but

[PATCH 4.5 004/200] efi/arm64: Dont apply MEMBLOCK_NOMAP to UEFI memory map mapping

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 7cc8cbcf82d165dd658d89a7a287140948e76413 upstream. Commit 4dffbfc48d65 ("arm64/efi: mark UEFI reserved regions as MEMBLOCK_NOMAP") updated the

[PATCH 4.5 042/200] ALSA: pcxhr: Fix missing mutex unlock

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 67f3754b51f22b18c4820fb84062f658c30e8644 upstream. The commit [9bef72bdb26e: ALSA: pcxhr: Use nonatomic PCM ops] converted to non-atomic PCM ops, but shamelessly with an

[PATCH 4.5 004/200] efi/arm64: Dont apply MEMBLOCK_NOMAP to UEFI memory map mapping

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 7cc8cbcf82d165dd658d89a7a287140948e76413 upstream. Commit 4dffbfc48d65 ("arm64/efi: mark UEFI reserved regions as MEMBLOCK_NOMAP") updated the mapping logic of both the

[PATCH 4.5 005/200] x86/mce: Avoid using object after free in genpool

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit a3125494cff084b098c80bb36fbe2061ffed9d52 upstream. When we loop over all queued machine check error records to pass them to the registered notifiers we

[PATCH 4.5 043/200] ALSA: hda - Add dock support for ThinkPad X260

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Conrad Kostecki commit 037e119738120c1cdc460c6ae33871c3000531f3 upstream. Fixes audio output on a ThinkPad X260, when using Lenovo CES 2013 docking station series

[PATCH 4.5 044/200] ALSA: hda - Update BCLK also at hotplug for i915 HSW/BDW

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit bb03ed216370cb021f377f923471e56d1de3ff5d upstream. The recent bug report suggests that BCLK setup for i915 HSW/BDW needs to be updated at each HDMI hotplug,

[PATCH 4.5 043/200] ALSA: hda - Add dock support for ThinkPad X260

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Conrad Kostecki commit 037e119738120c1cdc460c6ae33871c3000531f3 upstream. Fixes audio output on a ThinkPad X260, when using Lenovo CES 2013 docking station series (basic, pro, ultra).

[PATCH 4.5 044/200] ALSA: hda - Update BCLK also at hotplug for i915 HSW/BDW

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit bb03ed216370cb021f377f923471e56d1de3ff5d upstream. The recent bug report suggests that BCLK setup for i915 HSW/BDW needs to be updated at each HDMI hotplug, not only at

[PATCH 4.5 005/200] x86/mce: Avoid using object after free in genpool

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit a3125494cff084b098c80bb36fbe2061ffed9d52 upstream. When we loop over all queued machine check error records to pass them to the registered notifiers we use

[PATCH 4.5 000/200] 4.5.3-stable review

This is the start of the stable review cycle for the 4.5.3 release. There are 200 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 Thu May 5 00:05:29 UTC 2016. Anything

[PATCH 4.5 000/200] 4.5.3-stable review

This is the start of the stable review cycle for the 4.5.3 release. There are 200 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 Thu May 5 00:05:29 UTC 2016. Anything

[PATCH 4.5 061/200] crypto: sha1-mb - use corrcet pointer while completing jobs

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Xiaodong Liu commit 0851561d9c965df086ef8a53f981f5f95a57c2c8 upstream. In sha_complete_job, incorrect mcryptd_hash_request_ctx pointer is used when check and complete

[PATCH 4.5 006/200] kvm: x86: do not leak guest xcr0 into host interrupt handlers

4.5-stable review patch. If anyone has any objections, please let me know. -- From: David Matlack commit fc5b7f3bf1e1414bd4e91db6918c85ace0c873a5 upstream. An interrupt handler that uses the fpu can kill a KVM VM, if it runs under the following

[PATCH 4.5 061/200] crypto: sha1-mb - use corrcet pointer while completing jobs

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Xiaodong Liu commit 0851561d9c965df086ef8a53f981f5f95a57c2c8 upstream. In sha_complete_job, incorrect mcryptd_hash_request_ctx pointer is used when check and complete other jobs. If the memory

[PATCH 4.5 006/200] kvm: x86: do not leak guest xcr0 into host interrupt handlers

4.5-stable review patch. If anyone has any objections, please let me know. -- From: David Matlack commit fc5b7f3bf1e1414bd4e91db6918c85ace0c873a5 upstream. An interrupt handler that uses the fpu can kill a KVM VM, if it runs under the following conditions: - the guest's xcr0

[PATCH 4.5 062/200] crypto: talitos - fix crash in talitos_cra_init()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Jonas Eymann commit 89d124cb61b39900959e2839ac06b6339b6a54cb upstream. Conversion of talitos driver to the new AEAD interface hasn't been properly tested. AEAD algorithms

[PATCH 4.5 062/200] crypto: talitos - fix crash in talitos_cra_init()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Jonas Eymann commit 89d124cb61b39900959e2839ac06b6339b6a54cb upstream. Conversion of talitos driver to the new AEAD interface hasn't been properly tested. AEAD algorithms crash in

[PATCH 4.5 060/200] crypto: ccp - Prevent information leakage on export

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Tom Lendacky commit f709b45ec461b548c41a00044dba1f1b572783bf upstream. Prevent information from leaking to userspace by doing a memset to 0 of the export state

[PATCH 4.5 056/200] s390/pci: add extra padding to function measurement block

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 9d89d9e61d361f3adb75e1aebe4bb367faf16cfa upstream. Newer machines might use a different (larger) format for function measurement blocks. To

[PATCH 4.5 060/200] crypto: ccp - Prevent information leakage on export

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Tom Lendacky commit f709b45ec461b548c41a00044dba1f1b572783bf upstream. Prevent information from leaking to userspace by doing a memset to 0 of the export state structure before setting the

[PATCH 4.5 056/200] s390/pci: add extra padding to function measurement block

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 9d89d9e61d361f3adb75e1aebe4bb367faf16cfa upstream. Newer machines might use a different (larger) format for function measurement blocks. To ensure that we comply with the

[PATCH 4.5 058/200] iwlwifi: mvm: fix memory leak in paging

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Matti Gottlieb commit 7fdf9663261cc77a516396fec82cee8a8ea07e76 upstream. Currently paging download buffer is freed during the the unloading of the opmode which

[PATCH 4.5 058/200] iwlwifi: mvm: fix memory leak in paging

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Matti Gottlieb commit 7fdf9663261cc77a516396fec82cee8a8ea07e76 upstream. Currently paging download buffer is freed during the the unloading of the opmode which happens when the driver is

[PATCH 4.5 057/200] iwlwifi: pcie: lower the debug level for RSA semaphore access

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit 9fc515bc9e735c10cd327f05c20f5ef69474188d upstream. IWL_INFO is not an error but still printed by default. "can't access the RSA semaphore

[PATCH 4.5 064/200] powerpc: scan_features() updates incorrect bits for REAL_LE

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Anton Blanchard commit 6997e57d693b07289694239e52a10d2f02c3a46f upstream. The REAL_LE feature entry in the ibm_pa_feature struct is missing an MMU feature value, meaning all

[PATCH 4.5 057/200] iwlwifi: pcie: lower the debug level for RSA semaphore access

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit 9fc515bc9e735c10cd327f05c20f5ef69474188d upstream. IWL_INFO is not an error but still printed by default. "can't access the RSA semaphore it is write protected" seems

[PATCH 4.5 064/200] powerpc: scan_features() updates incorrect bits for REAL_LE

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Anton Blanchard commit 6997e57d693b07289694239e52a10d2f02c3a46f upstream. The REAL_LE feature entry in the ibm_pa_feature struct is missing an MMU feature value, meaning all the remaining

[PATCH 4.5 047/200] futex: Acknowledge a new waiter in counter before plist

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Davidlohr Bueso commit fe1bce9e2107ba3a8faffe572483b6974201a0e6 upstream. Otherwise an incoming waker on the dest hash bucket can miss the waiter adding itself to the plist

[PATCH 4.5 047/200] futex: Acknowledge a new waiter in counter before plist

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Davidlohr Bueso commit fe1bce9e2107ba3a8faffe572483b6974201a0e6 upstream. Otherwise an incoming waker on the dest hash bucket can miss the waiter adding itself to the plist during the lockless

[PATCH 4.5 063/200] crypto: talitos - fix AEAD tcrypt tests

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Horia Geant? commit 340ff60ae93a5db2b2be6f38868df9a1293b6007 upstream. After conversion to new AEAD interface, tcrypt tests fail as follows: [...] [1.145414] alg:

[PATCH 4.5 063/200] crypto: talitos - fix AEAD tcrypt tests

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Horia Geant? commit 340ff60ae93a5db2b2be6f38868df9a1293b6007 upstream. After conversion to new AEAD interface, tcrypt tests fail as follows: [...] [1.145414] alg: aead: Test 1 failed on

[PATCH 4.5 066/200] powerpc: Update TM user feature bits in scan_features()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Anton Blanchard commit 4705e02498d6d5a7ab98dfee9595cd5e91db2017 upstream. We need to update the user TM feature bits (PPC_FEATURE2_HTM and PPC_FEATURE2_HTM) to mirror what we

[PATCH 4.5 065/200] powerpc: Update cpu_user_features2 in scan_features()

4.5-stable review patch. If anyone has any objections, please let me know. -- From: Anton Blanchard commit beff82374b259d726e2625ec6c518a5f2613f0ae upstream. scan_features() updates cpu_user_features but not cpu_user_features2. Amongst other things,

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