[PATCH V4 17/25] mmc: mmci: add variant property to define irq pio mask

From: Ludovic Barre This patch allows to define specific pio mask for variants. Needed to support the STM32 sdmmc variant which has some bits with different meaning (bits: 21,20,13,12,9) Signed-off-by: Ludovic Barre --- drivers/mmc/host/mmci.c | 13 +++-- drivers/mmc/host/mmci.h | 5

[PATCH V4 25/25] mmc: mmci: add stm32 sdmmc variant

From: Ludovic Barre This patch adds a stm32 sdmmc variant, rev 1.1. Introduces a new Manufacturer id "0x53, ascii 'S' to define new stm32 sdmmc family with clean range of amba revision/configurations bits (corresponding to sdmmc_ver register with major/minor fields). Add 2 variants properties:

[PATCH V4 21/25] mmc: mmci: add optional reset property

From: Ludovic Barre This patch adds a optional reset management. STM32 sdmmc variant needs to reset hardware block during the power cycle procedure (for re-initialization). Signed-off-by: Ludovic Barre --- drivers/mmc/host/mmci.c | 7 +++ drivers/mmc/host/mmci.h | 2 ++ 2 files changed, 9

[PATCH V4 18/25] mmc: mmci: add variant property to write datactrl before command

From: Ludovic Barre This patch adds a boolean property to allow to write datactrl before to send command, whatever the command type (read or write). Needed to support the STM32 sdmmc variant. Signed-off-by: Ludovic Barre --- drivers/mmc/host/mmci.c | 6 -- drivers/mmc/host/mmci.h | 2 ++

[PATCH V4 14/25] mmc: mmci: expand startbiterr to irqmask and error check

From: Ludovic Barre All variants don't pretend to have a startbiterr. -While data error check, if status register return an error (like MCI_DATACRCFAIL) we must avoid to check MCI_STARTBITERR (if not desired). -expand start_err to MCI_IRQENABLE to avoid to set this bit by default.

[PATCH V4 05/25] mmc: mmci: add prepare/unprepare_data callbacks

From: Ludovic Barre This patch adds prepare/unprepare callbacks to mmci_host_ops. Like this mmci_pre/post_request can be generic, mmci_prepare_data and mmci_unprepare_data provide common next_cookie management. Signed-off-by: Ludovic Barre --- drivers/mmc/host/mmci.c | 101

[PATCH V4 02/25] mmc: mmci: create generic mmci_dma_setup

From: Ludovic Barre This patch creates a generic mmci_dma_setup which calls dma_setup callback of mmci_host_ops and manages common features like use_dma... If there is a fallbacks to pio mode, dma functions must check use_dma. If one of dma channels is not defined (in dma engine config) release

[PATCH V4 03/25] mmc: mmci: introduce dma_priv pointer to mmci_host

From: Ludovic Barre -Introduces dma_priv pointer to define specific needs for each dma engine. This patch is needed to prepare sdmmc variant with internal dma which not use dmaengine API. -Moves next cookie to mmci host structure to share same cookie management between all variants.

[PATCH V4 22/25] mmc: mmci: add clock divider for stm32 sdmmc

From: Ludovic Barre The STM32 sdmmc variant has a different clock divider. Signed-off-by: Ludovic Barre --- drivers/mmc/host/mmci.c | 2 ++ drivers/mmc/host/mmci.h | 2 ++ 2 files changed, 4 insertions(+) diff --git a/drivers/mmc/host/mmci.c b/drivers/mmc/host/mmci.c index 0898cc9..0421e18

[PATCH V4 13/25] mmc: mmci: add datactrl block size variant property

From: Ludovic Barre This patch allows to define a datactrl block size by variant, requested by STM32 sdmmc variant. Signed-off-by: Ludovic Barre --- drivers/mmc/host/mmci.c | 13 +++-- drivers/mmc/host/mmci.h | 2 ++ 2 files changed, 13 insertions(+), 2 deletions(-) diff --git

[PATCH V4 16/25] mmc: mmci: add variant property to define dpsm bit

From: Ludovic Barre This patch adds datactrl variant property to define dpsm enable bit. Needed to support the STM32 variant (STM32 has no dpsm enable bit). Signed-off-by: Ludovic Barre --- drivers/mmc/host/mmci.c | 15 --- drivers/mmc/host/mmci.h | 2 ++ 2 files changed, 14

