[PATCH 4.9 027/101] powerpc/powernv/ioda2: Remove redundant free of TCE pages

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kardashevskiy commit 98fd72fe82527fd26618062b60cfd329451f2329 upstream. When IODA2 creates a PE, it creates an IOMMU table with it_ops::free set to pnv_ioda2_table_free() which calls

[PATCH 4.9 025/101] powerpc/ptrace: Fix setting 512B aligned breakpoints with PTRACE_SET_DEBUGREG

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Neuling commit 4f7c06e26ec9cf7fe9f0c54dc90079b6a4f4b2c3 upstream. In commit e2a800beaca1 ("powerpc/hw_brk: Fix off by one error when validating DAWR region end") we fixed setting the

[PATCH 4.9 028/101] cpuidle: powernv: Fix promotion from snooze if next state disabled

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Gautham R. Shenoy commit 0a4ec6aa035a52c422eceb2ed51ed88392a3d6c2 upstream. The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of snooze to deeper idle state") introduced a

[PATCH 4.9 028/101] cpuidle: powernv: Fix promotion from snooze if next state disabled

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Gautham R. Shenoy commit 0a4ec6aa035a52c422eceb2ed51ed88392a3d6c2 upstream. The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of snooze to deeper idle state") introduced a

[PATCH 4.9 031/101] arm64: kpti: Use early_param for kpti= command-line option

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit b5b7dd647f2d21b93f734ce890671cd908e69b0a upstream. We inspect __kpti_forced early on as part of the cpufeature enable callback which remaps the swapper page table using

[PATCH 4.9 032/101] arm64: mm: Ensure writes to swapper are ordered wrt subsequent cache maintenance

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit 71c8fc0c96abf8e53e74ed4d891d671e585f9076 upstream. When rewriting swapper using nG mappings, we must performance cache maintenance around each page table access in order to

[PATCH 4.9 003/101] x86/mce: Check for alternate indication of machine check recovery on Skylake

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit 4c5717da1d021cf368eabb3cb1adcaead56c0d1e upstream. Currently we just check the "CAPID0" register to see whether the CPU can recover from machine checks. But there are also

[PATCH 4.9 033/101] of: unittest: for strings, account for trailing \0 in property length field

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stefan M Schaeckeler commit 3b9cf7905fe3ab35ab437b5072c883e609d3498d upstream. For strings, account for trailing \0 in property length field: This is consistent with how dtc builds string

[PATCH 4.9 031/101] arm64: kpti: Use early_param for kpti= command-line option

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit b5b7dd647f2d21b93f734ce890671cd908e69b0a upstream. We inspect __kpti_forced early on as part of the cpufeature enable callback which remaps the swapper page table using

[PATCH 4.9 032/101] arm64: mm: Ensure writes to swapper are ordered wrt subsequent cache maintenance

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit 71c8fc0c96abf8e53e74ed4d891d671e585f9076 upstream. When rewriting swapper using nG mappings, we must performance cache maintenance around each page table access in order to

[PATCH 4.9 003/101] x86/mce: Check for alternate indication of machine check recovery on Skylake

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit 4c5717da1d021cf368eabb3cb1adcaead56c0d1e upstream. Currently we just check the "CAPID0" register to see whether the CPU can recover from machine checks. But there are also

[PATCH 4.9 033/101] of: unittest: for strings, account for trailing \0 in property length field

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stefan M Schaeckeler commit 3b9cf7905fe3ab35ab437b5072c883e609d3498d upstream. For strings, account for trailing \0 in property length field: This is consistent with how dtc builds string

[PATCH 4.9 030/101] ARM: 8764/1: kgdb: fix NUMREGBYTES so that gdb_regs[] is the correct size

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Rivshin commit 76ed0b803a2ab793a1b27d1dfe0de7955282cd34 upstream. NUMREGBYTES (which is used as the size for gdb_regs[]) is incorrectly based on DBG_MAX_REG_NUM instead of GDB_MAX_REGS.

[PATCH 4.9 030/101] ARM: 8764/1: kgdb: fix NUMREGBYTES so that gdb_regs[] is the correct size

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Rivshin commit 76ed0b803a2ab793a1b27d1dfe0de7955282cd34 upstream. NUMREGBYTES (which is used as the size for gdb_regs[]) is incorrectly based on DBG_MAX_REG_NUM instead of GDB_MAX_REGS.

