Dear Friend,

2019-06-20 Thread Mrs Maria Ibrahim
Dear Friend, I am Mrs Maria Ibrahim. am sending you this brief letter to solicit your partnership to transfer $18.5 million US Dollars.I shall send you more information and procedures when I receive positive response from you. please send me a message in my Email box (mrsmariaibra...@gmail.com) a

Re: [PATCH 1/3] tools: memory-model: Expand definition of barrier

2019-06-20 Thread Paul E. McKenney
On Thu, Jun 20, 2019 at 11:55:36AM -0400, Alan Stern wrote: > Commit 66be4e66a7f4 ("rcu: locking and unlocking need to always be at > least barriers") added compiler barriers back into rcu_read_lock() and > rcu_read_unlock(). Furthermore, srcu_read_lock() and > srcu_read_unlock() have always conta

Re: [PATCH v2 4/6] mm/memory_hotplug: Rename walk_memory_range() and pass start+size instead of pfns

2019-06-20 Thread David Hildenbrand
On 20.06.19 18:05, Nathan Chancellor wrote: > On Thu, Jun 20, 2019 at 12:35:18PM +0200, David Hildenbrand wrote: >> walk_memory_range() was once used to iterate over sections. Now, it >> iterates over memory blocks. Rename the function, fixup the >> documentation. Also, pass start+size instead of P

[GIT PULL] KVM changes for 5.2-rc6

2019-06-20 Thread Paolo Bonzini
Linus, The following changes since commit f8d221d2e0e1572d0d60174c118e3554d1aa79fa: Merge tag 'kvm-s390-master-5.2-2' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into kvm-master (2019-06-01 00:49:02 +0200) are available in the git repository at: https://git.kernel.org/

[RFC PATCH v2 02/11] KVM: SVM: Add KVM_SEND_UPDATE_DATA command

2019-06-20 Thread Singh, Brijesh
The command is used for encrypting the guest memory region using the encryption context created with KVM_SEV_SEND_START. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Joerg Roedel Cc: Borislav Petkov Cc: Tom Lendacky Cc: x...@kernel.org C

[RFC PATCH v2 08/11] KVM: X86: Introduce KVM_HC_PAGE_ENC_STATUS hypercall

2019-06-20 Thread Singh, Brijesh
This hypercall is used by the SEV guest to notify a change in the page encryption status to the hypervisor. The hypercall should be invoked only when the encryption attribute is changed from encrypted -> decrypted and vice versa. By default all guest pages are considered encrypted. Cc: Thomas Glei

[RFC PATCH v2 09/11] KVM: x86: Introduce KVM_GET_PAGE_ENC_BITMAP ioctl

2019-06-20 Thread Singh, Brijesh
The ioctl can be used to retrieve page encryption bitmap for a given gfn range. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Joerg Roedel Cc: Borislav Petkov Cc: Tom Lendacky Cc: x...@kernel.org Cc: k...@vger.kernel.org Cc: linux-kernel@

[RFC PATCH v2 04/11] KVM: SVM: Add support for KVM_SEV_RECEIVE_START command

2019-06-20 Thread Singh, Brijesh
The command is used to create the encryption context for an incoming SEV guest. The encryption context can be later used by the hypervisor to import the incoming data into the SEV guest memory space. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: Paolo Bonzini Cc: "Radim Krčmář"

[RFC PATCH v2 10/11] mm: x86: Invoke hypercall when page encryption status is changed

2019-06-20 Thread Singh, Brijesh
Invoke a hypercall when a memory region is changed from encrypted -> decrypted and vice versa. Hypervisor need to know the page encryption status during the guest migration. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Joerg Roedel Cc: Bor

Re: [PATCH] kexec: fix warnig of crash_zero_bytes in crash.c

2019-06-20 Thread Borislav Petkov
On Sat, Jun 15, 2019 at 07:18:20AM +0800, Tiezhu Yang wrote: > This patch fixes the following sparse warning: Avoid having "This patch" or "This commit" in the commit message. It is tautologically useless. Also, do $ git grep 'This patch' Documentation/process for more details. > arch/x86/kern

[RFC PATCH v2 05/11] KVM: SVM: Add KVM_SEV_RECEIVE_UPDATE_DATA command

2019-06-20 Thread Singh, Brijesh
The command is used for copying the incoming buffer into the SEV guest memory space. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Joerg Roedel Cc: Borislav Petkov Cc: Tom Lendacky Cc: x...@kernel.org Cc: k...@vger.kernel.org Cc: linux-ke

[RFC PATCH v2 11/11] KVM: x86: Introduce KVM_SET_PAGE_ENC_BITMAP ioctl

2019-06-20 Thread Singh, Brijesh
The ioctl can be used to set page encryption bitmap for an incoming guest. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Joerg Roedel Cc: Borislav Petkov Cc: Tom Lendacky Cc: x...@kernel.org Cc: k...@vger.kernel.org Cc: linux-kernel@vger.

[RFC PATCH v2 03/11] KVM: SVM: Add KVM_SEV_SEND_FINISH command

2019-06-20 Thread Singh, Brijesh
The command is used to finailize the encryption context created with KVM_SEV_SEND_START command. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Joerg Roedel Cc: Borislav Petkov Cc: Tom Lendacky Cc: x...@kernel.org Cc: k...@vger.kernel.org