[PATCH V4 24/25] dt-bindings: mmci: add stm32 sdmmc variant

From: Ludovic Barre This patch adds properties for stm32 sdmmc variant. Signed-off-by: Ludovic Barre Acked-by: Rob Herring --- Documentation/devicetree/bindings/mmc/mmci.txt | 10 ++ 1 file changed, 10 insertions(+) diff --git a/Documentation/devicetree/bindings/mmc/mmci.txt

[PATCH V4 15/25] mmc: mmci: add variant properties to define cpsm & cmdresp bits

From: Ludovic Barre This patch adds command variant properties to define cpsm enable bit and responses. Needed to support the STM32 variant (shift of cpsm bit, specific definition of commands response). Signed-off-by: Ludovic Barre --- drivers/mmc/host/mmci.c | 47

[PATCH V4 20/25] dt-bindings: mmci: add optional reset property

From: Ludovic Barre This patch adds a optional reset management. Signed-off-by: Ludovic Barre Acked-by: Rob Herring --- Documentation/devicetree/bindings/mmc/mmci.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/mmc/mmci.txt

[PATCH V4 19/25] mmc: mmci: add variant property to not read datacnt

From: Ludovic Barre This patch adds a boolean property to not read datacnt register. Needed to support the STM32 sdmmc variant. MMCIDATACNT register should be read only after the data transfer is completed. When reading after an error event the read data count value may be different from the

Re: [PATCH v2] mtd: rawnand: denali: set SPARE_AREA_SKIP_BYTES register to 8 if unset

On Fri, 28 Sep 2018 13:16:01 +0900 Masahiro Yamada wrote: > NAND devices need additional data area (OOB) for error correction, > but it is also used for Bad Block Marker (BBM). In many cases, the > first byte in OOB is used for BBM, but the location actually depends > on chip vendors. The NAND

Re: [PATCH 1/4] mm/hugetlb: Enable PUD level huge page migration

Hi Anshuman On 02/10/18 13:15, Anshuman Khandual wrote: Architectures like arm64 have PUD level HugeTLB pages for certain configs (1GB huge page is PUD based on ARM64_4K_PAGES base page size) that can be enabled for migration. It can be achieved through checking for PUD_SHIFT order based

Re: [PATCH 1/4] mm/hugetlb: Enable PUD level huge page migration

On 10/02/2018 06:08 PM, Suzuki K Poulose wrote: > Hi Anshuman > > On 02/10/18 13:15, Anshuman Khandual wrote: >> Architectures like arm64 have PUD level HugeTLB pages for certain configs >> (1GB huge page is PUD based on ARM64_4K_PAGES base page size) that can be >> enabled for migration. It

Re: [PATCH] spidev: Enable the Liebherr's BK4 board to work with spidev driver

On Tue, Oct 02, 2018 at 10:11:20AM +0200, Lukasz Majewski wrote: > > As documented in SubmittingPatches please send patches to the > > maintainers for the code you would like to change. > I'm using the ./scripts/get_maintainer.py script to obtain list of > relevant people. Your patch went to

Re: [PATCH] ARM: makefile: pass -march=armv4 to assembler even on CPU32v3

On 2 October 2018 at 14:30, Jason A. Donenfeld wrote: > Hi Arnd, > > On Tue, Oct 2, 2018 at 9:58 AM Arnd Bergmann wrote: >> > I think we're going to wind up playing whack-a-mole in silly ways. The >> > fact of the matter is that the ARM assembly I'm adding to the tree is >> > for ARMv4 and up,

[PATCH 4.18 128/228] ARM: dts: dra7: fix DCAN node addresses

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Kevin Hilman [ Upstream commit 949bdcc8a97c6078f21c8d4966436b117f2e4cd3 ] Fix the DT node addresses to match the reg property addresses, which were verified to match the TRM:

[PATCH 4.14 033/137] scsi: klist: Make it safe to use klists in atomic context

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche [ Upstream commit 624fa7790f80575a4ec28fbdb2034097dc18d051 ] In the scsi_transport_srp implementation it cannot be avoided to iterate over a klist from atomic context when