[PATCH 4.9 034/101] IB/qib: Fix DMA api warning with debug kernel

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mike Marciniszyn commit 0252f73334f9ef68868e4684200bea3565a4fcee upstream. The following error occurs in a debug build when running MPI PSM: [ 307.415911] WARNING: CPU: 4 PID: 23867 at

[PATCH 4.9 036/101] IB/mlx5: Fetch soft WQEs on fatal error state

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Erez Shitrit commit 7b74a83cf54a3747e22c57e25712bd70eef8acee upstream. On fatal error the driver simulates CQE's for ULPs that rely on completion of all their posted work-request. For the GSI

[PATCH 4.9 005/101] x86/mce: Do not overwrite MCi_STATUS in mce_no_way_out()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov commit 1f74c8a64798e2c488f86efc97e308b85fb7d7aa upstream. mce_no_way_out() does a quick check during #MC to see whether some of the MCEs logged would require the kernel to

[PATCH 4.9 034/101] IB/qib: Fix DMA api warning with debug kernel

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mike Marciniszyn commit 0252f73334f9ef68868e4684200bea3565a4fcee upstream. The following error occurs in a debug build when running MPI PSM: [ 307.415911] WARNING: CPU: 4 PID: 23867 at

[PATCH 4.9 036/101] IB/mlx5: Fetch soft WQEs on fatal error state

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Erez Shitrit commit 7b74a83cf54a3747e22c57e25712bd70eef8acee upstream. On fatal error the driver simulates CQE's for ULPs that rely on completion of all their posted work-request. For the GSI

[PATCH 4.9 005/101] x86/mce: Do not overwrite MCi_STATUS in mce_no_way_out()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov commit 1f74c8a64798e2c488f86efc97e308b85fb7d7aa upstream. mce_no_way_out() does a quick check during #MC to see whether some of the MCEs logged would require the kernel to

[PATCH 4.9 007/101] m68k/mm: Adjust VM area to be unmapped by gap size for __iounmap()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Schmitz commit 3f90f9ef2dda316d64e420d5d51ba369587ccc55 upstream. If 020/030 support is enabled, get_io_area() leaves an IO_SIZE gap between mappings which is added to the vm_struct

[PATCH 4.9 007/101] m68k/mm: Adjust VM area to be unmapped by gap size for __iounmap()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Schmitz commit 3f90f9ef2dda316d64e420d5d51ba369587ccc55 upstream. If 020/030 support is enabled, get_io_area() leaves an IO_SIZE gap between mappings which is added to the vm_struct

[PATCH 4.9 008/101] serial: sh-sci: Use spin_{try}lock_irqsave instead of open coding version

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Wagner commit 8afb1d2c12163f7f84616a8e9444d0050ebe upstream. Commit 40f70c03e33a ("serial: sh-sci: add locking to console write function to avoid SMP lockup") copied the strategy to

[PATCH 4.9 008/101] serial: sh-sci: Use spin_{try}lock_irqsave instead of open coding version

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Wagner commit 8afb1d2c12163f7f84616a8e9444d0050ebe upstream. Commit 40f70c03e33a ("serial: sh-sci: add locking to console write function to avoid SMP lockup") copied the strategy to

[PATCH 4.9 038/101] IB/isert: fix T10-pi check mask setting

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Max Gurtovoy commit 0e12af84cdd3056460f928adc164f9e87f4b303b upstream. A copy/paste bug (probably) caused setting of an app_tag check mask in case where a ref_tag check was needed. Fixes:

[PATCH 4.9 050/101] MIPS: io: Add barrier after register read in inX()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Huacai Chen commit 18f3e95b90b28318ef35910d21c39908de672331 upstream. While a barrier is present in the outX() functions before the register write, a similar barrier is missing in the inX()

[PATCH 4.9 009/101] signal/xtensa: Consistenly use SIGBUS in do_unaligned_user

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric W. Biederman commit 7de712ccc096b81d23cc0a941cd9b8cb3956605d upstream. While working on changing this code to use force_sig_fault I discovered that do_unaliged_user is sets si_signo to

[PATCH 4.9 038/101] IB/isert: fix T10-pi check mask setting

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Max Gurtovoy commit 0e12af84cdd3056460f928adc164f9e87f4b303b upstream. A copy/paste bug (probably) caused setting of an app_tag check mask in case where a ref_tag check was needed. Fixes:

[PATCH 4.9 050/101] MIPS: io: Add barrier after register read in inX()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Huacai Chen commit 18f3e95b90b28318ef35910d21c39908de672331 upstream. While a barrier is present in the outX() functions before the register write, a similar barrier is missing in the inX()

[PATCH 4.9 009/101] signal/xtensa: Consistenly use SIGBUS in do_unaligned_user

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric W. Biederman commit 7de712ccc096b81d23cc0a941cd9b8cb3956605d upstream. While working on changing this code to use force_sig_fault I discovered that do_unaliged_user is sets si_signo to

[PATCH 4.9 047/101] PCI: Add ACS quirk for Intel 300 series

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mika Westerberg commit f154a718e6cc0d834f5ac4dc4c3b174e65f3659e upstream. Intel 300 series chipset still has the same ACS issue as the previous generations so extend the ACS quirk to cover it

[PATCH 4.9 047/101] PCI: Add ACS quirk for Intel 300 series

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mika Westerberg commit f154a718e6cc0d834f5ac4dc4c3b174e65f3659e upstream. Intel 300 series chipset still has the same ACS issue as the previous generations so extend the ACS quirk to cover it

[PATCH 4.9 053/101] Btrfs: fix return value on rename exchange failure

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit c5b4a50b74018b3677098151ec5f4fce07d5e6a0 upstream. If we failed during a rename exchange operation after starting/joining a transaction, we would end up replacing the

[PATCH 4.9 039/101] RDMA/mlx4: Discard unknown SQP work requests

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 6b1ca7ece15e94251d1d0d919f813943e4a58059 upstream. There is no need to crash the machine if unknown work request was received in SQP MAD. Cc: # 3.6 Fixes: 37bfc7c1e83f

[PATCH 4.9 039/101] RDMA/mlx4: Discard unknown SQP work requests

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 6b1ca7ece15e94251d1d0d919f813943e4a58059 upstream. There is no need to crash the machine if unknown work request was received in SQP MAD. Cc: # 3.6 Fixes: 37bfc7c1e83f

[PATCH 4.9 053/101] Btrfs: fix return value on rename exchange failure

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit c5b4a50b74018b3677098151ec5f4fce07d5e6a0 upstream. If we failed during a rename exchange operation after starting/joining a transaction, we would end up replacing the

[PATCH 4.9 052/101] X.509: unpack RSA signatureValue field from BIT STRING

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Maciej S. Szmigiero commit b65c32ec5a942ab3ada93a048089a938918aba7f upstream. The signatureValue field of a X.509 certificate is encoded as a BIT STRING. For RSA signatures this BIT STRING is

[PATCH 4.9 052/101] X.509: unpack RSA signatureValue field from BIT STRING

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Maciej S. Szmigiero commit b65c32ec5a942ab3ada93a048089a938918aba7f upstream. The signatureValue field of a X.509 certificate is encoded as a BIT STRING. For RSA signatures this BIT STRING is

[PATCH 4.9 055/101] iio:buffer: make length types match kfifo types

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Martin Kelly commit c043ec1ca5baae63726aae32abbe003192bc6eec upstream. Currently, we use int for buffer length and bytes_per_datum. However, kfifo uses unsigned int for length and size_t for

[PATCH 4.9 054/101] Btrfs: fix unexpected cow in run_delalloc_nocow

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo commit 5811375325420052fcadd944792a416a43072b7f upstream. Fstests generic/475 provides a way to fail metadata reads while checking if checksum exists for the inode inside

[PATCH 4.9 057/101] scsi: zfcp: fix missing SCSI trace for result of eh_host_reset_handler

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit df30781699f53e4fd4c494c6f7dd16e3d5c21d30 upstream. For problem determination we need to see whether and why we were successful or not. This allows deduction of scsi_eh

[PATCH 4.9 057/101] scsi: zfcp: fix missing SCSI trace for result of eh_host_reset_handler

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit df30781699f53e4fd4c494c6f7dd16e3d5c21d30 upstream. For problem determination we need to see whether and why we were successful or not. This allows deduction of scsi_eh

[PATCH 4.9 055/101] iio:buffer: make length types match kfifo types

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Martin Kelly commit c043ec1ca5baae63726aae32abbe003192bc6eec upstream. Currently, we use int for buffer length and bytes_per_datum. However, kfifo uses unsigned int for length and size_t for

