[PATCH 4.4 48/91] net: skb_needs_check() accepts CHECKSUM_NONE for tx

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 6e7bc478c9a006c701c14476ec9d389a484b4864 upstream. My recent change missed fact that UFO would perform a complete UDP checksum before segmenting in frags. In this case

[PATCH 4.4 07/91] drm/vmwgfx: Fix gcc-7.1.1 warning

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit fcfffdd8f98ac305285dca568b5065ef86be6458 upstream. The current code does not look correct, and the reason for it is probably lost. Since this now generates a compiler

[PATCH 4.4 08/91] drm/nouveau/bar/gf100: fix access to upper half of BAR2

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 38bcb208f60924a031b9f809f7cd252ea4a94e5f upstream. Bit 30 being set causes the upper half of BAR2 to stay in physical mode, mapped over the end of VRAM,

[PATCH 4.4 08/91] drm/nouveau/bar/gf100: fix access to upper half of BAR2

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 38bcb208f60924a031b9f809f7cd252ea4a94e5f upstream. Bit 30 being set causes the upper half of BAR2 to stay in physical mode, mapped over the end of VRAM, even when the rest of

[PATCH 4.4 53/91] tpm: Replace device number bitmap with IDR

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Berger commit 15516788e581eb32ec1c50e5f00aba3faf95d817 upstream. Replace the device number bitmap with IDR. Extend the number of devices we can create to

[PATCH 4.4 53/91] tpm: Replace device number bitmap with IDR

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Berger commit 15516788e581eb32ec1c50e5f00aba3faf95d817 upstream. Replace the device number bitmap with IDR. Extend the number of devices we can create to 64k. Since an IDR allows us to

[PATCH 4.4 47/91] pstore: Use dynamic spinlock initializer

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit e9a330c4289f2ba1ca4bf98c2b430ab165a8931b upstream. The per-prz spinlock should be using the dynamic initializer so that lockdep can correctly track it.

[PATCH 4.4 55/91] r8169: add support for RTL8168 series add-on card.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chun-Hao Lin [ Upstream commit 610c908773d30907c950ca3b2ee8ac4b2813537b ] This chip is the same as RTL8168, but its device id is 0x8161. Signed-off-by: Chun-Hao Lin

[PATCH 4.4 47/91] pstore: Use dynamic spinlock initializer

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit e9a330c4289f2ba1ca4bf98c2b430ab165a8931b upstream. The per-prz spinlock should be using the dynamic initializer so that lockdep can correctly track it. Without this, under

[PATCH 4.4 55/91] r8169: add support for RTL8168 series add-on card.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chun-Hao Lin [ Upstream commit 610c908773d30907c950ca3b2ee8ac4b2813537b ] This chip is the same as RTL8168, but its device id is 0x8161. Signed-off-by: Chun-Hao Lin Signed-off-by: David S.

[PATCH 4.4 54/91] x86/mce/AMD: Make the init code more robust

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner [ Upstream commit 0dad3a3014a0b9e72521ff44f17e0054f43dcdea ] If mce_device_init() fails then the mce device pointer is NULL and the AMD mce code happily

[PATCH 4.4 54/91] x86/mce/AMD: Make the init code more robust

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner [ Upstream commit 0dad3a3014a0b9e72521ff44f17e0054f43dcdea ] If mce_device_init() fails then the mce device pointer is NULL and the AMD mce code happily dereferences it. Add

[PATCH 4.4 58/91] net/mlx4: Remove BUG_ON from ICM allocation routine

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky [ Upstream commit c1d5f8ff80ea84768f5fae1ca9d1abfbb5e6bbaa ] This patch removes BUG_ON() macro from mlx4_alloc_icm_coherent() by checking DMA address

[PATCH 4.4 58/91] net/mlx4: Remove BUG_ON from ICM allocation routine

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky [ Upstream commit c1d5f8ff80ea84768f5fae1ca9d1abfbb5e6bbaa ] This patch removes BUG_ON() macro from mlx4_alloc_icm_coherent() by checking DMA address alignment in advance and