[PATCH 4.14 069/137] perf/x86/intel/lbr: Fix incomplete LBR call stack

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kan Liang [ Upstream commit 0592e57b24e7e05ec1f4c50b9666c013abff7017 ] LBR has a limited stack size. If a task has a deeper call stack than LBR's stack size, only the overflowed part is

[PATCH 4.14 075/137] module: exclude SHN_UNDEF symbols from kallsyms api

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jessica Yu [ Upstream commit 9f2d1e68cf4d641def734adaccfc3823d3575e6c ] Livepatch modules are special in that we preserve their entire symbol tables in order to be able to apply relocations

[PATCH 4.14 077/137] nfsd: fix corrupted reply to badly ordered compound

4.14-stable review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" [ Upstream commit 5b7b15aee641904ae269be9846610a3950cbd64c ] We're encoding a single op in the reply but leaving the number of ops zero, so the reply makes no sense.

[PATCH 4.18 220/228] arm/arm64: smccc-1.1: Make return values unsigned long

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier [ Upstream commit 1d8f574708a3fb6f18c85486d0c5217df893c0cf ] An unfortunate consequence of having a strong typing for the input values to the SMC call is that it also affects the

[PATCH 4.14 017/137] s390/mm: correct allocate_pgste proc_handler callback

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Gorbik [ Upstream commit 5bedf8aa03c28cb8dc98bdd32a41b66d8f7d3eaa ] Since proc_dointvec does not perform value range control, proc_dointvec_minmax should be used to limit value range,

[PATCH 4.14 020/137] RDMA/bnxt_re: Fix a couple off by one bugs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 474e5a86067e5f12c97d1db8b170c7f45b53097a ] The sgid_tbl->tbl[] array is allocated in bnxt_qplib_alloc_sgid_tbl(). It has sgid_tbl->max elements. So the >

[PATCH 4.14 042/137] s390/dasd: correct numa_node in dasd_alloc_queue

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Gorbik [ Upstream commit b17e3abb0af404cb62ad4ef1a5962f58b06e2b78 ] The numa_node field of the tag_set struct has to be explicitly initialized, otherwise it stays as 0, which is a

[PATCH 4.14 034/137] scsi: ibmvscsi: Improve strings handling

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Breno Leitao [ Upstream commit 1262dc09dc9ae7bf4ad00b6a2c5ed6a6936bcd10 ] Currently an open firmware property is copied into partition_name variable without keeping a room for \0. Later one,

[PATCH 4.14 031/137] ARM: dts: ls1021a: Add missing cooling device properties for CPUs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar [ Upstream commit 47768f372eae030db6fab5225f9504a820d2c07f ] The cooling device properties, like "#cooling-cells" and "dynamic-power-coefficient", should either be present for

[PATCH 4.14 066/137] arm: dts: mediatek: Add missing cooling device properties for CPUs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar [ Upstream commit 0c7f7a5150023f3c6f0b27c4d4940ce3dfaf62cc ] The cooling device properties, like "#cooling-cells" and "dynamic-power-coefficient", should either be present for

[PATCH 4.14 008/137] misc: sram: enable clock before registering regions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold [ Upstream commit d5b9653dd2bb7a2b1c8cc783c5d3b607bbb6b271 ] Make sure to enable the clock before registering regions and exporting partitions to user space at which point we

[PATCH 4.14 045/137] mtd: rawnand: atmel: add module param to avoid using dma

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Rosin [ Upstream commit efc6362c6f8c1e74b340e2611f1b35e7d557ce7b ] On a sama5d31 with a Full-HD dual LVDS panel (132MHz pixel clock) NAND flash accesses have a tendency to cause display

[PATCH 4.14 092/137] spi: rspi: Fix interrupted DMA transfers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit 8dbbaa47b96f6ea5f09f922b4e3c505cd8cf upstream. When interrupted, wait_event_interruptible_timeout() returns -ERESTARTSYS, and the SPI transfer in progress will

[PATCH 4.14 061/137] ath10k: transmit queued frames after processing rx packets

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Niklas Cassel [ Upstream commit 3f04950f32d5d592ab4fcaecac2178558a6f7437 ] When running iperf on ath10k SDIO, TX can stop working: iperf -c 192.168.1.1 -i 1 -t 20 -w 10K [ 3] 0.0- 1.0 sec

