[PATCH 2/3] mt76: mt7615: add 4 WMM sets support

2019-07-18 Thread Ryder Lee
MT7615 hardware supoorts 4 WMM sets, so this patch adds them accordingly. Also remove incorrect queue mapping in .conf_tx Signed-off-by: Ryder Lee --- drivers/net/wireless/mediatek/mt76/mt7615/mac.c | 5 +++-- drivers/net/wireless/mediatek/mt76/mt7615/main.c | 16 ++-- .../net/wire

[PATCH 3/3] mt76: mt7615: add cwmin/cwmax initial values

2019-07-18 Thread Ryder Lee
Add initial values in mt7615_mcu_set_wmm() to cleanup setup flow. Signed-off-by: Ryder Lee --- drivers/net/wireless/mediatek/mt76/mt7615/mcu.c | 17 ++--- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/drivers/net/wireless/mediatek/mt76/mt7615/mcu.c b/drivers/net/wir

[PATCH 1/3] mt76: fix checkpatch warnings and errors

2019-07-18 Thread Ryder Lee
Fix warnings and errors as much as possible. Signed-off-by: Ryder Lee --- drivers/net/wireless/mediatek/mt76/agg-rx.c | 21 + drivers/net/wireless/mediatek/mt76/dma.c | 2 +- drivers/net/wireless/mediatek/mt76/mac80211.c | 30 ++-- drivers/net/wireless/mediatek/mt76/mt76.

Re: [PATCH] reiserfs: fix code unwinding with clang

2019-07-18 Thread Arnd Bergmann
On Thu, Jul 18, 2019 at 5:20 PM Joe Perches wrote: > On Thu, 2019-07-18 at 15:49 +0200, Arnd Bergmann wrote: > > This will likely get fixed in a future clang release, but in the meantime > > the workaround helps us build cleanly with existing releases. > > The original code read better. > > This i

Re: [PATCH v3 02/11] s390x/mm: Fail when an altmap is used for arch_add_memory()

2019-07-18 Thread Michal Hocko
On Mon 15-07-19 12:51:27, David Hildenbrand wrote: > On 01.07.19 14:46, Michal Hocko wrote: > > On Mon 01-07-19 09:43:06, Michal Hocko wrote: > >> On Mon 27-05-19 13:11:43, David Hildenbrand wrote: > >>> ZONE_DEVICE is not yet supported, fail if an altmap is passed, so we > >>> don't forget arch_ad

Re: x86 - clang / objtool status

2019-07-18 Thread Thomas Gleixner
On Thu, 18 Jul 2019, Nick Desaulniers wrote: > On Thu, Jul 18, 2019 at 1:40 PM Thomas Gleixner wrote: > > after picking up Josh's objtool updates I gave clang a test ride again. > > Thanks for testing and the reports; these are valuable and we > appreciate the help debugging them. > > > 2) debia

Re: x86 - clang / objtool status

2019-07-18 Thread Thomas Gleixner
On Thu, 18 Jul 2019, Nathan Chancellor wrote: > Hi Thomas, > > I can't comment on the objtool stuff as it is a bit outside of my area > of expertise (probably going to be my next major learning project) but I > can comment on the other errors. > > On Thu, Jul 18, 2019 at 10:40:09PM +0200, Thomas

Re: [RFC PATCH v4 6/6] drm/i915/gvt: Add cursor plane reg update trap emulation handler

2019-07-18 Thread Zhenyu Wang
On 2019.07.18 23:56:40 +0800, Kechen Lu wrote: > This patch adds the cursor plane CURBASE reg update trap handler > in order to : > > - Deliver the cursor refresh event at each vblank emulation, > the flip_done_event bit check is supposed to do here. If cursor > plane updates happen, deliver the c

[PATCH v2] sched/core: Fix cpu controller for !RT_GROUP_SCHED

2019-07-18 Thread Juri Lelli
On !CONFIG_RT_GROUP_SCHED configurations it is currently not possible to move RT tasks between cgroups to which cpu controller has been attached; but it is oddly possible to first move tasks around and then make them RT (setschedule to FIFO/RR). E.g.: # mkdir /sys/fs/cgroup/cpu,cpuacct/group1

Re: [PATCH 3/3] dt-bindings: dsp: fsl: Add DSP core binding support

2019-07-18 Thread Daniel Baluta
On Thu, Jul 18, 2019 at 9:40 PM Leonard Crestez wrote: > > On 18.07.2019 21:24, Daniel Baluta wrote: > > On Thu, Jul 18, 2019 at 7:41 PM Rob Herring wrote: > >> > >> On Thu, Jul 18, 2019 at 9:13 AM Daniel Baluta > >> wrote: > >>> > >>> This describes the DSP device tree node. > >>> > >>> Signed

Re: [PATCH v2] remoteproc: copy parent dma_pfn_offset for vdev

2019-07-18 Thread Christoph Hellwig
On Mon, Jul 08, 2019 at 11:45:46AM -0700, Christoph Hellwig wrote: > > But that's breaking legacy as all platforms will have to add a virtio > > device node in > > their DT file... > > > > Is it aligned with your view ? > > Yes, that is how I'd assume it works. But given that until recently > y

Re: [PATCH v8 0/3] KVM: x86: Enable user wait instructions

2019-07-18 Thread Tao Xu
Ping for comments :) On 7/16/2019 2:55 PM, Tao Xu wrote: UMONITOR, UMWAIT and TPAUSE are a set of user wait instructions. UMONITOR arms address monitoring hardware using an address. A store to an address within the specified address range triggers the monitoring hardware to wake up the processo

Re: [RFC PATCH v4 4/6] drm/i915/gvt: Deliver vGPU refresh event to userspace

