[PATCH 4.9 001/152] ppdev: check before attaching port

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sudip Mukherjee commit dd5c472a60e43549d789a17a8444513eec64bd7e upstream. After parport starts using the device model, all pardevice drivers should decide in their match_port callback function

[PATCH 4.9 014/152] iio: bmg160: reset chip when probing

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Quentin Schulz commit 4bdc9029685ac03be50b320b29691766d2326c2b upstream. The gyroscope chip might need to be reset to be used. Without the chip being reset, the driver stopped at the first

[PATCH 4.9 010/152] staging: android: ashmem: lseek failed due to no FMODE_LSEEK.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shuxiao Zhang commit 97fbfef6bd597888485b653175fb846c6998b60c upstream. vfs_llseek will check whether the file mode has FMODE_LSEEK, no return failure. But ashmem can

[PATCH 4.9 013/152] kvm: arm/arm64: Fix locking for kvm_free_stage2_pgd

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Suzuki K Poulose commit 8b3405e345b5a098101b0c31b264c812bba045d9 upstream. In kvm_free_stage2_pgd() we don't hold the kvm->mmu_lock while calling unmap_stage2_range()

[PATCH 4.9 010/152] staging: android: ashmem: lseek failed due to no FMODE_LSEEK.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shuxiao Zhang commit 97fbfef6bd597888485b653175fb846c6998b60c upstream. vfs_llseek will check whether the file mode has FMODE_LSEEK, no return failure. But ashmem can be lseek, so add

[PATCH 4.9 013/152] kvm: arm/arm64: Fix locking for kvm_free_stage2_pgd

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Suzuki K Poulose commit 8b3405e345b5a098101b0c31b264c812bba045d9 upstream. In kvm_free_stage2_pgd() we don't hold the kvm->mmu_lock while calling unmap_stage2_range() on the entire memory

[PATCH 4.9 015/152] arm64: mm: unaligned access by user-land should be received as SIGBUS

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Victor Kamensky commit 09a6adf53d42ca3088fa3fb41f40b768efc711ed upstream. After 52d7523 (arm64: mm: allow the kernel to handle alignment faults on user accesses) commit

[PATCH 4.9 015/152] arm64: mm: unaligned access by user-land should be received as SIGBUS

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Victor Kamensky commit 09a6adf53d42ca3088fa3fb41f40b768efc711ed upstream. After 52d7523 (arm64: mm: allow the kernel to handle alignment faults on user accesses) commit user-land accesses that

[PATCH 4.9 016/152] cfg80211: check rdev resume callback only for registered wiphy

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arend Van Spriel commit b3ef5520c1eabb56064474043c7c55a1a65b8708 upstream. We got the following use-after-free KASAN report: BUG: KASAN: use-after-free in

[PATCH 4.9 016/152] cfg80211: check rdev resume callback only for registered wiphy

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arend Van Spriel commit b3ef5520c1eabb56064474043c7c55a1a65b8708 upstream. We got the following use-after-free KASAN report: BUG: KASAN: use-after-free in wiphy_resume+0x591/0x5a0 [cfg80211]

Re: WARN @lib/refcount.c:128 during hot unplug of I/O adapter.

On 04/06/2017 09:04 PM, Michael Ellerman wrote: > Tyrel Datwyler writes: > >> On 04/06/2017 03:27 AM, Sachin Sant wrote: >>> On a POWER8 LPAR running 4.11.0-rc5, a hot unplug operation on >>> any I/O adapter results in the following warning >>> >>> This problem has

Re: [PATCH 08/16] irqchip: Add driver for Cirrus Logic Madera codecs

On Wed, Apr 05, 2017 at 11:07:56AM +0100, Richard Fitzgerald wrote: > The Cirrus Logic Madera codecs (Cirrus Logic CS47L35/85/90/91 and WM1840) > are highly complex devices containing up to 7 programmable DSPs and many > other internal sources of interrupts plus a number of GPIOs that can be >

Re: WARN @lib/refcount.c:128 during hot unplug of I/O adapter.

On 04/06/2017 09:04 PM, Michael Ellerman wrote: > Tyrel Datwyler writes: > >> On 04/06/2017 03:27 AM, Sachin Sant wrote: >>> On a POWER8 LPAR running 4.11.0-rc5, a hot unplug operation on >>> any I/O adapter results in the following warning >>> >>> This problem has been in the code for some time