[PATCH 4.14 091/137] spi: rspi: Fix invalid SPI use during system suspend

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit c1ca59c22c56930b377a665fdd1b43351887830b upstream. If the SPI queue is running during system suspend, the system may lock up. Fix this by stopping/restarting the

[PATCH 4.14 083/137] floppy: Do not copy a kernel pointer to user memory in FDGETPRM ioctl

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Whitcroft commit 65eea8edc315589d6c993cf12dbb5d0e9ef1fe4e upstream. The final field of a floppy_struct is the field "name", which is a pointer to a string in kernel memory. The kernel

[PATCH 4.14 059/137] net: phy: xgmiitorgmii: Check phy_driver ready before accessing

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Brandon Maier [ Upstream commit ab4e6ee578e88a659938db8fbf33720bc048d29c ] Since a phy_device is added to the global mdio_bus list during phy_device_register(), but a phy_device's phy_driver

[PATCH 4.14 028/137] x86/tsc: Add missing header to tsc_msr.c

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko [ Upstream commit dbd0fbc76c77daac08ddd245afdcbade0d506e19 ] Add a missing header otherwise compiler warns about missed prototype: CC arch/x86/kernel/tsc_msr.o

[PATCH 4.14 094/137] USB: fix error handling in usb_driver_claim_interface()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit bd729f9d67aa9a303d8925bb8c4f06af25f407d1 upstream. The syzbot fuzzing project found a use-after-free bug in the USB core. The bug was caused by usbfs not unbinding from an

[PATCH 4.14 081/137] iio: 104-quad-8: Fix off-by-one error in register selection

4.14-stable review patch. If anyone has any objections, please let me know. -- From: William Breathitt Gray [ Upstream commit 2873c3f0e2bd12a7612e905c920c058855f4072a ] The reset flags operation is selected by bit 2 in the "Reset and Load Signals Decoders" register, not bit

[PATCH 4.14 062/137] rndis_wlan: potential buffer overflow in rndis_wlan_auth_indication()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit ae636fb1554833ee5133ca47bf4b2791b6739c52 ] This is a static checker fix, not something I have tested. The issue is that on the second iteration through the

[PATCH 4.14 056/137] ALSA: hda: Add AZX_DCAPS_PM_RUNTIME for AMD Raven Ridge

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng [ Upstream commit 1adca4b0cd65c14cb8b8c9c257720385869c3d5f ] This patch can make audio controller in AMD Raven Ridge gets runtime suspended to D3, to save ~1W power when it's

[PATCH 4.14 126/137] hwmon: (ina2xx) fix sysfs shunt resistor read access

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lothar Felten [ Upstream commit 3ad867001c91657c46dcf6656d52eb6080286fd5 ] fix the sysfs shunt resistor read access: return the shunt resistor value, not the calibration register contents.

[PATCH 4.14 105/137] IB/hfi1: Fix SL array bounds check

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ira Weiny commit 0dbfaa9f2813787679e296eb5476e40938ab48c8 upstream. The SL specified by a user needs to be a valid SL. Add a range check to the user specified SL value which protects from

[PATCH 4.14 114/137] qed: Wait for MCP halt and resume commands to take place

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tomer Tayar [ Upstream commit 76271809f49056f079e202bf6513d17b0d6dd34d ] Successive iterations of halting and resuming the management chip (MCP) might fail, since currently the driver doesn't

[PATCH 4.14 124/137] e1000: ensure to free old tx/rx rings in set_ringparam()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bo Chen [ Upstream commit ee400a3f1bfe7004a3e14b81c38ccc5583c26295 ] In 'e1000_set_ringparam()', the tx_ring and rx_ring are updated with new value and the old tx/rx rings are freed only when

[PATCH 4.14 019/137] md-cluster: clear another nodes suspend_area after the copy is finished

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Guoqing Jiang [ Upstream commit 010228e4a932ca1e8365e3b58c8e1e44c16ff793 ] When one node leaves cluster or stops the resyncing (resync or recovery) array, then other nodes need to call

