[PATCH 4.19 85/90] mac80211: drop robust management frames from unknown TA

2019-06-24 Thread Greg Kroah-Hartman
From: Johannes Berg commit 588f7d39b3592a36fb7702ae3b8bdd9be4621e2f upstream. When receiving a robust management frame, drop it if we don't have rx->sta since then we don't have a security association and thus couldn't possibly validate the frame. Cc: sta...@vger.kernel.org Signed-off-by: Johan

[PATCH 4.19 89/90] mac80211: Do not use stack memory with scatterlist for GMAC

2019-06-24 Thread Greg Kroah-Hartman
From: Jouni Malinen commit a71fd9dac23613d96ba3c05619a8ef4fd6cdf9b9 upstream. ieee80211_aes_gmac() uses the mic argument directly in sg_set_buf() and that does not allow use of stack memory (e.g., BUG_ON() is hit in sg_set_buf() with CONFIG_DEBUG_SG). BIP GMAC TX side is fine for this since it c

[PATCH 5.1 012/121] usb: xhci: Dont try to recover an endpoint if port is in error state.

2019-06-24 Thread Greg Kroah-Hartman
From: Mathias Nyman commit b8c3b718087bf7c3c8e388eb1f72ac1108a4926e upstream. A USB3 device needs to be reset and re-enumarated if the port it connects to goes to a error state, with link state inactive. There is no use in trying to recover failed transactions by resetting endpoints at this sta

[PATCH 5.1 014/121] cifs: fix GlobalMid_Lock bug in cifs_reconnect

2019-06-24 Thread Greg Kroah-Hartman
From: Ronnie Sahlberg commit 61cabc7b0a5cf0d3c532cfa96594c801743fe7f6 upstream. We can not hold the GlobalMid_Lock spinlock during the dfs processing in cifs_reconnect since it invokes things that may sleep and thus trigger : BUG: sleeping function called from invalid context at kernel/locking/

[PATCH 5.1 018/121] IB/hfi1: Correct tid qp rcd to match verbs context

2019-06-24 Thread Greg Kroah-Hartman
From: Mike Marciniszyn commit cc78076af14e1478c1a8fb18997674b5f8cbe3c8 upstream. The qp priv rcd pointer doesn't match the context being used for verbs causing issues when 9B and kdeth packets are processed by different receive contexts and hence different CPUs. When running on different CPUs t

[PATCH 5.1 015/121] IB/hfi1: Validate fault injection opcode user input

2019-06-24 Thread Greg Kroah-Hartman
From: Kaike Wan commit 5f90677ed31963abb184ee08ebee4a4a68225dd8 upstream. The opcode range for fault injection from user should be validated before it is applied to the fault->opcodes[] bitmap to avoid out-of-bound error. Cc: Fixes: a74d5307caba ("IB/hfi1: Rework fault injection machinery") Re

[PATCH 5.1 019/121] IB/hfi1: Silence txreq allocation warnings

2019-06-24 Thread Greg Kroah-Hartman
From: Mike Marciniszyn commit 3230f4a8d44e4a0bb7afea814b280b5129521f52 upstream. The following warning can happen when a memory shortage occurs during txreq allocation: [10220.939246] SLUB: Unable to allocate memory on node -1, gfp=0xa20(GFP_ATOMIC) [10220.939246] Hardware name: Intel Corporati

[PATCH 5.1 017/121] IB/hfi1: Avoid hardlockup with flushlist_lock

2019-06-24 Thread Greg Kroah-Hartman
From: Mike Marciniszyn commit cf131a81967583ae737df6383a0893b9fee75b4e upstream. Heavy contention of the sde flushlist_lock can cause hard lockups at extreme scale when the flushing logic is under stress. Mitigate by replacing the item at a time copy to the local list with an O(1) list_splice_i

[PATCH 5.1 021/121] iio: temperature: mlx90632 Relax the compatibility check

2019-06-24 Thread Greg Kroah-Hartman
From: Crt Mori commit 389fc70b60f534d679aea9a3f05146040ce20d77 upstream. Register EE_VERSION contains mixture of calibration information and DSP version. So far, because calibrations were definite, the driver compatibility depended on whole contents, but in the newer production process the calib

[PATCH 5.1 002/121] mmc: sdhci: sdhci-pci-o2micro: Correctly set bus width when tuning

2019-06-24 Thread Greg Kroah-Hartman
From: Raul E Rangel commit 0f7b79a44e7d7dd3ef1f59758c1a341f217ff5e5 upstream. The O2Micro controller only supports tuning at 4-bits. So the host driver needs to change the bus width while tuning and then set it back when done. There was a bug in the original implementation in that mmc->ios.bus_

[PATCH 4.19 90/90] x86/resctrl: Dont stop walking closids when a locksetup group is found

2019-06-24 Thread Greg Kroah-Hartman
From: James Morse commit 87d3aa28f345bea77c396855fa5d5fec4c24461f upstream. When a new control group is created __init_one_rdt_domain() walks all the other closids to calculate the sets of used and unused bits. If it discovers a pseudo_locksetup group, it breaks out of the loop. This means any

[PATCH 5.1 001/121] tracing: Silence GCC 9 array bounds warning

2019-06-24 Thread Greg Kroah-Hartman
From: Miguel Ojeda commit 0c97bf863efce63d6ab7971dad811601e6171d2f upstream. Starting with GCC 9, -Warray-bounds detects cases when memset is called starting on a member of a struct but the size to be cleared ends up writing over further members. Such a call happens in the trace code to clear,

[PATCH 5.1 027/121] apparmor: reset pos on failure to unpack for various functions