Re: [PATCH 08/16] irqchip: Add driver for Cirrus Logic Madera codecs

On Wed, Apr 05, 2017 at 11:07:56AM +0100, Richard Fitzgerald wrote: > The Cirrus Logic Madera codecs (Cirrus Logic CS47L35/85/90/91 and WM1840) > are highly complex devices containing up to 7 programmable DSPs and many > other internal sources of interrupts plus a number of GPIOs that can be >

Re: [PATCH -v2 0/9] mm: make movable onlining suck less

On Mon 10-04-17 12:35:53, Jerome Glisse wrote: > On Mon, Apr 10, 2017 at 01:03:42PM +0200, Michal Hocko wrote: > > Hi, > > The last version of this series has been posted here [1]. It has seen > > some more serious testing (thanks to Reza Arbab) and fixes for the found > > issues. I have also

Re: [PATCH -v2 0/9] mm: make movable onlining suck less

On Mon 10-04-17 12:35:53, Jerome Glisse wrote: > On Mon, Apr 10, 2017 at 01:03:42PM +0200, Michal Hocko wrote: > > Hi, > > The last version of this series has been posted here [1]. It has seen > > some more serious testing (thanks to Reza Arbab) and fixes for the found > > issues. I have also

[PATCH 4.9 017/152] Reset TreeId to zero on SMB2 TREE_CONNECT

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jan-Marek Glogowski commit 806a28efe9b78ffae5e2757e1ee924b8e50c08ab upstream. Currently the cifs module breaks the CIFS specs on reconnect as described in

[PATCH 4.9 017/152] Reset TreeId to zero on SMB2 TREE_CONNECT

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jan-Marek Glogowski commit 806a28efe9b78ffae5e2757e1ee924b8e50c08ab upstream. Currently the cifs module breaks the CIFS specs on reconnect as described in

[PATCH 4.9 020/152] dm verity fec: limit error correction recursion

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sami Tolvanen commit f1a880a93baaadb14c10a348fd199f1cdb6bcccd upstream. If the hash tree itself is sufficiently corrupt in addition to data blocks, it's possible for

[PATCH 4.9 019/152] ptrace: fix PTRACE_LISTEN race corrupting task->state

4.9-stable review patch. If anyone has any objections, please let me know. -- From: bseg...@google.com commit 5402e97af667e35e54177af8f6575518bf251d51 upstream. In PT_SEIZED + LISTEN mode STOP/CONT signals cause a wakeup against __TASK_TRACED. If this

[PATCH 4.9 020/152] dm verity fec: limit error correction recursion

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sami Tolvanen commit f1a880a93baaadb14c10a348fd199f1cdb6bcccd upstream. If the hash tree itself is sufficiently corrupt in addition to data blocks, it's possible for error correction to end up

[PATCH 4.9 019/152] ptrace: fix PTRACE_LISTEN race corrupting task->state

4.9-stable review patch. If anyone has any objections, please let me know. -- From: bseg...@google.com commit 5402e97af667e35e54177af8f6575518bf251d51 upstream. In PT_SEIZED + LISTEN mode STOP/CONT signals cause a wakeup against __TASK_TRACED. If this races with the

[PATCH 4.9 004/152] drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Murray McAllister commit 36274ab8c596f1240c606bb514da329add2a1bcd upstream. Before memory allocations vmw_surface_define_ioctl() checks the upper-bounds of a

[PATCH 4.9 004/152] drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Murray McAllister commit 36274ab8c596f1240c606bb514da329add2a1bcd upstream. Before memory allocations vmw_surface_define_ioctl() checks the upper-bounds of a user-supplied size, but does not

[PATCH v7 2/4] x86/syscalls: Architecture specific pre-usermode check

Garnier <thgar...@google.com> --- Based on next-20170410 --- arch/x86/Kconfig| 1 + arch/x86/entry/common.c | 3 +++ arch/x86/entry/entry_64.S | 8 arch/x86/include/asm/pgtable_64_types.h | 11 +++ arch/x86/inclu