[RFC PATCH v2 01/11] KVM: SVM: Add KVM_SEV SEND_START command

2019-06-20 Thread Singh, Brijesh
The command is used to create an outgoing SEV guest encryption context. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Joerg Roedel Cc: Borislav Petkov Cc: Tom Lendacky Cc: x...@kernel.org Cc: k...@vger.kernel.org Cc: linux-kernel@vger.ker

[RFC PATCH v2 06/11] KVM: SVM: Add KVM_SEV_RECEIVE_FINISH command

2019-06-20 Thread Singh, Brijesh
The command finalize the guest receiving process and make the SEV guest ready for the execution. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Joerg Roedel Cc: Borislav Petkov Cc: Tom Lendacky Cc: x...@kernel.org Cc: k...@vger.kernel.org

[RFC PATCH v2 07/11] KVM: x86: Add AMD SEV specific Hypercall3

2019-06-20 Thread Singh, Brijesh
KVM hypercall framework relies on alternative framework to patch the VMCALL -> VMMCALL on AMD platform. If a hypercall is made before apply_alternative() is called then it defaults to VMCALL. The approach works fine on non SEV guest. A VMCALL would causes #UD, and hypervisor will be able to decode

Re: [PATCH] dmaengine: tegra210-adma: fix transfer failure

2019-06-20 Thread Jon Hunter
On 20/06/2019 17:15, Sameer Pujar wrote: > From Tegra186 onwards OUTSTANDING_REQUESTS field is added in channel > configuration register (bits 7:4). ADMA allows a maximum of 8 reads > to source and that many writes to target memory be outstanding at any > given point of time. If this field is not

Re: mmotm 2019-06-19-20-32 uploaded (drivers/base/memory.c)

2019-06-20 Thread David Hildenbrand
On 20.06.19 17:48, Randy Dunlap wrote: > On 6/19/19 8:32 PM, a...@linux-foundation.org wrote: >> The mm-of-the-moment snapshot 2019-06-19-20-32 has been uploaded to >> >>http://www.ozlabs.org/~akpm/mmotm/ >> >> mmotm-readme.txt says >> >> README for mm-of-the-moment: >> >> http://www.ozlabs.org

Re: [PATCH V2 2/2] mailbox: introduce ARM SMC based mailbox

2019-06-20 Thread Jassi Brar
On Mon, Jun 3, 2019 at 3:28 AM wrote: > > From: Peng Fan > > This mailbox driver implements a mailbox which signals transmitted data > via an ARM smc (secure monitor call) instruction. The mailbox receiver > is implemented in firmware and can synchronously return data when it > returns execution

Re: [PATCH V4 1/2] PCI: dwc: Add API support to de-initialize host

2019-06-20 Thread Lorenzo Pieralisi
On Wed, Jun 19, 2019 at 10:41:26AM +0530, Kishon Vijay Abraham I wrote: > Hi Lorenzo, > > On 18/06/19 7:58 PM, Lorenzo Pieralisi wrote: > > On Tue, Jun 18, 2019 at 04:21:17PM +0530, Vidya Sagar wrote: > > > > [...] > > > >>> 2) It is not related to this patch but I fail to see the reasoning > >>

Re: [PATCH v10 08/13] mm/sparsemem: Prepare for sub-section ranges

2019-06-20 Thread Dan Williams
On Thu, Jun 20, 2019 at 9:37 AM David Hildenbrand wrote: > > On 20.06.19 18:19, Dan Williams wrote: > > On Thu, Jun 20, 2019 at 3:31 AM David Hildenbrand wrote: > >> > >> On 19.06.19 07:52, Dan Williams wrote: > >>> Prepare the memory hot-{add,remove} paths for handling sub-section > >>> ranges b

[GIT PULL] arm64: fixes for -rc6

2019-06-20 Thread Will Deacon
Hi Linus, Please pull these arm64 fixes for -rc6. It's mainly a couple of email address updates to MAINTAINERS, but we've also fixed a UAPI build issue with musl libc and an accidental double-initialisation of our pgd_cache due to a naming conflict with a weak symbol. There are a couple of outsta

Re: [PATCH v10 00/13] mm: Sub-section memory hotplug support

2019-06-20 Thread Oscar Salvador
On Tue, Jun 18, 2019 at 10:51:33PM -0700, Dan Williams wrote: > Changes since v9 [1]: > - Fix multiple issues related to the fact that pfn_valid() has > traditionally returned true for any pfn in an 'early' (onlined at > boot) section regardless of whether that pfn represented 'System RAM'. >

[PATCH] arm64: dts: fsl: librem5: Limit the USB to 5V

2019-06-20 Thread Angus Ainslie (Purism)
The charge controller can handle 14V but the PTC on the devkit can only handle 6V so limit the negotiated voltage to 5V. Signed-off-by: Angus Ainslie (Purism) --- arch/arm64/boot/dts/freescale/imx8mq-librem5-devkit.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm6

[PATCH] arm64: dts: fsl: librem5: enable the SNVS power key

2019-06-20 Thread Angus Ainslie (Purism)
Enable the snvs power key. Signed-off-by: Angus Ainslie (Purism) --- arch/arm64/boot/dts/freescale/imx8mq-librem5-devkit.dts | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/arm64/boot/dts/freescale/imx8mq-librem5-devkit.dts b/arch/arm64/boot/dts/freescale/imx8mq-librem5-devkit.dts i