2019-07-18 Thread Zhenyu Wang
On 2019.07.18 23:56:38 +0800, Kechen Lu wrote: > From: Tina Zhang > > Deliver the display refresh events to the user land. Userspace can use > the irq mask/unmask mechanism to disable or enable the event delivery. > > As we know, delivering refresh event at each vblank safely avoids > tearing an

Re: [PATCH v2 1/2] mm, slab: Extend slab/shrink to shrink all memcg caches

2019-07-18 Thread Michal Hocko
On Wed 17-07-19 16:24:12, Waiman Long wrote: > Currently, a value of '1" is written to /sys/kernel/slab//shrink > file to shrink the slab by flushing out all the per-cpu slabs and free > slabs in partial lists. This can be useful to squeeze out a bit more memory > under extreme condition as well as

Re: [PATCH] iomap: hide iomap_sector with CONFIG_BLOCK=n

2019-07-18 Thread Christoph Hellwig
On Fri, Jul 19, 2019 at 03:16:55PM +0900, Masahiro Yamada wrote: > > headers-$(CONFIG_IOMAP) += iomap.h > > I cannot find CONFIG_IOMAP. > > Do you mean > > header-test-$(CONFIG_BLOCK) += iomap.h Yeah, we could use CONFIG_BLOCK.

Re: [PATCH] iomap: hide iomap_sector with CONFIG_BLOCK=n

2019-07-18 Thread Masahiro Yamada
On Fri, Jul 19, 2019 at 2:59 PM Christoph Hellwig wrote: > > On Fri, Jul 19, 2019 at 11:19:15AM +0900, Masahiro Yamada wrote: > > I started to think > > compiling all headers is more painful than useful. > > > > > > MW is closing, so I am thinking of disabling it for now > > to take time to re-thi

Re: [PATCH v2 2/2] mm, slab: Show last shrink time in us when slab/shrink is read

2019-07-18 Thread Michal Hocko
On Wed 17-07-19 16:24:13, Waiman Long wrote: > The show method of /sys/kernel/slab//shrink sysfs file currently > returns nothing. This is now modified to show the time of the last > cache shrink operation in us. Isn't this something that tracing can be used for without any kernel modifications? -

Re: [patch 23/38] mm/sparsemem: introduce struct mem_section_usage

2019-07-18 Thread Michal Hocko
On Thu 18-07-19 15:57:57, Andrew Morton wrote: > From: Dan Williams > Subject: mm/sparsemem: introduce struct mem_section_usage > > Patch series "mm: Sub-section memory hotplug support", v10. Has this been properly reviewed after the last rebase and is this actually ready for merging? I have see

[GIT PULL] xen: fixes and features for 5.3-rc1

2019-07-18 Thread Juergen Gross
Linus, Please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-5.3a-rc1-tag xen: fixes and features for 5.3-rc1 It contains: - A series to introduce a common command line parameter for disabling paravirtual extensions when running as a guest i

Re: [RFC PATCH v4 1/6] vfio: Define device specific irq type capability

2019-07-18 Thread Zhenyu Wang
On 2019.07.18 23:56:35 +0800, Kechen Lu wrote: > From: Tina Zhang > > Cap the number of irqs with fixed indexes and use capability chains > to chain device specific irqs. > > Signed-off-by: Tina Zhang > Signed-off-by: Eric Auger > --- > include/uapi/linux/vfio.h | 19 ++- > 1

Re: [PATCH v4 20/24] PM / devfreq: tegra30: Optimize upper average watermark selection

2019-07-18 Thread Chanwoo Choi
On 19. 7. 19. 오후 3:09, Chanwoo Choi wrote: > On 19. 7. 19. 오전 11:21, Dmitry Osipenko wrote: >> В Fri, 19 Jul 2019 11:06:05 +0900 >> Chanwoo Choi пишет: >> >>> On 19. 7. 19. 오전 10:59, Dmitry Osipenko wrote: В Fri, 19 Jul 2019 10:36:30 +0900 Chanwoo Choi пишет: > On 19. 7. 8.

Re: [PATCH v4 20/24] PM / devfreq: tegra30: Optimize upper average watermark selection

2019-07-18 Thread Chanwoo Choi
On 19. 7. 19. 오전 11:21, Dmitry Osipenko wrote: > В Fri, 19 Jul 2019 11:06:05 +0900 > Chanwoo Choi пишет: > >> On 19. 7. 19. 오전 10:59, Dmitry Osipenko wrote: >>> В Fri, 19 Jul 2019 10:36:30 +0900 >>> Chanwoo Choi пишет: >>> On 19. 7. 8. 오전 7:32, Dmitry Osipenko wrote: > I noticed th

Re: [PATCH v3 10/11] mm/memory_hotplug: Make unregister_memory_block_under_nodes() never fail

2019-07-18 Thread Michal Hocko
On Mon 15-07-19 13:10:33, David Hildenbrand wrote: > On 01.07.19 12:27, Michal Hocko wrote: > > On Mon 01-07-19 11:36:44, Oscar Salvador wrote: > >> On Mon, Jul 01, 2019 at 10:51:44AM +0200, Michal Hocko wrote: > >>> Yeah, we do not allow to offline multi zone (node) ranges so the current > >>> cod

Re: [PATCH 09/16] sparc64: use the generic get_user_pages_fast code

2019-07-18 Thread Christoph Hellwig
On Thu, Jul 18, 2019 at 02:14:05PM -0700, David Miller wrote: > From: "Dmitry V. Levin" > Date: Thu, 18 Jul 2019 00:59:56 +0300 > > > So this ended up as commit 7b9afb86b6328f10dc2cad9223d7def12d60e505 > > (thanks to Anatoly for bisecting) and introduced a regression: > > futex.test from the str

Re: [PATCH] iomap: hide iomap_sector with CONFIG_BLOCK=n