[PATCH 4.14 064/137] wlcore: Add missing PM call for wlcore_cmd_wait_for_event_or_timeout()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren [ Upstream commit 4ec7cece87b3ed21ffcd407c62fb2f151a366bc1 ] Otherwise we can get: WARNING: CPU: 0 PID: 55 at drivers/net/wireless/ti/wlcore/io.h:84 I've only seen this few

[PATCH 4.14 021/137] RDMA/i40w: Hold read semaphore while looking after VMA

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky [ Upstream commit 5d9a2b0e28759e319a623da33940dbb3ce952b7d ] VMA lookup is supposed to be performed while mmap_sem is held. Fixes: f26c7c83395b ("i40iw: Add 2MB page

[PATCH 4.14 023/137] media: exynos4-is: Prevent NULL pointer dereference in __isp_video_try_fmt()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sylwester Nawrocki [ Upstream commit 7c1b9a5aeed91bef98988ac0fcf38c8c1f4f9a3a ] This patch fixes potential NULL pointer dereference as indicated by the following static checker warning:

[PATCH 4.14 026/137] media: fsl-viu: fix error handling in viu_of_probe()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Khoroshilov [ Upstream commit 662a99e145661c2b35155cf375044deae9b79896 ] viu_of_probe() ignores fails in i2c_get_adapter(), tries to unlock uninitialized mutex on error path. The

[PATCH 4.14 078/137] EDAC: Fix memleak in module init error path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold [ Upstream commit 4708aa85d50cc6e962dfa8acf5ad4e0d290a21db ] Make sure to use put_device() to free the initialised struct device so that resources managed by driver core also

[PATCH 4.14 067/137] HID: hid-ntrig: add error handling for sysfs_create_group

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Zhouyang Jia [ Upstream commit 44d4d51de9a3534a2b63d69efda02a10e66541e4 ] When sysfs_create_group fails, the lack of error-handling code may cause unexpected results. This patch adds

[PATCH 4.14 071/137] iomap: complete partial direct I/O writes synchronously

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Gruenbacher [ Upstream commit ebf00be37de35788cad72f4f20b4a39e30c0be4a ] According to xfstest generic/240, applications seem to expect direct I/O writes to either complete as a whole

[PATCH 4.14 040/137] s390/sysinfo: add missing #ifdef CONFIG_PROC_FS

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Carstens [ Upstream commit 9f35b818a2f90fb6cb291aa0c9f835d4f0974a9a ] Get rid of this compile warning for !PROC_FS: CC arch/s390/kernel/sysinfo.o

[PATCH 4.14 012/137] iommu/amd: make sure TLB to be flushed before IOVA freed

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Zhen Lei [ Upstream commit 3c120143f584360a13614787e23ae2cdcb5e5ccd ] Although the mapping has already been removed in the page table, it maybe still exist in TLB. Suppose the freed IOVAs is

[PATCH 4.18 171/228] bus: ti-sysc: Fix module register ioremap for larger offsets

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren [ Upstream commit 0ef8e3bb974af56346b34393e643d491d9141c66 ] We can have the interconnect target module control registers pretty much anywhere within the module range. The

[PATCH 4.18 204/228] e1000: check on netif_running() before calling e1000_up()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Bo Chen [ Upstream commit cf1acec008f8d7761aa3fd7c4bca7e17b2d2512d ] When the device is not up, the call to 'e1000_up()' from the error handling path of 'e1000_set_ringparam()' causes a

[PATCH 4.18 228/228] powerpc/pseries: Fix unitialized timer reset on migration

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Bringmann commit 8604895a34d92f5e186ceb931b0d1b384030ea3d upstream. After migration of a powerpc LPAR, the kernel executes code to update the system state to reflect new platform

[PATCH 4.18 226/228] powerpc: fix csum_ipv6_magic() on little endian platforms

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit 85682a7e3b9c664995ad477520f917039afdc330 upstream. On little endian platforms, csum_ipv6_magic() keeps len and proto in CPU byte order. This generates a bad results

[PATCH 4.18 213/228] Revert "ARM: dts: imx7d: Invert legacy PCI irq mapping"

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Leonard Crestez [ Upstream commit 538d6e9d597584e80514698e24321645debde78f ] This reverts commit 1c86c9dd82f859b474474a7fee0d5195da2c9c1d. That commit followed the reference manual but

[PATCH 4.14 032/137] scsi: target/iscsi: Make iscsit_ta_authentication() respect the output buffer size

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche [ Upstream commit 35bea5c84fd13c643cce63f0b5cd4b148f8c901d ] Fixes: e48354ce078c ("iscsi-target: Add iSCSI fabric support for target v4.1") Signed-off-by: Bart Van Assche

[PATCH 4.18 214/228] drm/amdgpu: Enable/disable gfx PG feature in rlc safe mode

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Rex Zhu [ Upstream commit 8ef23364b654d44244400d79988e677e504b21ba ] This is required by gfx hw and can fix the rlc hang when do s3 stree test on Cz/St. Reviewed-by: Alex Deucher

[PATCH 4.14 014/137] USB: serial: kobil_sct: fix modem-status error handling

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold [ Upstream commit a420b5d939ee58f1d950f0ea782834056520aeaa ] Make sure to return -EIO in case of a short modem-status read request. While at it, split the debug message to not

[PATCH 4.14 065/137] ARM: mvebu: declare asm symbols as character arrays in pmsu.c

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ethan Tuttle [ Upstream commit d0d378ff451a66e486488eec842e507d28145813 ] With CONFIG_FORTIFY_SOURCE, memcpy uses the declared size of operands to detect buffer overflows. If src or dest is

[PATCH 4.14 107/137] IB/hfi1: Fix context recovery when PBC has an UnsupportedVL

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael J. Ruhl commit d623500b3c4efd8d4e945ac9003c6b87b469a9ab upstream. If a packet stream uses an UnsupportedVL (virtual lane), the send engine will not send the packet, and it will not

[PATCH 4.14 115/137] qed: Prevent a possible deadlock during driver load and unload

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tomer Tayar [ Upstream commit eaa50fc59e5841910987e90b0438b2643041f508 ] The MFW manages an internal lock to prevent concurrent hardware (de)initialization of different PFs. This, together

[PATCH 4.14 106/137] IB/hfi1: Invalid user input can result in crash

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael J. Ruhl commit 94694d18cf27a6faad91487a38ce516c2b16e7d9 upstream. If the number of packets in a user sdma request does not match the actual iovectors being sent, sdma_cleanup can be

[PATCH 4.14 116/137] qed: Avoid sending mailbox commands when MFW is not responsive

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tomer Tayar [ Upstream commit b310974e041913231b6e3d5d475d4df55c312301 ] Keep sending mailbox commands to the MFW when it is not responsive ends up with a redundant amount of timeout

[PATCH 4.14 108/137] RDMA/uverbs: Atomically flush and mark closed the comp event queue

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steve Wise commit 67e3816842fe6414d629c7515b955952ec40c7d7 upstream. Currently a uverbs completion event queue is flushed of events in ib_uverbs_comp_event_close() with the queue spinlock

[PATCH 4.18 172/228] qed: Wait for ready indication before rereading the shmem

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Tomer Tayar [ Upstream commit f00d25f3154b676fcea4502a25b94bd7f142ca74 ] The MFW might be reset and re-update its shared memory. Upon the detection of such a reset the driver rereads this

[PATCH 4.18 174/228] qed: Prevent a possible deadlock during driver load and unload

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Tomer Tayar [ Upstream commit eaa50fc59e5841910987e90b0438b2643041f508 ] The MFW manages an internal lock to prevent concurrent hardware (de)initialization of different PFs. This, together

[PATCH 4.18 163/228] IB/hfi1: Invalid user input can result in crash

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael J. Ruhl commit 94694d18cf27a6faad91487a38ce516c2b16e7d9 upstream. If the number of packets in a user sdma request does not match the actual iovectors being sent, sdma_cleanup can be

[PATCH 4.18 185/228] bpf: sockmap: write_space events need to be passed to TCP handler

4.18-stable review patch. If anyone has any objections, please let me know. -- From: John Fastabend [ Upstream commit 9b2e0388bec8ec5427403e23faff3b58dd1c3200 ] When sockmap code is using the stream parser it also handles the write space events in order to handle the case

[PATCH 4.18 184/228] tls: possible hang when do_tcp_sendpages hits sndbuf is full case

4.18-stable review patch. If anyone has any objections, please let me know. -- From: John Fastabend [ Upstream commit 67db7cd249e71f64346f481b629724376d063e08 ] Currently, the lower protocols sk_write_space handler is not called if TLS is sending a scatterlist via

[PATCH 4.18 179/228] mmc: android-goldfish: fix bad logic of sg_copy_{from,to}_buffer conversion

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches [ Upstream commit 17e96d8516e31c3cb52cb8e2ee79d1d2e6948c11 ] The conversion to sg_copy_{from,to}_buffer has been done in the wrong way. sg_copy_to_buffer is a copy from an

[PATCH 4.18 180/228] bus: ti-sysc: Fix no_console_suspend handling

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren [ Upstream commit 4f3530f4a41d49c41015020cd9a5ed5c95b5d2db ] If no_console_suspend is set, we should keep console enabled during suspend. Lets fix this by only producing a

[PATCH 4.18 178/228] mmc: atmel-mci: fix bad logic of sg_copy_{from,to}_buffer conversion

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches [ Upstream commit 19f5e9e015675fcdbf2c20e804b2e84e80201454 ] The conversion to sg_copy_{from,to}_buffer has been done in the wrong way. sg_copy_to_buffer is a copy from an

Re: [PATCH v2] dma-debug: Check for drivers mapping invalid addresses in dma_map_single()

On 01/10/18 22:53, Stephen Boyd wrote: I recently debugged a DMA mapping oops where a driver was trying to map a buffer returned from request_firmware() with dma_map_single(). Memory returned from request_firmware() is mapped into the vmalloc region and this isn't a valid region to map with

[PATCH 4.18 073/228] media: ov772x: allow i2c controllers without I2C_FUNC_PROTOCOL_MANGLING

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Akinobu Mita [ Upstream commit 0b964d183cbf3f95a062ad9f3eec87ffa2790558 ] The ov772x driver only works when the i2c controller have I2C_FUNC_PROTOCOL_MANGLING. However, many i2c controller

[PATCH 4.18 076/228] arm64: dts: renesas: salvator-common: Fix adv7482 decimal unit addresses

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit c5a884838ce34681200b5a45b2330177036affd0 ] With recent dtc and W=1: ...salvator-x.dtb: Warning (graph_port):