[PATCH v7 2/4] x86/syscalls: Architecture specific pre-usermode check

Garnier --- Based on next-20170410 --- arch/x86/Kconfig| 1 + arch/x86/entry/common.c | 3 +++ arch/x86/entry/entry_64.S | 8 arch/x86/include/asm/pgtable_64_types.h | 11 +++ arch/x86/include/asm/processor.h| 11

[PATCH 4.9 005/152] drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Murray McAllister commit 63774069d9527a1aeaa4aa20e929ef5e8e9ecc38 upstream. In vmw_get_cap_3d_ioctl(), a user can supply 0 for a size that is used in

[PATCH v7 3/4] arm/syscalls: Architecture specific pre-usermode check

. If the address limit was changed, a generic handler is called to stop the kernel on an explicit check. Signed-off-by: Thomas Garnier <thgar...@google.com> --- Based on next-20170410 --- arch/arm/Kconfig | 1 + arch/arm/kernel/entry-common.S | 10 +- 2 files changed, 10 inse

[PATCH 4.9 005/152] drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Murray McAllister commit 63774069d9527a1aeaa4aa20e929ef5e8e9ecc38 upstream. In vmw_get_cap_3d_ioctl(), a user can supply 0 for a size that is used in vzalloc(). This eventually calls

[PATCH v7 3/4] arm/syscalls: Architecture specific pre-usermode check

. If the address limit was changed, a generic handler is called to stop the kernel on an explicit check. Signed-off-by: Thomas Garnier --- Based on next-20170410 --- arch/arm/Kconfig | 1 + arch/arm/kernel/entry-common.S | 10 +- 2 files changed, 10 insertions(+), 1 deletion(-) diff

[PATCH v7 1/4] syscalls: Restore address limit after a syscall

The CONFIG_ARCH_NO_SYSCALL_VERIFY_PRE_USERMODE_STATE option is also added so each architecture can optimize this change. Signed-off-by: Thomas Garnier <thgar...@google.com> Tested-by: Kees Cook <keesc...@chromium.org> --- Based on next-20170410 --- arch/s390/Kconfig| 1 + include/linux/sys

[PATCH v7 1/4] syscalls: Restore address limit after a syscall

The CONFIG_ARCH_NO_SYSCALL_VERIFY_PRE_USERMODE_STATE option is also added so each architecture can optimize this change. Signed-off-by: Thomas Garnier Tested-by: Kees Cook --- Based on next-20170410 --- arch/s390/Kconfig| 1 + include/linux/syscalls.h | 26 +- init/Kconfig

Re: [PATCH v2 5/5] iio: dac: stm32: add support for waveform generator

On 04/09/2017 11:34 AM, Jonathan Cameron wrote: > On 06/04/17 17:11, Fabrice Gasnier wrote: >> STM32 DAC has built-in noise or triangle waveform generator. >> - "wavetype" extended attribute selects noise or triangle. >> - "amplitude" extended attribute selects amplitude for waveform generator >>

[PATCH 4.9 007/152] drm/vmwgfx: Remove getparam error message

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Hellstrom commit 53e16798b0864464c5444a204e1bb93ae246c429 upstream. The mesa winsys sometimes uses unimplemented parameter requests to check for features. Remove

[PATCH 4.9 021/152] dm verity fec: fix bufio leaks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sami Tolvanen commit 86e3e83b443669dd2bcc5c8a83b23e3aa0694c0d upstream. Buffers read through dm_bufio_read() were not released in all code paths. Fixes: a739ff3f543a

[PATCH 4.9 007/152] drm/vmwgfx: Remove getparam error message

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Hellstrom commit 53e16798b0864464c5444a204e1bb93ae246c429 upstream. The mesa winsys sometimes uses unimplemented parameter requests to check for features. Remove the error message to