2019-07-18 Thread Christoph Hellwig
On Fri, Jul 19, 2019 at 11:19:15AM +0900, Masahiro Yamada wrote: > I started to think > compiling all headers is more painful than useful. > > > MW is closing, so I am thinking of disabling it for now > to take time to re-think. For now this seems like the best idea. In the long run maybe we ca

Re: [PATCH v4 12/24] PM / devfreq: tegra30: Inline all one-line functions

2019-07-18 Thread Chanwoo Choi
On 19. 7. 19. 오전 11:14, Dmitry Osipenko wrote: > В Fri, 19 Jul 2019 10:27:16 +0900 > Chanwoo Choi пишет: > >> On 19. 7. 19. 오전 10:24, Chanwoo Choi wrote: >>> On 19. 7. 19. 오전 10:22, Dmitry Osipenko wrote: В Thu, 18 Jul 2019 18:09:05 +0900 Chanwoo Choi пишет: > On 19. 7. 16

Re: [PATCH] mm/Kconfig: additional help text for HMM_MIRROR option

2019-07-18 Thread Christoph Hellwig
On Thu, Jul 18, 2019 at 06:32:53PM -0700, john.hubb...@gmail.com wrote: > + HMM_MIRROR provides a way to mirror ranges of the CPU page tables > + of a process into a device page table. Here, mirror means "keep > + synchronized". Prerequisites: the device must provide the ability >

Re: [RFC PATCH v3 00/16] Core scheduling v3

2019-07-18 Thread Aaron Lu
On Thu, Jul 18, 2019 at 04:27:19PM -0700, Tim Chen wrote: > > > On 7/18/19 3:07 AM, Aaron Lu wrote: > > On Wed, Jun 19, 2019 at 02:33:02PM -0400, Julien Desfossez wrote: > > > > > With the below patch on top of v3 that makes use of util_avg to decide > > which task win, I can do all 8 steps and

KASAN: slab-out-of-bounds Write in check_noncircular

2019-07-18 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:22051d9c Merge tag 'platform-drivers-x86-v5.3-2' of git://.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14090a3460 kernel config: https://syzkaller.appspot.com/x/.config?x=135cb826ac59d7fc da

KASAN: use-after-free Write in tlb_finish_mmu

2019-07-18 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:22051d9c Merge tag 'platform-drivers-x86-v5.3-2' of git://.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=130c6ad060 kernel config: https://syzkaller.appspot.com/x/.config?x=d831b9cbe82e79e4 da

KASAN: use-after-free Read in finish_task_switch (2)

2019-07-18 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:22051d9c Merge tag 'platform-drivers-x86-v5.3-2' of git://.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12dab5a460 kernel config: https://syzkaller.appspot.com/x/.config?x=135cb826ac59d7fc da

Re: [PATCHv4 1/2] media: docs-rst: Document memory-to-memory video decoder interface

2019-07-18 Thread Tomasz Figa
On Wed, Jul 17, 2019 at 9:18 PM Nicolas Dufresne wrote: > > Hello, > > there is one little detail/proposal, see inline . > > Le lundi 03 juin 2019 à 13:28 +0200, Hans Verkuil a écrit : > > From: Tomasz Figa > > > > Due to complexity of the video decoding process, the V4L2 drivers of > > stateful

Re: [PATCH v3] nvme-pci: Support shared tags across queues for Apple 2018 controllers

2019-07-18 Thread Balbir Singh
On Fri, Jul 19, 2019 at 3:31 PM Benjamin Herrenschmidt wrote: > > From 8dcba2ef5b1466b023b88b4eca463b30de78d9eb Mon Sep 17 00:00:00 2001 > From: Benjamin Herrenschmidt > Date: Fri, 19 Jul 2019 15:03:06 +1000 > Subject: > > Another issue with the Apple T2 based 2018 controllers seem to be > that t

Здравствуйте! Вас интересуют клиентские базы данных?

2019-07-18 Thread jyb2011
Здравствуйте! Вас интересуют клиентские базы данных?

[PATCH v3] nvme-pci: Support shared tags across queues for Apple 2018 controllers

2019-07-18 Thread Benjamin Herrenschmidt
>From 8dcba2ef5b1466b023b88b4eca463b30de78d9eb Mon Sep 17 00:00:00 2001 From: Benjamin Herrenschmidt Date: Fri, 19 Jul 2019 15:03:06 +1000 Subject: Another issue with the Apple T2 based 2018 controllers seem to be that they blow up (and shut the machine down) if there's a tag collision between t

Re: [PATCH v2 1/3] tools/perf: Move kvm-stat header file from conditional inclusion to common include section

2019-07-18 Thread Ravi Bangoria
LGTM. For the series, Reviewed-By: Ravi Bangoria

Re: [PATCH v2] nvme-pci: Support shared tags across queues for Apple 2018 controllers

2019-07-18 Thread Benjamin Herrenschmidt
On Fri, 2019-07-19 at 05:01 +, Damien Le Moal wrote: > > I suppose that would work and be simpler. I honestly don't know much > > about the block layer and tag allocation so I stayed away from it :-) > > > > I'll dig, but a hint would be welcome :) > > Uuuh.. Never played with the tag managem

Re: [PATCH] mm/Kconfig: additional help text for HMM_MIRROR option

2019-07-18 Thread John Hubbard
On 7/18/19 9:34 PM, Ira Weiny wrote: > On Thu, Jul 18, 2019 at 06:32:53PM -0700, john.hubb...@gmail.com wrote: >> From: John Hubbard ... >> + Select HMM_MIRROR if you have hardware that meets the above >> + description. An early, partial list of such hardware is: >> + an NVIDIA GPU

[PATCH] PCI: Add ACS quirk for Cavium ThunderX 2 root port devices