[PATCH 4.4 39/91] ipmi/watchdog: fix watchdog timeout set on reboot

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Valentin Vidic commit 860f01e96981a68553f3ca49f574ff14fe955e72 upstream. systemd by default starts watchdog on reboot and sets the timer to ShutdownWatchdogSec=10min.

[PATCH 4.4 39/91] ipmi/watchdog: fix watchdog timeout set on reboot

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Valentin Vidic commit 860f01e96981a68553f3ca49f574ff14fe955e72 upstream. systemd by default starts watchdog on reboot and sets the timer to ShutdownWatchdogSec=10min. Reboot handler in

[PATCH 4.4 52/91] tpm: fix a kernel memory leak in tpm-sysfs.c

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jarkko Sakkinen commit 13b47cfcfc60495cde216eef4c01040d76174cbe upstream. While cleaning up sysfs callback that prints EK we discovered a kernel memory leak.

[PATCH 4.4 52/91] tpm: fix a kernel memory leak in tpm-sysfs.c

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jarkko Sakkinen commit 13b47cfcfc60495cde216eef4c01040d76174cbe upstream. While cleaning up sysfs callback that prints EK we discovered a kernel memory leak. This commit fixes the issue by

[PATCH 4.4 59/91] drm/msm: Ensure that the hardware write pointer is valid

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jordan Crouse [ Upstream commit 88b333b0ed790f9433ff542b163bf972953b74d3 ] Currently the value written to CP_RB_WPTR is calculated on the fly as (rb->next -

[PATCH 4.4 59/91] drm/msm: Ensure that the hardware write pointer is valid

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jordan Crouse [ Upstream commit 88b333b0ed790f9433ff542b163bf972953b74d3 ] Currently the value written to CP_RB_WPTR is calculated on the fly as (rb->next - rb->start). But as the code is

[PATCH 4.4 57/91] ipv6: Should use consistent conditional judgement for ip6 fragment between __ip6_append_data and ip6_finish_output

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Zheng Li [ Upstream commit e4c5e13aa45c23692e4acf56f0b3533f328199b2 ] There is an inconsistent conditional judgement between __ip6_append_data and ip6_finish_output

[PATCH 4.4 60/91] drm/msm: Verify that MSM_SUBMIT_BO_FLAGS are set

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jordan Crouse [ Upstream commit a6cb3b864b21b7345f824a4faa12b723c8aaf099 ] For every submission buffer object one of MSM_SUBMIT_BO_WRITE and MSM_SUBMIT_BO_READ must be

[PATCH 4.4 62/91] irqchip/keystone: Fix "scheduling while atomic" on rt

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "Strashko, Grygorii" [ Upstream commit 2f884e6e688a0deb69e6c9552e51aef8b7e3f5f1 ] The below call chain generates "scheduling while atomic" backtrace and causes

[PATCH 4.4 57/91] ipv6: Should use consistent conditional judgement for ip6 fragment between __ip6_append_data and ip6_finish_output

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Zheng Li [ Upstream commit e4c5e13aa45c23692e4acf56f0b3533f328199b2 ] There is an inconsistent conditional judgement between __ip6_append_data and ip6_finish_output functions, the variable

[PATCH 4.4 60/91] drm/msm: Verify that MSM_SUBMIT_BO_FLAGS are set

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jordan Crouse [ Upstream commit a6cb3b864b21b7345f824a4faa12b723c8aaf099 ] For every submission buffer object one of MSM_SUBMIT_BO_WRITE and MSM_SUBMIT_BO_READ must be set (and nothing else).

[PATCH 4.4 62/91] irqchip/keystone: Fix "scheduling while atomic" on rt

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "Strashko, Grygorii" [ Upstream commit 2f884e6e688a0deb69e6c9552e51aef8b7e3f5f1 ] The below call chain generates "scheduling while atomic" backtrace and causes system crash when Keystone 2

[PATCH 4.4 61/91] vfio-pci: use 32-bit comparisons for register address for gcc-4.5

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit 45e869714489431625c569d21fc952428d761476 ] Using ancient compilers (gcc-4.5 or older) on ARM, we get a link failure with the vfio-pci driver:

[PATCH 4.4 61/91] vfio-pci: use 32-bit comparisons for register address for gcc-4.5

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit 45e869714489431625c569d21fc952428d761476 ] Using ancient compilers (gcc-4.5 or older) on ARM, we get a link failure with the vfio-pci driver: ERROR:

[PATCH 4.4 63/91] ASoC: tlv320aic3x: Mark the RESET register as volatile

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi [ Upstream commit 63c3194b82530bd71fd49db84eb7ab656b8d404a ] The RESET register only have one self clearing bit and it should not be cached. If it is

[PATCH 4.4 63/91] ASoC: tlv320aic3x: Mark the RESET register as volatile

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi [ Upstream commit 63c3194b82530bd71fd49db84eb7ab656b8d404a ] The RESET register only have one self clearing bit and it should not be cached. If it is cached, when we sync the

[PATCH 4.4 66/91] irqchip/mxs: Enable SKIP_SET_WAKE and MASK_ON_SUSPEND

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Wahren [ Upstream commit 88e20c74ee020f9e0c99dfce0dd9aa61c3f0cca0 ] The ICOLL controller doesn't provide any facility to configure the wakeup sources. That's

[PATCH 4.4 66/91] irqchip/mxs: Enable SKIP_SET_WAKE and MASK_ON_SUSPEND

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Wahren [ Upstream commit 88e20c74ee020f9e0c99dfce0dd9aa61c3f0cca0 ] The ICOLL controller doesn't provide any facility to configure the wakeup sources. That's the reason why this

[PATCH 4.4 65/91] ASoC: nau8825: fix invalid configuration in Pre-Scalar of FLL

4.4-stable review patch. If anyone has any objections, please let me know. -- From: John Hsu [ Upstream commit a1792cda51300e15b03549cccf0b09f3be82e697 ] The clk_ref_div is not configured in the correct position of the register. The patch fixes that

[PATCH 4.4 64/91] spi: dw: Make debugfs name unique between instances

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Phil Reid [ Upstream commit 13288bdf4adbaa6bd1267f10044c1bc25d90ce7f ] Some system have multiple dw devices. Currently the driver uses a fixed name for the debugfs

[PATCH 4.4 65/91] ASoC: nau8825: fix invalid configuration in Pre-Scalar of FLL

4.4-stable review patch. If anyone has any objections, please let me know. -- From: John Hsu [ Upstream commit a1792cda51300e15b03549cccf0b09f3be82e697 ] The clk_ref_div is not configured in the correct position of the register. The patch fixes that clk_ref_div, Pre-Scalar,

[PATCH 4.4 64/91] spi: dw: Make debugfs name unique between instances

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Phil Reid [ Upstream commit 13288bdf4adbaa6bd1267f10044c1bc25d90ce7f ] Some system have multiple dw devices. Currently the driver uses a fixed name for the debugfs dir. Append dev name to the

[PATCH 4.4 67/91] openrisc: Add _text symbol to fix ksym build error

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stafford Horne [ Upstream commit 086cc1c31a0ec075dac02425367c871bb65bc2c9 ] The build robot reports: .tmp_kallsyms1.o: In function `kallsyms_relative_base': >>

[PATCH 4.4 67/91] openrisc: Add _text symbol to fix ksym build error

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stafford Horne [ Upstream commit 086cc1c31a0ec075dac02425367c871bb65bc2c9 ] The build robot reports: .tmp_kallsyms1.o: In function `kallsyms_relative_base': >> (.rodata+0x8a18): undefined

