[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 indicate

[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 fix

[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 the

[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 rath

[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 c

[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 rath

[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 ca

[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 obje

[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 statu

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 plannin

[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 https://tools.ietf.

[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. Signed-o

[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. Sig

[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 ca

[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 after

[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 fil

[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 err

[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 i2c_smbus_read_bloc

[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 pa

[PATCH 4.9 099/101] block: Fix transfer when chunk sectors exceeds max

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Keith Busch commit 15bfd21fbc5d35834b9ea383dc458a1f0c9e3434 upstream. A device may have boundary restrictions where the number of sectors between boundaries exceeds its max transfer size. In th

[PATCH 4.9 078/101] perf intel-pt: Fix MTC timing after overflow

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit dd27b87ab5fcf3ea1c060b5e3ab5d31cc78e9f4c upstream. On some platforms, overflows will clear before MTC wraparound, and there is no following TSC/TMA packet. In that case the

[PATCH 4.9 098/101] ALSA: hda/realtek - Add a quirk for FSC ESPRIMO U9210

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 275ec0cb946cb75ac8977f662e608fce92f8b8a8 upstream. Fujitsu Seimens ESPRIMO Mobile U9210 requires the same fixup as H270 for the correct pin configs. Bugzilla: https://bugzi

[PATCH 4.9 097/101] ALSA: hda/realtek - Fix pop noise on Lenovo P50 & co

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit d5a6cabf02210b896a60eee7c04c670ee9ba6dca upstream. Some Lenovo laptops, e.g. Lenovo P50, showed the pop noise at resume or runtime resume. It turned out to be reduced by ap

Re: [PATCH v2 0/3] Add clock driver for Actions S700 SoC

Hi Saravannan, Am 28.06.2018 um 21:18 schrieb Saravanan Sekar: > Changelog v2: > Fixed 0 day compilation warning > Modified existing dts Actions S900 clock bindings common to Actions > Soc family Please post v3 without --in-reply-to. It's becoming messy to read. > This patchset adds clock suppor

[PATCH 4.9 084/101] nfsd: restrict rd_maxcount to svc_max_payload in nfsd_encode_readdir

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Scott Mayhew commit 9c2ece6ef67e9d376f32823086169b489c422ed0 upstream. nfsd4_readdir_rsize restricts rd_maxcount to svc_max_payload when estimating the size of the readdir reply, but nfsd_encod

[PATCH 0/3] cast sizeof to int for comparison

Comparing an int to a size, which is unsigned, causes the int to become unsigned, giving the wrong result. The semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/) // @safe disable not_int2@ int x; position p; binary operator op = {<,<=}; expression e; @@ ( x < 0 |

[PATCH 1/3] Input: elan_i2c_smbus - cast sizeof to int for comparison

Comparing an int to a size, which is unsigned, causes the int to become unsigned, giving the wrong result. i2c_smbus_read_block_data can return the result of i2c_smbus_xfer, whih can return a negative error code. A simplified version of the semantic match that finds this problem is as follows: (h

[PATCH 4.9 076/101] perf intel-pt: Fix sync_switch INTEL_PT_SS_NOT_TRACING

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit dbcb82b93f3e8322891e47472c89e63058b81e99 upstream. sync_switch is a facility to synchronize decoding more closely with the point in the kernel when the context actually swi

[PATCH 4.14 001/157] x86/spectre_v1: Disable compiler optimizations over array_index_mask_nospec()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit eab6870fee877258122a042bfd99ee7908c40280 upstream. Mark Rutland noticed that GCC optimization passes have the potential to elide necessary invocations of the array_index_ma

[PATCH 4.9 085/101] NFSv4: Fix possible 1-byte stack overflow in nfs_idmap_read_and_verify_message

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dave Wysochanski commit d68894800ec5712d7ddf042356f11e36f87d7f78 upstream. In nfs_idmap_read_and_verify_message there is an incorrect sprintf '%d' that converts the __u32 'im_id' from struct id

[PATCH 4.9 082/101] media: cx231xx: Add support for AverMedia DVD EZMaker 7

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit 29e61d6ef061b012d320327af7dbb3990e75be45 upstream. User reports AverMedia DVD EZMaker 7 can be driven by VIDEO_GRABBER. Add the device to the id_table to make it work. Bug

[PATCH 4.14 010/157] serial: sh-sci: Use spin_{try}lock_irqsave instead of open coding version

4.14-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 083/101] media: dvb_frontend: fix locking issues at dvb_frontend_get_event()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit 76d81243a487c09619822ef8e7201a756e58a87d upstream. As warned by smatch: drivers/media/dvb-core/dvb_frontend.c:314 dvb_frontend_get_event() warn: inconsiste

[PATCH 4.14 011/157] signal/xtensa: Consistenly use SIGBUS in do_unaligned_user

4.14-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 SI

[PATCH 4.14 013/157] PM / core: Fix supplier device runtime PM usage counter imbalance

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit 47e5abfb546a3ace23a77453dc2e9db92704c5ac upstream. If a device link is added via device_link_add() by the driver of the link's consumer device, the supplier's runtime

[PATCH 4.14 014/157] PM / OPP: Update voltage in case freq == old_freq

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Waldemar Rymarkiewicz commit c5c2a97b3ac7d1ec19e7cff9e38caca6afefc3de upstream. This commit fixes a rare but possible case when the clk rate is updated without update of the regulator voltage.

[PATCH 4.14 015/157] usb: do not reset if a low-speed or full-speed device timed out

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Maxim Moseychuk commit 6e01827ed93947895680fbdad68c072a0f4e2450 upstream. Some low-speed and full-speed devices (for example, bluetooth) do not have time to initialize. For them, ETIMEDOUT is

[PATCH 4.14 018/157] ASoC: cs35l35: Add use_single_rw to regmap config

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paul Handrigan commit 6a6ad7face95af0b9e6aaf1eb2261eb70240b89b upstream. Add the use_single_rw flag to regmap config since the device does not support bulk transactions over i2c. Signed-off-b

[PATCH 4.14 019/157] ASoC: cirrus: i2s: Fix LRCLK configuration

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Sverdlin commit 2d534113be9a2aa532a1ae127a57e83558aed358 upstream. The bit responsible for LRCLK polarity is i2s_tlrs (0), not i2s_trel (2) (refer to "EP93xx User's Guide"). Previou

Re: [PATCH 3.18 35/85] parisc: Move setup_profiling_timer() out of init section

Hi Greg, On 01.07.2018 18:01, Greg Kroah-Hartman wrote: > 3.18-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Helge Deller > > [ Upstream commit 01f56832cfb6fcc204e7203f46841b6185ebd574 ] I wonder how this patch and patch #22 ([PATCH 3

[PATCH 4.14 021/157] thermal: bcm2835: Stop using printk format %pCr

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit bd2a07f71a1e2e198f8a30cb551d9defe422d83d upstream. Printk format "%pCr" will be removed soon, as clk_get_rate() must not be called in atomic context. Replace it by p

[PATCH 4.14 024/157] ftrace/selftest: Have the reset_trigger code be a bit more careful

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit 756b56a9e832e063edc83be7c3889e98c536dd2b upstream. The trigger code is picky in how it can be disabled as there may be dependencies between different events and

[PATCH 4.14 003/157] x86/mce: Improve error message when kernel cannot recover

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit c7d606f560e4c698884697fef503e4abacdd8c25 upstream. Since we added support to add recovery from some errors inside the kernel in: commit b2f9d678e28c ("x86/mce: Check for faul

[PATCH 4.14 026/157] branch-check: fix long->int truncation when profiling branches

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 2026d35741f2c3ece73c11eb7e4a15d7c2df9ebe upstream. The function __builtin_expect returns long type (see the gcc documentation), and so do macros likely and unlikely. Unf

[PATCH 4.14 025/157] mips: ftrace: fix static function graph tracing

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Matthias Schiffer commit 6fb8656646f996d1eef42e6d56203c4915cb9e08 upstream. ftrace_graph_caller was never run after calling ftrace_trace_function, breaking the function graph tracer. Fix this,

[PATCH 4.14 030/157] fuse: fix congested state leak on aborted connections

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 8a301eb16d99983a4961f884690ec97b92e7dcfe upstream. If a connection gets aborted while congested, FUSE can leave nr_wb_congested[] stuck until reboot causing wait_iff_congested

[PATCH 4.14 027/157] ipmi:bt: Set the timeout before doing a capabilities check

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Corey Minyard commit fe50a7d0393a552e4539da2d31261a59d6415950 upstream. There was one place where the timeout value for an operation was not being set, if a capabilities request was done from

[PATCH 4.14 004/157] x86/mce: Check for alternate indication of machine check recovery on Skylake

4.14-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 so

[PATCH 4.14 031/157] fuse: atomic_o_trunc should truncate pagecache

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit df0e91d488276086bc07da2e389986cae0048c37 upstream. Fuse has an "atomic_o_trunc" mode, where userspace filesystem uses the O_TRUNC flag in the OPEN request to truncate the

[PATCH 4.14 007/157] x86: Call fixup_exception() before notify_die() in math_error()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Siarhei Liakh commit 3ae6295ccb7cf6d344908209701bad503e40 upstream. fpu__drop() has an explicit fwait which under some conditions can trigger a fixable FPU exception while in kernel. Thus,

[PATCH 4.14 005/157] x86/mce: Fix incorrect "Machine check from unknown source" message

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit 40c36e2741d7fe1e66d6ec55477ba5fd19c9c5d2 upstream. Some injection testing resulted in the following console log: mce: [Hardware Error]: CPU 22: Machine Check Exception: f B

Re: [PATCH v2 3/3] dt-bindings: clock: Modify Actions Soc clock bindings

Hi, Am 01.07.2018 um 19:37 schrieb Manivannan Sadhasivam: > On Sun, Jul 01, 2018 at 07:26:20PM +0200, Saravanan Sekar wrote: >> Hi Mani >> >> >> On 06/30/18 11:32, Manivannan Sadhasivam wrote: >>> Hi Saravanan, >>> >>> I agree with modifying the existing binding to accomodate other >>> SoC's of th

[PATCH 4.14 008/157] m68k/mm: Adjust VM area to be unmapped by gap size for __iounmap()

4.14-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 re

[PATCH 4.14 043/157] soc: rockchip: power-domain: Fix wrong value when power up pd with writemask

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Finley Xiao commit 9e59c5f66c624b43c766a9fe3b2430e0e976bf0e upstream. Solve the pd could only ever turn off but never turn them on again, if the pd registers have the writemask bits. So far t

[PATCH 4.14 044/157] cxl: Disable prefault_mode in Radix mode

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vaibhav Jain commit b6c84ba22ff3a198eb8d5552cf9b8fda1d792e54 upstream. Currently we see a kernel-oops reported on Power-9 while attaching a context to an AFU, with radix-mode and sysfs attr 'p

[PATCH 4.14 000/157] 4.14.53-stable review

This is the start of the stable review cycle for the 4.14.53 release. There are 157 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Tue Jul 3 16:08:21 UTC 2018. Anything recei

[PATCH 4.14 006/157] x86/mce: Do not overwrite MCi_STATUS in mce_no_way_out()

4.14-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 pani

[PATCH 4.14 046/157] ARM: dts: Fix SPI node for Arria10

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thor Thayer commit 975ba94c2c3aca4d9f1ae26f3916d7787495ce86 upstream. Remove the unused bus-num node and change num-chipselect to num-cs to match SPI bindings. Cc: sta...@vger.kernel.org Fixe

[PATCH 4.14 049/157] ARM: dts: socfpga: Fix NAND controller node compatible for Arria10

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dinh Nguyen commit 3877ef7a1ccecaae378c497e1dcddbc2dccb664c upstream. The NAND compatible "denali,denal-nand-dt" property has never been used and is obsolete. Remove it. Cc: sta...@vger.kerne

[PATCH 4.14 050/157] arm64: Fix syscall restarting around signal suppressed by tracer

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Martin commit 0fe42512b2f03f9e5a20b9f55ef1013a68b4cd48 upstream. Commit 17c2895 ("arm64: Abstract syscallno manipulation") abstracts out the pt_regs.syscallno value for a syscall cancelle

[PATCH 4.14 047/157] ARM: dts: socfpga: Fix NAND controller node compatible

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marek Vasut commit d9a695f3c8098ac9684689774a151cff30d8aa25 upstream. The compatible string for the Denali NAND controller is incorrect, fix it by replacing it with one matching the DT binding

[PATCH 4.14 052/157] arm64: mm: Ensure writes to swapper are ordered wrt subsequent cache maintenance

4.14-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.14 051/157] arm64: kpti: Use early_param for kpti= command-line option

4.14-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 non-

[PATCH 4.14 053/157] ARM64: dts: meson: disable sd-uhs modes on the libretech-cc

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jerome Brunet commit d5b4885b1dff72ac670b518cfeaac719d768bd4d upstream. There is a problem with the sd-uhs mode when doing a soft reboot. Switching back from 1.8v to 3.3v messes with the card,

[PATCH 4.14 059/157] IB/qib: Fix DMA api warning with debug kernel

4.14-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 lib/d

[PATCH 4.14 055/157] of: unittest: for strings, account for trailing \0 in property length field

4.14-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 pro

[PATCH 4.14 058/157] tpm: fix race condition in tpm_common_write()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tadeusz Struk commit 3ab2011ea368ec3433ad49e1b9e1c7b70d2e65df upstream. There is a race condition in tpm_common_write function allowing two threads on the same /dev/tpm, or two different appli

Re: [PATCH v2 3/3] dt-bindings: clock: Modify Actions Soc clock bindings

Hi Mani, On 07/01/18 19:37, Manivannan Sadhasivam wrote: On Sun, Jul 01, 2018 at 07:26:20PM +0200, Saravanan Sekar wrote: Hi Mani On 06/30/18 11:32, Manivannan Sadhasivam wrote: Hi Saravanan, I agree with modifying the existing binding to accomodate other SoC's of the same family. But the

[PATCH 4.14 062/157] IB/core: Make testing MR flags for writability a static inline function

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein commit 08bb558ac11ab944e0539e78619d7b4c356278bd upstream. Make the MR writability flags check, which is performed in umem.c, a static inline function in file ib_verbs.h This

[PATCH 4.14 061/157] IB/mlx4: Mark user MR as writable if actual virtual memory is writable

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein commit d8f9cc328c369880e2527e9186d745f2bbf6 upstream. To allow rereg_user_mr to modify the MR from read-only to writable without using get_user_pages again, we needed to d

[PATCH 4.14 066/157] IB/hfi1: Fix fault injection init/exit issues

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mike Marciniszyn commit 8c79d8223bb11b2f005695a32ddd3985de97727c upstream. There are config dependent code paths that expose panics in unload paths both in this file and in debugfs_remove_recu

[PATCH 4.14 065/157] IB/isert: fix T10-pi check mask setting

4.14-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: 38a

[PATCH 4.14 063/157] IB/mlx5: Fetch soft WQEs on fatal error state

4.14-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

Re: [PATCH v2 2/3] clk: actions: Add S700 SoC clock support

On 07/01/18 19:30, Manivannan Sadhasivam wrote: On Sun, Jul 01, 2018 at 07:23:58PM +0200, Saravanan Sekar wrote: On 06/30/18 11:22, Manivannan Sadhasivam wrote: Hi Saravanan, On Thu, Jun 28, 2018 at 09:18:04PM +0200, Saravanan Sekar wrote: Add Actions Semi S700 SoC clock support Signed-o

[PATCH 4.14 064/157] IB/isert: Fix for lib/dma_debug check_sync warning

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alex Estrin commit 763b69654bfb88ea3230d015e7d755ee8339f8ee upstream. The following error message occurs on a target host in a debug build during session login: [ 3524.411874] WARNING: CPU: 5

[PATCH 4.14 068/157] IB/hfi1: Optimize kthread pointer locking when queuing CQ entries

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Sanchez commit af8aab71370a692eaf7e7969ba5b1a455ac20113 upstream. All threads queuing CQ entries on different CQs are unnecessarily synchronized by a spin lock to check if the CQ kth

[PATCH 4.14 067/157] IB/hfi1: Reorder incorrect send context disable

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael J. Ruhl commit a93a0a3231bb1949f4a83b17238f0fa32d6a upstream. User send context integrity bits are cleared before the context is disabled. If the send context is still processing

[PATCH 4.14 069/157] IB/hfi1: Fix user context tail allocation for DMA_RTAIL

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mike Marciniszyn commit 1bc0299d976e000ececc6acd76e33b4582646cb7 upstream. The following code fails to allocate a buffer for the tail address that the hardware DMAs into when the user context

[PATCH 4.14 036/157] powerpc/perf: Fix memory allocation for core-imc based on num_possible_cpus()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Anju T Sudhakar commit d2032678e57fc508d7878307badde8f89b632ba3 upstream. Currently memory is allocated for core-imc based on cpu_present_mask, which has bit 'cpu' set iff cpu is populated. We

[PATCH 4.14 038/157] powerpc/powernv/ioda2: Remove redundant free of TCE pages

4.14-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 pn

[PATCH 4.14 071/157] xprtrdma: Return -ENOBUFS when no pages are available

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Chuck Lever commit a8f688ec437dc2045cc8f0c89fe877d5803850da upstream. The use of -EAGAIN in rpcrdma_convert_iovs() is a latent bug: the transport never calls xprt_write_space() when more pages

[PATCH 4.14 039/157] powerpc/powernv: copy/paste - Mask SO bit in CR

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Haren Myneni commit 75743649064ec0cf5ddd69f240ef23af66dde16e upstream. NX can set the 3rd bit in CR register for XER[SO] (Summary overflow) which is not related to paste request. The current p

[PATCH 4.14 073/157] mtd: cfi_cmdset_0002: Use right chip in do_ppb_xxlock()

4.14-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 stat

[PATCH 4.14 040/157] powerpc/powernv/cpuidle: Init all present cpus for deep states

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Akshay Adiga commit ac9816dcbab53c57bcf1d7b15370b08f1e284318 upstream. Init all present cpus for deep states instead of "all possible" cpus. Init fails if a possible cpu is guarded. Resulting

Re: [PATCH v2 1/3] arm64: dts: actions: Enable clock controller for S700

Hi Mani, On 06/30/18 11:42, Manivannan Sadhasivam wrote: On Thu, Jun 28, 2018 at 09:18:03PM +0200, Saravanan Sekar wrote: Added clock management controller for S700 Signed-off-by: Parthiban Nallathambi Signed-off-by: Saravanan Sekar --- .../boot/dts/actions/s700-cubieboard7.dts | 7

[PATCH 4.14 089/157] X.509: unpack RSA signatureValue field from BIT STRING

4.14-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.14 086/157] MIPS: io: Add barrier after register read in inX()

4.14-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() fu

[PATCH 4.14 094/157] scsi: hpsa: disable device during shutdown

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sinan Kaya commit 0d98ba8d70b0070ac117452ea0b663e26bbf46bf upstream. 'Commit cc27b735ad3a ("PCI/portdrv: Turn off PCIe services during shutdown")' has been added to kernel to shutdown pending

[PATCH 4.14 090/157] Btrfs: fix return value on rename exchange failure

4.14-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 retu

[PATCH 4.14 093/157] mm: fix __gup_device_huge vs unmap

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit a9b6de77b1a3ff729f7bfc54b2e17711776a416c upstream. get_user_pages_fast() for device pages is missing the typical validation that all page references have been taken while t

[PATCH 4.14 074/157] mtd: cfi_cmdset_0002: fix SEGV unlocking multiple chips

4.14-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.14 096/157] scsi: qla2xxx: Mask off Scope bits in retry delay

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Anil Gurumurthy commit 3cedc8797b9c0ffd45a01f849c57c088828b upstream. Some newer target uses "Status Qualifier" response in a returned "Busy Status". This new response code of 0x4001, whic

[PATCH 4.14 101/157] scsi: zfcp: fix missing REC trigger trace on terminate_rport_io for ERP_FAILED

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit d70aab55924b44f213fec2b900b095430b33eec6 upstream. For problem determination we always want to see when we were invoked on the terminate_rport_io callback whether we perfo

[PATCH 4.14 100/157] scsi: zfcp: fix missing REC trigger trace on terminate_rport_io early return

4.14-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. zfcp_get_port_b

[PATCH 4.14 103/157] scsi: zfcp: fix missing REC trigger trace on enqueue without ERP thread

4.14-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.14 075/157] mtd: cfi_cmdset_0002: Fix unlocking requests crossing a chip boudary

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Joakim Tjernlund commit 0cd8116f172eed018907303dbff5c112690eeb91 upstream. The "sector is in requested range" test used to determine whether sectors should be re-locked or not is done on a var

[PATCH 4.14 099/157] scsi: zfcp: fix misleading REC trigger trace where erp_action setup failed

4.14-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 scsi_d

[PATCH 4.14 102/157] scsi: zfcp: fix missing REC trigger trace for all objects in ERP_FAILED

4.14-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

<    1   2   3   4   5   6   7   8   9   >