2019-07-18 Thread Shannon Zhao
From: Shannon Zhao Like commit f2ddaf8(PCI: Apply Cavium ThunderX ACS quirk to more Root Ports), it should apply ACS quirk to ThunderX 2 root port devices. Signed-off-by: Shannon Zhao --- drivers/pci/quirks.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/pci/qu

Re: [PATCH] [RFC] dmaengine: add fifo_size member

2019-07-18 Thread Vinod Koul
On 05-07-19, 11:45, Sameer Pujar wrote: > Hi Vinod, > > What are your final thoughts regarding this? Hi sameer, Sorry for the delay in replying On this, I am inclined to think that dma driver should not be involved. The ADMAIF needs this configuration and we should take the path of dma_router f

Re: [PATCH v2] nvme-pci: Support shared tags across queues for Apple 2018 controllers

2019-07-18 Thread Damien Le Moal
On 2019/07/19 13:49, Benjamin Herrenschmidt wrote: > On Fri, 2019-07-19 at 04:43 +, Damien Le Moal wrote: >> On 2019/07/19 13:37, Benjamin Herrenschmidt wrote: >>> Another issue with the Apple T2 based 2018 controllers seem to be >>> that they blow up (and shut the machine down) if there's a ta

Re: [PATCH v2] nvme-pci: Support shared tags across queues for Apple 2018 controllers