2019-06-24 Thread Greg Kroah-Hartman
From: Mike Salvatore commit 156e42996bd84eccb6acf319f19ce0cb140d00e3 upstream. Each function that manipulates the aa_ext struct should reset it's "pos" member on failure. This ensures that, on failure, no changes are made to the state of the aa_ext struct. There are paths were elements are opti

[PATCH 5.1 025/121] apparmor: fix PROFILE_MEDIATES for untrusted input

2019-06-24 Thread Greg Kroah-Hartman
From: John Johansen commit 23375b13f98c5464c2b4d15f983cc062940f1f4e upstream. While commit 11c236b89d7c2 ("apparmor: add a default null dfa") ensure every profile has a policy.dfa it does not resize the policy.start[] to have entries for every possible start value. Which means PROFILE_MEDIATES i

Re: [PATCH] x86/mm: Handle physical-virtual alignment mismatch in phys_p4d_init()

2019-06-24 Thread Baoquan He
On 06/21/19 at 01:54pm, Kirill A. Shutemov wrote: > > The code block as below is to zero p4d entries which are not coverred by > > the current memory range, and if haven't been mapped already. It's > > clearred away in this patch, could you also mention it in log, and tell > > why it doesn't matter

[PATCH 5.1 008/121] mmc: core: Prevent processing SDIO IRQs when the card is suspended

2019-06-24 Thread Greg Kroah-Hartman
From: Ulf Hansson commit 83293386bc95cf5e9f0c0175794455835bd1cb4a upstream. Processing of SDIO IRQs must obviously be prevented while the card is system suspended, otherwise we may end up trying to communicate with an uninitialized SDIO card. Reports throughout the years shows that this is not

[PATCH 5.1 024/121] Input: silead - add MSSL0017 to acpi_device_id

2019-06-24 Thread Greg Kroah-Hartman
From: Daniel Smith commit 0e658060e5fc50dc282885dc424a94b5d95547e5 upstream. On Chuwi Hi10 Plus, the Silead device id is MSSL0017. Signed-off-by: Daniel Smith Reviewed-by: Hans de Goede Cc: sta...@vger.kernel.org Signed-off-by: Dmitry Torokhov Signed-off-by: Greg Kroah-Hartman --- drivers

[PATCH 5.1 005/121] mmc: mediatek: fix SDIO IRQ detection issue

2019-06-24 Thread Greg Kroah-Hartman
From: jjian zhou commit 20314ce30af197963b0c239f0952db6aaef73f99 upstream. If cmd19 timeout or response crcerr occurs during execute_tuning(), it need invoke msdc_reset_hw(). Otherwise SDIO IRQ can't be detected. Signed-off-by: jjian zhou Signed-off-by: Chaotian Jing Signed-off-by: Yong Mao

[PATCH 5.1 020/121] iio: imu: st_lsm6dsx: fix PM support for st_lsm6dsx i2c controller

2019-06-24 Thread Greg Kroah-Hartman
From: Lorenzo Bianconi commit bce0d57db388cdb1c1931d0aa7d31c77b590e0f0 upstream. Properly suspend/resume i2c slaves connected to st_lsm6dsx master controller if the CPU goes in suspended state Fixes: c91c1c844ebd ("imu: st_lsm6dsx: add i2c embedded controller support") Signed-off-by: Lorenzo Bi

[PATCH 5.1 007/121] mmc: core: Add sdio_retune_hold_now() and sdio_retune_release()

2019-06-24 Thread Greg Kroah-Hartman
From: Douglas Anderson commit b4c9f938d542d5f88c501744d2d12fad4fd2915f upstream. We want SDIO drivers to be able to temporarily stop retuning when the driver knows that the SDIO card is not in a state where retuning will work (maybe because the card is asleep). We'll move the relevant functions

[PATCH 5.1 009/121] scsi: ufs: Avoid runtime suspend possibly being blocked forever

2019-06-24 Thread Greg Kroah-Hartman
From: Stanley Chu commit 24e2e7a19f7e4b83d0d5189040d997bce3596473 upstream. UFS runtime suspend can be triggered after pm_runtime_enable() is invoked in ufshcd_pltfrm_init(). However if the first runtime suspend is triggered before binding ufs_hba structure to ufs device structure via platform_s

[PATCH 5.1 030/121] brcmfmac: sdio: Dont tune while the card is off

2019-06-24 Thread Greg Kroah-Hartman
From: Douglas Anderson commit 65dade6044079a5c206fd1803642ff420061417a upstream. When Broadcom SDIO cards are idled they go to sleep and a whole separate subsystem takes over their SDIO communication. This is the Always-On-Subsystem (AOS) and it can't handle tuning requests. Specifically, as t

[PATCH 5.1 033/121] dmaengine: jz4780: Fix transfers being ACKed too soon

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 4e4106f5e942bff65548e82fc330d40385c89220 ] When a multi-descriptor DMA transfer is in progress, the "IRQ pending" flag will apparently be set for that channel as soon as the last descriptor loads, way before the IRQ actually happens. This behaviour has been observed on the JZ4725