[PATCH 4.9 054/101] Btrfs: fix unexpected cow in run_delalloc_nocow

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo commit 5811375325420052fcadd944792a416a43072b7f upstream. Fstests generic/475 provides a way to fail metadata reads while checking if checksum exists for the inode inside

Re: [PATCH][next] mtd: rawnand: fix a couple of spelling mistakes

Hi Colin, > On 26.06.2018 12:26, Colin King wrote: > > From: Colin Ian King > > > > Trival fix of two spelling mistakes in dev_err error messages: > > "supportes" -> "supports" and "strenght" -> "strength" > > Acked-by: Stefan Agner > > > > > Signed-off-by: Colin Ian King > > --- Thanks

Re: [PATCH][next] mtd: rawnand: fix a couple of spelling mistakes

Hi Colin, > On 26.06.2018 12:26, Colin King wrote: > > From: Colin Ian King > > > > Trival fix of two spelling mistakes in dev_err error messages: > > "supportes" -> "supports" and "strenght" -> "strength" > > Acked-by: Stefan Agner > > > > > Signed-off-by: Colin Ian King > > --- Thanks

[PATCH 4.9 058/101] scsi: zfcp: fix missing SCSI trace for retry of abort / scsi_eh TMF

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 81979ae63e872ef650a7197f6ce6590059d37172 upstream. We already have a SCSI trace for the end of abort and scsi_eh TMF. Due to zfcp_erp_wait() and fc_block_scsi_eh() time

[PATCH 4.9 059/101] scsi: zfcp: fix misleading REC trigger trace where erp_action setup failed

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 512857a795cbbda5980efa4cdb3c0b6602330408 upstream. If a SCSI device is deleted during scsi_eh host reset, we cannot get a reference to the SCSI device anymore since

[PATCH 4.9 058/101] scsi: zfcp: fix missing SCSI trace for retry of abort / scsi_eh TMF

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 81979ae63e872ef650a7197f6ce6590059d37172 upstream. We already have a SCSI trace for the end of abort and scsi_eh TMF. Due to zfcp_erp_wait() and fc_block_scsi_eh() time

[PATCH 4.9 059/101] scsi: zfcp: fix misleading REC trigger trace where erp_action setup failed

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 512857a795cbbda5980efa4cdb3c0b6602330408 upstream. If a SCSI device is deleted during scsi_eh host reset, we cannot get a reference to the SCSI device anymore since

[PATCH 4.9 062/101] scsi: zfcp: fix missing REC trigger trace for all objects in ERP_FAILED

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 8c3d20aada70042a39c6a6625be037c1472ca610 upstream. That other commit introduced an inconsistency because it would trace on ERP_FAILED for all callers of port forced reopen

[PATCH 4.9 063/101] scsi: zfcp: fix missing REC trigger trace on enqueue without ERP thread

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 6a76550841d412330bd86aed3238d1888ba70f0e upstream. Example trace record formatted with zfcpdbf from s390-tools: Timestamp : ... Area : REC Subarea:

[PATCH 4.9 060/101] scsi: zfcp: fix missing REC trigger trace on terminate_rport_io early return

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 96d9270499471545048ed8a6d7f425a49762283d upstream. get_device() and its internally used kobject_get() only return NULL if they get passed NULL as argument.

[PATCH 4.9 062/101] scsi: zfcp: fix missing REC trigger trace for all objects in ERP_FAILED

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 8c3d20aada70042a39c6a6625be037c1472ca610 upstream. That other commit introduced an inconsistency because it would trace on ERP_FAILED for all callers of port forced reopen

[PATCH 4.9 063/101] scsi: zfcp: fix missing REC trigger trace on enqueue without ERP thread

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 6a76550841d412330bd86aed3238d1888ba70f0e upstream. Example trace record formatted with zfcpdbf from s390-tools: Timestamp : ... Area : REC Subarea:

[PATCH 4.9 060/101] scsi: zfcp: fix missing REC trigger trace on terminate_rport_io early return

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 96d9270499471545048ed8a6d7f425a49762283d upstream. get_device() and its internally used kobject_get() only return NULL if they get passed NULL as argument.

[PATCH 4.9 064/101] linvdimm, pmem: Preserve read-only setting for pmem devices

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Robert Elliott commit 254a4cd50b9fe2291a12b8902e08e56dcc4e9b10 upstream. The pmem driver does not honor a forced read-only setting for very long: $ blockdev --setro /dev/pmem0