2019-07-18 Thread Benjamin Herrenschmidt
On Fri, 2019-07-19 at 14:49 +1000, Benjamin Herrenschmidt wrote: > On Fri, 2019-07-19 at 04:43 +, Damien Le Moal wrote: > > On 2019/07/19 13:37, Benjamin Herrenschmidt wrote: > > > Another issue with the Apple T2 based 2018 controllers seem to be > > > that they blow up (and shut the machine do

Re: [PATCH v3 8/9] x86/mm/tlb: Remove UV special case

2019-07-18 Thread Nadav Amit
> On Jul 18, 2019, at 7:25 PM, Mike Travis wrote: > > It is a fact that the UV is still the UV and SGI is now part of HPE. The > current external product is known as SuperDome Flex. It is both up to date > as well as very well maintained. The ACK I provided was an okay to change > the code,

Re: [PATCH] arm64: Explicitly set pstate.ssbs for el0 on kernel entry

2019-07-18 Thread Neeraj Upadhyay
Hi Marc, On 7/9/19 7:52 PM, Marc Zyngier wrote: On 09/07/2019 15:18, Neeraj Upadhyay wrote: Hi Marc, On 7/9/19 6:38 PM, Marc Zyngier wrote: Hi Neeraj, On 09/07/2019 12:22, Neeraj Upadhyay wrote: For cpus which do not support pstate.ssbs feature, el0 might not retain spsr.ssbs. This is prob

Re: [PATCH v2] nvme-pci: Support shared tags across queues for Apple 2018 controllers

2019-07-18 Thread Benjamin Herrenschmidt
On Fri, 2019-07-19 at 04:43 +, Damien Le Moal wrote: > On 2019/07/19 13:37, Benjamin Herrenschmidt wrote: > > Another issue with the Apple T2 based 2018 controllers seem to be > > that they blow up (and shut the machine down) if there's a tag > > collision between the IO queue and the Admin que

Re: [PATCH v2] nvme-pci: Support shared tags across queues for Apple 2018 controllers

2019-07-18 Thread Damien Le Moal
On 2019/07/19 13:37, Benjamin Herrenschmidt wrote: > Another issue with the Apple T2 based 2018 controllers seem to be > that they blow up (and shut the machine down) if there's a tag > collision between the IO queue and the Admin queue. > > My suspicion is that they use our tags for their interna

Re: [PATCH 4.14 00/80] 4.14.134-stable review

2019-07-18 Thread Bharath Vedartham
Built and booted on my x86 machine. No dmesg regressions. Thank you Bharath

Re: [PATCH 4.4 00/40] 4.4.186-stable review

2019-07-18 Thread Bharath Vedartham
Built and booted on my x86 system. No dmesg regressions found. Thank you Bharath

Re: [PATCH 5.1 00/54] 5.1.19-stable review

2019-07-18 Thread Bharath Vedartham
Built and booted on my x86 machine. No dmesg regressions found. Thank you Bharath

Re: [PATCH 4.9 00/54] 4.9.186-stable review

2019-07-18 Thread Bharath Vedartham
Built and booted in my x86 test machine. No regressions found. Thank you Bharath

[PATCH AUTOSEL 5.2 009/171] drm/bochs: Fix connector leak during driver unload

2019-07-18 Thread Sasha Levin
From: Sam Bobroff [ Upstream commit 3c6b8625dde82600fd03ad1fcba223f1303ee535 ] When unloading the bochs-drm driver, a warning message is printed by drm_mode_config_cleanup() because a reference is still held to one of the drm_connector structs. Correct this by calling drm_atomic_helper_shutdown

[PATCH AUTOSEL 5.2 008/171] staging: vt6656: use meaningful error code during buffer allocation

2019-07-18 Thread Sasha Levin
From: Quentin Deslandes [ Upstream commit d8c2869300ab5f7a19bf6f5a04fe473c5c9887e3 ] Check on called function's returned value for error and return 0 on success or a negative errno value on error instead of a boolean value. Signed-off-by: Quentin Deslandes Signed-off-by: Greg Kroah-Hartman Si

[PATCH AUTOSEL 5.2 026/171] drm/amd/display: Disable ABM before destroy ABM struct

2019-07-18 Thread Sasha Levin
From: Paul Hsieh [ Upstream commit 1090d58d4815b1fcd95a80987391006c86398b4c ] [Why] When disable driver, OS will set backlight optimization then do stop device. But this flag will cause driver to enable ABM when driver disabled. [How] Send ABM disable command before destroy ABM construct Sign

[PATCH AUTOSEL 5.2 011/171] tty: max310x: Fix invalid baudrate divisors calculator

2019-07-18 Thread Sasha Levin
From: Serge Semin [ Upstream commit 35240ba26a932b279a513f66fa4cabfd7af55221 ] Current calculator doesn't do it' job quite correct. First of all the max310x baud-rates generator supports the divisor being less than 16. In this case the x2/x4 modes can be used to double or quadruple the reference

[PATCH AUTOSEL 5.2 031/171] PCI: Return error if cannot probe VF

2019-07-18 Thread Sasha Levin
From: Alex Williamson [ Upstream commit 76002d8b48c4b08c9bd414517dd295e132ad910b ] Commit 0e7df22401a3 ("PCI: Add sysfs sriov_drivers_autoprobe to control VF driver binding") allows the user to specify that drivers for VFs of a PF should not be probed, but it actually causes pci_device_probe() t

[PATCH AUTOSEL 5.2 038/171] f2fs: Fix accounting for unusable blocks

2019-07-18 Thread Sasha Levin
From: Daniel Rosenberg [ Upstream commit a4c3ecaaadac5693f555cfef1c9eecf4c39df818 ] Fixes possible underflows when dealing with unusable blocks. Signed-off-by: Daniel Rosenberg Reviewed-by: Chao Yu Signed-off-by: Jaegeuk Kim Signed-off-by: Sasha Levin --- fs/f2fs/f2fs.h | 15 ++

[PATCH AUTOSEL 5.2 044/171] i2c: nvidia-gpu: resume ccgx i2c client

2019-07-18 Thread Sasha Levin
From: Ajay Gupta [ Upstream commit 9f2e244d0a39eb437f98324ac315e605e48636db ] Cypress USB Type-C CCGx controller firmware version 3.1.10 (which is being used in many NVIDIA GPU cards) has known issue of not triggering interrupt when a USB device is hot plugged to runtime resume the controller. I

[PATCH AUTOSEL 5.2 039/171] f2fs: Lower threshold for disable_cp_again

2019-07-18 Thread Sasha Levin
From: Daniel Rosenberg [ Upstream commit ae4ad7ea09d32ff1b6fb908ff12f8c1bd5241b29 ] The existing threshold for allowable holes at checkpoint=disable time is too high. The OVP space contains reserved segments, which are always in the form of free segments. These must be subtracted from the OVP va

[PATCH AUTOSEL 5.2 048/171] tty/serial: digicolor: Fix digicolor-usart already registered warning

2019-07-18 Thread Sasha Levin
From: Kefeng Wang [ Upstream commit c7ad9ba0611c53cfe194223db02e3bca015f0674 ] When modprobe/rmmod/modprobe module, if platform_driver_register() fails, the kernel complained, proc_dir_entry 'driver/digicolor-usart' already registered WARNING: CPU: 1 PID: 5636 at fs/proc/generic.c:360 proc_

[PATCH AUTOSEL 5.2 046/171] drm/omap: don't check dispc timings for DSI

2019-07-18 Thread Sasha Levin
From: Sebastian Reichel [ Upstream commit ad9df7d91b4a6e8f4b20c2bf539ac09b3b2ad6eb ] While most display types only forward their VM to the DISPC, this is not true for DSI. DSI calculates the VM for DISPC based on its own, but it's not identical. Actually the DSI VM is not even a valid DISPC VM m

[PATCH AUTOSEL 5.2 041/171] drm/crc-debugfs: User irqsafe spinlock in drm_crtc_add_crc_entry

2019-07-18 Thread Sasha Levin
From: Daniel Vetter [ Upstream commit 1882018a70e06376234133e69ede9dd743b4dbd9 ] We can be called from any context, we need to be prepared. Noticed this while hacking on vkms, which calls this function from a normal worker. Which really upsets lockdep. Cc: Rodrigo Siqueira Cc: Tomeu Vizoso C

[PATCH AUTOSEL 5.2 047/171] memstick: Fix error cleanup path of memstick_init

2019-07-18 Thread Sasha Levin
From: Wang Hai [ Upstream commit 65f1a0d39c289bb6fc85635528cd36c4b07f560e ] If bus_register fails. On its error handling path, it has cleaned up what it has done. There is no need to call bus_unregister again. Otherwise, if bus_unregister is called, issues such as null-ptr-deref will arise. Syz

[PATCH AUTOSEL 5.2 065/171] iio: adxl372: fix iio_triggered_buffer_{pre,post}enable positions

2019-07-18 Thread Sasha Levin
From: Alexandru Ardelean [ Upstream commit 0e4f0b42f42d88507b48282c8915f502551534e4 ] The iio_triggered_buffer_{predisable,postenable} functions attach/detach the poll functions. For the predisable hook, the disable code should occur before detaching the poll func, and for the postenable hook,

[PATCH AUTOSEL 5.2 066/171] serial: imx: fix locking in set_termios()

2019-07-18 Thread Sasha Levin
From: Sergey Organov [ Upstream commit 4e828c3e09201512be5ee162393f334321f7cf01 ] imx_uart_set_termios() called imx_uart_rts_active(), or imx_uart_rts_inactive() before taking port->port.lock. As a consequence, sport->port.mctrl that these functions modify could have been changed without holdin

[PATCH AUTOSEL 5.2 061/171] dma-remap: Avoid de-referencing NULL atomic_pool

2019-07-18 Thread Sasha Levin
From: Florian Fainelli [ Upstream commit 4b4b077cbd0a998aebaa72c199e06b8a4c8dcfee ] With architectures allowing the kernel to be placed almost arbitrarily in memory (e.g.: ARM64), it is possible to have the kernel resides at physical addresses above 4GB, resulting in neither the default CMA area

[PATCH AUTOSEL 5.2 064/171] iio:core: Fix bug in length of event info_mask and catch unhandled bits set in masks.

2019-07-18 Thread Sasha Levin
From: Young Xiao <92siuy...@gmail.com> [ Upstream commit 936d3e536dcf88ce80d27bdb637009b13dba6d8c ] The incorrect limit for the for_each_set_bit loop was noticed whilst fixing this other case. Note that as we only have 3 possible entries a the moment and the value was set to 4, the bug would not

[PATCH AUTOSEL 5.2 073/171] mmc: sdhci: sdhci-pci-o2micro: Check if controller supports 8-bit width

2019-07-18 Thread Sasha Levin
From: Raul E Rangel [ Upstream commit de23f0b757766d9fae59df97da6e8bdc5b231351 ] The O2 controller supports 8-bit EMMC access. JESD84-B51 section A.6.3.a defines the bus testing procedure that `mmc_select_bus_width()` implements. This is used to determine the actual bus width of the eMMC. Sign

[PATCH AUTOSEL 5.2 071/171] kvm: vmx: fix limit checking in get_vmx_mem_address()

2019-07-18 Thread Sasha Levin
From: Eugene Korenevsky [ Upstream commit c1a9acbc5295e278d788e9f7510f543bc9864fa2 ] Intel SDM vol. 3, 5.3: The processor causes a general-protection exception (or, if the segment is SS, a stack-fault exception) any time an attempt is made to access the following addresses in a segment: - A byte

[PATCH AUTOSEL 5.2 063/171] platform/x86: asus-wmi: Increase input buffer size of WMI methods

2019-07-18 Thread Sasha Levin
From: Yurii Pavlovskyi [ Upstream commit 98e865a522983f2afde075648ec9d15ea4bb9194 ] The asus-nb-wmi driver is matched by WMI alias but fails to load on TUF Gaming series laptops producing multiple ACPI errors in the kernel log. The input buffer for WMI method invocation size is 2 dwords, wherea

[PATCH AUTOSEL 5.2 067/171] serial: uartps: Use the same dynamic major number for all ports

2019-07-18 Thread Sasha Levin
From: Shubhrajyoti Datta [ Upstream commit ab262666018de6f4e206b021386b93ed0c164316 ] Let kernel to find out major number dynamically for the first device and then reuse it for other instances. This fixes the issue that each uart is registered with a different major number. After the patch: crw

[PATCH AUTOSEL 5.2 074/171] KVM: nVMX: Intercept VMWRITEs to GUEST_{CS,SS}_AR_BYTES

2019-07-18 Thread Sasha Levin
From: Sean Christopherson [ Upstream commit b643780562af5378ef7fe731c65b8f93e49c59c6 ] VMMs frequently read the guest's CS and SS AR bytes to detect 64-bit mode and CPL respectively, but effectively never write said fields once the VM is initialized. Intercepting VMWRITEs for the two fields sav

[PATCH AUTOSEL 5.2 076/171] drm/msm/adreno: Ensure that the zap shader region is big enough

2019-07-18 Thread Sasha Levin
From: Jordan Crouse [ Upstream commit 6672e11cad662ce6631e04c38f92a140a99c042c ] Before loading the zap shader we should ensure that the reserved memory region is big enough to hold the loaded file. Signed-off-by: Jordan Crouse Reviewed-by: Bjorn Andersson Reviewed-by: Jeffrey Hugo Signed-of

[PATCH AUTOSEL 5.2 083/171] i2c: stm32f7: fix the get_irq error cases

2019-07-18 Thread Sasha Levin
From: Fabrice Gasnier [ Upstream commit 79b4499524ed659fb76323efc30f3dc03967c88f ] During probe, return the "get_irq" error value instead of -EINVAL which allows the driver to be deferred probed if needed. Fix also the case where of_irq_get() returns a negative value. Note : On failure of_irq_ge

[PATCH AUTOSEL 5.2 084/171] iio: st_accel: fix iio_triggered_buffer_{pre,post}enable positions

2019-07-18 Thread Sasha Levin
From: Alexandru Ardelean [ Upstream commit 05b8bcc96278c9ef927a6f25a98e233e55de42e1 ] The iio_triggered_buffer_{predisable,postenable} functions attach/detach the poll functions. For the predisable hook, the disable code should occur before detaching the poll func, and for the postenable hook,

[PATCH AUTOSEL 5.2 080/171] staging: ks7010: Fix build error

2019-07-18 Thread Sasha Levin
From: YueHaibing [ Upstream commit 3e5bc68fa596874500e8c718605aa44d5e42a34c ] when CRYPTO is m and KS7010 is y, building fails: drivers/staging/ks7010/ks_hostif.o: In function `michael_mic.constprop.13': ks_hostif.c:(.text+0x560): undefined reference to `crypto_alloc_shash' ks_hostif.c:(.text+0

[PATCH AUTOSEL 5.2 095/171] fixdep: check return value of printf() and putchar()

2019-07-18 Thread Sasha Levin
From: Masahiro Yamada [ Upstream commit 6f9ac9f4427ec0470ccffbf852cfaf326677cc21 ] When there is not enough space on your storage device, the build will fail with 'No space left on device' error message. The reason is obvious from the message, so you will free up some disk space, then you will

[PATCH AUTOSEL 5.2 077/171] powerpc/pci/of: Fix OF flags parsing for 64bit BARs

2019-07-18 Thread Sasha Levin
From: Alexey Kardashevskiy [ Upstream commit df5be5be8735ef2ae80d5ae1f2453cd81a035c4b ] When the firmware does PCI BAR resource allocation, it passes the assigned addresses and flags (prefetch/64bit/...) via the "reg" property of a PCI device device tree node so the kernel does not need to do re

[PATCH AUTOSEL 5.2 088/171] phy: meson-g12a-usb3-pcie: disable locking for cr_regmap

2019-07-18 Thread Sasha Levin
From: Neil Armstrong [ Upstream commit 5fc2aa3ec9efad97dd7c316f3c8e4c6268bbed9b ] Locking is not needed for the phy_g12a_usb3_pcie_cr_bus_read/write() and currently it causes the following BUG because of the usage of the regmap_read_poll_timeout() running in spinlock_irq, configured by regmap f

[PATCH AUTOSEL 5.2 072/171] usb: gadget: storage: Remove warning message

2019-07-18 Thread Sasha Levin
From: EJ Hsu [ Upstream commit e70b3f5da00119e057b7faa557753fee7f786f17 ] This change is to fix below warning message in following scenario: usb_composite_setup_continue: Unexpected call When system tried to enter suspend, the fsg_disable() will be called to disable fsg driver and send a signal

[PATCH AUTOSEL 5.2 075/171] kvm: vmx: segment limit check: use access length

2019-07-18 Thread Sasha Levin
From: Eugene Korenevsky [ Upstream commit fdb28619a8f033c13f5d9b9e8b5536bb6e68a2c3 ] There is an imperfection in get_vmx_mem_address(): access length is ignored when checking the limit. To fix this, pass access length as a function argument. The access length is usually obvious since it is used

[PATCH AUTOSEL 5.2 097/171] mfd: cros_ec: Register cros_ec_lid_angle driver when presented

2019-07-18 Thread Sasha Levin
From: Gwendal Grignou [ Upstream commit 1bb407f17c5316888c3c446e26cb2bb78943f236 ] Register driver when EC indicates has precise lid angle calculation code running. Fix incorrect extra resource allocation in cros_ec_sensors_register(). Signed-off-by: Gwendal Grignou Signed-off-by: Lee Jones S

[PATCH AUTOSEL 5.2 090/171] iio: iio-utils: Fix possible incorrect mask calculation

2019-07-18 Thread Sasha Levin
From: Bastien Nocera [ Upstream commit 208a68c8393d6041a9086299f3d7943d44d6 ] On some machines, iio-sensor-proxy was returning all 0's for IIO sensor values. It turns out that the bits_used for this sensor is 32, which makes the mask calculation: *mask = (1 << 32) - 1; If the compiler inte

[PATCH AUTOSEL 5.2 093/171] powerpc/xmon: Fix disabling tracing while in xmon

2019-07-18 Thread Sasha Levin
From: "Naveen N. Rao" [ Upstream commit aaf06665f7ea3ee9f9754e16c1a507a89f1de5b1 ] Commit ed49f7fd6438d ("powerpc/xmon: Disable tracing when entering xmon") added code to disable recording trace entries while in xmon. The commit introduced a variable 'tracing_enabled' to record if tracing was en

[PATCH AUTOSEL 5.2 092/171] powerpc/cacheflush: fix variable set but not used

2019-07-18 Thread Sasha Levin
From: Qian Cai [ Upstream commit 04db3ede40ae4fc23a5c4237254c4a53bbe4c1f2 ] The powerpc's flush_cache_vmap() is defined as a macro and never use both of its arguments, so it will generate a compilation warning, lib/ioremap.c: In function 'ioremap_page_range': lib/ioremap.c:203:16: warning: vari

[PATCH AUTOSEL 5.2 089/171] PCI: xilinx-nwl: Fix Multi MSI data programming

2019-07-18 Thread Sasha Levin
From: Bharat Kumar Gogada [ Upstream commit 181fa434d0514e40ebf6e9721f2b72700287b6e2 ] According to the PCI Local Bus specification Revision 3.0, section 6.8.1.3 (Message Control for MSI), endpoints that are Multiple Message Capable as defined by bits [3:1] in the Message Control for MSI can req

[PATCH AUTOSEL 5.2 086/171] kbuild: Add -Werror=unknown-warning-option to CLANG_FLAGS

2019-07-18 Thread Sasha Levin
From: Nathan Chancellor [ Upstream commit 589834b3a0097a4908f4112eac0ca2feb486fa32 ] In commit ebcc5928c5d9 ("arm64: Silence gcc warnings about arch ABI drift"), the arm64 Makefile added -Wno-psabi to KBUILD_CFLAGS, which is a GCC only option so clang rightfully complains: warning: unknown warn

[PATCH v2] nvme-pci: Support shared tags across queues for Apple 2018 controllers

2019-07-18 Thread Benjamin Herrenschmidt
Another issue with the Apple T2 based 2018 controllers seem to be that they blow up (and shut the machine down) if there's a tag collision between the IO queue and the Admin queue. My suspicion is that they use our tags for their internal tracking and don't mix them with the queue id. They also se

[PATCH AUTOSEL 5.2 107/171] powerpc/mm: mark more tlb functions as __always_inline

2019-07-18 Thread Sasha Levin
From: Masahiro Yamada [ Upstream commit 6d3ca7e73642ce17398f4cd5df1780da4a1ccdaf ] With CONFIG_OPTIMIZE_INLINING enabled, Laura Abbott reported error with gcc 9.1.1: arch/powerpc/mm/book3s64/radix_tlb.c: In function '_tlbiel_pid': arch/powerpc/mm/book3s64/radix_tlb.c:104:2: warning: asm ope

[PATCH AUTOSEL 5.2 098/171] mfd: madera: Add missing of table registration

2019-07-18 Thread Sasha Levin
From: Daniel Gomez [ Upstream commit 5aa3709c0a5c026735b0ddd4ec80810a23d65f5b ] MODULE_DEVICE_TABLE(of, ) should be called to complete DT OF mathing mechanism and register it. Before this patch: modinfo ./drivers/mfd/madera.ko | grep alias After this patch: modinfo ./drivers/mfd/madera.ko | gr

[PATCH AUTOSEL 5.2 096/171] recordmcount: Fix spurious mcount entries on powerpc

2019-07-18 Thread Sasha Levin
From: "Naveen N. Rao" [ Upstream commit 80e5302e4bc85a6b685b7668c36c6487b5f90e9a ] An impending change to enable HAVE_C_RECORDMCOUNT on powerpc leads to warnings such as the following: # modprobe kprobe_example ftrace-powerpc: Not expected bl: opcode is 3c4c0001 WARNING: CPU: 0 PID: 227 a

[PATCH AUTOSEL 5.2 101/171] mfd: hi655x-pmic: Fix missing return value check for devm_regmap_init_mmio_clk

2019-07-18 Thread Sasha Levin
From: Axel Lin [ Upstream commit 7efd105c27fd2323789b41b64763a0e33ed79c08 ] Since devm_regmap_init_mmio_clk can fail, add return value checking. Signed-off-by: Axel Lin Acked-by: Chen Feng Signed-off-by: Lee Jones Signed-off-by: Sasha Levin --- drivers/mfd/hi655x-pmic.c | 2 ++ 1 file chan

[PATCH AUTOSEL 5.2 109/171] serial: sh-sci: Terminate TX DMA during buffer flushing

2019-07-18 Thread Sasha Levin
From: Geert Uytterhoeven [ Upstream commit 775b7ffd7d6d5db320d99b0a485c51e04dfcf9f1 ] While the .flush_buffer() callback clears sci_port.tx_dma_len since commit 1cf4a7efdc71cab8 ("serial: sh-sci: Fix race condition causing garbage during shutdown"), it does not terminate a transmit DMA operation

[PATCH AUTOSEL 5.2 112/171] powerpc/mm: Handle page table allocation failures

2019-07-18 Thread Sasha Levin
From: "Aneesh Kumar K.V" [ Upstream commit 2230ebf6e6dd0b7751e2921b40f6cfe34f09bb16 ] This fixes kernel crash that arises due to not handling page table allocation failures while allocating hugetlb page table. Fixes: e2b3d202d1db ("powerpc: Switch 16GB and 16MB explicit hugepages to a differen

[PATCH AUTOSEL 5.2 122/171] perf test mmap-thread-lookup: Initialize variable to suppress memory sanitizer warning

2019-07-18 Thread Sasha Levin
From: Numfor Mbiziwo-Tiapo [ Upstream commit 4e4cf62b37da5ff45c904a3acf242ab29ed5881d ] Running the 'perf test' command after building perf with a memory sanitizer causes a warning that says: WARNING: MemorySanitizer: use-of-uninitialized-value... in mmap-thread-lookup.c Initializing the go

[PATCH AUTOSEL 5.2 117/171] PCI: mobiveil: Fix PCI base address in MEM/IO outbound windows

2019-07-18 Thread Sasha Levin
From: Hou Zhiqiang [ Upstream commit f99536e9d2f55996038158a6559d4254a7cc1693 ] The outbound memory windows PCI base addresses should be taken from the 'ranges' property of DT node to setup MEM/IO outbound windows decoding correctly instead of being hardcoded to zero. Update the code to retriev

[PATCH AUTOSEL 5.2 116/171] KVM: nVMX: Stash L1's CR3 in vmcs01.GUEST_CR3 on nested entry w/o EPT

2019-07-18 Thread Sasha Levin
From: Sean Christopherson [ Upstream commit f087a02941feacf7d6f097522bc67c602fda18e6 ] KVM does not have 100% coverage of VMX consistency checks, i.e. some checks that cause VM-Fail may only be detected by hardware during a nested VM-Entry. In such a case, KVM must restore L1's state to the pre

[PATCH AUTOSEL 5.2 120/171] PCI: mobiveil: Initialize Primary/Secondary/Subordinate bus numbers

2019-07-18 Thread Sasha Levin
From: Hou Zhiqiang [ Upstream commit 6f3ab451aa5c2cbff33197d82fe8489cbd55ad91 ] The reset value of Primary, Secondary and Subordinate bus numbers is zero which is a broken setup. Program a sensible default value for Primary/Secondary/Subordinate bus numbers. Signed-off-by: Hou Zhiqiang Signed

[PATCH AUTOSEL 5.2 113/171] IB/ipoib: Add child to parent list only if device initialized

2019-07-18 Thread Sasha Levin
From: Valentine Fatiev [ Upstream commit 91b01061fef9c57d2f5b712a6322ef51061f4efd ] Despite failure in ipoib_dev_init() we continue with initialization flow and creation of child device. It causes to the situation where this child device is added too early to parent device list. Change the logi

[PATCH AUTOSEL 5.2 110/171] serial: sh-sci: Fix TX DMA buffer flushing and workqueue races

2019-07-18 Thread Sasha Levin
From: Geert Uytterhoeven [ Upstream commit 8493eab02608b0e82f67b892aa72882e510c31d0 ] When uart_flush_buffer() is called, the .flush_buffer() callback zeroes the tx_dma_len field. This may race with the work queue function handling transmit DMA requests: 1. If the buffer is flushed before th

[PATCH AUTOSEL 5.2 114/171] arm64: assembler: Switch ESB-instruction with a vanilla nop if !ARM64_HAS_RAS

2019-07-18 Thread Sasha Levin
From: James Morse [ Upstream commit 2b68a2a963a157f024c67c0697b16f5f792c8a35 ] The ESB-instruction is a nop on CPUs that don't implement the RAS extensions. This lets us use it in places like the vectors without having to use alternatives. If someone disables CONFIG_ARM64_RAS_EXTN, this instruc

  1   2   3   4   5   6   7   8   9   10   >