[PATCH 5.1 031/121] lkdtm/usercopy: Moves the KERNEL_DS test to non-canonical

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 2bf8496f6e9b7e9a557f65eb95eab16fea7958c7 ] The prior implementation of the KERNEL_DS fault checking would work on any unmapped kernel address, but this was narrowed to the non-canonical range instead. This adjusts the LKDTM test to match. Fixes: 00c42373d397 ("x86-64: add warnin

[PATCH 5.1 028/121] Revert "brcmfmac: disable command decode in sdio_aos"

2019-06-24 Thread Greg Kroah-Hartman
From: Douglas Anderson commit abdd5dcc00207e7c38680f3754d1bfffafff1093 upstream. This reverts commit 29f6589140a10ece8c1d73f58043ea5b3473ab3e. After that patch landed I find that my kernel log on rk3288-veyron-minnie and rk3288-veyron-speedy is filled with: brcmfmac: brcmf_sdio_bus_sleep: error

[PATCH 5.1 048/121] parisc: Fix compiler warnings in float emulation code

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 6b98d9134e14f5ef4bcf64b27eedf484ed19a1ec ] Avoid such compiler warnings: arch/parisc/math-emu/cnv_float.h:71:27: warning: ‘<<’ in boolean context, did you mean ‘<’ ? [-Wint-in-bool-context] ((Dintp1(dint_valueA) << 33 - SGL_EXP_LENGTH) || Dintp2(dint_valueB)) arch/parisc/ma

[PATCH 5.1 055/121] crypto: hmac - fix memory leak in hmac_init_tfm()

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 7829a0c1cb9c80debfb4fdb49b4d90019f2ea1ac ] When I added the sanity check of 'descsize', I missed that the child hash tfm needs to be freed if the sanity check fails. Of course this should never happen, hence the use of WARN_ON(), but it should be fixed. Fixes: e1354400b25d ("cr

[PATCH 5.1 057/121] kselftest/cgroup: fix unexpected testing failure on test_memcontrol

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit f6131f28057d4fd8922599339e701a2504e0f23d ] The cgroup testing relies on the root cgroup's subtree_control setting, If the 'memory' controller isn't set, all test cases will be failed as following: $ sudo ./test_memcontrol not ok 1 test_memcg_subtree_control not ok 2 test_memcg_c

[PATCH 5.1 047/121] parport: Fix mem leak in parport_register_dev_model

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 1c7ebeabc9e5ee12e42075a597de40fdb9059530 ] BUG: memory leak unreferenced object 0x8881df48cda0 (size 16): comm "syz-executor.0", pid 5077, jiffies 4295994670 (age 22.280s) hex dump (first 16 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b

[PATCH 5.1 034/121] dmaengine: dw-axi-dmac: fix null dereference when pointer first is null

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 0788611c9a0925c607de536b2449de5ed98ef8df ] In the unlikely event that axi_desc_get returns a null desc in the very first iteration of the while-loop the error exit path ends up calling axi_desc_put on a null pointer 'first' and this causes a null pointer dereference. Fix this by

[PATCH 5.1 049/121] habanalabs: fix bug in checking huge page optimization

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit d724170160f800fa8dfd3c0cdebb8b093570b504 ] This patch fix a bug in the mmu code that checks whether we can use huge page mappings for host pages. The code is supposed to enable huge page mappings only if ALL DMA addresses are aligned to 2MB AND the number of pages in each DMA ch

[PATCH 5.1 052/121] IB/{qib, hfi1, rdmavt}: Correct ibv_devinfo max_mr value

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 35164f5259a47ea756fa1deb3e463ac2a4f10dc9 ] The command 'ibv_devinfo -v' reports 0 for max_mr. Fix by assigning the query values after the mr lkey_table has been built rather than early on in the driver. Fixes: 7b1e2099adc8 ("IB/rdmavt: Move memory registration into rdmavt") Rev

[PATCH 5.1 050/121] IB/rdmavt: Fix alloc_qpn() WARN_ON()

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 2abae62a26a265129b364d8c1ef3be55e2c01309 ] The qpn allocation logic has a WARN_ON() that intends to detect the use of an index that will introduce bits in the lower order bits of the QOS bits in the QPN. Unfortunately, it has the following bugs: - it misfires when wrapping QPN a

[PATCH 5.1 042/121] ARC: [plat-hsdk]: Add missing FIFO size entry in GMAC node

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 4c70850aeb2e40016722cd1abd43c679666d3ca0 ] Add the binding for RX/TX fifo size of GMAC node. Cc: Joao Pinto Cc: Rob Herring Cc: Mark Rutland Cc: Vineet Gupta Tested-by: Eugeniy Paltsev Acked-by: Alexey Brodkin Signed-off-by: Jose Abreu Signed-off-by: Vineet Gupta Signed-

[PATCH 5.1 053/121] IB/hfi1: Validate page aligned for a given virtual address

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 97736f36dbebf2cda2799db3b54717ba5b388255 ] User applications can register memory regions for TID buffers that are not aligned on page boundaries. Hfi1 is expected to pin those pages in memory and cache the pages with mmu_rb. The rb tree will fail to insert pages that are not alig

[PATCH 5.1 054/121] MIPS: uprobes: remove set but not used variable epc

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit f532beeeff0c0a3586cc15538bc52d249eb19e7c ] Fixes gcc '-Wunused-but-set-variable' warning: arch/mips/kernel/uprobes.c: In function 'arch_uprobe_pre_xol': arch/mips/kernel/uprobes.c:115:17: warning: variable 'epc' set but not used [-Wunused-but-set-variable] It's never used sinc

[PATCH 5.1 051/121] IB/hfi1: Insure freeze_work work_struct is canceled on shutdown

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 6d517353c70bb0818b691ca003afdcb5ee5ea44e ] By code inspection, the freeze_work is never canceled. Fix by adding a cancel_work_sync in the shutdown path to insure it is no longer running. Fixes: 7724105686e7 ("IB/hfi1: add driver files") Reviewed-by: Michael J. Ruhl Reviewed-by