Re: [PATCH 1/5] usb: xhci: add firmware loader for uPD720201 and uPD720202 w/o ROM

2019-06-20 Thread Vinod Koul
Thanks Greg for a quick review :) On 20-06-19, 14:19, Greg Kroah-Hartman wrote: > On Thu, Jun 20, 2019 at 03:51:50PM +0530, Vinod Koul wrote: > > From: Christian Lamparter > > > > This patch adds a firmware loader for the uPD720201K8-711-BAC-A > > and uPD720202K8-711-BAA-A variant. Both of these

Re: [PATCH net-next v1] net: stmmac: initialize the reset delay array

2019-06-20 Thread Martin Blumenstingl
On Wed, Jun 19, 2019 at 11:41 PM David Miller wrote: > > From: Martin Blumenstingl > Date: Tue, 18 Jun 2019 22:39:27 +0200 > > > Commit ce4ab73ab0c27c ("net: stmmac: drop the reset delays from struct > > stmmac_mdio_bus_data") moved the reset delay array from struct > > stmmac_mdio_bus_data to a

Re: [PATCH] watchdog: convert remaining drivers to use SPDX license identifier

2019-06-20 Thread Jerry Hoemann
On Thu, Jun 20, 2019 at 09:28:46AM -0700, Guenter Roeck wrote: > This gets rid of the unnecessary license boilerplate, and avoids > having to deal with individual patches one by one. > > No functional changes. > > Signed-off-by: Guenter Roeck > --- > Note: Several drivers include a paragraph suc

Re: [PATCH 5/5] usb: xhci: allow multiple firmware versions

2019-06-20 Thread Vinod Koul
On 20-06-19, 14:20, Greg Kroah-Hartman wrote: > On Thu, Jun 20, 2019 at 03:51:54PM +0530, Vinod Koul wrote: > > Allow multiple firmware file versions in table and load them in > > increasing order as we find them in the file system. > > > > Signed-off-by: Vinod Koul > > Cc: Yoshihiro Shimoda > >

Re: [PATCH] regulator: qcom_spmi: Do NULL check for lvs

2019-06-20 Thread Bjorn Andersson
On Thu 20 Jun 07:22 PDT 2019, Jeffrey Hugo wrote: > Low-voltage switches (lvs) don't have set_points since the voltage ranges > of the output are really controlled by the inputs. This is a problem for > the newly added linear range support in the probe(), as that will cause > a null pointer deref

Re: [PATCH 16/16] mm: pass get_user_pages_fast iterator arguments in a structure

2019-06-20 Thread Linus Torvalds
On Thu, Jun 20, 2019 at 5:19 AM Nicholas Piggin wrote: > > The processor aliasing problem happens because the struct will > be initialised with stores using one base register (e.g., stack > register), and then same memory is loaded using a different > register (e.g., parameter register). Hmm. Hon

Re: [PATCH 2/3] jbd2: introduce jbd2_inode dirty range scoping

2019-06-20 Thread Theodore Ts'o
On Thu, Jun 20, 2019 at 09:09:11AM -0600, Ross Zwisler wrote: > We could definitely keep separate dirty ranges for each of the current and > next transaction. I think the case where you would see a difference would be > if you had multiple transactions in a row which grew the dirty range for a > g

[PATCH v7 0/5] MTD: Add Initial HyperBus support

2019-06-20 Thread Vignesh Raghavendra
Change log: Since v6: Fix up DT bindings for TI HBMC driver to move hyperbus node out of syscon Since v5: Fix up DT bindings comments for TI HBMC driver Move calibration sequence out of core into TI HBMC driver Since v4: Fix Rob's comments on dt-bindings of TI HBMC driver Since v3: * Drop readin

[PATCH v7 3/5] mtd: Add support for HyperBus memory devices

2019-06-20 Thread Vignesh Raghavendra
Cypress' HyperBus is Low Signal Count, High Performance Double Data Rate Bus interface between a host system master and one or more slave interfaces. HyperBus is used to connect microprocessor, microcontroller, or ASIC devices with random access NOR flash memory (called HyperFlash) or self refresh

[PATCH v7 1/5] mtd: cfi_cmdset_0002: Add support for polling status register

2019-06-20 Thread Vignesh Raghavendra
HyperFlash devices are compliant with CFI AMD/Fujitsu Extended Command Set (0x0002) for flash operations, therefore drivers/mtd/chips/cfi_cmdset_0002.c can be used as is. But these devices do not support DQ polling method of determining chip ready/good status. These flashes provide Status Register

[PATCH v7 5/5] mtd: hyperbus: Add driver for TI's HyperBus memory controller

2019-06-20 Thread Vignesh Raghavendra
Add driver for HyperBus memory controller on TI's AM654 SoC. Programming IP is pretty simple and provides direct memory mapped access to connected Flash devices. Add basic support for the IP without DMA. Second chipSelect is not supported for now. Signed-off-by: Vignesh Raghavendra --- v7: No ch

[PATCH v7 4/5] dt-bindings: mtd: Add bindings for TI's AM654 HyperBus memory controller

2019-06-20 Thread Vignesh Raghavendra
Add binding documentation for TI's HyperBus memory controller present on AM654 SoC. Signed-off-by: Vignesh Raghavendra --- v7: Fix example to move HyperBus node out of syscon v6: Use generic names for bindings .../devicetree/bindings/mtd/ti,am654-hbmc.txt | 52 +++ MAINTAINERS