[PATCH 4.4 68/91] dmaengine: ioatdma: Add Skylake PCI Dev ID

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dave Jiang [ Upstream commit 1594c18fd297a8edcc72bc4b161f3f52603ebb92 ] Adding Skylake Xeon PCI device ids for ioatdma and related bits. Signed-off-by: Dave Jiang

[PATCH 4.4 40/91] dentry name snapshots

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 49d31c2f389acfe83417083e1208422b4091cd9e upstream. take_dentry_name_snapshot() takes a safe snapshot of dentry name; if the name is a short one, it gets

[PATCH 4.4 68/91] dmaengine: ioatdma: Add Skylake PCI Dev ID

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dave Jiang [ Upstream commit 1594c18fd297a8edcc72bc4b161f3f52603ebb92 ] Adding Skylake Xeon PCI device ids for ioatdma and related bits. Signed-off-by: Dave Jiang Signed-off-by: Vinod Koul

[PATCH 4.4 40/91] dentry name snapshots

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 49d31c2f389acfe83417083e1208422b4091cd9e upstream. take_dentry_name_snapshot() takes a safe snapshot of dentry name; if the name is a short one, it gets copied into

[PATCH 4.4 41/91] [media] v4l: s5c73m3: fix negation operator

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andrzej Hajda commit a2370ba2752538404e363346b339869c9973aeac upstream. Bool values should be negated using logical operators. Using bitwise operators results in

[PATCH 4.4 41/91] [media] v4l: s5c73m3: fix negation operator

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andrzej Hajda commit a2370ba2752538404e363346b339869c9973aeac upstream. Bool values should be negated using logical operators. Using bitwise operators results in unexpected and possibly

[PATCH 4.4 70/91] dmaengine: ti-dma-crossbar: Add some of_node_put() in error path.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 75bdc7f31a3a6e9a12e218b31a44a1f54a91554c ] Add some missing 'of_node_put()' in early exit error path. Signed-off-by:

[PATCH 4.4 70/91] dmaengine: ti-dma-crossbar: Add some of_node_put() in error path.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 75bdc7f31a3a6e9a12e218b31a44a1f54a91554c ] Add some missing 'of_node_put()' in early exit error path. Signed-off-by: Christophe JAILLET Signed-off-by:

[PATCH 4.4 69/91] dmaengine: ioatdma: workaround SKX ioatdma version

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dave Jiang [ Upstream commit 34a31f0af84158955a9747fb5c6712da5bbb5331 ] The Skylake ioatdma is technically CBDMA 3.2+ and contains the same hardware bits with some

[PATCH 4.4 69/91] dmaengine: ioatdma: workaround SKX ioatdma version

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dave Jiang [ Upstream commit 34a31f0af84158955a9747fb5c6712da5bbb5331 ] The Skylake ioatdma is technically CBDMA 3.2+ and contains the same hardware bits with some additional 3.3 features,