[PATCH 4.9 021/152] dm verity fec: fix bufio leaks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sami Tolvanen commit 86e3e83b443669dd2bcc5c8a83b23e3aa0694c0d upstream. Buffers read through dm_bufio_read() were not released in all code paths. Fixes: a739ff3f543a ("dm verity: add support

Re: [PATCH v2 5/5] iio: dac: stm32: add support for waveform generator

On 04/09/2017 11:34 AM, Jonathan Cameron wrote: > On 06/04/17 17:11, Fabrice Gasnier wrote: >> STM32 DAC has built-in noise or triangle waveform generator. >> - "wavetype" extended attribute selects noise or triangle. >> - "amplitude" extended attribute selects amplitude for waveform generator >>

[PATCH 4.9 009/152] sysfs: be careful of error returns from ops->show()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit c8a139d001a1aab1ea8734db14b22dac9dd143b6 upstream. ops->show() can return a negative error code. Commit 65da3484d9be ("sysfs: correctly handle short reads on

Re: [PATCH] mm, numa: Fix bad pmd by atomically check for pmd_trans_huge when marking page tables prot_numa

On 10 Apr 2017, at 12:20, Mel Gorman wrote: > On Mon, Apr 10, 2017 at 11:45:08AM -0500, Zi Yan wrote: >>> While this could be fixed with heavy locking, it's only necessary to >>> make a copy of the PMD on the stack during change_pmd_range and avoid >>> races. A new helper is created for this as

[PATCH 4.9 009/152] sysfs: be careful of error returns from ops->show()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit c8a139d001a1aab1ea8734db14b22dac9dd143b6 upstream. ops->show() can return a negative error code. Commit 65da3484d9be ("sysfs: correctly handle short reads on PREALLOC attrs.")

Re: [PATCH] mm, numa: Fix bad pmd by atomically check for pmd_trans_huge when marking page tables prot_numa

On 10 Apr 2017, at 12:20, Mel Gorman wrote: > On Mon, Apr 10, 2017 at 11:45:08AM -0500, Zi Yan wrote: >>> While this could be fixed with heavy locking, it's only necessary to >>> make a copy of the PMD on the stack during change_pmd_range and avoid >>> races. A new helper is created for this as

[PATCH 4.9 032/152] metag/usercopy: Zero rest of buffer from copy_from_user

4.9-stable review patch. If anyone has any objections, please let me know. -- From: James Hogan commit 563ddc1076109f2b3f88e6d355eab7b6fd4662cb upstream. Currently we try to zero the destination for a failed read from userland in fixup code in the

[PATCH 4.9 032/152] metag/usercopy: Zero rest of buffer from copy_from_user

4.9-stable review patch. If anyone has any objections, please let me know. -- From: James Hogan commit 563ddc1076109f2b3f88e6d355eab7b6fd4662cb upstream. Currently we try to zero the destination for a failed read from userland in fixup code in the usercopy.c macros. The rest

Re: [PATCH 06/16] regulator: madera-ldo1: LDO1 driver for Cirrus Logic Madera codecs

On Wed, Apr 05, 2017 at 11:07:54AM +0100, Richard Fitzgerald wrote: > This patch adds a driver for the internal LDO1 regulator on > some Cirrus Logic Madera class codecs. > > Signed-off-by: Richard Fitzgerald > Signed-off-by: Charles Keepax

Re: [PATCH 06/16] regulator: madera-ldo1: LDO1 driver for Cirrus Logic Madera codecs

On Wed, Apr 05, 2017 at 11:07:54AM +0100, Richard Fitzgerald wrote: > This patch adds a driver for the internal LDO1 regulator on > some Cirrus Logic Madera class codecs. > > Signed-off-by: Richard Fitzgerald > Signed-off-by: Charles Keepax > --- >

[PATCH 4.9 008/152] drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Li Qiang commit e7e11f99564222d82f0ce84bd521e57d78a6b678 upstream. In vmw_surface_define_ioctl(), the 'num_sizes' is the sum of the 'req->mip_levels' array. This array can be

[PATCH 4.9 008/152] drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Li Qiang commit e7e11f99564222d82f0ce84bd521e57d78a6b678 upstream. In vmw_surface_define_ioctl(), the 'num_sizes' is the sum of the 'req->mip_levels' array. This array can be assigned any

Re: [PATCH] ipmi_si: use smi_num for init_name

On 04/10/2017 01:43 PM, miny...@acm.org wrote: From: Tony Camuso Commit 1abf71e moved the creation of new_smi->dev to earlier in the init sequence in order to provide infrastructure for log printing. However, the init_name was created with a hard-coded value of zero. This

Re: [PATCH] ipmi_si: use smi_num for init_name

On 04/10/2017 01:43 PM, miny...@acm.org wrote: From: Tony Camuso Commit 1abf71e moved the creation of new_smi->dev to earlier in the init sequence in order to provide infrastructure for log printing. However, the init_name was created with a hard-coded value of zero. This presents a problem

[PATCH 4.9 036/152] powerpc: Disable HFSCR[TM] if TM is not supported

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Herrenschmidt commit 7ed23e1bae8bf7e37fd555066550a00b95a3a98b upstream. On Power8 & Power9 the early CPU inititialisation in __init_HFSCR() turns on

[PATCH 4.9 036/152] powerpc: Disable HFSCR[TM] if TM is not supported

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Herrenschmidt commit 7ed23e1bae8bf7e37fd555066550a00b95a3a98b upstream. On Power8 & Power9 the early CPU inititialisation in __init_HFSCR() turns on HFSCR[TM] (Hypervisor Facility

[PATCH 4.9 034/152] metag/usercopy: Fix src fixup in from user rapf loops

4.9-stable review patch. If anyone has any objections, please let me know. -- From: James Hogan commit 2c0b1df88b987a12d95ea1d6beaf01894f3cc725 upstream. The fixup code to rewind the source pointer in __asm_copy_from_user_{32,64}bit_rapf_loop() always

[PATCH 4.9 034/152] metag/usercopy: Fix src fixup in from user rapf loops

4.9-stable review patch. If anyone has any objections, please let me know. -- From: James Hogan commit 2c0b1df88b987a12d95ea1d6beaf01894f3cc725 upstream. The fixup code to rewind the source pointer in __asm_copy_from_user_{32,64}bit_rapf_loop() always rewound the source by a

Re: [PATCH v3] lightnvm: physical block device (pblk) target

On 04/10/2017 05:55 PM, Bart Van Assche wrote: On Sun, 2017-04-09 at 11:15 +0200, Javier González wrote: On 8 Apr 2017, at 22.56, Bart Van Assche wrote: On 04/07/17 11:50, Javier González wrote: struct ppa_addr, which is the physical address format is not

[PATCH] PCI: Improve __pci_read_base robustness

Local variables 'l' and 'sz' are uninitialized. Normally, they would be initialized by pci_read_config_dword() but when an error occurs, some drivers immediately return an error code, which leaves the argument uninitialized. Provide a safe initial value to make the code more robust.

Re: [PATCH v3] lightnvm: physical block device (pblk) target

On 04/10/2017 05:55 PM, Bart Van Assche wrote: On Sun, 2017-04-09 at 11:15 +0200, Javier González wrote: On 8 Apr 2017, at 22.56, Bart Van Assche wrote: On 04/07/17 11:50, Javier González wrote: struct ppa_addr, which is the physical address format is not affected, but pblk's internal L2P

[PATCH] PCI: Improve __pci_read_base robustness

Local variables 'l' and 'sz' are uninitialized. Normally, they would be initialized by pci_read_config_dword() but when an error occurs, some drivers immediately return an error code, which leaves the argument uninitialized. Provide a safe initial value to make the code more robust.

[PATCH 4.9 038/152] powerpc/64: Fix flush_(d|i)cache_range() called from modules

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Oliver O'Halloran commit 8f5f525d5b83f7d76a6baf9c4e94d4bf312ea7f6 upstream. When the kernel is compiled to use 64bit ABIv2 the _GLOBAL() macro does not include a global entry

[PATCH 4.9 038/152] powerpc/64: Fix flush_(d|i)cache_range() called from modules

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Oliver O'Halloran commit 8f5f525d5b83f7d76a6baf9c4e94d4bf312ea7f6 upstream. When the kernel is compiled to use 64bit ABIv2 the _GLOBAL() macro does not include a global entry point. A

Re: net/ipv4: use-after-free in ip_queue_xmit

On Mon, Apr 10, 2017 at 7:42 PM, Cong Wang wrote: > On Mon, Apr 10, 2017 at 7:40 AM, Andrey Konovalov > wrote: >> Hi, >> >> I've got the following error report while fuzzing the kernel with syzkaller. >> >> On commit

[PATCH] checkpatch: Avoid suggesting struct definitions should be const

Many structs are generally used const and there is a known list of these structs. struct definitions should not be generally be declared const. Add a test for the lack of an open brace immediately after the struct to avoid definitions. This avoids the false positive "struct foo should normally

Re: net/ipv4: use-after-free in ip_queue_xmit

On Mon, Apr 10, 2017 at 7:42 PM, Cong Wang wrote: > On Mon, Apr 10, 2017 at 7:40 AM, Andrey Konovalov > wrote: >> Hi, >> >> I've got the following error report while fuzzing the kernel with syzkaller. >> >> On commit 39da7c509acff13fc8cb12ec1bb20337c988ed36 (4.11-rc6). >> >> Unfortunately it's

[PATCH] checkpatch: Avoid suggesting struct definitions should be const

Many structs are generally used const and there is a known list of these structs. struct definitions should not be generally be declared const. Add a test for the lack of an open brace immediately after the struct to avoid definitions. This avoids the false positive "struct foo should normally

[PATCH 4.9 039/152] powerpc: Dont try to fix up misaligned load-with-reservation instructions

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 48fe9e9488743eec9b7c1addd3c93f12f2123d54 upstream. In the past, there was only one load-with-reservation instruction, lwarx, and if a program attempted

[PATCH 4.9 039/152] powerpc: Dont try to fix up misaligned load-with-reservation instructions

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 48fe9e9488743eec9b7c1addd3c93f12f2123d54 upstream. In the past, there was only one load-with-reservation instruction, lwarx, and if a program attempted a lwarx on a

[PATCH 4.9 042/152] nios2: reserve boot memory for device tree

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tobias Klauser commit 921d701e6f31e1ffaca3560416af1aa04edb4c4f upstream. Make sure to reserve the boot memory for the flattened device tree. Otherwise it might get

[PATCH 4.9 042/152] nios2: reserve boot memory for device tree

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tobias Klauser commit 921d701e6f31e1ffaca3560416af1aa04edb4c4f upstream. Make sure to reserve the boot memory for the flattened device tree. Otherwise it might get overwritten, e.g. when

Re: [PATCH] mm, numa: Fix bad pmd by atomically check for pmd_trans_huge when marking page tables prot_numa

On 10 Apr 2017, at 4:48, Mel Gorman wrote: > A user reported a bug against a distribution kernel while running > a proprietary workload described as "memory intensive that is not > swapping" that is expected to apply to mainline kernels. The workload > is read/write/modifying ranges of memory and

Re: [PATCH] mm, numa: Fix bad pmd by atomically check for pmd_trans_huge when marking page tables prot_numa

On 10 Apr 2017, at 4:48, Mel Gorman wrote: > A user reported a bug against a distribution kernel while running > a proprietary workload described as "memory intensive that is not > swapping" that is expected to apply to mainline kernels. The workload > is read/write/modifying ranges of memory and

[PATCH 4.9 044/152] s390/decompressor: fix initrd corruption caused by bss clear

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marcelo Henrique Cerri commit d82c0d12c92705ef468683c9b7a8298dd61ed191 upstream. Reorder the operations in decompress_kernel() to ensure initrd is moved to a safe

[PATCH 4.9 044/152] s390/decompressor: fix initrd corruption caused by bss clear

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marcelo Henrique Cerri commit d82c0d12c92705ef468683c9b7a8298dd61ed191 upstream. Reorder the operations in decompress_kernel() to ensure initrd is moved to a safe location before the bss

[PATCH 4.9 043/152] xtensa: make __pa work with uncached KSEG addresses

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit 2b83878dd74a7c73bedcb6600663c1c46836e8af upstream. When __pa is applied to virtual address in uncached KSEG region the result is incorrect. Fix it by

[PATCH 4.9 046/152] MIPS: Force o32 fp64 support on 32bit MIPS64r6 kernels

4.9-stable review patch. If anyone has any objections, please let me know. -- From: James Hogan commit 2e6c7747730296a6d4fd700894286db1132598c4 upstream. When a 32-bit kernel is configured to support MIPS64r6 (CPU_MIPS64_R6), MIPS_O32_FP64_SUPPORT

[PATCH 4.9 043/152] xtensa: make __pa work with uncached KSEG addresses

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit 2b83878dd74a7c73bedcb6600663c1c46836e8af upstream. When __pa is applied to virtual address in uncached KSEG region the result is incorrect. Fix it by checking if the

[PATCH 4.9 046/152] MIPS: Force o32 fp64 support on 32bit MIPS64r6 kernels

4.9-stable review patch. If anyone has any objections, please let me know. -- From: James Hogan commit 2e6c7747730296a6d4fd700894286db1132598c4 upstream. When a 32-bit kernel is configured to support MIPS64r6 (CPU_MIPS64_R6), MIPS_O32_FP64_SUPPORT won't be selected as it

[PATCH] ipmi_si: use smi_num for init_name

From: Tony Camuso Commit 1abf71e moved the creation of new_smi->dev to earlier in the init sequence in order to provide infrastructure for log printing. However, the init_name was created with a hard-coded value of zero. This presents a problem in systems with more than one

[PATCH] ipmi_si: use smi_num for init_name

From: Tony Camuso Commit 1abf71e moved the creation of new_smi->dev to earlier in the init sequence in order to provide infrastructure for log printing. However, the init_name was created with a hard-coded value of zero. This presents a problem in systems with more than one interface, producing

Re: net/ipv4: use-after-free in ip_queue_xmit

On Mon, Apr 10, 2017 at 7:40 AM, Andrey Konovalov wrote: > Hi, > > I've got the following error report while fuzzing the kernel with syzkaller. > > On commit 39da7c509acff13fc8cb12ec1bb20337c988ed36 (4.11-rc6). > > Unfortunately it's not reproducible. > > BUG: KASAN:

Re: [PATCH 4.9 112/152] Input: gpio_keys - add support for GPIO descriptors

On Mon, Apr 10, 2017 at 9:42 AM, Greg Kroah-Hartman wrote: > 4.9-stable review patch. If anyone has any objections, please let me know. Confused why it needs to be in stable as there should be no chnage in behavior. Is it because there are other patches depending on

Re: net/ipv4: use-after-free in ip_queue_xmit

On Mon, Apr 10, 2017 at 7:40 AM, Andrey Konovalov wrote: > Hi, > > I've got the following error report while fuzzing the kernel with syzkaller. > > On commit 39da7c509acff13fc8cb12ec1bb20337c988ed36 (4.11-rc6). > > Unfortunately it's not reproducible. > > BUG: KASAN: use-after-free in

Re: [PATCH 4.9 112/152] Input: gpio_keys - add support for GPIO descriptors

On Mon, Apr 10, 2017 at 9:42 AM, Greg Kroah-Hartman wrote: > 4.9-stable review patch. If anyone has any objections, please let me know. Confused why it needs to be in stable as there should be no chnage in behavior. Is it because there are other patches depending on this one? > >

[PATCH 4.9 025/152] xfs: Honor FALLOC_FL_KEEP_SIZE when punching ends of files

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Calvin Owens commit 3dd09d5a8589c640abb49cfcf92b4ed669eafad1 upstream. When punching past EOF on XFS, fallocate(mode=PUNCH_HOLE|KEEP_SIZE) will round the file size up to

[PATCH 4.9 025/152] xfs: Honor FALLOC_FL_KEEP_SIZE when punching ends of files

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Calvin Owens commit 3dd09d5a8589c640abb49cfcf92b4ed669eafad1 upstream. When punching past EOF on XFS, fallocate(mode=PUNCH_HOLE|KEEP_SIZE) will round the file size up to the nearest multiple

[PATCH 4.9 049/152] MIPS: Lantiq: fix missing xbar kernel panic

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Hauke Mehrtens commit 6ef90877eee63a0d03e83183bb44b64229b624e6 upstream. Commit 08b3c894e565 ("MIPS: lantiq: Disable xbar fpi burst mode") accidentally requested the

[PATCH 4.9 049/152] MIPS: Lantiq: fix missing xbar kernel panic

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Hauke Mehrtens commit 6ef90877eee63a0d03e83183bb44b64229b624e6 upstream. Commit 08b3c894e565 ("MIPS: lantiq: Disable xbar fpi burst mode") accidentally requested the resources from the pmu

[PATCH 4.9 053/152] MIPS: c-r4k: Fix Loongson-3s vcache/scache waysize calculation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Huacai Chen commit 0be032c190abcdcfa948082b6a1e0d461184ba4d upstream. If scache.waysize is 0, r4k___flush_cache_all() will do nothing and then cause bugs. BTW, though

[PATCH 4.9 053/152] MIPS: c-r4k: Fix Loongson-3s vcache/scache waysize calculation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Huacai Chen commit 0be032c190abcdcfa948082b6a1e0d461184ba4d upstream. If scache.waysize is 0, r4k___flush_cache_all() will do nothing and then cause bugs. BTW, though vcache.waysize isn't

[PATCH 4.9 056/152] random: use chacha20 for get_random_int/long

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason A. Donenfeld commit f5b98461cb8167ba362ad9f74c41d126b7becea7 upstream. Now that our crng uses chacha20, we can rely on its speedy characteristics for replacing MD5,

[PATCH 4.9 056/152] random: use chacha20 for get_random_int/long

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason A. Donenfeld commit f5b98461cb8167ba362ad9f74c41d126b7becea7 upstream. Now that our crng uses chacha20, we can rely on its speedy characteristics for replacing MD5, while simultaneously

[PATCH 4.9 054/152] Documentation: stable-kernel-rules: fix stable-tag format

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit cf903e9d3a97f89b224d2d07be37c0f160db8192 upstream. A patch documenting how to specify which kernels a particular fix should be backported to (seemingly)

[PATCH 4.9 054/152] Documentation: stable-kernel-rules: fix stable-tag format

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit cf903e9d3a97f89b224d2d07be37c0f160db8192 upstream. A patch documenting how to specify which kernels a particular fix should be backported to (seemingly) inadvertently added

[PATCH 4.9 058/152] drm/sun4i: Add compatible strings for A31/A31s display pipelines

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit 49c440e87cd6f547f93d0dc53571ae0e11d9ec8f upstream. The A31's display pipeline has 2 frontends, 2 backends, and 2 TCONs. It also has new display enhancement

[PATCH 4.9 057/152] drm/sun4i: tcon: Move SoC specific quirks to a DT matched data structure

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit 91ea2f29cba6a7fe035ea232e4f981211a9fce5d upstream. We already have some differences between the 2 supported SoCs. More will be added as we support other

[PATCH 4.9 058/152] drm/sun4i: Add compatible strings for A31/A31s display pipelines

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit 49c440e87cd6f547f93d0dc53571ae0e11d9ec8f upstream. The A31's display pipeline has 2 frontends, 2 backends, and 2 TCONs. It also has new display enhancement blocks, such as

[PATCH 4.9 057/152] drm/sun4i: tcon: Move SoC specific quirks to a DT matched data structure

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit 91ea2f29cba6a7fe035ea232e4f981211a9fce5d upstream. We already have some differences between the 2 supported SoCs. More will be added as we support other SoCs. To avoid

[PATCH 4.9 059/152] drm/sun4i: Add compatible string for A31/A31s TCON (timing controller)

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit 93a5ec14da24a8abbac5bcb953b45cc7a5d0198a upstream. The A31 TCON has mux controls for how TCON outputs are routed to the HDMI and MIPI DSI blocks. Since the

[PATCH 4.9 059/152] drm/sun4i: Add compatible string for A31/A31s TCON (timing controller)

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit 93a5ec14da24a8abbac5bcb953b45cc7a5d0198a upstream. The A31 TCON has mux controls for how TCON outputs are routed to the HDMI and MIPI DSI blocks. Since the A31s does not

[PATCH 4.9 028/152] brcmfmac: use local iftype avoiding use-after-free of virtual interface

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arend Van Spriel commit d77facb88448cdeaaa3adba5b9704a48ac2ac8d6 upstream. A use-after-free was found using KASAN. In brcmf_p2p_del_if() the virtual interface is

[PATCH 4.9 062/152] HID: i2c-hid: add a simple quirk to fix device defects

4.9-stable review patch. If anyone has any objections, please let me know. -- From: HungNien Chen [ Upstream commit 71af01a8c85ad89449209594133bdfdfaa9f1e2a ] Certain devices produced by Weida Tech need to have a wakeup command sent to them before

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