[PATCH v7 2/5] dt-bindings: mtd: Add binding documentation for HyperFlash

2019-06-20 Thread Vignesh Raghavendra
Add DT binding documentation for HyperFlash devices. Signed-off-by: Vignesh Raghavendra Reviewed-by: Rob Herring --- v7: No change .../devicetree/bindings/mtd/cypress,hyperflash.txt | 13 + 1 file changed, 13 insertions(+) create mode 100644 Documentation/devicetree/bindings/mtd/

[PATCH v4 2/6] filemap: update offset check in filemap_fault()

2019-06-20 Thread Song Liu
With THP, current check of offset: VM_BUG_ON_PAGE(page->index != offset, page); is no longer accurate. Update it to: VM_BUG_ON_PAGE(page_to_pgoff(page) != offset, page); Acked-by: Rik van Riel Signed-off-by: Song Liu --- mm/filemap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion

[PATCH v4 0/6] [PATCH v3 0/6] Enable THP for text section of non-shmem files

2019-06-20 Thread Song Liu
Changes v3 => v4: 1. Put the logic to drop THP from pagecache in a separate function (Rik). 2. Move the function to drop THP from pagecache to exit_mmap(). 3. Revise confusing commit log 6/6. Changes v2 => v3: 1. Removed the limitation (cannot write to file with THP) by truncating whole file d

[PATCH v4 1/6] filemap: check compound_head(page)->mapping in filemap_fault()

2019-06-20 Thread Song Liu
Currently, filemap_fault() avoids trace condition with truncate by checking page->mapping == mapping. This does not work for compound pages. This patch let it check compound_head(page)->mapping instead. Acked-by: Rik van Riel Signed-off-by: Song Liu --- mm/filemap.c | 2 +- 1 file changed, 1 in

[PATCH v4 3/6] mm,thp: stats for file backed THP

2019-06-20 Thread Song Liu
In preparation for non-shmem THP, this patch adds two stats and exposes them in /proc/meminfo Acked-by: Rik van Riel Signed-off-by: Song Liu --- fs/proc/meminfo.c | 4 include/linux/mmzone.h | 2 ++ mm/vmstat.c| 2 ++ 3 files changed, 8 insertions(+) diff --git a/fs/proc/

[PATCH v4 6/6] mm,thp: avoid writes to file with THP in pagecache

2019-06-20 Thread Song Liu
In previous patch, an application could put part of its text section in THP via madvise(). These THPs will be protected from writes when the application is still running (TXTBSY). However, after the application exits, the file is available for writes. This patch avoids writes to file THP by droppi

[PATCH v4 5/6] mm,thp: add read-only THP support for (non-shmem) FS

2019-06-20 Thread Song Liu
This patch is (hopefully) the first step to enable THP for non-shmem filesystems. This patch enables an application to put part of its text sections to THP via madvise, for example: madvise((void *)0x60, 0x20, MADV_HUGEPAGE); We tried to reuse the logic for THP on tmpfs. Currently,

[PATCH v4 4/6] khugepaged: rename collapse_shmem() and khugepaged_scan_shmem()

2019-06-20 Thread Song Liu
Next patch will add khugepaged support of non-shmem files. This patch renames these two functions to reflect the new functionality: collapse_shmem()=> collapse_file() khugepaged_scan_shmem() => khugepaged_scan_file() Acked-by: Rik van Riel Signed-off-by: Song Liu --- mm/khuge

Re: [PATCH v4 5/6] mm,thp: add read-only THP support for (non-shmem) FS

2019-06-20 Thread Rik van Riel
On Thu, 2019-06-20 at 10:27 -0700, Song Liu wrote: > This patch is (hopefully) the first step to enable THP for non-shmem > filesystems. > > This patch enables an application to put part of its text sections to > THP > via madvise, for example: > > madvise((void *)0x60, 0x20, MADV_HUG

[PATCH 3/3] usb: musb: jz4740: Add support for DMA

2019-06-20 Thread Paul Cercueil
Add support for using the DMA channels built into the Inventra IP. Signed-off-by: Paul Cercueil Tested-by: Artur Rojek --- drivers/usb/musb/Kconfig | 2 +- drivers/usb/musb/jz4740.c | 21 +++-- 2 files changed, 16 insertions(+), 7 deletions(-) diff --git a/drivers/usb/musb/Kc

[PATCH 2/3] usb: musb: dma: Add support for shared IRQ

2019-06-20 Thread Paul Cercueil
The implementation of the Inventra IP in some of the Ingenic JZ47xx SoCs does not use a separate IRQ line for DMA transfers. Allow these SoCs to be supported by adding a flag 'dma_share_usb_irq' in the struct musb. If set, no extra IRQ line is required, and the musb glue will need to call the API

[PATCH 1/3] usb: musb: dma: Correct parameter passed to IRQ handler

2019-06-20 Thread Paul Cercueil
The IRQ handler was passed a pointer to a struct dma_controller, but the argument was then casted to a pointer to a struct musb_dma_controller. Signed-off-by: Paul Cercueil Tested-by: Artur Rojek --- drivers/usb/musb/musbhsdma.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] structleak: disable BYREF_ALL in combination with KASAN_STACK