[PATCH 5.1 056/121] xtensa: Fix section mismatch between memblock_reserve and mem_reserve

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit adefd051a6707a6ca0ebad278d3c1c05c960fc3b ] Since commit 9012d011660ea5cf2 ("compiler: allow all arches to enable CONFIG_OPTIMIZE_INLINING"), xtensa:tinyconfig fails to build with section mismatch errors. WARNING: vmlinux.o(.text.unlikely+0x68): Section mismatch in reference

[PATCH 5.1 043/121] MIPS: mark ginvt() as __always_inline

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 6074c33c6b2eabc70867ef76d57ca256e9ea9da7 ] To meet the 'i' (immediate) constraint for the asm operands, this function must be always inlined. Signed-off-by: Masahiro Yamada Signed-off-by: Paul Burton Cc: linux-m...@vger.kernel.org Cc: Ralf Baechle Cc: James Hogan Cc: linux-k

[PATCH 5.1 004/121] mmc: mediatek: fix SDIO IRQ interrupt handle flow

2019-06-24 Thread Greg Kroah-Hartman
From: jjian zhou commit 8a5df8ac628f4febea1e6cd3044bff2d536dd096 upstream. SDIO IRQ is triggered by low level. It need disable SDIO IRQ detected function. Otherwise the interrupt register can't be cleared. It will process the interrupt more. Signed-off-by: Jjian Zhou Signed-off-by: Chaotian Ji

[PATCH 5.1 045/121] fpga: dfl: afu: Pass the correct device to dma_mapping_error()

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 13069847a475b60069918dc9971f5adb42811ce3 ] dma_mapping_error() was being called on a different device struct than what was passed to map/unmap. Besides rendering the error checking ineffective, it caused a debug splat with CONFIG_DMA_API_DEBUG. Signed-off-by: Scott Wood Acked-

Re: x86: Spurious vectors not handled robustly

2019-06-24 Thread Thomas Gleixner
Jan, On Mon, 24 Jun 2019, Jan Kiszka wrote: > probably since "x86: Avoid building unused IRQ entry stubs" (2414e021ac8d), > the kernel can no longer tell spurious IRQs by the APIC apart from spuriously > triggered unused vectors. Err. It does. > We've managed to trigger such a cause with the Jai

[PATCH 5.1 003/121] mmc: sdhi: disallow HS400 for M3-W ES1.2, RZ/G2M, and V3H

2019-06-24 Thread Greg Kroah-Hartman
From: Wolfram Sang commit 97bf85b6ec9e6597ce81c79b26a28f7918fc4eaf upstream. Our HW engineers informed us that HS400 is not working on these SoC revisions. Fixes: 0f4e2054c971 ("mmc: renesas_sdhi: disable HS400 on H3 ES1.x and M3-W ES1.[012]") Signed-off-by: Wolfram Sang Reviewed-by: Geert Uy

[PATCH 5.1 000/121] 5.1.15-stable review

2019-06-24 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.15 release. There are 121 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 Wed 26 Jun 2019 09:22:03 AM UTC. Anything rec

Re: [PATCH v2 12/28] drivers: Introduce class_find_device_by_name() helper

2019-06-24 Thread Alexandre Belloni
On 14/06/2019 18:54:07+0100, Suzuki K Poulose wrote: > Add a new wrapper for class_find_device() to search for devices > by name and convert the existing users to use the new helper. > > Cc: Alexander Shishkin > Cc: Maxime Coquelin > Cc: Alessandro Zummo > Cc: Alexander Aring > Cc: Alexandre B

[PATCH 5.1 044/121] fpga: stratix10-soc: fix use-after-free on s10_init()

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit f5dd87326fefe42a4b1a4b1a1a695060c33a88d6 ] The refcount of fw_np has already been decreased by of_find_matching_node() so it shouldn't be used anymore. This patch adds an of_node_get() before of_find_matching_node() to avoid the use-after-free problem. Fixes: e7eef1d7633a ("fpga

[PATCH 5.1 029/121] brcmfmac: sdio: Disable auto-tuning around commands expected to fail

2019-06-24 Thread Greg Kroah-Hartman
From: Douglas Anderson commit 2de0b42da263c97d330d276f5ccf7c4470e3324f upstream. There are certain cases, notably when transitioning between sleep and active state, when Broadcom SDIO WiFi cards will produce errors on the SDIO bus. This is evident from the source code where you can see that we