[PATCH 4.9 065/101] clk: at91: PLL recalc_rate() now using cached MUL and DIV values

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marcin Ziemianowicz commit a982e45dc150da3a08907b6dd676b735391704b4 upstream. When a USB device is connected to the USB host port on the SAM9N12 then you get "-62" error which seems to

Re: [PATCH v3] mtd: rawnand: mxc: remove __init qualifier from mxcnd_probe_dt

Hi Martin, Martin Kaiser wrote on Wed, 27 Jun 2018 22:47:44 +0200: > Using the sysfs unbind, bind nodes, mxcnd_probe and mxcnd_probe_dt can > potentially be called at any time. After the __init functions are cleaned, > mxcnd_probe_dt is no longer available. Calling it anyway causes a crash. >

[PATCH 4.9 066/101] md: fix two problems with setting the "re-add" device state.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 011abdc9df559ec75779bb7c53a744c69b2a94c6 upstream. If "re-add" is written to the "state" file for a device which is faulty, this has an effect similar to removing and

[PATCH 4.9 067/101] rpmsg: smd: do not use mananged resources for endpoints and channels

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Kandagatla commit 4a2e84c6ed85434ce7843e4844b4d3263f7e233b upstream. All the managed resources would be freed by the time release function is invoked. Handling such memory in

Re: [PATCH v3] mtd: rawnand: mxc: remove __init qualifier from mxcnd_probe_dt

Hi Martin, Martin Kaiser wrote on Wed, 27 Jun 2018 22:47:44 +0200: > Using the sysfs unbind, bind nodes, mxcnd_probe and mxcnd_probe_dt can > potentially be called at any time. After the __init functions are cleaned, > mxcnd_probe_dt is no longer available. Calling it anyway causes a crash. >

[PATCH 4.9 066/101] md: fix two problems with setting the "re-add" device state.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 011abdc9df559ec75779bb7c53a744c69b2a94c6 upstream. If "re-add" is written to the "state" file for a device which is faulty, this has an effect similar to removing and

[PATCH 4.9 067/101] rpmsg: smd: do not use mananged resources for endpoints and channels

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Kandagatla commit 4a2e84c6ed85434ce7843e4844b4d3263f7e233b upstream. All the managed resources would be freed by the time release function is invoked. Handling such memory in

[PATCH 4.9 064/101] linvdimm, pmem: Preserve read-only setting for pmem devices

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Robert Elliott commit 254a4cd50b9fe2291a12b8902e08e56dcc4e9b10 upstream. The pmem driver does not honor a forced read-only setting for very long: $ blockdev --setro /dev/pmem0

[PATCH 4.9 065/101] clk: at91: PLL recalc_rate() now using cached MUL and DIV values

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marcin Ziemianowicz commit a982e45dc150da3a08907b6dd676b735391704b4 upstream. When a USB device is connected to the USB host port on the SAM9N12 then you get "-62" error which seems to

[PATCH 4.9 068/101] ubi: fastmap: Cancel work upon detach

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit 6e7d80161066c99d12580d1b985cb1408bb58cf1 upstream. Ben Hutchings pointed out that 29b7a6fa1ec0 ("ubi: fastmap: Don't flush fastmap work on detach") does not really

[PATCH 4.9 068/101] ubi: fastmap: Cancel work upon detach

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit 6e7d80161066c99d12580d1b985cb1408bb58cf1 upstream. Ben Hutchings pointed out that 29b7a6fa1ec0 ("ubi: fastmap: Don't flush fastmap work on detach") does not really

[PATCH 4.9 070/101] UBIFS: Fix potential integer overflow in allocation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Silvio Cesare commit 353748a359f1821ee934afc579cf04572406b420 upstream. There is potential for the size and len fields in ubifs_data_node to be too large causing either a negative value for

[PATCH 4.9 070/101] UBIFS: Fix potential integer overflow in allocation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Silvio Cesare commit 353748a359f1821ee934afc579cf04572406b420 upstream. There is potential for the size and len fields in ubifs_data_node to be too large causing either a negative value for

[PATCH 4.9 072/101] backlight: max8925_bl: Fix Device Tree node lookup

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit d1cc0ec3da23e44c23712579515494b374f111c9 upstream. Fix child-node lookup during probe, which ended up searching the whole device tree depth-first starting at the parent

[PATCH 4.9 072/101] backlight: max8925_bl: Fix Device Tree node lookup

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit d1cc0ec3da23e44c23712579515494b374f111c9 upstream. Fix child-node lookup during probe, which ended up searching the whole device tree depth-first starting at the parent