2019-06-20 Thread Kees Cook
On Tue, Jun 18, 2019 at 11:47:13AM +0200, Arnd Bergmann wrote: > The combination of KASAN_STACK and GCC_PLUGIN_STRUCTLEAK_BYREF_ALL > leads to much larger kernel stack usage, as seen from the warnings > about functions that now exceed the 2048 byte limit: Is the preference that this go into v5.2 (

Re: [PATCH 1/2] coresight: Set affinity to invalid for missing CPU phandle

2019-06-20 Thread Mathieu Poirier
Hi Sai, On Thu, Jun 20, 2019 at 07:15:46PM +0530, Sai Prakash Ranjan wrote: > Affinity defaults to CPU0 in case of missing CPU phandle > and this leads to crashes in some cases because of such > wrong assumption. Fix this by returning -ENODEV in > coresight platform for such cases and then handle

Re: [PATCH] mips: Remove q-accessors from non-64bit platforms

2019-06-20 Thread Paul Burton
Hi Serge, On Fri, Jun 14, 2019 at 09:33:42AM +0300, Serge Semin wrote: > There are some generic drivers in the kernel, which make use of the > q-accessors or their derivatives. While at current asm/io.h the accessors > are defined, their implementation is only applicable either for 64bit > systems

Re: [PATCH v4 6/6] mm,thp: avoid writes to file with THP in pagecache

2019-06-20 Thread Rik van Riel
On Thu, 2019-06-20 at 10:27 -0700, Song Liu wrote: > +++ b/mm/mmap.c > @@ -3088,6 +3088,18 @@ int vm_brk(unsigned long addr, unsigned long > len) > } > EXPORT_SYMBOL(vm_brk); > > +static inline void release_file_thp(struct vm_area_struct *vma) > +{ > +#ifdef CONFIG_READ_ONLY_THP_FOR_FS > +

Re: [PATCH 2/2] coresight: Abort probe for missing CPU phandle

2019-06-20 Thread Mathieu Poirier
On Thu, Jun 20, 2019 at 07:15:47PM +0530, Sai Prakash Ranjan wrote: > Currently the coresight etm and cpu-debug drivers > assume the affinity to CPU0 returned by coresight > platform and continue the probe in case of missing > CPU phandle. This is not true and leads to crash > in some cases, so abo

[PATCH] usb: dwc2: use a longer AHB idle timeout in dwc2_core_reset()

2019-06-20 Thread Martin Blumenstingl
Use a 1us AHB idle timeout in dwc2_core_reset() and make it consistent with the other "wait for AHB master IDLE state" ocurrences. This fixes a problem for me where dwc2 would not want to initialize when updating to 4.19 on a MIPS Lantiq VRX200 SoC. dwc2 worked fine with 4.14. Testing on my bo

[PATCH 4.4 01/84] fs/fat/file.c: issue flush after the writeback of FAT

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit bd8309de0d60838eef6fb575b0c4c7e95841cf73 ] fsync() needs to make sure the data & meta-data of file are persistent after the return of fsync(), even when a power-failure occurs later. In the case of fat-fs, the FAT belongs to the meta-data of file, so we need to issue a flush aft

[PATCH 4.4 00/84] 4.4.183-stable review

2019-06-20 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.4.183 release. There are 84 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 Sat 22 Jun 2019 05:42:15 PM UTC. Anything rec

[PATCH 4.4 03/84] ipc: prevent lockup on alloc_msg and free_msg

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit d6a2946a88f524a47cc9b79279667137899db807 ] msgctl10 of ltp triggers the following lockup When CONFIG_KASAN is enabled on large memory SMP systems, the pages initialization can take a long time, if msgctl10 requests a huge block memory, and it will block rcu scheduler, so release

Re: [PATCH] x86/build: Move _etext to actual end of .text

2019-06-20 Thread Kees Cook
On Wed, Jun 19, 2019 at 12:37:11PM -0600, Ross Zwisler wrote: > On Sun, Jun 9, 2019 at 1:00 PM Johannes Hirte > wrote: > > On 2019 Jun 09, Klaus Kusche wrote: > > > Hello, > > > > > > Same problem for linux 5.1.7: > > > Kernel building fails with the same relocation error. > > > > > > 5.1.5 does n

[PATCH 4.4 13/84] f2fs: fix to avoid panic in do_recover_data()

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 22d61e286e2d9097dae36f75ed48801056b77cac ] As Jungyeon reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203227 - Overview When mounting the attached crafted image, following errors are reported. Additionally, it hangs on sync after trying to mount it. The imag

[PATCH 4.4 12/84] ntp: Allow TAI-UTC offset to be set to zero

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit fdc6bae940ee9eb869e493990540098b8c0fd6ab ] The ADJ_TAI adjtimex mode sets the TAI-UTC offset of the system clock. It is typically set by NTP/PTP implementations and it is automatically updated by the kernel on leap seconds. The initial value is zero (which applications may interp

[PATCH 4.4 17/84] nvmem: core: fix read buffer in place

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 2fe518fecb3a4727393be286db9804cd82ee2d91 ] When the bit_offset in the cell is zero, the pointer to the msb will not be properly initialized (ie, will still be pointing to the first byte in the buffer). This being the case, if there are bits to clear in the msb, those will be lef

