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

2019-07-02 Thread Kees Cook
On Mon, Jul 01, 2019 at 09:52:08AM -0600, Ross Zwisler wrote: > This reverts commit 392bef709659abea614abfe53cf228e7a59876a4. > > Per the discussion here: > > https://lkml.org/lkml/2019/6/20/830 > > the above referenced commit breaks kernel compilation with old GCC > toolchains as well as

Re: [PATCH 4/6] vfs: Allow mount information to be queried by fsinfo() [ver #15]

2019-07-02 Thread Ian Kent
On Wed, 2019-07-03 at 09:09 +0800, Ian Kent wrote: > Hi Christian, > > About the propagation attributes you mentioned ... Umm ... how did you work out if a mount is unbindable from proc mountinfo? I didn't notice anything that could be used for that when I was looking at this. > > On Fri,

Re: pagecache locking

2019-07-02 Thread Boaz Harrosh
On 03/07/2019 04:07, Patrick Farrell wrote: > Recursively read locking is generally unsafe, that’s why lockdep > complains about it. The common RW lock primitives are queued in > their implementation, meaning this recursive read lock sequence: > P1 - read (gets lock) > P2 - write > P1 - read > >

答复: [PATCH RFC v2] mtd: ubi: Add fastmap sysfs attribute

2019-07-02 Thread chengzhihao
ping ~ -邮件原件- 发件人: chengzhihao 发送时间: 2019年6月28日 20:06 收件人: david.oberhollen...@sigma-star.at; rich...@nod.at; da...@sigma-star.at; boris.brezil...@free-electrons.com; zhangyi (F) 抄送: linux-...@lists.infradead.org; linux-kernel@vger.kernel.org; chengzhihao 主题: [PATCH RFC v2] mtd: ubi:

Re: [PATCH 5.1 00/55] 5.1.16-stable review

2019-07-02 Thread Kelsey Skunberg
On Tue, Jul 02, 2019 at 10:01:08AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 5.1.16 release. > There are 55 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

Re: [PATCH net-next v6 05/15] ethtool: helper functions for netlink interface

2019-07-02 Thread Jakub Kicinski
On Tue, 2 Jul 2019 18:34:37 +0200, Michal Kubecek wrote: > > >+ ret = nla_parse_nested(tb, ETHTOOL_A_HEADER_MAX, nest, > > >+ policy ?: dflt_header_policy, extack); > > >+ if (ret < 0) > > > > if (ret) > > > > Same remark goes to the rest of the code (also the rest of

Re: [PATCH] module: add usage links when calling ref_module func

2019-07-02 Thread Zhiqiang Liu
On 2019/7/1 21:55, Jessica Yu wrote: > +++ Zhiqiang Liu [28/06/19 20:32 +0800]: >> From: Zhiqiang Liu >> >> Problem: Users can call ref_module func in their modules to construct >> relationships with other modules. However, the holders >> '/sys/module//holders' of the target module donot include

Re: [PATCH net-next v6 04/15] ethtool: introduce ethtool netlink interface

2019-07-02 Thread Jakub Kicinski
On Tue, 2 Jul 2019 13:49:59 +0200 (CEST), Michal Kubecek wrote: > diff --git a/Documentation/networking/ethtool-netlink.txt > b/Documentation/networking/ethtool-netlink.txt > new file mode 100644 > index ..97c369aa290b > --- /dev/null > +++

Re: [PATCH 4.19 00/72] 4.19.57-stable review

2019-07-02 Thread Guenter Roeck
On Tue, Jul 02, 2019 at 10:01:01AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.19.57 release. > There are 72 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

[PATCH v4] dmaengine: tegra-apb: Support per-burst residue granularity

2019-07-02 Thread Dmitry Osipenko
Tegra's APB DMA engine updates words counter after each transferred burst of data, hence it can report transfer's residual with more fidelity which may be required in cases like audio playback. In particular this fixes audio stuttering during playback in a chromium web browser. The patch is based

linux-next: Fixes tag needs some work in the staging tree

2019-07-02 Thread Stephen Rothwell
Hi all, In commit 597382cbd3c1 ("dt-bindings: iio: adc: stm32: add missing vdda supply") Fixes tag Fixes: 841fcea454fe ("Documentation: dt-bindings: Document STM32 ADC DT has these problem(s): - Subject has leading but no trailing parentheses - Subject has leading but no trailing

Re: [PATCH] mm, slab: Extend slab/shrink to shrink all the memcg caches

2019-07-02 Thread Waiman Long
On 7/2/19 4:03 PM, Andrew Morton wrote: > On Tue, 2 Jul 2019 14:37:30 -0400 Waiman Long wrote: > >> Currently, a value of '1" is written to /sys/kernel/slab//shrink >> file to shrink the slab by flushing all the per-cpu slabs and free >> slabs in partial lists. This applies only to the root

[PATCH] PCI: hv: fix pci-hyperv build, depends on SYSFS

2019-07-02 Thread Randy Dunlap
From: Randy Dunlap Fix build errors when building almost-allmodconfig but with SYSFS not set (not enabled). Fixes these build errors: ERROR: "pci_destroy_slot" [drivers/pci/controller/pci-hyperv.ko] undefined! ERROR: "pci_create_slot" [drivers/pci/controller/pci-hyperv.ko] undefined!

Re: [PATCH] x86/stacktrace: Do not access user space memory unnecessarily

2019-07-02 Thread Peter Zijlstra
On Tue, Jul 02, 2019 at 10:18:27PM +0200, Peter Zijlstra wrote: > I think; lemme re-read that thread. *completely* untested, not even been near a compiler yet. but it now includes 32bit support and should be more or less complete. I removed the most horrendous (rbx control flow) hacks from

Re: [PATCH] PCI: hv: fix pci-hyperv build, depends on SYSFS

2019-07-02 Thread Matthew Wilcox
On Tue, Jul 02, 2019 at 04:24:30PM -0700, Randy Dunlap wrote: > From: Randy Dunlap > > Fix build errors when building almost-allmodconfig but with SYSFS > not set (not enabled). Fixes these build errors: > > ERROR: "pci_destroy_slot" [drivers/pci/controller/pci-hyperv.ko] undefined! > ERROR:

[Problem]testOpenUpgradeLock test failed in nfsv4.0 in 5.2.0-rc7

2019-07-02 Thread Su Yanjun
Hi Frank We tested the pynfs of NFSv4.0 on the latest version of the kernel (5.2.0-rc7). I encountered a problem while testing st_lock.testOpenUpgradeLock. The problem is now as follows: ** LOCK24 st_lock.testOpenUpgradeLock : FAILURE    

Re: [PATCH v1 10/11] perf intel-pt: Smatch: Fix potential NULL pointer dereference

2019-07-02 Thread Leo Yan
Hi Adrian, On Tue, Jul 02, 2019 at 02:07:40PM +0300, Adrian Hunter wrote: > On 2/07/19 1:34 PM, Leo Yan wrote: > > Based on the following report from Smatch, fix the potential > > NULL pointer dereference check. > > It never is NULL. Remove the NULL test if you want: > > - if

Regression caused by commit c54f24e3 (nfsd: fix performance-limiting session calculation)

2019-07-02 Thread Paul Menzel
Dear Bruce, Could it be that commit c54f24e3 (nfsd: fix performance-limiting session calculation) causes a regression on big memory machines (1 TB)? From c54f24e338ed2a35218f117a4a1afb5f9e2b4e64 Mon Sep 17 00:00:00 2001 From: "J. Bruce Fields" Date: Thu, 21 Feb 2019 10:47:00 -0500 Subject:

Re: [PATCH net-next v6 05/15] ethtool: helper functions for netlink interface

2019-07-02 Thread Jakub Kicinski
On Tue, 2 Jul 2019 13:50:04 +0200 (CEST), Michal Kubecek wrote: > Add common request/reply header definition and helpers to parse request > header and fill reply header. Provide ethnl_update_* helpers to update > structure members from request attributes (to be used for *_SET requests). > >

Re: [PATCH] filesystem-dax: Disable PMD support

2019-07-02 Thread Boaz Harrosh
On 03/07/2019 03:42, Dan Williams wrote: > On Tue, Jul 2, 2019 at 5:23 PM Boaz Harrosh wrote: <> > > Yes, but the trick is how to manage cases where someone waiting on one > type needs to be woken up by an event on the other. Exactly I'm totally with you on this. > So all I'm saying it lets

Re: [PATCH] net: core: page_pool: add user refcnt and reintroduce page_pool_destroy

2019-07-02 Thread Ivan Khoronzhuk
On Tue, Jul 02, 2019 at 09:58:40PM +0300, Ivan Khoronzhuk wrote: On Tue, Jul 02, 2019 at 08:29:07PM +0200, Jesper Dangaard Brouer wrote: On Tue, 2 Jul 2019 18:21:13 +0300 Ivan Khoronzhuk wrote: On Tue, Jul 02, 2019 at 05:10:29PM +0200, Jesper Dangaard Brouer wrote: On Tue, 2 Jul 2019

Re: [PATCH 4/6] vfs: Allow mount information to be queried by fsinfo() [ver #15]

2019-07-02 Thread Ian Kent
On Wed, 2019-07-03 at 09:24 +0800, Ian Kent wrote: > On Wed, 2019-07-03 at 09:09 +0800, Ian Kent wrote: > > Hi Christian, > > > > About the propagation attributes you mentioned ... > > Umm ... how did you work out if a mount is unbindable from proc > mountinfo? > > I didn't notice anything that

[PATCH 1/4] dt-bindings: phy: add binding for the Lantiq VRX200 and ARX300 PCIe PHYs

2019-07-02 Thread Martin Blumenstingl
Add the bindings for the PCIe PHY on Lantiq VRX200 and ARX300 SoCs. The IP block contains settings for the PHY and a PLL. The PLL mode is configurable through a dedicated #phy-cell in .dts. Signed-off-by: Martin Blumenstingl --- .../bindings/phy/lantiq,vrx200-pcie-phy.yaml | 87

Re: objtool warnings in prerelease clang-9

2019-07-02 Thread Peter Zijlstra
Hi Nick, That is good news; and I'll strive to read the email in more detail in the morning when there is a better chance of me actually understanding some of it :-) But his here is something I felt needed clarification: On Tue, Jul 02, 2019 at 01:53:51PM -0700, Nick Desaulniers wrote: > Of

Re: [PATCH] x86/stacktrace: Do not access user space memory unnecessarily

2019-07-02 Thread Peter Zijlstra
On Tue, Jul 02, 2019 at 01:39:05PM -0400, Steven Rostedt wrote: > On Tue, 2 Jul 2019 11:33:55 -0400 > Steven Rostedt wrote: > > > On Tue, 2 Jul 2019 16:14:05 +0200 (CEST) > > Thomas Gleixner wrote: > > > > > On Tue, 2 Jul 2019, Peter Zijlstra wrote: > > > > > > > On Tue, Jul 02, 2019 at

Re: [PATCH 4.14 00/43] 4.14.132-stable review

2019-07-02 Thread Guenter Roeck
On Tue, Jul 02, 2019 at 10:01:40AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.132 release. > There are 43 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

Re: [PATCH v1 00/11] perf: Fix errors detected by Smatch

2019-07-02 Thread Leo Yan
On Tue, Jul 02, 2019 at 01:07:43PM +0200, Jiri Olsa wrote: > On Tue, Jul 02, 2019 at 06:34:09PM +0800, Leo Yan wrote: > > When I used static checker Smatch for perf building, the main target is > > to check if there have any potential issues in Arm cs-etm code. So > > finally I get many reporting

[PATCH v1 net-next] net: stmmac: enable clause 45 mdio support

2019-07-02 Thread Voon Weifeng
From: Kweh Hock Leong DWMAC4 is capable to support clause 45 mdio communication. This patch enable the feature on stmmac_mdio_write() and stmmac_mdio_read() by following phy_write_mmd() and phy_read_mmd() mdiobus read write implementation format. Reviewed-by: Li, Yifan Signed-off-by: Kweh Hock

[PATCH 0/2] iommu: handle drivers that manage iommu directly

2019-07-02 Thread Rob Clark
From: Rob Clark One of the challenges we need to handle to enable the aarch64 laptops upstream is dealing with the fact that the bootloader enables the display and takes the corresponding SMMU context-bank out of BYPASS. Unfortunately, currently, the IOMMU framework attaches a DMA (or

Re: [PATCH v5] net: netfilter: Fix rpfilter dropping vrf packets by mistake

2019-07-02 Thread linmiaohe
Add David Ahern. @David Ahern I'am so sorry but I rerun scripts/get_maintainer.pl . You are not in the list , so I forgot to add you to the email-to list. I'am sorry again. Have a good day. Best wishes. When firewalld is enabled with ipv4/ipv6 rpfilter, vrf ipv4/ipv6 packets will be dropped.

Re: [PATCH 5.1 51/55] bpf, arm64: use more scalable stadd over ldxr / stxr loop in xadd

2019-07-02 Thread Sasha Levin
On Tue, Jul 02, 2019 at 10:01:59AM +0200, Greg Kroah-Hartman wrote: From: Daniel Borkmann commit 34b8ab091f9ef57a2bb3c8c8359a0a03a8abf2f9 upstream. Since ARMv8.1 supplement introduced LSE atomic instructions back in 2016, lets add support for STADD and use that in favor of LDXR / STXR loop

Re: [PATCH 4.19 26/72] usb: dwc3: gadget: use num_trbs when skipping TRBs on ->dequeue()

2019-07-02 Thread Sasha Levin
On Tue, Jul 02, 2019 at 10:01:27AM +0200, Greg Kroah-Hartman wrote: commit c3acd59014148470dc58519870fbc779785b4bf7 upstream Now that we track how many TRBs a request uses, it's easier to skip over them in case of a call to usb_ep_dequeue(). Let's do so and simplify the code a bit. Cc: Fei

Klientskie bazy. Email: proda...@armyspy.com Uznajte podrobnee!

2019-07-02 Thread Zk7info
Klientskie bazy. Email: proda...@armyspy.com Uznajte podrobnee!

Re: [PATCH net-next v6 11/15] ethtool: provide link mode names as a string set

2019-07-02 Thread Jakub Kicinski
On Tue, 2 Jul 2019 13:50:34 +0200 (CEST), Michal Kubecek wrote: > +const char *const link_mode_names[] = { > + __DEFINE_LINK_MODE_NAME(10, T, Half), > + __DEFINE_LINK_MODE_NAME(10, T, Full), > + __DEFINE_LINK_MODE_NAME(100, T, Half), > + __DEFINE_LINK_MODE_NAME(100, T, Full), > +

[PATCH 4/4] MIPS: lantiq: update the clock alias' for the mainline PCIe PHY driver

2019-07-02 Thread Martin Blumenstingl
The mainline PCIe PHY driver has it's own devicetree node. Update the clock alias so the mainline driver finds the clocks. The first PCIe PHY is located at 0x1f106800 and exists on VRX200, ARX300 and GRX390. The second PCIe PHY is located at 0x1f700400 and exists on ARX300 and GRX390. The third

CFP: LPC Testing and Fuzzing microconference.

2019-07-02 Thread Dhaval Giani
Hi folks, I am pleased to announce the Testing Microconference has been accepted at LPC this year. The CfP process is now open, and please submit your talks on the LPC website. It can be found at https://linuxplumbersconf.org/event/4/abstracts/ Potential topics include, but are not limited to -

Re: [PATCH] net: pci: Fix hotplug event timeout with shpchp

2019-07-02 Thread linmiaohe
On Tue, Jul 02, 2019 at 01:35:19PM +, Miaohe Lin wrote: > > Hotplug a network card would take more than 5 seconds in qemu + shpchp > > scene. It’s because 5 seconds delayed_work in func > > I'm dropping this because of the required delay pointed out by Lukas. > > If you think we still need

Re: [PATCH net-next v6 11/15] ethtool: provide link mode names as a string set

2019-07-02 Thread Jakub Kicinski
On Tue, 2 Jul 2019 19:04:19 -0700, Jakub Kicinski wrote: > On Tue, 2 Jul 2019 13:50:34 +0200 (CEST), Michal Kubecek wrote: > > +const char *const link_mode_names[] = { > > + __DEFINE_LINK_MODE_NAME(10, T, Half), > > + __DEFINE_LINK_MODE_NAME(10, T, Full), > > + __DEFINE_LINK_MODE_NAME(100,

[PATCH v2] module: add usage links when calling ref_module func

2019-07-02 Thread Zhiqiang Liu
From: Zhiqiang Liu Users can call ref_module func in their modules to construct relationships with other modules. However, the holders '/sys/module//holders' of the target module donot include the users` module. So lsmod command misses detailed info of 'Used by'. When load module, the process

[PATCH V2] media: usb: technisat-usb2: fix buffer overflow

2019-07-02 Thread Phong Tran
The buffer will be overflow in case of the while loop can not break. Add the checking buffer condition in while loop for avoiding overlooping index. This issue was reported by syzbot Reported-by: syzbot+eaaaf38a95427be88...@syzkaller.appspotmail.com Tested-by:

Re: [PATCH v4 5/5] xen: Add 'xen_nopv' parameter back for backward compatibility

2019-07-02 Thread Zhenzhong Duan
On 2019/7/3 2:13, Boris Ostrovsky wrote: On 7/1/19 1:19 AM, Zhenzhong Duan wrote: Map 'xen_nopv' to 'nopv' and mark 'xen_nopv' obsolete in kernel-parameters.txt I am not sure we want patch #3, why not do everything in a single patch? Thanks for review. I'll fix all those based on your

[PATCH AUTOSEL 5.1 02/39] ARM: dts: meson8b: fix the operating voltage of the Mali GPU

2019-07-02 Thread Sasha Levin
From: Martin Blumenstingl [ Upstream commit 26d65140e92a626e39c73c9abf769fd174bf5076 ] Amlogic's vendor kernel defines an OPP for the GPU on Meson8b boards with a voltage of 1.15V. It turns out that the vendor kernel relies on the bootloader to set up the voltage. The bootloader however sets a

Re: [PATCH v2 2/3] augmented rbtree: add new RB_DECLARE_CALLBACKS_MAX macro

2019-07-02 Thread Michel Lespinasse
On Tue, Jul 2, 2019 at 9:09 AM Davidlohr Bueso wrote: > > On Tue, 02 Jul 2019, Michel Lespinasse wrote: > > >diff --git a/arch/x86/mm/pat_rbtree.c b/arch/x86/mm/pat_rbtree.c > >index fa16036fa592..2afad8e869fc 100644 > >--- a/arch/x86/mm/pat_rbtree.c > >+++ b/arch/x86/mm/pat_rbtree.c > >@@ -54,23

[PATCH AUTOSEL 5.1 05/39] irqchip/gic-v3-its: Fix command queue pointer comparison bug

2019-07-02 Thread Sasha Levin
From: Heyi Guo [ Upstream commit a050fa5476d418fc16b25abe168b3d38ba11e13c ] When we run several VMs with PCI passthrough and GICv4 enabled, not pinning vCPUs, we will occasionally see below warnings in dmesg: ITS queue timeout (65440 65504 480) ITS cmd its_build_vmovp_cmd failed The reason

[PATCH AUTOSEL 5.1 11/39] ARM: dts: gemini Fix up DNS-313 compatible string

2019-07-02 Thread Sasha Levin
From: Linus Walleij [ Upstream commit 36558020128b1a48b7bddd5792ee70e3f64b04b0 ] It's a simple typo in the DNS file, which was pretty serious. No scripts were working properly. Fix it up. Signed-off-by: Linus Walleij Signed-off-by: Sasha Levin --- arch/arm/boot/dts/gemini-dlink-dns-313.dts

[PATCH AUTOSEL 5.1 13/39] afs: Fix uninitialised spinlock afs_volume::cb_break_lock

2019-07-02 Thread Sasha Levin
From: David Howells [ Upstream commit 90fa9b64523a645a97edc0bdcf2d74759957 ] Fix the cb_break_lock spinlock in afs_volume struct by initialising it when the volume record is allocated. Also rename the lock to cb_v_break_lock to distinguish it from the lock of the same name in the

[PATCH AUTOSEL 5.1 18/39] net: stmmac: fixed new system time seconds value calculation

2019-07-02 Thread Sasha Levin
From: Roland Hii [ Upstream commit a1e5388b4d5fc78688e5e9ee6641f779721d6291 ] When ADDSUB bit is set, the system time seconds field is calculated as the complement of the seconds part of the update value. For example, if 3.1 seconds need to be subtracted from the system time, this

[PATCH AUTOSEL 5.1 17/39] ppp: mppe: Add softdep to arc4

2019-07-02 Thread Sasha Levin
From: Takashi Iwai [ Upstream commit aad1dcc4f011ea409850e040363dff1e59aa4175 ] The arc4 crypto is mandatory at ppp_mppe probe time, so let's put a softdep line, so that the corresponding module gets prepared gracefully. Without this, a simple inclusion to initrd via dracut failed due to the

[PATCH AUTOSEL 5.1 09/39] selftests/powerpc: Add test of fork with mapping above 512TB

2019-07-02 Thread Sasha Levin
From: Michael Ellerman [ Upstream commit 16391bfc862342f285195013b73c1394fab28b97 ] This tests that when a process with a mapping above 512TB forks we correctly separate the parent and child address spaces. This exercises the bug in the context id handling fixed in the previous commit.

[PATCH AUTOSEL 5.1 24/39] pinctrl: ocelot: fix gpio direction for pins after 31

2019-07-02 Thread Sasha Levin
From: Alexandre Belloni [ Upstream commit f2818ba3a0125670cbbb5a65ebb631a8da2f ] The third argument passed to REG is not the correct one and ocelot_gpio_set_direction is not working for pins after 31. Fix that by passing the pin number instead of the modulo 32 value. Fixes: da801ab56ad8

[PATCH AUTOSEL 5.1 07/39] efi/bgrt: Drop BGRT status field reserved bits check

2019-07-02 Thread Sasha Levin
From: Hans de Goede [ Upstream commit a483fcab38b43fb34a7f12ab1daadd3907f150e2 ] Starting with ACPI 6.2 bits 1 and 2 of the BGRT status field are no longer reserved. These bits are now used to indicate if the image needs to be rotated before being displayed. The first device using these bits

[PATCH AUTOSEL 5.1 19/39] net: stmmac: set IC bit when transmitting frames with HW timestamp

2019-07-02 Thread Sasha Levin
From: Roland Hii [ Upstream commit d0bb82fd60183868f46c8ccc595a3d61c3334a18 ] When transmitting certain PTP frames, e.g. SYNC and DELAY_REQ, the PTP daemon, e.g. ptp4l, is polling the driver for the frame transmit hardware timestamp. The polling will most likely timeout if the tx coalesce is

[PATCH AUTOSEL 5.1 21/39] ARM: dts: imx6ul: fix PWM[1-4] interrupts

2019-07-02 Thread Sasha Levin
From: Sébastien Szymanski [ Upstream commit 3cf10132ac8d536565f2c02f60a3aeb315863a52 ] According to the i.MX6UL/L RM, table 3.1 "ARM Cortex A7 domain interrupt summary", the interrupts for the PWM[1-4] go from 83 to 86. Fixes: b9901fe84f02 ("ARM: dts: imx6ul: add pwm[1-4] nodes")

[PATCH AUTOSEL 5.1 28/39] x86/boot/64: Fix crash if kernel image crosses page table boundary

2019-07-02 Thread Sasha Levin
From: "Kirill A. Shutemov" [ Upstream commit 81c7ed296dcd02bc0b4488246d040e03e633737a ] A kernel which boots in 5-level paging mode crashes in a small percentage of cases if KASLR is enabled. This issue was tracked down to the case when the kernel image unpacks in a way that it crosses an 1G

[PATCH AUTOSEL 5.1 25/39] pinctrl: ocelot: fix pinmuxing for pins after 31

2019-07-02 Thread Sasha Levin
From: Alexandre Belloni [ Upstream commit 4b36082e2e09c2769710756390d54cfca563ed96 ] The actual layout for OCELOT_GPIO_ALT[01] when there are more than 32 pins is interleaved, i.e. OCELOT_GPIO_ALT0[0], OCELOT_GPIO_ALT1[0], OCELOT_GPIO_ALT0[1], OCELOT_GPIO_ALT1[1]. Introduce a new REG_ALT macro

[PATCH AUTOSEL 5.1 29/39] x86/boot/64: Add missing fixup_pointer() for next_early_pgt access

2019-07-02 Thread Sasha Levin
From: "Kirill A. Shutemov" [ Upstream commit c1887159eb48ba40e775584cfb2a443962cf1a05 ] __startup_64() uses fixup_pointer() to access global variables in a position-independent fashion. Access to next_early_pgt was wrapped into the helper, but one instance in the 5-level paging branch was

[PATCH AUTOSEL 5.1 36/39] pinctrl: mediatek: Update cur_mask in mask/mask ops

2019-07-02 Thread Sasha Levin
From: Nicolas Boichat [ Upstream commit 9d957a959bc8c3dfe37572ac8e99affb5a885965 ] During suspend/resume, mtk_eint_mask may be called while wake_mask is active. For example, this happens if a wake-source with an active interrupt handler wakes the system: irq/pm.c:irq_pm_check_wakeup would

[PATCH AUTOSEL 5.1 33/39] pinctrl: mediatek: Ignore interrupts that are wake only during resume

2019-07-02 Thread Sasha Levin
From: Nicolas Boichat [ Upstream commit 35594bc7cecf3a78504b590e350570e8f4d7779e ] Before suspending, mtk-eint would set the interrupt mask to the one in wake_mask. However, some of these interrupts may not have a corresponding interrupt handler, or the interrupt may be disabled. On resume,

[PATCH AUTOSEL 5.1 37/39] mm/oom_kill.c: fix uninitialized oc->constraint

2019-07-02 Thread Sasha Levin
From: Yafang Shao [ Upstream commit 432b1de0de02a83f64695e69a2d83cbee10c236f ] In dump_oom_summary() oc->constraint is used to show oom_constraint_text, but it hasn't been set before. So the value of it is always the default value 0. We should inititialize it before. Bellow is the output

[PATCH AUTOSEL 5.1 39/39] linux/kernel.h: fix overflow for DIV_ROUND_UP_ULL

2019-07-02 Thread Sasha Levin
From: Vinod Koul [ Upstream commit 8f9fab480c7a87b10bb5440bf370272a5d59 ] DIV_ROUND_UP_ULL adds the two arguments and then invokes DIV_ROUND_DOWN_ULL. But on a 32bit system the addition of two 32 bit values can overflow. DIV_ROUND_DOWN_ULL does it correctly and stashes the addition into a

[PATCH AUTOSEL 4.19 15/26] qmi_wwan: Fix out-of-bounds read

2019-07-02 Thread Sasha Levin
From: Bjørn Mork [ Upstream commit 904d88d743b0c94092c5117955eab695df8109e8 ] The syzbot reported Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0xca/0x13e lib/dump_stack.c:113 print_address_description+0x67/0x231 mm/kasan/report.c:188 __kasan_report.cold+0x1a/0x32

[PATCH AUTOSEL 4.19 11/26] net: stmmac: fixed new system time seconds value calculation

2019-07-02 Thread Sasha Levin
From: Roland Hii [ Upstream commit a1e5388b4d5fc78688e5e9ee6641f779721d6291 ] When ADDSUB bit is set, the system time seconds field is calculated as the complement of the seconds part of the update value. For example, if 3.1 seconds need to be subtracted from the system time, this

[PATCH AUTOSEL 4.19 04/26] perf/core: Fix perf_sample_regs_user() mm check

2019-07-02 Thread Sasha Levin
From: Peter Zijlstra [ Upstream commit 085ebfe937d7a7a5df1729f35a12d6d655fea68c ] perf_sample_regs_user() uses 'current->mm' to test for the presence of userspace, but this is insufficient, consider use_mm(). A better test is: '!(current->flags & PF_KTHREAD)', exec() clears PF_KTHREAD after it

[PATCH AUTOSEL 4.19 09/26] be2net: fix link failure after ethtool offline test

2019-07-02 Thread Sasha Levin
From: Petr Oros [ Upstream commit 2e5db6eb3c23e5dc8171eb8f6af7a97ef9fcf3a9 ] Certain cards in conjunction with certain switches need a little more time for link setup that results in ethtool link test failure after offline test. Patch adds a loop that waits for a link setup finish. Changes in

[PATCH AUTOSEL 4.19 05/26] ARM: dts: gemini Fix up DNS-313 compatible string

2019-07-02 Thread Sasha Levin
From: Linus Walleij [ Upstream commit 36558020128b1a48b7bddd5792ee70e3f64b04b0 ] It's a simple typo in the DNS file, which was pretty serious. No scripts were working properly. Fix it up. Signed-off-by: Linus Walleij Signed-off-by: Sasha Levin --- arch/arm/boot/dts/gemini-dlink-dns-313.dts

[PATCH AUTOSEL 4.19 18/26] dm verity: use message limit for data block corruption message

2019-07-02 Thread Sasha Levin
From: Milan Broz [ Upstream commit 2eba4e640b2c4161e31ae20090a53ee02a518657 ] DM verity should also use DMERR_LIMIT to limit repeat data block corruption messages. Signed-off-by: Milan Broz Signed-off-by: Mike Snitzer Signed-off-by: Sasha Levin --- drivers/md/dm-verity-target.c | 4 ++-- 1

[PATCH AUTOSEL 4.19 14/26] ARM: dts: imx6ul: fix PWM[1-4] interrupts

2019-07-02 Thread Sasha Levin
From: Sébastien Szymanski [ Upstream commit 3cf10132ac8d536565f2c02f60a3aeb315863a52 ] According to the i.MX6UL/L RM, table 3.1 "ARM Cortex A7 domain interrupt summary", the interrupts for the PWM[1-4] go from 83 to 86. Fixes: b9901fe84f02 ("ARM: dts: imx6ul: add pwm[1-4] nodes")

[PATCH AUTOSEL 4.19 21/26] HID: chicony: add another quirk for PixArt mouse

2019-07-02 Thread Sasha Levin
From: Oleksandr Natalenko [ Upstream commit dcf768b0ac868630e7bdb6f2f1c9fe72788012fa ] I've spotted another Chicony PixArt mouse in the wild, which requires HID_QUIRK_ALWAYS_POLL quirk, otherwise it disconnects each minute. USB ID of this device is 0x04f2:0x0939. We've introduced quirks like

[PATCH AUTOSEL 4.19 16/26] pinctrl: mcp23s08: Fix add_data and irqchip_add_nested call order

2019-07-02 Thread Sasha Levin
From: Phil Reid [ Upstream commit 6dbc6e6f58556369bf999cd7d9793586f1b0e4b4 ] Currently probing of the mcp23s08 results in an error message "detected irqchip that is shared with multiple gpiochips: please fix the driver" This is due to the following: Call to mcp23s08_irqchip_setup() with call

[PATCH AUTOSEL 4.19 17/26] dm table: don't copy from a NULL pointer in realloc_argv()

2019-07-02 Thread Sasha Levin
From: Jerome Marchand [ Upstream commit a0651926553cfe7992166432e418987760882652 ] For the first call to realloc_argv() in dm_split_args(), old_argv is NULL and size is zero. Then memcpy is called, with the NULL old_argv as the source argument and a zero size argument. AFAIK, this is undefined

[PATCH AUTOSEL 4.19 20/26] x86/boot/64: Add missing fixup_pointer() for next_early_pgt access

2019-07-02 Thread Sasha Levin
From: "Kirill A. Shutemov" [ Upstream commit c1887159eb48ba40e775584cfb2a443962cf1a05 ] __startup_64() uses fixup_pointer() to access global variables in a position-independent fashion. Access to next_early_pgt was wrapped into the helper, but one instance in the 5-level paging branch was

[PATCH AUTOSEL 4.19 25/26] pinctrl: mediatek: Update cur_mask in mask/mask ops

2019-07-02 Thread Sasha Levin
From: Nicolas Boichat [ Upstream commit 9d957a959bc8c3dfe37572ac8e99affb5a885965 ] During suspend/resume, mtk_eint_mask may be called while wake_mask is active. For example, this happens if a wake-source with an active interrupt handler wakes the system: irq/pm.c:irq_pm_check_wakeup would

[PATCH] cgroup: minor tweak for logic to get cgroup css

2019-07-02 Thread Peng Wang
We could only handle the case that css exists and css_try_get_online() fails. Signed-off-by: Peng Wang --- kernel/cgroup/cgroup.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c index bf9dbffd46b1..a988d77f6c6d 100644 ---

[PATCH AUTOSEL 4.19 19/26] x86/boot/64: Fix crash if kernel image crosses page table boundary

2019-07-02 Thread Sasha Levin
From: "Kirill A. Shutemov" [ Upstream commit 81c7ed296dcd02bc0b4488246d040e03e633737a ] A kernel which boots in 5-level paging mode crashes in a small percentage of cases if KASLR is enabled. This issue was tracked down to the case when the kernel image unpacks in a way that it crosses an 1G

[PATCH AUTOSEL 4.19 26/26] linux/kernel.h: fix overflow for DIV_ROUND_UP_ULL

2019-07-02 Thread Sasha Levin
From: Vinod Koul [ Upstream commit 8f9fab480c7a87b10bb5440bf370272a5d59 ] DIV_ROUND_UP_ULL adds the two arguments and then invokes DIV_ROUND_DOWN_ULL. But on a 32bit system the addition of two 32 bit values can overflow. DIV_ROUND_DOWN_ULL does it correctly and stashes the addition into a

[PATCH AUTOSEL 4.19 22/26] HID: multitouch: Add pointstick support for ALPS Touchpad

2019-07-02 Thread Sasha Levin
From: Kai-Heng Feng [ Upstream commit 0a95fc733da375de0688d0f1fd3a2869a1c1d499 ] There's a new ALPS touchpad/pointstick combo device that requires MT_CLS_WIN_8_DUAL to make its pointsitck work as a mouse. The device can be found on HP ZBook 17 G5. Signed-off-by: Kai-Heng Feng Signed-off-by:

[PATCH AUTOSEL 4.19 23/26] pinctrl: mediatek: Ignore interrupts that are wake only during resume

2019-07-02 Thread Sasha Levin
From: Nicolas Boichat [ Upstream commit 35594bc7cecf3a78504b590e350570e8f4d7779e ] Before suspending, mtk-eint would set the interrupt mask to the one in wake_mask. However, some of these interrupts may not have a corresponding interrupt handler, or the interrupt may be disabled. On resume,

[PATCH AUTOSEL 4.19 24/26] cpu/hotplug: Fix out-of-bounds read when setting fail state

2019-07-02 Thread Sasha Levin
From: Eiichi Tsukata [ Upstream commit 33d4a5a7a5b4d02915d765064b2319e90a11cbde ] Setting invalid value to /sys/devices/system/cpu/cpuX/hotplug/fail can control `struct cpuhp_step *sp` address, results in the following global-out-of-bounds read. Reproducer: # echo -2 >

[PATCH AUTOSEL 4.19 10/26] ppp: mppe: Add softdep to arc4

2019-07-02 Thread Sasha Levin
From: Takashi Iwai [ Upstream commit aad1dcc4f011ea409850e040363dff1e59aa4175 ] The arc4 crypto is mandatory at ppp_mppe probe time, so let's put a softdep line, so that the corresponding module gets prepared gracefully. Without this, a simple inclusion to initrd via dracut failed due to the

[PATCH AUTOSEL 4.14 01/13] clk: ti: clkctrl: Fix returning uninitialized data

2019-07-02 Thread Sasha Levin
From: Tony Lindgren [ Upstream commit 41b3588dba6ef4b7995735a97e47ff0aeea6c276 ] If we do a clk_get() for a clock that does not exists, we have _ti_omap4_clkctrl_xlate() return uninitialized data if no match is found. This can be seen in some cases with SLAB_DEBUG enabled: Unable to handle

[PATCH AUTOSEL 4.19 12/26] net: stmmac: set IC bit when transmitting frames with HW timestamp

2019-07-02 Thread Sasha Levin
From: Roland Hii [ Upstream commit d0bb82fd60183868f46c8ccc595a3d61c3334a18 ] When transmitting certain PTP frames, e.g. SYNC and DELAY_REQ, the PTP daemon, e.g. ptp4l, is polling the driver for the frame transmit hardware timestamp. The polling will most likely timeout if the tx coalesce is

[PATCH AUTOSEL 4.19 07/26] afs: Fix uninitialised spinlock afs_volume::cb_break_lock

2019-07-02 Thread Sasha Levin
From: David Howells [ Upstream commit 90fa9b64523a645a97edc0bdcf2d74759957 ] Fix the cb_break_lock spinlock in afs_volume struct by initialising it when the volume record is allocated. Also rename the lock to cb_v_break_lock to distinguish it from the lock of the same name in the

[PATCH AUTOSEL 4.14 02/13] efi/bgrt: Drop BGRT status field reserved bits check

2019-07-02 Thread Sasha Levin
From: Hans de Goede [ Upstream commit a483fcab38b43fb34a7f12ab1daadd3907f150e2 ] Starting with ACPI 6.2 bits 1 and 2 of the BGRT status field are no longer reserved. These bits are now used to indicate if the image needs to be rotated before being displayed. The first device using these bits

[PATCH AUTOSEL 4.19 08/26] x86/apic: Fix integer overflow on 10 bit left shift of cpu_khz

2019-07-02 Thread Sasha Levin
From: Colin Ian King [ Upstream commit ea136a112d89bade596314a1ae49f748902f4727 ] The left shift of unsigned int cpu_khz will overflow for large values of cpu_khz, so cast it to a long long before shifting it to avoid overvlow. For example, this can happen when cpu_khz is 4194305, i.e. ~4.2

[PATCH AUTOSEL 4.19 13/26] sis900: fix TX completion

2019-07-02 Thread Sasha Levin
From: Sergej Benilov [ Upstream commit 8ac8a01092b2added0749ef937037bf1912e13e3 ] Since commit 605ad7f184b60cfaacbc038aa6c55ee68dee3c89 "tcp: refine TSO autosizing", outbound throughput is dramatically reduced for some connections, as sis900 is doing TX completion within idle states only.

[PATCH AUTOSEL 4.14 11/13] x86/boot/64: Fix crash if kernel image crosses page table boundary

2019-07-02 Thread Sasha Levin
From: "Kirill A. Shutemov" [ Upstream commit 81c7ed296dcd02bc0b4488246d040e03e633737a ] A kernel which boots in 5-level paging mode crashes in a small percentage of cases if KASLR is enabled. This issue was tracked down to the case when the kernel image unpacks in a way that it crosses an 1G

[PATCH AUTOSEL 4.14 09/13] ARM: dts: imx6ul: fix PWM[1-4] interrupts

2019-07-02 Thread Sasha Levin
From: Sébastien Szymanski [ Upstream commit 3cf10132ac8d536565f2c02f60a3aeb315863a52 ] According to the i.MX6UL/L RM, table 3.1 "ARM Cortex A7 domain interrupt summary", the interrupts for the PWM[1-4] go from 83 to 86. Fixes: b9901fe84f02 ("ARM: dts: imx6ul: add pwm[1-4] nodes")

[PATCH AUTOSEL 4.14 10/13] dm verity: use message limit for data block corruption message

2019-07-02 Thread Sasha Levin
From: Milan Broz [ Upstream commit 2eba4e640b2c4161e31ae20090a53ee02a518657 ] DM verity should also use DMERR_LIMIT to limit repeat data block corruption messages. Signed-off-by: Milan Broz Signed-off-by: Mike Snitzer Signed-off-by: Sasha Levin --- drivers/md/dm-verity-target.c | 4 ++-- 1

[PATCH AUTOSEL 4.14 04/13] ARM: omap2: remove incorrect __init annotation

2019-07-02 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 27e23d8975270df6999f8b5b3156fc0c04927451 ] omap3xxx_prm_enable_io_wakeup() is marked __init, but its caller is not, so we get a warning with clang-8: WARNING: vmlinux.o(.text+0x343c8): Section mismatch in reference from the function

[PATCH AUTOSEL 4.9 5/8] net: stmmac: fixed new system time seconds value calculation

2019-07-02 Thread Sasha Levin
From: Roland Hii [ Upstream commit a1e5388b4d5fc78688e5e9ee6641f779721d6291 ] When ADDSUB bit is set, the system time seconds field is calculated as the complement of the seconds part of the update value. For example, if 3.1 seconds need to be subtracted from the system time, this

[PATCH AUTOSEL 4.4 3/6] be2net: fix link failure after ethtool offline test

2019-07-02 Thread Sasha Levin
From: Petr Oros [ Upstream commit 2e5db6eb3c23e5dc8171eb8f6af7a97ef9fcf3a9 ] Certain cards in conjunction with certain switches need a little more time for link setup that results in ethtool link test failure after offline test. Patch adds a loop that waits for a link setup finish. Changes in

[PATCH AUTOSEL 4.14 13/13] linux/kernel.h: fix overflow for DIV_ROUND_UP_ULL

2019-07-02 Thread Sasha Levin
From: Vinod Koul [ Upstream commit 8f9fab480c7a87b10bb5440bf370272a5d59 ] DIV_ROUND_UP_ULL adds the two arguments and then invokes DIV_ROUND_DOWN_ULL. But on a 32bit system the addition of two 32 bit values can overflow. DIV_ROUND_DOWN_ULL does it correctly and stashes the addition into a

[PATCH AUTOSEL 4.9 1/8] perf/core: Fix perf_sample_regs_user() mm check

2019-07-02 Thread Sasha Levin
From: Peter Zijlstra [ Upstream commit 085ebfe937d7a7a5df1729f35a12d6d655fea68c ] perf_sample_regs_user() uses 'current->mm' to test for the presence of userspace, but this is insufficient, consider use_mm(). A better test is: '!(current->flags & PF_KTHREAD)', exec() clears PF_KTHREAD after it

[PATCH AUTOSEL 4.14 07/13] net: stmmac: fixed new system time seconds value calculation

2019-07-02 Thread Sasha Levin
From: Roland Hii [ Upstream commit a1e5388b4d5fc78688e5e9ee6641f779721d6291 ] When ADDSUB bit is set, the system time seconds field is calculated as the complement of the seconds part of the update value. For example, if 3.1 seconds need to be subtracted from the system time, this

[PATCH AUTOSEL 4.14 12/13] cpu/hotplug: Fix out-of-bounds read when setting fail state

2019-07-02 Thread Sasha Levin
From: Eiichi Tsukata [ Upstream commit 33d4a5a7a5b4d02915d765064b2319e90a11cbde ] Setting invalid value to /sys/devices/system/cpu/cpuX/hotplug/fail can control `struct cpuhp_step *sp` address, results in the following global-out-of-bounds read. Reproducer: # echo -2 >

[PATCH AUTOSEL 4.9 8/8] dm verity: use message limit for data block corruption message

2019-07-02 Thread Sasha Levin
From: Milan Broz [ Upstream commit 2eba4e640b2c4161e31ae20090a53ee02a518657 ] DM verity should also use DMERR_LIMIT to limit repeat data block corruption messages. Signed-off-by: Milan Broz Signed-off-by: Mike Snitzer Signed-off-by: Sasha Levin --- drivers/md/dm-verity-target.c | 4 ++-- 1

[PATCH AUTOSEL 4.4 4/6] ppp: mppe: Add softdep to arc4

2019-07-02 Thread Sasha Levin
From: Takashi Iwai [ Upstream commit aad1dcc4f011ea409850e040363dff1e59aa4175 ] The arc4 crypto is mandatory at ppp_mppe probe time, so let's put a softdep line, so that the corresponding module gets prepared gracefully. Without this, a simple inclusion to initrd via dracut failed due to the

[PATCH AUTOSEL 4.4 2/6] ARM: omap2: remove incorrect __init annotation

2019-07-02 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 27e23d8975270df6999f8b5b3156fc0c04927451 ] omap3xxx_prm_enable_io_wakeup() is marked __init, but its caller is not, so we get a warning with clang-8: WARNING: vmlinux.o(.text+0x343c8): Section mismatch in reference from the function

[PATCH AUTOSEL 4.9 3/8] be2net: fix link failure after ethtool offline test

2019-07-02 Thread Sasha Levin
From: Petr Oros [ Upstream commit 2e5db6eb3c23e5dc8171eb8f6af7a97ef9fcf3a9 ] Certain cards in conjunction with certain switches need a little more time for link setup that results in ethtool link test failure after offline test. Patch adds a loop that waits for a link setup finish. Changes in

[PATCH AUTOSEL 4.4 5/6] sis900: fix TX completion

2019-07-02 Thread Sasha Levin
From: Sergej Benilov [ Upstream commit 8ac8a01092b2added0749ef937037bf1912e13e3 ] Since commit 605ad7f184b60cfaacbc038aa6c55ee68dee3c89 "tcp: refine TSO autosizing", outbound throughput is dramatically reduced for some connections, as sis900 is doing TX completion within idle states only.

<    5   6   7   8   9   10   11   12   >