[PATCH 4.9 042/101] mtd: cfi_cmdset_0002: fix SEGV unlocking multiple chips

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Joakim Tjernlund commit 5fdfc3dbad099281bf027a353d5786c09408a8e5 upstream. cfi_ppb_unlock() tries to relock all sectors that were locked before unlocking the whole chip. This locking used the

[PATCH 4.9 073/101] backlight: tps65217_bl: Fix Device Tree node lookup

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 2b12dfa124dbadf391cb9a616aaa6b056823bf75 upstream. Fix child-node lookup during probe, which ended up searching the whole device tree depth-first starting at the parent

[PATCH 4.9 074/101] mfd: intel-lpss: Program REMAP register in PIO mode

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit d28b62520830b2d0bffa2d98e81afc9f5e537e8b upstream. According to documentation REMAP register has to be programmed in either DMA or PIO mode of the slice. Move the DMA

[PATCH 4.9 042/101] mtd: cfi_cmdset_0002: fix SEGV unlocking multiple chips

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Joakim Tjernlund commit 5fdfc3dbad099281bf027a353d5786c09408a8e5 upstream. cfi_ppb_unlock() tries to relock all sectors that were locked before unlocking the whole chip. This locking used the

[PATCH 4.9 073/101] backlight: tps65217_bl: Fix Device Tree node lookup

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 2b12dfa124dbadf391cb9a616aaa6b056823bf75 upstream. Fix child-node lookup during probe, which ended up searching the whole device tree depth-first starting at the parent

[PATCH 4.9 074/101] mfd: intel-lpss: Program REMAP register in PIO mode

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit d28b62520830b2d0bffa2d98e81afc9f5e537e8b upstream. According to documentation REMAP register has to be programmed in either DMA or PIO mode of the slice. Move the DMA

[PATCH 4.9 075/101] perf tools: Fix symbol and object code resolution for vdso32 and vdsox32

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit aef4feace285f27c8ed35830a5d575bec7f3e90a upstream. Fix __kmod_path__parse() so that perf tools does not treat vdso32 and vdsox32 as kernel modules and fail to find the

[PATCH 4.9 041/101] mtd: cfi_cmdset_0002: Use right chip in do_ppb_xxlock()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Joakim Tjernlund commit f93aa8c4de307069c270b2d81741961162bead6c upstream. do_ppb_xxlock() fails to add chip->start when querying for lock status (and chip_ready test), which caused false

[PATCH 4.9 075/101] perf tools: Fix symbol and object code resolution for vdso32 and vdsox32

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit aef4feace285f27c8ed35830a5d575bec7f3e90a upstream. Fix __kmod_path__parse() so that perf tools does not treat vdso32 and vdsox32 as kernel modules and fail to find the

[PATCH 4.9 041/101] mtd: cfi_cmdset_0002: Use right chip in do_ppb_xxlock()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Joakim Tjernlund commit f93aa8c4de307069c270b2d81741961162bead6c upstream. do_ppb_xxlock() fails to add chip->start when querying for lock status (and chip_ready test), which caused false

Re: [PATCH v4 00/15] Update for QCOM NAND driver

Hi Abhishek, Abhishek Sahu wrote on Wed, 20 Jun 2018 12:57:27 +0530: > * v4: > > 1. Added patch to make other ECC configurations function static. > 2. Clubbed the DT update patches. > 3. Removed the bad block related patch. Discussion is going on >related with for proper solution so

Re: [PATCH v4 00/15] Update for QCOM NAND driver

Hi Abhishek, Abhishek Sahu wrote on Wed, 20 Jun 2018 12:57:27 +0530: > * v4: > > 1. Added patch to make other ECC configurations function static. > 2. Clubbed the DT update patches. > 3. Removed the bad block related patch. Discussion is going on >related with for proper solution so

[PATCH 4.9 046/101] PCI: Add ACS quirk for Intel 7th & 8th Gen mobile

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alex Williamson commit e8440f4bfedc623bee40c84797ac78d9303d0db6 upstream. The specification update indicates these have the same errata for implementing non-standard ACS capabilities.

[PATCH 4.9 086/101] NFSv4: Revert commit 5f83d86cf531d ("NFSv4.x: Fix wraparound issues..")

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit fc40724fc6731d90cc7fb6d62d66135f85a33dd2 upstream. The correct behaviour for NFSv4 sequence IDs is to wrap around to the value 0 after 0x. See