[PATCH 4.4 15/84] iommu/vt-d: Set intel_iommu_gfx_mapped correctly

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit cf1ec4539a50bdfe688caad4615ca47646884316 ] The intel_iommu_gfx_mapped flag is exported by the Intel IOMMU driver to indicate whether an IOMMU is used for the graphic device. In a virtualized IOMMU environment (e.g. QEMU), an include-all IOMMU is used for graphic device. This flag

[PATCH 4.4 20/84] x86/PCI: Fix PCI IRQ routing table memory leak

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit ea094d53580f40c2124cef3d072b73b2425e7bfd ] In pcibios_irq_init(), the PCI IRQ routing table 'pirq_table' is first found through pirq_find_routing_table(). If the table is not found and CONFIG_PCI_BIOS is defined, the table is then allocated in pcibios_get_irq_routing_table() usi

[PATCH 4.4 16/84] ALSA: hda - Register irq handler after the chip initialization

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit f495222e28275222ab6fd93813bd3d462e16d340 ] Currently the IRQ handler in HD-audio controller driver is registered before the chip initialization. That is, we have some window opened between the azx_acquire_irq() call and the CORB/RIRB setup. If an interrupt is triggered in this

[PATCH 4.4 04/84] hugetlbfs: on restore reserve error path retain subpool reservation

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 0919e1b69ab459e06df45d3ba6658d281962db80 ] When a huge page is allocated, PagePrivate() is set if the allocation consumed a reservation. When freeing a huge page, PagePrivate is checked. If set, it indicates the reservation should be restored. PagePrivate being set at free huge

[PATCH 4.4 18/84] fuse: retrieve: cap requested size to negotiated max_write

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 7640682e67b33cab8628729afec8ca92b851394f ] FUSE filesystem server and kernel client negotiate during initialization phase, what should be the maximum write size the client will ever issue. Correspondingly the filesystem server then queues sys_read calls to read requests with buff

[PATCH 4.4 27/84] PCI: rpadlpar: Fix leaked device_node references in add/remove paths

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit fb26228bfc4ce3951544848555c0278e2832e618 ] The find_dlpar_node() helper returns a device node with its reference incremented. Both the add and remove paths use this helper for find the appropriate node, but fail to release the reference when done. Annotate the find_dlpar_node()

[PATCH 4.4 26/84] ARM: dts: imx6qdl: Specify IMX6QDL_CLK_IPG as "ipg" clock to SDMA

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit b14c872eebc501b9640b04f4a152df51d6eaf2fc ] Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX6QDL_CLK_SDMA re

[PATCH 4.4 21/84] platform/chrome: cros_ec_proto: check for NULL transfer function

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 94d4e7af14a1170e34cf082d92e4c02de9e9fb88 ] As new transfer mechanisms are added to the EC codebase, they may not support v2 of the EC protocol. If the v3 initial handshake transfer fails, the kernel will try and call cmd_xfer as a fallback. If v2 is not supported, cmd_xfer will

[PATCH 4.4 24/84] ARM: dts: imx6sx: Specify IMX6SX_CLK_IPG as "ahb" clock to SDMA

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit cc839d0f8c284fcb7591780b568f13415bbb737c ] Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX6SL_CLK_SDMA res

[PATCH 4.4 30/84] video: imsttfb: fix potential NULL pointer dereferences

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 1d84353d205a953e2381044953b7fa31c8c9702d ] In case ioremap fails, the fix releases resources and returns -ENOMEM to avoid NULL pointer dereferences. Signed-off-by: Kangjie Lu Cc: Aditya Pakki Cc: Finn Thain Cc: Rob Herring Cc: Greg Kroah-Hartman [b.zolnierkie: minor patch s

[PATCH 4.4 31/84] PCI: xilinx: Check for __get_free_pages() failure

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 699ca30162686bf305cdf94861be02eb0cf9bda2 ] If __get_free_pages() fails, return -ENOMEM to avoid a NULL pointer dereference. Signed-off-by: Kangjie Lu Signed-off-by: Lorenzo Pieralisi Reviewed-by: Steven Price Reviewed-by: Mukesh Ojha Signed-off-by: Sasha Levin --- drivers/

[PATCH 4.4 22/84] soc: mediatek: pwrap: Zero initialize rdata in pwrap_init_cipher

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 89e28da82836530f1ac7a3a32fecc31f22d79b3e ] When building with -Wsometimes-uninitialized, Clang warns: drivers/soc/mediatek/mtk-pmic-wrap.c:1358:6: error: variable 'rdata' is used uninitialized whenever '||' condition is true [-Werror,-Wsometimes-uninitialized] If pwrap_write re

[PATCH 4.4 28/84] PCI: rcar: Fix a potential NULL pointer dereference

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit f0d14edd2ba43b995bef4dd5da5ffe0ae19321a1 ] In case __get_free_pages() fails and returns NULL, fix the return value to -ENOMEM and release resources to avoid dereferencing a NULL pointer. Signed-off-by: Kangjie Lu Signed-off-by: Lorenzo Pieralisi Reviewed-by: Ulrich Hecht Revi

[PATCH 4.4 08/84] mfd: intel-lpss: Set the device in reset state when init

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit dad06532292d77f37fbe831a02948a593500f682 ] In virtualized setup, when system reboots due to warm reset interrupt storm is seen. Call Trace: dump_stack+0x70/0xa5 __report_bad_irq+0x2e/0xc0 note_interrupt+0x248/0x290 ? add_interrupt_randomness+0x30/0x220 handle_irq_event_percpu+0