[PATCH 5.1 046/121] fpga: dfl: Add lockdep classes for pdata->lock

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit dfe3de8d397bf878b31864d4e489d41118ec475f ] struct dfl_feature_platform_data (and it's mutex) is used by both fme and port devices, and when lockdep is enabled it complains about nesting between these locks. Tell lockdep about the difference so it can track each class separately.

[PATCH 5.1 006/121] mmc: core: API to temporarily disable retuning for SDIO CRC errors

2019-06-24 Thread Greg Kroah-Hartman
From: Douglas Anderson commit 0a55f4ab9678413a01e740c86e9367ba0c612b36 upstream. Normally when the MMC core sees an "-EILSEQ" error returned by a host controller then it will trigger a retuning of the card. This is generally a good idea. However, if a command is expected to sometimes cause tra

[PATCH 5.1 026/121] apparmor: enforce nullbyte at end of tag string

2019-06-24 Thread Greg Kroah-Hartman
From: Jann Horn commit 8404d7a674c49278607d19726e0acc0cae299357 upstream. A packed AppArmor policy contains null-terminated tag strings that are read by unpack_nameX(). However, unpack_nameX() uses string functions on them without ensuring that they are actually null-terminated, potentially lead

[PATCH 5.1 023/121] Input: uinput - add compat ioctl number translation for UI_*_FF_UPLOAD

2019-06-24 Thread Greg Kroah-Hartman
From: Andrey Smirnov commit 7c7da40da1640ce6814dab1e8031b44e19e5a3f6 upstream. In the case of compat syscall ioctl numbers for UI_BEGIN_FF_UPLOAD and UI_END_FF_UPLOAD need to be adjusted before being passed on uinput_ioctl_handler() since code built with -m32 will be passing slightly different v

Re: [PATCH v2 0/3] DCMI bridge support

2019-06-24 Thread Hugues FRUCHET
Hi Sakari, > - Where's the sub-device representing the bridge itself? This is pointed by [1]: drivers/media/i2c/st-mipid02.c > - As the driver becomes MC-centric, crop configuration takes place through > V4L2 sub-device interface, not through the video device node. > - Same goes for accessi

[PATCH 5.1 022/121] Input: synaptics - enable SMBus on ThinkPad E480 and E580

2019-06-24 Thread Greg Kroah-Hartman
From: Alexander Mikhaylenko commit 9843f3e08e2144724be7148e08d77a195dea257a upstream. They are capable of using intertouch and it works well with psmouse.synaptics_intertouch=1, so add them to the list. Without it, scrolling and gestures are jumpy, three-finger pinch gesture doesn't work and th

[PATCH 5.1 010/121] usb: chipidea: udc: workaround for endpoint conflict issue

2019-06-24 Thread Greg Kroah-Hartman
From: Peter Chen commit c19dffc0a9511a7d7493ec21019aefd97e9a111b upstream. An endpoint conflict occurs when the USB is working in device mode during an isochronous communication. When the endpointA IN direction is an isochronous IN endpoint, and the host sends an IN token to endpointA on another

[PATCH 5.1 011/121] xhci: detect USB 3.2 capable host controllers correctly

2019-06-24 Thread Greg Kroah-Hartman
From: Mathias Nyman commit ddd57980a0fde30f7b5d14b888a2cc84d01610e8 upstream. USB 3.2 capability in a host can be detected from the xHCI Supported Protocol Capability major and minor revision fields. If major is 0x3 and minor 0x20 then the host is USB 3.2 capable. For USB 3.2 capable hosts set

[PATCH 5.1 013/121] cifs: add spinlock for the openFileList to cifsInodeInfo

2019-06-24 Thread Greg Kroah-Hartman
From: Ronnie Sahlberg commit 487317c99477d00f22370625d53be3239febabbe upstream. We can not depend on the tcon->open_file_lock here since in multiuser mode we may have the same file/inode open via multiple different tcons. The current code is race prone and will crash if one user deletes a file

[PATCH 5.1 016/121] IB/hfi1: Close PSM sdma_progress sleep window

2019-06-24 Thread Greg Kroah-Hartman
From: Mike Marciniszyn commit da9de5f8527f4b9efc82f967d29a583318c034c7 upstream. The call to sdma_progress() is called outside the wait lock. In this case, there is a race condition where sdma_progress() can return false and the sdma_engine can idle. If that happens, there will be no more sdma

[PATCH 5.1 061/121] selftests: vm: install test_vmalloc.sh for run_vmtests

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit bc2cce3f2ebcae02aa4bb29e3436bf75ee674c32 ] Add test_vmalloc.sh to TEST_FILES to make sure it gets installed for run_vmtests. Fixed below error: ./run_vmtests: line 217: ./test_vmalloc.sh: No such file or directory Tested with: make TARGETS=vm install INSTALL_PATH=$PWD/x Signed

[PATCH 4.19 88/90] nl80211: fix station_info pertid memory leak

2019-06-24 Thread Greg Kroah-Hartman
From: Andy Strohman commit f77bf4863dc2218362f4227d56af4a5f3f08830c upstream. When dumping stations, memory allocated for station_info's pertid member will leak if the nl80211 header cannot be added to the sk_buff due to insufficient tail room. I noticed this leak in the kmalloc-2048 cache. Cc

[PATCH 5.1 060/121] userfaultfd: selftest: fix compiler warning

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 98a13a8d253999cf25eb16d901c35fbd2a8455c4 ] Fixes following compiler warning userfaultfd.c: In function ‘usage’: userfaultfd.c:126:2: warning: format not a string literal and no format arguments [-Wformat-security] fprintf(stderr, examples); Signed-off-by: Alakesh Halo

[PATCH 4.19 83/90] SMB3: retry on STATUS_INSUFFICIENT_RESOURCES instead of failing write

2019-06-24 Thread Greg Kroah-Hartman
From: Steve French commit 8d526d62db907e786fd88948c75d1833d82bd80e upstream. Some servers such as Windows 10 will return STATUS_INSUFFICIENT_RESOURCES as the number of simultaneous SMB3 requests grows (even though the client has sufficient credits). Return EAGAIN on STATUS_INSUFFICIENT_RESOURCE

[PATCH 5.1 059/121] kselftest/cgroup: fix incorrect test_core skip

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit f97f3f8839eb9de5843066d80819884f7722c8c5 ] The test_core will skip the test_cgcore_no_internal_process_constraint_on_threads test case if the 'cpu' controller missing in root's subtree_control. In fact we need to set the 'cpu' in subtree_control, to make the testing meaningful.