[PATCH 4.18 041/228] x86/tsc: Add missing header to tsc_msr.c

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko [ Upstream commit dbd0fbc76c77daac08ddd245afdcbade0d506e19 ] Add a missing header otherwise compiler warns about missed prototype: CC arch/x86/kernel/tsc_msr.o

[PATCH 4.18 072/228] staging: android: ashmem: Fix mmap size validation

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alistair Strachan [ Upstream commit 8632c614565d0c5fdde527889601c018e97b6384 ] The ashmem driver did not check that the size/offset of the vma passed to its .mmap() function was not larger

[PATCH 4.18 043/228] x86/entry/64: Add two more instruction suffixes

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jan Beulich [ Upstream commit 6709812f094d96543b443645c68daaa32d3d3e77 ] Sadly, other than claimed in: a368d7fd2a ("x86/entry/64: Add instruction suffix") ... there are two more instances

[PATCH 4.18 044/228] ARM: dts: ls1021a: Add missing cooling device properties for CPUs

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar [ Upstream commit 47768f372eae030db6fab5225f9504a820d2c07f ] The cooling device properties, like "#cooling-cells" and "dynamic-power-coefficient", should either be present for

[PATCH 4.18 077/228] serial: pxa: Fix an error handling path in serial_pxa_probe()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 95a0e656580fab3128c7bee5f660c50784f53651 ] If port.line is out of range, we still need to release some resources, or we will leak them. Fixes:

[PATCH 4.18 070/228] media: omap3isp: zero-initialize the isp cam_xclk{a,b} initial data

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Javier Martinez Canillas [ Upstream commit 2ec7debd44b49927a6e2861521994cc075a389ed ] The struct clk_init_data init variable is declared in the isp_xclk_init() function so is an automatic

[PATCH 4.18 071/228] media: ov772x: add checks for register read errors

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Akinobu Mita [ Upstream commit 30f3b17eaf4913e9e56be15915ce57aae69db701 ] This change adds checks for register read errors and returns correct error code. Cc: Laurent Pinchart Cc: Hans

Re: [PATCH 4/5] locking/lockdep: Make class->ops a percpu counter

On 10/02/2018 05:55 AM, Ingo Molnar wrote: > * Peter Zijlstra wrote: > >> On Fri, Sep 28, 2018 at 01:53:20PM -0400, Waiman Long wrote: >>> diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c >>> index ca002c0..7a0ed1d 100644 >>> --- a/kernel/locking/lockdep.c >>> +++

[PATCH 4.18 046/228] thermal: i.MX: Allow thermal probe to fail gracefully in case of bad calibration.

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jean-Christophe Dubois [ Upstream commit be926ceeb4efc3bf44cb9b56f5c71aac9b1f8bbe ] Without this fix, the thermal probe on i.MX6 might trigger a division by zero exception later in the probe