[PATCH 4.4 09/84] mfd: twl6040: Fix device init errors for ACCCTL register

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 48171d0ea7caccf21c9ee3ae75eb370f2a756062 ] I noticed that we can get a -EREMOTEIO errors on at least omap4 duovero: twl6040 0-004b: Failed to write 2d = 19: -121 And then any following register access will produce errors. There 2d offset above is register ACCCTL that gets writ

[PATCH 4.4 10/84] perf/x86/intel: Allow PEBS multi-entry in watermark mode

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit c7a286577d7592720c2f179aadfb325a1ff48c95 ] This patch fixes a restriction/bug introduced by: 583feb08e7f7 ("perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS") The original patch prevented using multi-entry PEBS when wakeup_events != 0. However given that w

[PATCH 4.4 06/84] mm/cma_debug.c: fix the break condition in cma_maxchunk_get()

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit f0fd50504a54f5548eb666dc16ddf8394e44e4b7 ] If not find zero bit in find_next_zero_bit(), it will return the size parameter passed in, so the start bit should be compared with bitmap_maxno rather than cma->count. Although getting maxchunk is working fine due to zero value of orde

[PATCH 4.4 34/84] pwm: tiehrpwm: Update shadow register for disabling PWMs

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit b00ef53053191d3025c15e8041699f8c9d132daf ] It must be made sure that immediate mode is not already set, when modifying shadow register value in ehrpwm_pwm_disable(). Otherwise modifications to the action-qualifier continuous S/W force register(AQSFRC) will be done in the active r

[PATCH 4.4 05/84] mm/cma.c: fix crash on CMA allocation if bitmap allocation fails

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 1df3a339074e31db95c4790ea9236874b13ccd87 ] f022d8cb7ec7 ("mm: cma: Don't crash on allocation if CMA area can't be activated") fixes the crash issue when activation fails via setting cma->count as 0, same logic exists if bitmap allocation fails. Link: http://lkml.kernel.org/r/201

[PATCH 4.4 02/84] sysctl: return -EINVAL if val violates minmax

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit e260ad01f0aa9e96b5386d5cd7184afd949dc457 ] Currently when userspace gives us a values that overflow e.g. file-max and other callers of __do_proc_doulongvec_minmax() we simply ignore the new value and leave the current value untouched. This can be problematic as it gives the ill

[PATCH 4.4 46/84] i2c: acorn: fix i2c warning

2019-06-20 Thread Greg Kroah-Hartman
From: Russell King commit ca21f851cc9643af049226d57fabc3c883ea648e upstream. The Acorn i2c driver (for RiscPC) triggers the "i2c adapter has no name" warning in the I2C core driver, resulting in the RTC being inaccessible. Fix this. Fixes: 2236baa75f70 ("i2c: Sanity checks on adapter registrati

[PATCH 4.4 47/84] bcache: fix stack corruption by PRECEDING_KEY()

2019-06-20 Thread Greg Kroah-Hartman
From: Coly Li commit 31b90956b124240aa8c63250243ae1a53585c5e2 upstream. Recently people report bcache code compiled with gcc9 is broken, one of the buggy behavior I observe is that two adjacent 4KB I/Os should merge into one but they don't. Finally it turns out to be a stack corruption caused by

[PATCH 4.4 45/84] ptrace: restore smp_rmb() in __ptrace_may_access()

2019-06-20 Thread Greg Kroah-Hartman
From: Jann Horn commit f6581f5b55141a95657ef5742cf6a6bfa20a109f upstream. Restore the read memory barrier in __ptrace_may_access() that was deleted a couple years ago. Also add comments on this barrier and the one it pairs with to explain why they're there (as far as I understand). Fixes: bfedb

[PATCH 4.4 44/84] [PATCH] signal/ptrace: Dont leak unitialized kernel memory with PTRACE_PEEK_SIGINFO

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit f6e2aa91a46d2bc79fce9b93a988dbe7655c90c0 ] Recently syzbot in conjunction with KMSAN reported that ptrace_peek_siginfo can copy an uninitialized siginfo to userspace. Inspecting ptrace_peek_siginfo confirms this. The problem is that off when initialized from args.off can be init

[PATCH 4.4 49/84] ASoC: cs42xx8: Add regcache mask dirty

2019-06-20 Thread Greg Kroah-Hartman
From: S.j. Wang commit ad6eecbfc01c987e0253371f274c3872042e4350 upstream. Add regcache_mark_dirty before regcache_sync for power of codec may be lost at suspend, then all the register need to be reconfigured. Fixes: 0c516b4ff85c ("ASoC: cs42xx8: Add codec driver support for CS42448/CS42888") Cc

[PATCH 4.4 52/84] scsi: bnx2fc: fix incorrect cast to u64 on shift operation

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit d0c0d902339249c75da85fd9257a86cbb98dfaa5 ] Currently an int is being shifted and the result is being cast to a u64 which leads to undefined behaviour if the shift is more than 31 bits. Fix this by casting the integer value 1 to u64 before the shift operation. Addresses-Coverity:

[PATCH 4.4 35/84] ARM: dts: exynos: Always enable necessary APIO_1V8 and ABB_1V8 regulators on Arndale Octa

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 5ab99cf7d5e96e3b727c30e7a8524c976bd3723d ] The PVDD_APIO_1V8 (LDO2) and PVDD_ABB_1V8 (LDO8) regulators were turned off by Linux kernel as unused. However they supply critical parts of SoC so they should be always on: 1. PVDD_APIO_1V8 supplies SYS pins (gpx[0-3], PSHOLD), HDMI l

[PATCH 4.4 51/84] scsi: lpfc: add check for loss of ndlp when sending RRQ

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit c8cb261a072c88ca1aff0e804a30db4c7606521b ] There was a missing qualification of a valid ndlp structure when calling to send an RRQ for an abort. Add the check. Signed-off-by: Dick Kennedy Signed-off-by: James Smart Tested-by: Bart Van Assche Signed-off-by: Martin K. Petersen

[PATCH 4.4 50/84] Drivers: misc: fix out-of-bounds access in function param_set_kgdbts_var

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit b281218ad4311a0342a40cb02fb17a363df08b48 ] There is an out-of-bounds access to "config[len - 1]" array when the variable "len" is zero. See commit dada6a43b040 ("kgdboc: fix KASAN global-out-of-bounds bug in param_set_kgdboc_var()") for details. Signed-off-by: Young Xiao Signe

[PATCH 4.4 37/84] ARM: exynos: Fix undefined instruction during Exynos5422 resume

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 4d8e3e951a85620272ce27f2c738a3eeef8c ] During early system resume on Exynos5422 with performance counters enabled the following kernel oops happens: Internal error: Oops - undefined instruction: 0 [#1] PREEMPT SMP ARM Modules linked in: CPU: 0 PID: 1433 Comm: bas

[PATCH 4.4 38/84] futex: Fix futex lock the wrong page

2019-06-20 Thread Greg Kroah-Hartman
From: ZhangXiaoxu The upstram commit 65d8fc777f6d ("futex: Remove requirement for lock_page() in get_futex_key()") use variable 'page' as the page head, when merge it to stable branch, the variable `page_head` is page head. In the stable branch, the variable `page` not means the page head, when

[PATCH 4.4 36/84] pwm: Fix deadlock warning when removing PWM device

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 347ab9480313737c0f1aaa08e8f2e1a791235535 ] This patch fixes deadlock warning if removing PWM device when CONFIG_PROVE_LOCKING is enabled. This issue can be reproceduced by the following steps on the R-Car H3 Salvator-X board if the backlight is disabled: # cd /sys/class/pwm/pw

[PATCH 4.4 54/84] KVM: x86/pmu: do not mask the value that is written to fixed PMUs

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 2924b52117b2812e9633d5ea337333299166d373 ] According to the SDM, for MSR_IA32_PERFCTR0/1 "the lower-order 32 bits of each MSR may be written with any value, and the high-order 8 bits are sign-extended according to the value of bit 31", but the fixed counters in real hardware are

[PATCH 4.4 53/84] usbnet: ipheth: fix racing condition

2019-06-20 Thread Greg Kroah-Hartman
[ Upstream commit 94d250fae48e6f873d8362308f5c4d02cd1b1fd2 ] Fix a racing condition in ipheth.c that can lead to slow performance. Bug: In ipheth_tx(), netif_wake_queue() may be called on the callback ipheth_sndbulk_callback(), _before_ netif_stop_queue() is called. When this happens, the queue i

[PATCH 4.4 58/84] USB: Fix chipmunk-like voice when using Logitech C270 for recording audio.

2019-06-20 Thread Greg Kroah-Hartman
From: Marco Zatta commit bd21f0222adab64974b7d1b4b8c7ce6b23e9ea4d upstream. This patch fixes the chipmunk-like voice that manifets randomly when using the integrated mic of the Logitech Webcam HD C270. The issue was solved initially for this device by commit 2394d67e446b ("USB: add RESET_RESUME

[PATCH 4.4 56/84] drm/vmwgfx: integer underflow in vmw_cmd_dx_set_shader() leading to an invalid read

2019-06-20 Thread Greg Kroah-Hartman
From: Murray McAllister commit 5ed7f4b5eca11c3c69e7c8b53e4321812bc1ee1e upstream. If SVGA_3D_CMD_DX_SET_SHADER is called with a shader ID of SVGA3D_INVALID_ID, and a shader type of SVGA3D_SHADERTYPE_INVALID, the calculated binding.shader_slot will be 4294967295, leading to an out-of-bounds read

[PATCH 4.4 61/84] USB: serial: option: add support for Simcom SIM7500/SIM7600 RNDIS mode

2019-06-20 Thread Greg Kroah-Hartman
From: Jörgen Storvist commit 5417a7e482962952e622eabd60cd3600dd65dedf upstream. Added IDs for Simcom SIM7500/SIM7600 series cellular module in RNDIS mode. Reserved the interface for ADB. T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 7 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00

[PATCH 4.4 59/84] USB: usb-storage: Add new ID to ums-realtek

2019-06-20 Thread Greg Kroah-Hartman
From: Kai-Heng Feng commit 1a6dd3fea131276a4fc44ae77b0f471b0b473577 upstream. There is one more Realtek card reader requires ums-realtek to work correctly. Add the device ID to support it. Signed-off-by: Kai-Heng Feng Cc: stable Signed-off-by: Greg Kroah-Hartman --- drivers/usb/storage/un

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