[PATCH 4.19 53/90] net: ethernet: mediatek: Use hw_feature to judge if HWLRO is supported

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 9e4f56f1a7f3287718d0083b5cb85298dc05a5fd ] Should hw_feature as hardware capability flags to check if hardware LRO got support. Signed-off-by: Mark Lee Signed-off-by: Sean Wang Signed-off-by: David S. Miller Signed-off-by: Sasha Levin --- drivers/net/ethernet/mediatek/mtk_e

[PATCH 4.19 54/90] net: ethernet: mediatek: Use NET_IP_ALIGN to judge if HW RX_2BYTE_OFFSET is enabled

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 880c2d4b2fdfd580ebcd6bb7240a8027a1d34751 ] Should only enable HW RX_2BYTE_OFFSET function in the case NET_IP_ALIGN equals to 2. Signed-off-by: Mark Lee Signed-off-by: Sean Wang Signed-off-by: David S. Miller Signed-off-by: Sasha Levin --- drivers/net/ethernet/mediatek/mtk_e

Re: [RFC PATCH bpf-next] RV32G eBPF JIT

2019-06-24 Thread Björn Töpel
On Sat, 22 Jun 2019 at 00:59, Luke Nelson wrote: > > From: Luke Nelson > Yay! Thanks for working on this! Nice work! > This is an eBPF JIT for RV32G, adapted from the JIT for RV64G. > Any feedback would be greatly appreciated. > > It passes 359 out of 378 tests in test_bpf.ko. The failing tests

Re: [PATCH] drivers: Adjust scope for CONFIG_HAS_IOMEM before devm_platform_ioremap_resource()

2019-06-24 Thread Enrico Weigelt, metux IT consult
On 24.06.19 10:29, Bartosz Golaszewski wrote: > pt., 14 cze 2019 o 18:50 Markus Elfring napisał(a): >> >> From: Markus Elfring >> Date: Fri, 14 Jun 2019 17:45:13 +0200 >> >> Move the preprocessor statement “#ifdef CONFIG_HAS_IOMEM” so that >> the corresponding scope for conditional compilation in

Re: [PATCH] arm64: defconfig: update and enable CONFIG_RANDOMIZE_BASE

2019-06-24 Thread Ard Biesheuvel
On Mon, 24 Jun 2019 at 11:57, Will Deacon wrote: > > Hi Nick, Kees, Ard, > > Thanks for the responses. > > On Fri, Jun 21, 2019 at 01:27:45PM -0700, Nick Desaulniers wrote: > > On Thu, Jun 20, 2019 at 1:17 AM Ard Biesheuvel > > wrote: > > > On Thu, 20 Jun 2019 at 09:47, Will Deacon wrote: > > >

[PATCH 4.19 75/90] ARM: dts: dra76x: Update MMC2_HS200_MANUAL1 iodelay values

2019-06-24 Thread Greg Kroah-Hartman
From: Faiz Abbas commit c3c0b70cd3f801bded7a548198ee1c9851a0ca82 upstream. Update the MMC2_HS200_MANUAL1 iodelay values to match with the latest dra76x data manual[1]. The new iodelay values will have better marginality and should prevent issues in corner cases. Also this particular pinctrl-arr

[PATCH 4.19 87/90] mac80211: handle deauthentication/disassociation from TDLS peer

2019-06-24 Thread Greg Kroah-Hartman
From: Yu Wang commit 79c92ca42b5a3e0ea172ea2ce8df8e125af237da upstream. When receiving a deauthentication/disassociation frame from a TDLS peer, a station should not disconnect the current AP, but only disable the current TDLS link if it's enabled. Without this change, a TDLS issue can be repro

[PATCH 4.19 76/90] ARM: dts: am57xx-idk: Remove support for voltage switching for SD card

2019-06-24 Thread Greg Kroah-Hartman
From: Faiz Abbas commit 88a748419b84187fd1da05637b8e5928b04a1e06 upstream. If UHS speed modes are enabled, a compatible SD card switches down to 1.8V during enumeration. If after this a software reboot/crash takes place and on-chip ROM tries to enumerate the SD card, the difference in IO voltage

[PATCH 4.19 71/90] can: purge socket error queue on sock destruct

2019-06-24 Thread Greg Kroah-Hartman
From: Willem de Bruijn commit fd704bd5ee749d560e86c4f1fd2ef486d8abf7cf upstream. CAN supports software tx timestamps as of the below commit. Purge any queued timestamp packets on socket destroy. Fixes: 51f31cabe3ce ("ip: support for TX timestamps on UDP and RAW sockets") Reported-by: syzbot+a90

[PATCH 4.19 78/90] arm64: ssbd: explicitly depend on

2019-06-24 Thread Greg Kroah-Hartman
From: Anisse Astier commit adeaa21a4b6954e878f3f7d1c5659ed9c1fe567a upstream. Fix ssbd.c which depends implicitly on asm/ptrace.h including linux/prctl.h (through for example linux/compat.h, then linux/time.h, linux/seqlock.h, linux/spinlock.h and linux/irqflags.h), and uses PR_SPEC* defines. T

[PATCH 4.19 50/90] net: hns: Fix loopback test failed at copper ports

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 2e1f164861e500f4e068a9d909bbd3fcc7841483 ] When doing a loopback test at copper ports, the serdes loopback and the phy loopback will fail, because of the adjust link had not finished, and phy not ready. Adds sleep between adjust link and test process to fix it. Signed-off-by: Y

[PATCH 4.19 57/90] drm/arm/hdlcd: Allow a bit of clock tolerance

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 1c810739097fdeb31b393b67a0a1e3d7ffdd9f63 ] On the Arm Juno platform, the HDLCD pixel clock is constrained to 250KHz resolution in order to avoid the tiny System Control Processor spending aeons trying to calculate exact PLL coefficients. This means that modes like my oddball 1600