Re: [PATCH 2/2] x86/tsc: Fix UV TSC initialization

On 10/1/2018 11:22 PM, Thomas Gleixner wrote: On Mon, 1 Oct 2018, Mike Travis wrote: Fix regression introduced by commit cf7a63ef4e02 ("x86/tsc: Calibrate tsc only once") as it changed setup_arch() so that it now calls tsc_early_init() before acpi_boot_table_init() which is a necessary

Re: KASAN: use-after-free Read in seq_escape

On Sun, Sep 30, 2018 at 11:58:02PM -0700, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:17b57b1883c1 Linux 4.19-rc6 > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=1672d71140 > kernel config:

Re: [LKP] [fsnotify] 60f7ed8c7c: will-it-scale.per_thread_ops -5.9% regression

On Mon, Oct 1, 2018 at 12:52 PM Amir Goldstein wrote: > > On Mon, Oct 1, 2018 at 12:32 PM Jan Kara wrote: > > > > On Sun 30-09-18 12:00:46, Amir Goldstein wrote: > [...] > > > > commit: > > > > 1e6cb72399 ("fsnotify: add super block object type") > > > > 60f7ed8c7c ("fsnotify: send path type

[RFC PATCH v3 0/5] Do not touch pages/zones during hot-remove path

I was about to send the patchset without RFC as suggested, but I wanted to give it one more spin before sending it officially. I rebased this patchset on top of [1] and [2]. I chose to rebase this on top of [1] because after that, HMM/devm got some of their code unified, and the changes to be

[RFC PATCH v3 5/5] mm/memory-hotplug: Rework unregister_mem_sect_under_nodes

From: Oscar Salvador This tries to address another issue about accessing unitiliazed pages. Jonathan reported a problem [1] where we can access steal pages in case we hot-remove memory without onlining it first. This time is in unregister_mem_sect_under_nodes. This function tries to get the

[RFC PATCH v3 3/5] mm/memory_hotplug: Check for IORESOURCE_SYSRAM in release_mem_region_adjustable

From: Oscar Salvador This is a preparation for the next patch. Currently, we only call release_mem_region_adjustable() in __remove_pages if the zone is not ZONE_DEVICE, because resources that belong to HMM/devm are being released by themselves with devm_release_mem_region. Since we do not want

Re: [tip:x86/hyperv] x86/hyperv: Enable PV qspinlock for Hyper-V

Sorry for noticing this only now, but I have been fighting with Xen PV qspinlocks last weekend: On 02/10/2018 13:28, tip-bot for Yi Sun wrote: > Commit-ID: aaa7fc34c003bd8133a49f7634480cef6288ad55 > Gitweb: > https://git.kernel.org/tip/aaa7fc34c003bd8133a49f7634480cef6288ad55 > Author:

Re: [PATCH 2/2] ARM: dts: at91: at91sam9x5cm: fix addressable nand flash size

On Tue, Oct 02, 2018 at 02:29:49PM +0300, Tudor Ambarus wrote: > at91sam9x5cm comes with a 2Gb NAND flash. Fix the rootfs size to > match this limit. > > Signed-off-by: Tudor Ambarus Acked-by: Ludovic Desroches Thanks > --- > arch/arm/boot/dts/at91sam9x5cm.dtsi | 2 +- > 1 file changed, 1

  1   2   3   4   5   6   7   8   9   10   >