[PATCH 4.4 43/91] /proc/iomem: only expose physical resource addresses to privileged users

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 51d7b120418e99d6b3bf8df9eb3cc31e8171dee4 upstream. In commit c4004b02f8e5b ("x86: remove the kernel code/data/bss resources from

[PATCH 4.4 42/91] Make file credentials available to the seqfile interfaces

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 34dbbcdbf63360661ff7bda6c5f52f99ac515f92 upstream. A lot of seqfile users seem to be using things like %pK that uses the credentials of the

[PATCH 4.4 43/91] /proc/iomem: only expose physical resource addresses to privileged users

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 51d7b120418e99d6b3bf8df9eb3cc31e8171dee4 upstream. In commit c4004b02f8e5b ("x86: remove the kernel code/data/bss resources from /proc/iomem") I was hoping to remove the

[PATCH 4.4 42/91] Make file credentials available to the seqfile interfaces

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 34dbbcdbf63360661ff7bda6c5f52f99ac515f92 upstream. A lot of seqfile users seem to be using things like %pK that uses the credentials of the current process, but that is

[PATCH 4.4 44/91] vlan: Propagate MAC address to VLANs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mike Manning commit 308453aa9156a3b8ee382c0949befb507a32b0c1 upstream. The MAC address of the physical interface is only copied to the VLAN when it is first created,

[PATCH 4.4 44/91] vlan: Propagate MAC address to VLANs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mike Manning commit 308453aa9156a3b8ee382c0949befb507a32b0c1 upstream. The MAC address of the physical interface is only copied to the VLAN when it is first created, resulting in an

[PATCH 4.4 71/91] ARM64: zynqmp: Fix W=1 dtc 1.4 warnings

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michal Simek [ Upstream commit 4ea2a6be9565455f152c12f80222af1582ede0c7 ] The patch removes these warnings reported by dtc 1.4: Warning (unit_address_vs_reg): Node

[PATCH 4.4 46/91] pstore: Correctly initialize spinlock and flags

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 76d5692a58031696e282384cbd893832bc92bd76 upstream. The ram backend wasn't always initializing its spinlock correctly. Since it was coming from kzalloc

[PATCH 4.4 71/91] ARM64: zynqmp: Fix W=1 dtc 1.4 warnings

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michal Simek [ Upstream commit 4ea2a6be9565455f152c12f80222af1582ede0c7 ] The patch removes these warnings reported by dtc 1.4: Warning (unit_address_vs_reg): Node /amba_apu has a reg or

[PATCH 4.4 46/91] pstore: Correctly initialize spinlock and flags

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 76d5692a58031696e282384cbd893832bc92bd76 upstream. The ram backend wasn't always initializing its spinlock correctly. Since it was coming from kzalloc memory, though, it was

[PATCH 4.4 45/91] pstore: Allow prz to control need for locking

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Joel Fernandes commit 663deb47880f2283809669563c5a52ac7c6aef1a upstream. In preparation of not locking at all for certain buffers depending on if there's contention, make

Re: [PATCH v2 4/5] xfs: introduce XFS_DIFLAG2_IOMAP_IMMUTABLE

On Fri, Aug 04, 2017 at 01:33:12PM -0700, Darrick J. Wong wrote: > On Thu, Aug 03, 2017 at 07:28:30PM -0700, Dan Williams wrote: > > Add an on-disk inode flag to record the state of the S_IOMAP_IMMUTABLE > > in-memory vfs inode flags. This allows the protections against reflink > > and hole punch

[PATCH 4.4 45/91] pstore: Allow prz to control need for locking

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Joel Fernandes commit 663deb47880f2283809669563c5a52ac7c6aef1a upstream. In preparation of not locking at all for certain buffers depending on if there's contention, make locking optional

Re: [PATCH v2 4/5] xfs: introduce XFS_DIFLAG2_IOMAP_IMMUTABLE

On Fri, Aug 04, 2017 at 01:33:12PM -0700, Darrick J. Wong wrote: > On Thu, Aug 03, 2017 at 07:28:30PM -0700, Dan Williams wrote: > > Add an on-disk inode flag to record the state of the S_IOMAP_IMMUTABLE > > in-memory vfs inode flags. This allows the protections against reflink > > and hole punch

[PATCH 4.4 37/91] RDMA/uverbs: Fix the check for port number

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ismail, Mustafa commit 5a7a88f1b488e4ee49eb3d5b82612d4d9ffdf2c3 upstream. The port number is only valid if IB_QP_PORT is set in the mask. So only check port number if

[PATCH 4.4 37/91] RDMA/uverbs: Fix the check for port number

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ismail, Mustafa commit 5a7a88f1b488e4ee49eb3d5b82612d4d9ffdf2c3 upstream. The port number is only valid if IB_QP_PORT is set in the mask. So only check port number if it is valid to prevent

[PATCH 4.4 87/91] HID: ignore Petzl USB headlamp

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Kosina [ Upstream commit 08f9572671c8047e7234cbf150869aa3c3d59a97 ] This headlamp contains a dummy HID descriptor which pretends to be a mouse-like device, but can't be

[PATCH 4.4 87/91] HID: ignore Petzl USB headlamp

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Kosina [ Upstream commit 08f9572671c8047e7234cbf150869aa3c3d59a97 ] This headlamp contains a dummy HID descriptor which pretends to be a mouse-like device, but can't be used as a mouse

[PATCH 4.4 77/91] tools lib traceevent: Fix prev/next_prio for deadline tasks

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Bristot de Oliveira [ Upstream commit 074859184d770824f4437dca716bdeb625ae8b1c ] Currently, the sched:sched_switch tracepoint reports deadline tasks with priority

[PATCH 4.4 77/91] tools lib traceevent: Fix prev/next_prio for deadline tasks

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Bristot de Oliveira [ Upstream commit 074859184d770824f4437dca716bdeb625ae8b1c ] Currently, the sched:sched_switch tracepoint reports deadline tasks with priority -1. But when reading

[PATCH 4.4 74/91] ACPI / scan: Prefer devices without _HID/_CID for _ADR matching

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "Rafael J. Wysocki" [ Upstream commit c2a6bbaf0c5f90463a7011a295bbdb7e33c80b51 ] The way acpi_find_child_device() works currently is that, if there are two (or

[PATCH 4.4 74/91] ACPI / scan: Prefer devices without _HID/_CID for _ADR matching

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "Rafael J. Wysocki" [ Upstream commit c2a6bbaf0c5f90463a7011a295bbdb7e33c80b51 ] The way acpi_find_child_device() works currently is that, if there are two (or more) devices with the same

[PATCH 4.4 86/91] ALSA: usb-audio: test EP_FLAG_RUNNING at urb completion

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ioan-Adrian Ratiu [ Upstream commit 13a6c8328e6056932dc680e447d4c5e8ad9add17 ] Testing EP_FLAG_RUNNING in snd_complete_urb() before running the completion logic allows us to

[PATCH 4.4 86/91] ALSA: usb-audio: test EP_FLAG_RUNNING at urb completion

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ioan-Adrian Ratiu [ Upstream commit 13a6c8328e6056932dc680e447d4c5e8ad9add17 ] Testing EP_FLAG_RUNNING in snd_complete_urb() before running the completion logic allows us to save a few cpu

[PATCH 4.4 88/91] scsi: fnic: Avoid sending reset to firmware when another reset is in progress

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Satish Kharat [ Upstream commit 9698b6f473555a722bf81a3371998427d5d27bde ] This fix is to avoid calling fnic_fw_reset_handler through fnic_host_reset when a finc reset is

[PATCH 4.4 88/91] scsi: fnic: Avoid sending reset to firmware when another reset is in progress

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Satish Kharat [ Upstream commit 9698b6f473555a722bf81a3371998427d5d27bde ] This fix is to avoid calling fnic_fw_reset_handler through fnic_host_reset when a finc reset is alreay in progress.

[PATCH 4.4 73/91] ARM: s3c2410_defconfig: Fix invalid values for NF_CT_PROTO_*

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski [ Upstream commit 3ef01c968fbfb21c2f16281445d30a865ee4412c ] NF_CT_PROTO_DCCP/SCTP/UDPLITE were switched from tristate to boolean so defconfig needs to be

Re: [PATCH 0/2] mm,fork,security: introduce MADV_WIPEONFORK

On Fri, Aug 04, 2017 at 03:07:28PM -0400, r...@redhat.com wrote: > [resend because half the recipients got dropped due to IPv6 firewall issues] > > Introduce MADV_WIPEONFORK semantics, which result in a VMA being > empty in the child process after fork. This differs from MADV_DONTFORK > in one

[PATCH 4.4 73/91] ARM: s3c2410_defconfig: Fix invalid values for NF_CT_PROTO_*

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski [ Upstream commit 3ef01c968fbfb21c2f16281445d30a865ee4412c ] NF_CT_PROTO_DCCP/SCTP/UDPLITE were switched from tristate to boolean so defconfig needs to be adjusted to

Re: [PATCH 0/2] mm,fork,security: introduce MADV_WIPEONFORK

On Fri, Aug 04, 2017 at 03:07:28PM -0400, r...@redhat.com wrote: > [resend because half the recipients got dropped due to IPv6 firewall issues] > > Introduce MADV_WIPEONFORK semantics, which result in a VMA being > empty in the child process after fork. This differs from MADV_DONTFORK > in one

[PATCH 4.4 89/91] scsi: snic: Return error code on memory allocation failure

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Burak Ok [ Upstream commit 0371adcdaca92912baaa3256ed13e058a016e62d ] If a call to mempool_create_slab_pool() in snic_probe() returns NULL, return -ENOMEM to indicate

[PATCH 4.4 89/91] scsi: snic: Return error code on memory allocation failure

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Burak Ok [ Upstream commit 0371adcdaca92912baaa3256ed13e058a016e62d ] If a call to mempool_create_slab_pool() in snic_probe() returns NULL, return -ENOMEM to indicate failure.

[PATCH 4.4 90/91] ASoC: dpcm: Avoid putting stream state to STOP when FE stream is paused

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Patrick Lai [ Upstream commit 9f169b9f52a4afccdab7a7d2311b0c53a78a1e6b ] When multiple front-ends are using the same back-end, putting state of a front-end to STOP state

[PATCH 4.4 90/91] ASoC: dpcm: Avoid putting stream state to STOP when FE stream is paused

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Patrick Lai [ Upstream commit 9f169b9f52a4afccdab7a7d2311b0c53a78a1e6b ] When multiple front-ends are using the same back-end, putting state of a front-end to STOP state upon receiving pause

Re: [PATCH v2 2/5] fs, xfs: introduce FALLOC_FL_SEAL_BLOCK_MAP

On Fri, Aug 4, 2017 at 4:31 PM, Dave Chinner wrote: > On Thu, Aug 03, 2017 at 07:28:17PM -0700, Dan Williams wrote: >> diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c >> index fe0f8f7f4bb7..46d8eb9e19fc 100644 >> --- a/fs/xfs/xfs_bmap_util.c >> +++

Re: [PATCH v2 2/5] fs, xfs: introduce FALLOC_FL_SEAL_BLOCK_MAP

On Fri, Aug 4, 2017 at 4:31 PM, Dave Chinner wrote: > On Thu, Aug 03, 2017 at 07:28:17PM -0700, Dan Williams wrote: >> diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c >> index fe0f8f7f4bb7..46d8eb9e19fc 100644 >> --- a/fs/xfs/xfs_bmap_util.c >> +++ b/fs/xfs/xfs_bmap_util.c >> @@

[PATCH 4.4 78/91] xfrm: Dont use sk_family for socket policy lookups

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert commit 4c86d77743a54fb2d8a4d18a037a074c892bb3be upstream. On IPv4-mapped IPv6 addresses sk_family is AF_INET6, but the flow informations are

[PATCH 4.4 91/91] Btrfs: use down_read_nested to make lockdep silent

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo [ Upstream commit e321f8a801d7b4c40da8005257b05b9c2b51b072 ] If @block_group is not @used_bg, it'll try to get @used_bg's lock without droping @block_group 's

[PATCH 4.4 91/91] Btrfs: use down_read_nested to make lockdep silent

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo [ Upstream commit e321f8a801d7b4c40da8005257b05b9c2b51b072 ] If @block_group is not @used_bg, it'll try to get @used_bg's lock without droping @block_group 's lock and lockdep has

[PATCH 4.4 78/91] xfrm: Dont use sk_family for socket policy lookups

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert commit 4c86d77743a54fb2d8a4d18a037a074c892bb3be upstream. On IPv4-mapped IPv6 addresses sk_family is AF_INET6, but the flow informations are created based on AF_INET. So the

[PATCH 4.4 81/91] video: fbdev: cobalt_lcdfb: Handle return NULL error from devm_ioremap

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arvind Yadav [ Upstream commit 4dcd19bfabaee8f9f4bcf203afba09b98ccbaf76 ] Here, If devm_ioremap will fail. It will return NULL. Kernel can run into a NULL-pointer

[PATCH 4.4 81/91] video: fbdev: cobalt_lcdfb: Handle return NULL error from devm_ioremap

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arvind Yadav [ Upstream commit 4dcd19bfabaee8f9f4bcf203afba09b98ccbaf76 ] Here, If devm_ioremap will fail. It will return NULL. Kernel can run into a NULL-pointer dereference. This error

[PATCH 4.4 80/91] perf symbols: Robustify reading of build-id from sysfs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnaldo Carvalho de Melo [ Upstream commit 7934c98a6e04028eb34c1293bfb5a6b0ab630b66 ] Markus reported that perf segfaults when reading /sys/kernel/notes from a kernel linked

[PATCH 4.4 75/91] usb: gadget: Fix copy/pasted error message

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Lechner [ Upstream commit 43aef5c2ca90535b3227e97e71604291875444ed ] This fixes an error message that was probably copied and pasted. The same message is used for

[PATCH 4.4 80/91] perf symbols: Robustify reading of build-id from sysfs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnaldo Carvalho de Melo [ Upstream commit 7934c98a6e04028eb34c1293bfb5a6b0ab630b66 ] Markus reported that perf segfaults when reading /sys/kernel/notes from a kernel linked with GNU gold,

[PATCH 4.4 75/91] usb: gadget: Fix copy/pasted error message

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Lechner [ Upstream commit 43aef5c2ca90535b3227e97e71604291875444ed ] This fixes an error message that was probably copied and pasted. The same message is used for both the in and out

[PATCH 4.4 82/91] vfio-pci: Handle error from pci_iomap

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arvind Yadav [ Upstream commit e19f32da5ded958238eac1bbe001192acef191a2 ] Here, pci_iomap can fail, handle this case release selected pci regions and return

[PATCH 4.4 79/91] perf tools: Install tools/lib/traceevent plugins with install-bin

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnaldo Carvalho de Melo [ Upstream commit 30a9c6444810429aa2b7cbfbd453ce339baaadbf ] Those are binaries as well, so should be installed by: make -C tools/perf

[PATCH 4.4 82/91] vfio-pci: Handle error from pci_iomap

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arvind Yadav [ Upstream commit e19f32da5ded958238eac1bbe001192acef191a2 ] Here, pci_iomap can fail, handle this case release selected pci regions and return -ENOMEM. Signed-off-by: Arvind

[PATCH 4.4 79/91] perf tools: Install tools/lib/traceevent plugins with install-bin

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnaldo Carvalho de Melo [ Upstream commit 30a9c6444810429aa2b7cbfbd453ce339baaadbf ] Those are binaries as well, so should be installed by: make -C tools/perf install-bin' too. Cc:

[PATCH 4.4 84/91] nvmem: imx-ocotp: Fix wrong register size

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Schultz [ Upstream commit 14ba972842f9e84e6d3264bc0302101b8a792288 ] All i.MX6 SoCs have an OCOTP Controller with 4kbit fuses. The i.MX6SL is an exception and has

[PATCH 4.4 84/91] nvmem: imx-ocotp: Fix wrong register size

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Schultz [ Upstream commit 14ba972842f9e84e6d3264bc0302101b8a792288 ] All i.MX6 SoCs have an OCOTP Controller with 4kbit fuses. The i.MX6SL is an exception and has only 2kbit fuses. In

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