[PATCH 4.19 63/90] s390/qeth: fix VLAN attribute in bridge_hostnotify udev event

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 335726195e460cb6b3f795b695bfd31f0ea70ef0 ] Enabling sysfs attribute bridge_hostnotify triggers a series of udev events for the MAC addresses of all currently connected peers. In case no VLAN is set for a peer, the device reports the corresponding MAC addresses with VLAN ID 4096.

[PATCH 4.19 65/90] hwmon: (pmbus/core) Treat parameters as paged if on multiple pages

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 4a60570dce658e3f8885bbcf852430b99f65aca5 ] Some chips have attributes which exist on more than one page but the attribute is not presently marked as paged. This causes the attributes to be generated with the same label, which makes it impossible for userspace to tell them apart.

[PATCH 4.19 62/90] net: ipvlan: Fix ipvlan device tso disabled while NETIF_F_IP_CSUM is set

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit ceae266bf0ae6564ac16d086bf749a096fa90ded ] There's some NICs, such as hinic, with NETIF_F_IP_CSUM and NETIF_F_TSO on but NETIF_F_HW_CSUM off. And ipvlan device features will be NETIF_F_TSO on with NETIF_F_IP_CSUM and NETIF_F_IP_CSUM both off as IPVLAN_FEATURES only care about NET

[PATCH 4.19 67/90] nvme: Fix u32 overflow in the number of namespace list calculation

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit c8e8c77b3bdbade6e26e8e76595f141ede12b692 ] The Number of Namespaces (nn) field in the identify controller data structure is defined as u32 and the maximum allowed value in NVMe specification is 0xFFFEUL. This change fixes the possible overflow of the DIV_ROUND_UP() operation

[PATCH 4.19 73/90] powerpc/bpf: use unsigned division instruction for 64-bit operations

2019-06-24 Thread Greg Kroah-Hartman
From: Naveen N. Rao commit 758f2046ea040773ae8ea7f72dd3bbd8fa984501 upstream. BPF_ALU64 div/mod operations are currently using signed division, unlike BPF_ALU32 operations. Fix the same. DIV64 and MOD64 overflow tests pass with this fix. Fixes: 156d0e290e969c ("powerpc/ebpf/jit: Implement JIT c

[PATCH 4.19 69/90] can: xilinx_can: use correct bittiming_const for CAN FD core

2019-06-24 Thread Greg Kroah-Hartman
From: Anssi Hannula commit 904044dd8fff43e289c11a2f90fa532e946a1d8b upstream. Commit 9e5f1b273e6a ("can: xilinx_can: add support for Xilinx CAN FD core") added a new can_bittiming_const structure for CAN FD cores that support larger values for tseg1, tseg2, and sjw than previous Xilinx CAN cores

[PATCH 4.19 40/90] IB/hfi1: Insure freeze_work work_struct is canceled on shutdown

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 6d517353c70bb0818b691ca003afdcb5ee5ea44e ] By code inspection, the freeze_work is never canceled. Fix by adding a cancel_work_sync in the shutdown path to insure it is no longer running. Fixes: 7724105686e7 ("IB/hfi1: add driver files") Reviewed-by: Michael J. Ruhl Reviewed-by

[PATCH 4.19 60/90] scsi: ufs: Check that space was properly alloced in copy_query_response

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 1c90836f70f9a8ef7b7ad9e1fdd8961903e6ced6 ] struct ufs_dev_cmd is the main container that supports device management commands. In the case of a read descriptor request, we assume that the proper space was allocated in dev_cmd to hold the returning descriptor. This is no longer tr

[PATCH 5.1 062/121] nds32: Avoid IEX status being incorrectly modified

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit ed32949e0acb73e7bc054bb02e0453d4d561ceda ] In order for kernel to capture each denormalized output, the UDF trapping enable bit is always raised in $fpcsr. Because underflow case will issue not an underflow exception but also an inexact exception, it causes that the IEX, IEX cumu

[PATCH 5.1 063/121] net: dsa: mv88e6xxx: avoid error message on remove from VLAN 0

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 62394708f3e01c9f2be6be74eb6305bae1ed924f ] When non-bridged, non-vlan'ed mv88e6xxx port is moving down, error message is logged: failed to kill vid 0081/0 for device eth_cu_1000_4 This is caused by call from __vlan_vid_del() with vin set to zero, over call chain this results in

[PATCH 4.19 61/90] scsi: smartpqi: unlock on error in pqi_submit_raid_request_synchronous()

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit cc8f52609bb4177febade24d11713e20c0893b0a ] We need to drop the "ctrl_info->sync_request_sem" lock before returning. Fixes: 6c223761eb54 ("smartpqi: initial commit of Microsemi smartpqi driver") Signed-off-by: Dan Carpenter Acked-by: Don Brace Signed-off-by: Martin K. Petersen

[PATCH 4.19 42/90] IB/hfi1: Validate page aligned for a given virtual address

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 97736f36dbebf2cda2799db3b54717ba5b388255 ] User applications can register memory regions for TID buffers that are not aligned on page boundaries. Hfi1 is expected to pin those pages in memory and cache the pages with mmu_rb. The rb tree will fail to insert pages that are not alig

[PATCH 4.19 47/90] kselftest/cgroup: fix incorrect test_core skip

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit f97f3f8839eb9de5843066d80819884f7722c8c5 ] The test_core will skip the test_cgcore_no_internal_process_constraint_on_threads test case if the 'cpu' controller missing in root's subtree_control. In fact we need to set the 'cpu' in subtree_control, to make the testing meaningful.