[PATCH 4.9 086/101] NFSv4: Revert commit 5f83d86cf531d ("NFSv4.x: Fix wraparound issues..")

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit fc40724fc6731d90cc7fb6d62d66135f85a33dd2 upstream. The correct behaviour for NFSv4 sequence IDs is to wrap around to the value 0 after 0x. See

[PATCH 4.9 046/101] PCI: Add ACS quirk for Intel 7th & 8th Gen mobile

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alex Williamson commit e8440f4bfedc623bee40c84797ac78d9303d0db6 upstream. The specification update indicates these have the same errata for implementing non-standard ACS capabilities.

[PATCH 4.9 077/101] perf intel-pt: Fix decoding to accept CBR between FUP and corresponding TIP

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit bd2e49ec48feb1855f7624198849eea4610e2286 upstream. It is possible to have a CBR packet between a FUP packet and corresponding TIP packet. Stop treating it as an error.

[PATCH 4.9 087/101] video: uvesafb: Fix integer overflow in allocation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 9f645bcc566a1e9f921bdae7528a01ced5bc3713 upstream. cmap->len can get close to INT_MAX/2, allowing for an integer overflow in allocation. This uses kmalloc_array() instead to

[PATCH 4.9 077/101] perf intel-pt: Fix decoding to accept CBR between FUP and corresponding TIP

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit bd2e49ec48feb1855f7624198849eea4610e2286 upstream. It is possible to have a CBR packet between a FUP packet and corresponding TIP packet. Stop treating it as an error.

[PATCH 4.9 087/101] video: uvesafb: Fix integer overflow in allocation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 9f645bcc566a1e9f921bdae7528a01ced5bc3713 upstream. cmap->len can get close to INT_MAX/2, allowing for an integer overflow in allocation. This uses kmalloc_array() instead to

[PATCH 4.9 089/101] pwm: lpss: platform: Save/restore the ctrl register over a suspend/resume

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 1d375b58c12f08d8570b30b865def4734517f04f upstream. On some devices the contents of the ctrl register get lost over a suspend/resume and the PWM comes back up disabled

[PATCH 4.9 089/101] pwm: lpss: platform: Save/restore the ctrl register over a suspend/resume

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 1d375b58c12f08d8570b30b865def4734517f04f upstream. On some devices the contents of the ctrl register get lost over a suspend/resume and the PWM comes back up disabled

[PATCH 4.9 091/101] mm: fix devmem_is_allowed() for sub-page System RAM intersections

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 2bdce74412c249ac01dfe36b6b0043ffd7a5361e upstream. Hussam reports: I was poking around and for no real reason, I did cat /dev/mem and strings /dev/mem. Then I saw

[PATCH 4.9 091/101] mm: fix devmem_is_allowed() for sub-page System RAM intersections

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 2bdce74412c249ac01dfe36b6b0043ffd7a5361e upstream. Hussam reports: I was poking around and for no real reason, I did cat /dev/mem and strings /dev/mem. Then I saw

[PATCH 4.9 093/101] udf: Detect incorrect directory size

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit fa65653e575fbd958bdf5fb9c4a71a324e39510d upstream. Detect when a directory entry is (possibly partially) beyond directory size and return EIO in that case since it means the

[PATCH 4.9 096/101] Input: elantech - fix V4 report decoding for module with middle key

4.9-stable review patch. If anyone has any objections, please let me know. -- From: ??? commit e0ae2519ca004a628fa55aeef969c37edce522d3 upstream. Some touchpad has middle key and it will be indicated in bit 2 of packet[0]. We need to fix V4 formation's byte mask to prevent

[PATCH 4.9 094/101] Input: elan_i2c_smbus - fix more potential stack buffer overflows

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 50fc7b61959af4b95fafce7fe5dd565199e0b61a upstream. Commit 40f7090bb1b4 ("Input: elan_i2c_smbus - fix corrupted stack") fixed most of the functions using

[PATCH 4.9 092/101] xen: Remove unnecessary BUG_ON from __unbind_from_irq()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Boris Ostrovsky commit eef04c7b3786ff0c9cb1019278b6c6c2ea0ad4ff upstream. Commit 910f8befdf5b ("xen/pirq: fix error path cleanup when binding MSIs") fixed a couple of errors in error cleanup

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