[PATCH 4.19 11/90] s390/ap: rework assembler functions to use unions for in/out register variables

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 159491f3b509bd8101199944dc7b0673b881c734 ] The inline assembler functions ap_aqic() and ap_qact() used two variables declared on the very same register. One variable was for input only, the other for output. Looks like newer versions of the gcc don't like this. Anyway it is a bet

[PATCH 4.19 12/90] mmc: sdhci: sdhci-pci-o2micro: Correctly set bus width when tuning

2019-06-24 Thread Greg Kroah-Hartman
From: Raul E Rangel commit 0f7b79a44e7d7dd3ef1f59758c1a341f217ff5e5 upstream. The O2Micro controller only supports tuning at 4-bits. So the host driver needs to change the bus width while tuning and then set it back when done. There was a bug in the original implementation in that mmc->ios.bus_

[PATCH 5.1 064/121] net: hns: Fix loopback test failed at copper ports

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 2e1f164861e500f4e068a9d909bbd3fcc7841483 ] When doing a loopback test at copper ports, the serdes loopback and the phy loopback will fail, because of the adjust link had not finished, and phy not ready. Adds sleep between adjust link and test process to fix it. Signed-off-by: Y

[PATCH 4.19 14/90] mmc: core: Add sdio_retune_hold_now() and sdio_retune_release()

2019-06-24 Thread Greg Kroah-Hartman
From: Douglas Anderson commit b4c9f938d542d5f88c501744d2d12fad4fd2915f upstream. We want SDIO drivers to be able to temporarily stop retuning when the driver knows that the SDIO card is not in a state where retuning will work (maybe because the card is asleep). We'll move the relevant functions

[PATCH 4.19 10/90] s390/jump_label: Use "jdd" constraint on gcc9

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 146448524bddbf6dfc62de31957e428de001cbda ] [heiko.carst...@de.ibm.com]: - Laura Abbott reported that the kernel doesn't build anymore with gcc 9, due to the "X" constraint. Ilya provided the gcc 9 patch "S/390: Introduce jdd constraint" which introduces the new "jdd" constrai

[PATCH 4.19 01/90] tracing: Silence GCC 9 array bounds warning

2019-06-24 Thread Greg Kroah-Hartman
From: Miguel Ojeda commit 0c97bf863efce63d6ab7971dad811601e6171d2f upstream. Starting with GCC 9, -Warray-bounds detects cases when memset is called starting on a member of a struct but the size to be cleared ends up writing over further members. Such a call happens in the trace code to clear,

RE: [PATCH v4 2/5] net: macb: add support for sgmii MAC-PHY interface

2019-06-24 Thread Parshuram Raju Thombare
>> >I still don't think this makes much sense, splitting the interface >> > configuration between here and below. >> Do you mean splitting mac_config in two *_configure functions ? >> This was done as per Andrew's suggestion to make code mode readable >> and easy to manage by splitting MAC configur

[PATCH 5.1 069/121] selftests: set sysctl bc_forwarding properly in router_broadcast.sh

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 67c0aaa1eaec60e9dab301012bdebe6726ae04bd ] sysctl setting bc_forwarding for $rp2 is needed when ping_test_from h2, otherwise the bc packets from $rp2 won't be forwarded. This patch is to add this setting for $rp2. Also, as ping_test_from does grep "$from" only, which could match

[PATCH 5.1 068/121] net: ethernet: mediatek: Use NET_IP_ALIGN to judge if HW RX_2BYTE_OFFSET is enabled

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 880c2d4b2fdfd580ebcd6bb7240a8027a1d34751 ] Should only enable HW RX_2BYTE_OFFSET function in the case NET_IP_ALIGN equals to 2. Signed-off-by: Mark Lee Signed-off-by: Sean Wang Signed-off-by: David S. Miller Signed-off-by: Sasha Levin --- drivers/net/ethernet/mediatek/mtk_e

[PATCH 5.1 058/121] kselftest/cgroup: fix unexpected testing failure on test_core

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 00e38a5d753d7788852f81703db804a60a84c26e ] The cgroup testing relys on the root cgroup's subtree_control setting, If the 'memory' controller isn't set, some test cases will be failed as following: $sudo ./test_core not ok 1 test_cgcore_internal_process_constraint ok 2 test_cgco

[PATCH 5.1 066/121] sparc: perf: fix updated event period in response to PERF_EVENT_IOC_PERIOD

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 56cd0aefa475079e9613085b14a0f05037518fed ] The PERF_EVENT_IOC_PERIOD ioctl command can be used to change the sample period of a running perf_event. Consequently, when calculating the next event period, the new period will only be considered after the previous one has overflowed.

[PATCH 5.1 036/121] dmaengine: sprd: Fix the possible crash when getting descriptor status

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 16d0f85e45b99411ac10cb12cdd9279204a72381 ] We will get a NULL virtual descriptor by vchan_find_desc() when the descriptor has been submitted, that will crash the kernel when getting the descriptor status. In this case, since the descriptor has been submitted to process, but it i

[PATCH 5.1 040/121] dmaengine: sprd: Fix the right place to configure 2-stage transfer

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit c434e377dad1dec05cad1870ce21bc539e1e024f ] Move the 2-stage configuration before configuring the link-list mode, since we will use some 2-stage configuration to fill the link-list configuration. Signed-off-by: Eric Long Signed-off-by: Baolin Wang Signed-off-by: Vinod Koul Sig

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