[PATCH 5.2 03/56] libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock

2019-08-08 Thread Greg Kroah-Hartman
commit ca6bf264f6d856f959c4239cda1047b587745c67 upstream. A multithreaded namespace creation/destruction stress test currently deadlocks with the following lockup signature: INFO: task ndctl:2924 blocked for more than 122 seconds. Tainted: G OE 5.2.0-rc4+ #3382 "ec

[PATCH 5.2 06/56] HID: wacom: fix bit shift for Cintiq Companion 2

2019-08-08 Thread Greg Kroah-Hartman
From: Aaron Armstrong Skomra commit 693c3dab4e50403f91bca4b52fc6d8562a3180f6 upstream. The bit indicating BTN_6 on this device is overshifted by 2 bits, resulting in the incorrect button being reported. Also fix copy-paste mistake in comments. Signed-off-by: Aaron Armstrong Skomra Reviewed-by

[PATCH 5.2 25/56] net: phylink: dont start and stop SGMII PHYs in SFP modules twice

2019-08-08 Thread Greg Kroah-Hartman
From: Arseny Solokha [ Upstream commit c7fa7f567cab6532be285a5df104617d80bce245 ] SFP modules connected using the SGMII interface have their own PHYs which are handled by the struct phylink's phydev field. On the other hand, for the modules connected using 1000Base-X interface that field is not

[PATCH 5.2 24/56] net: phy: fixed_phy: print gpio error only if gpio node is present

2019-08-08 Thread Greg Kroah-Hartman
From: Hubert Feurstein [ Upstream commit ab98c008ac761752cdc27f9eb053419feadeb2f7 ] It is perfectly ok to not have an gpio attached to the fixed-link node. So the driver should not throw an error message when the gpio is missing. Fixes: 5468e82f7034 ("net: phy: fixed-phy: Drop GPIO from fixed_p

[PATCH 5.2 10/56] drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case

2019-08-08 Thread Greg Kroah-Hartman
From: "Arnaud Patard (Rtp)" [ Upstream commit d934423ac26ed373dfe089734d505dca5ff679b6 ] Orion5.x systems are still using machine files and not device-tree. Commit 96cb4342382290c9 ("net: mvmdio: allow up to three clocks to be specified for orion-mdio") has replaced devm_clk_get() with of_clk_ge

[PATCH 5.2 16/56] mvpp2: fix panic on module removal

2019-08-08 Thread Greg Kroah-Hartman
From: Matteo Croce [ Upstream commit 944a83a2669ae8aa2c7664e79376ca7468eb0a2b ] mvpp2 uses a delayed workqueue to gather traffic statistics. On module removal the workqueue can be destroyed before calling cancel_delayed_work_sync() on its works. Fix it by moving the destroy_workqueue() call afte

[PATCH 5.2 17/56] mvpp2: refactor MTU change code

2019-08-08 Thread Greg Kroah-Hartman
From: Matteo Croce [ Upstream commit 230bd958c2c846ee292aa38bc6b006296c24ca01 ] The MTU change code can call napi_disable() with the device already down, leading to a deadlock. Also, lot of code is duplicated unnecessarily. Rework mvpp2_change_mtu() to avoid the deadlock and remove duplicated c

[PATCH 5.2 02/56] libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant

2019-08-08 Thread Greg Kroah-Hartman
commit 6de5d06e657acdbcf9637dac37916a4a5309e0f4 upstream. In preparation for not holding a lock over the execution of nd_ioctl(), update the implementation to allow multiple threads to be attempting ioctls at the same time. The bus lock still prevents multiple in-flight ->ndctl() invocations from

[PATCH 5.2 20/56] net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER

2019-08-08 Thread Greg Kroah-Hartman
From: Nikolay Aleksandrov [ Upstream commit 091adf9ba6cdb432cbcc217b47e4ffb8aa0d8865 ] Most of the bridge device's vlan init bugs come from the fact that its default pvid is created at the wrong time, way too early in ndo_init() before the device is even assigned an ifindex. It introduces a bug

[PATCH 5.2 23/56] net/mlx5: Use reversed order when unregister devices

2019-08-08 Thread Greg Kroah-Hartman
From: Mark Zhang [ Upstream commit 08aa5e7da6bce1a1963f63cf32c2e7ad434ad578 ] When lag is active, which is controlled by the bonded mlx5e netdev, mlx5 interface unregestering must happen in the reverse order where rdma is unregistered (unloaded) first, to guarantee all references to the lag cont

[PATCH 5.2 18/56] net: bridge: delete local fdb on device init failure

2019-08-08 Thread Greg Kroah-Hartman
From: Nikolay Aleksandrov [ Upstream commit d7bae09fa008c6c9a489580db0a5a12063b97f97 ] On initialization failure we have to delete the local fdb which was inserted due to the default pvid creation. This problem has been present since the inception of default_pvid. Note that currently there are 2

[PATCH 5.2 14/56] ipip: validate header length in ipip_tunnel_xmit

2019-08-08 Thread Greg Kroah-Hartman
From: Haishuang Yan [ Upstream commit 47d858d0bdcd47cc1c6c9eeca91b091dd9e55637 ] We need the same checks introduced by commit cb9f1b783850 ("ip: validate header length on virtual device xmit") for ipip tunnel. Fixes: cb9f1b783850b ("ip: validate header length on virtual device xmit") Signed-off

[PATCH 5.2 19/56] net: bridge: mcast: dont delete permanent entries when fast leave is enabled

2019-08-08 Thread Greg Kroah-Hartman
From: Nikolay Aleksandrov [ Upstream commit 5c725b6b65067909548ac9ca9bc777098ec9883d ] When permanent entries were introduced by the commit below, they were exempt from timing out and thus igmp leave wouldn't affect them unless fast leave was enabled on the port which was added before permanent

[PATCH 5.2 13/56] ip6_tunnel: fix possible use-after-free on xmit

2019-08-08 Thread Greg Kroah-Hartman
From: Haishuang Yan [ Upstream commit 01f5bffad555f8e22a61f4b1261fe09cf1b96994 ] ip4ip6/ip6ip6 tunnels run iptunnel_handle_offloads on xmit which can cause a possible use-after-free accessing iph/ipv6h pointer since the packet will be 'uncloned' running pskb_expand_head if it is a cloned gso skb

[PATCH 5.2 12/56] ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6

2019-08-08 Thread Greg Kroah-Hartman
From: Haishuang Yan [ Upstream commit 3bc817d665ac6d9de89f59df522ad86f5b5dfc03 ] Since ip6_tnl_parse_tlv_enc_lim() can call pskb_may_pull() which may change skb->data, so we need to re-load ipv6h at the right place. Fixes: 898b29798e36 ("ip6_gre: Refactor ip6gre xmit codes") Cc: William Tu Sig

[PATCH 5.2 01/56] scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure

2019-08-08 Thread Greg Kroah-Hartman
From: Hannes Reinecke commit 023358b136d490ca91735ac6490db3741af5a8bd upstream. Gcc-9 complains for a memset across pointer boundaries, which happens as the code tries to allocate a flexible array on the stack. Turns out we cannot do this without relying on gcc-isms, so with this patch we'll em

Re: [PATCH net-next] net/ncsi: allow to customize BMC MAC Address offset

2019-08-08 Thread Tao Ren
Hi Andrew, On 8/8/19 6:32 AM, Andrew Lunn wrote: >> Let me prepare patch v2 using device tree. I'm not sure if standard >> "mac-address" fits this situation because all we need is an offset >> (integer) and BMC MAC is calculated by adding the offset to NIC's >> MAC address. Anyways, let me work ou

[PATCH] soc: xilinx: Set CAP_UNUSABLE requirement for versal while powering down domain

2019-08-08 Thread Jolly Shah
From: Tejas Patel For "0" requirement which is used to inform firmware that device is not required currently by master, Versal LibPM disables clock, power it down and reset the device. genpd_power_off() is being called during runtime suspend also. So, if any device goes to runtime suspend state d

Re: Let's talk about the elephant in the room - the Linux kernel's inability to gracefully handle low memory pressure

2019-08-08 Thread Michal Hocko
On Thu 08-08-19 18:57:02, ndrw...@redhazel.co.uk wrote: > > > On 8 August 2019 17:32:28 BST, Michal Hocko wrote: > > > >> Would it be possible to reserve a fixed (configurable) amount of RAM > >for caches, > > > >I am afraid there is nothing like that available and I would even argue > >it doesn

[Linux-kernel-mentees][PATCH v4 1/1] sgi-gru: Remove *pte_lookup functions

2019-08-08 Thread Bharath Vedartham
The *pte_lookup functions can be removed and be easily replaced with get_user_pages_fast functions. In the case of atomic lookup, __get_user_pages_fast is used which does not fall back to slow get_user_pages. get_user_pages_fast on the other hand tries to use __get_user_pages_fast but fallbacks to

[PATCH 10/10] perf pmu-events: Fix missing "cpu_clk_unhalted.core" event

2019-08-08 Thread Arnaldo Carvalho de Melo
From: Jin Yao The events defined in pmu-events JSON are parsed and added into perf tool. For fixed counters, we handle the encodings between JSON and perf by using a static array fixed[]. But the fixed[] has missed an important event "cpu_clk_unhalted.core". For example, on the Tremont platform

Re: [PATCH v2 2/2] spi: npcm-fiu: add NPCM FIU controller driver

2019-08-08 Thread Mark Brown
On Thu, Aug 08, 2019 at 06:37:06PM +0300, Tomer Maimon wrote: > for example in our driver we modify the access type (singe, dual or quad) > according the op->addr.buswidth > for example in the npcm_fiu_set_drd function. > regmap_update_bits(fiu->regmap, NPCM_FIU_DRD_CFG, >

[Linux-kernel-mentees][PATCH v4 0/1] get_user_pages changes

2019-08-08 Thread Bharath Vedartham
In this 4th version of the patch series, I have compressed the patches of the v2 patch series into one patch. This was suggested by Christoph Hellwig. The suggestion was to remove the pte_lookup functions and use the get_user_pages* functions directly instead of the pte_lookup functions. There is

[PATCH 09/10] perf annotate: Fix s390 gap between kernel end and module start

2019-08-08 Thread Arnaldo Carvalho de Melo
From: Thomas Richter During execution of command 'perf top' the error message: Not enough memory for annotating '__irf_end' symbol!) is emitted from this call sequence: __cmd_top perf_top__mmap_read perf_top__mmap_read_idx perf_event__process_sample hist_entry_i

[PATCH 08/10] perf record: Fix module size on s390

2019-08-08 Thread Arnaldo Carvalho de Melo
From: Thomas Richter On s390 the modules loaded in memory have the text segment located after the GOT and Relocation table. This can be seen with this output: [root@m35lp76 perf]# fgrep qeth /proc/modules qeth 151552 1 qeth_l2, Live 0x03ff800b2000 ... [root@m35lp76 perf]# cat /sys/mo

[PATCH 01/10] perf bench numa: Fix cpu0 binding

2019-08-08 Thread Arnaldo Carvalho de Melo
From: Jiri Olsa Michael reported an issue with perf bench numa failing with binding to cpu0 with '-0' option. # perf bench numa mem -p 3 -t 1 -P 512 -s 100 -zZcm0 --thp 1 -M 1 -ddd # Running 'numa/mem' benchmark: # Running main, "perf bench numa numa-mem -p 3 -t 1 -P 512 -s 100 -zZcm0 -

[PATCH 07/10] perf tools: Fix include paths in ui directory

2019-08-08 Thread Arnaldo Carvalho de Melo
From: Ian Rogers These paths point to the wrong location but still work because they get picked up by a -I flag that happens to direct to the correct file. Fix paths to point to the correct location without -I flags. Signed-off-by: Ian Rogers Cc: Alexander Shishkin Cc: Andi Kleen Cc: Jiri Ols

[PATCH 06/10] perf tools: Fix a typo in a variable name in the Documentation Makefile

2019-08-08 Thread Arnaldo Carvalho de Melo
From: Masanari Iida This patch fix a spelling typo in a variable name in the Documentation Makefile. Signed-off-by: Masanari Iida Reviewed-by: Mukesh Ojha Cc: Alexander Shishkin Cc: Namhyung Kim Cc: Peter Zijlstra Link: http://lkml.kernel.org/r/20190801032812.25018-1-standby2...@gmail.com S

[PATCH 02/10] perf annotate: Fix printing of unaugmented disassembled instructions from BPF

2019-08-08 Thread Arnaldo Carvalho de Melo
From: Arnaldo Carvalho de Melo The code to disassemble BPF programs uses binutil's disassembling routines, and those use in turn fprintf to print to a memstream FILE, adding a newline at the end of each line, which ends up confusing the TUI routines called from: annotate_browser__write() a

[PATCH 03/10] perf db-export: Fix thread__exec_comm()

2019-08-08 Thread Arnaldo Carvalho de Melo
From: Adrian Hunter Threads synthesized from /proc have comms with a start time of zero, and not marked as "exec". Currently, there can be 2 such comms. The first is created by processing a synthesized fork event and is set to the parent's comm string, and the second by processing a synthesized c

[PATCH 05/10] perf cpumap: Fix writing to illegal memory in handling cpumap mask

2019-08-08 Thread Arnaldo Carvalho de Melo
From: He Zhe cpu_map__snprint_mask() would write to illegal memory pointed by zalloc(0) when there is only one cpu. This patch fixes the calculation and adds sanity check against the input parameters. Signed-off-by: He Zhe Cc: Alexander Shishkin Cc: Alexey Budankov Cc: Jiri Olsa Cc: Kan Lia

[PATCH 04/10] perf ftrace: Fix failure to set cpumask when only one cpu is present

2019-08-08 Thread Arnaldo Carvalho de Melo
From: He Zhe The buffer containing the string used to set cpumask is overwritten at the end of the string later in cpu_map__snprint_mask due to not enough memory space, when there is only one cpu. And thus causes the following failure: $ perf ftrace ls failed to reset ftrace $ This patch

[GIT PULL] perf/urgent improvements and fixes

2019-08-08 Thread Arnaldo Carvalho de Melo
kernel/git/acme/linux into perf/urgent (2019-07-29 23:24:07 +0200) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-urgent-for-mingo-5.3-20190808 for you to fetch changes up to 8e6e5bea2e34c61291d00cb3f47560341aa84bc3: perf

Re: [PATCH] hugetlbfs: fix hugetlb page migration/fault race causing SIGBUS

2019-08-08 Thread Michal Hocko
On Thu 08-08-19 09:55:45, Mike Kravetz wrote: > On 8/8/19 12:47 AM, Michal Hocko wrote: > > On Thu 08-08-19 09:46:07, Michal Hocko wrote: > >> On Wed 07-08-19 17:05:33, Mike Kravetz wrote: > >>> Li Wang discovered that LTP/move_page12 V2 sometimes triggers SIGBUS > >>> in the kernel-v5.2.3 testing.

Re: [PATCH] mm/oom: Add killed process selection information

2019-08-08 Thread Michal Hocko
On Thu 08-08-19 11:32:47, Edward Chron wrote: > For an OOM event: print oomscore, memory pct, oom adjustment of the process > that OOM kills and the totalpages value in kB (KiB) used in the calculation > with the OOM killed process message. This is helpful to document why the > process was selected

Re: [PATCH] liquidio: Use pcie_flr() instead of reimplementing it

2019-08-08 Thread Bjorn Helgaas
On Thu, Aug 08, 2019 at 07:57:53AM +0300, Denis Efremov wrote: > octeon_mbox_process_cmd() directly writes the PCI_EXP_DEVCTL_BCR_FLR > bit, which bypasses timing requirements imposed by the PCIe spec. > This patch fixes the function to use the pcie_flr() interface instead. > > Signed-off-by: Deni

RE: [PATCH v3 1/1] ixgbe: sync the first fragment unconditionally

2019-08-08 Thread Bowers, AndrewX
> -Original Message- > From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On > Behalf Of Firo Yang > Sent: Wednesday, August 7, 2019 9:04 PM > To: net...@vger.kernel.org > Cc: maciejromanfijalkow...@gmail.com; Firo Yang ; > linux-kernel@vger.kernel.org; intel-wired-...@lists.

[PATCH] mm/oom: Add killed process selection information

2019-08-08 Thread Edward Chron
For an OOM event: print oomscore, memory pct, oom adjustment of the process that OOM kills and the totalpages value in kB (KiB) used in the calculation with the OOM killed process message. This is helpful to document why the process was selected by OOM at the time of the OOM event. Sample message

Re: [PATCH 2/2] drivers: qcom: Add SoC sleep stats driver

2019-08-08 Thread Stephen Boyd
Quoting Maulik Shah (2019-08-07 23:12:28) > Qualcomm Technologies Inc's (QTI) chipsets support SoC level > low power modes. Statistics for SoC sleep stats are produced > by remote processor. > > Lets's add a driver to read the shared memory exported by the > remote processor and export to sysfs. >

[PATCH 2/2] parport: parport_serial: Add support for Sunix Multi I/O boards

2019-08-08 Thread Kai-Heng Feng
Sunix Multi I/O boards are different to Timedia's. This patch adds proper support for Sunix MIO boards with 1 parallel and up to 4 serial ports. Cc: Morris Ku Cc: Debbie Liu Signed-off-by: Kai-Heng Feng --- drivers/parport/parport_serial.c | 44 +++- 1 file changed

[PATCH 1/2] serial: 8250_pci: Add support for Sunix serial boards

2019-08-08 Thread Kai-Heng Feng
Add support to Sunix serial boards with up to 16 ports. Sunix board need its own setup callback instead of using Timedia's, to properly support more than 4 ports. Cc: Morris Ku Cc: Debbie Liu Signed-off-by: Kai-Heng Feng --- drivers/tty/serial/8250/8250_pci.c | 93 +++

Re: [PATCH] dt-bindings: mfd: rn5t618: Document optional property system-power-controller

2019-08-08 Thread Jonathan Neuschäfer
On Fri, Feb 01, 2019 at 09:24:11AM +, Lee Jones wrote: > On Tue, 29 Jan 2019, Jonathan Neuschäfer wrote: > > > The RN5T618 family of PMICs can be used as system management > > controllers, in which case they handle poweroff and restart. Document > > this capability by referring to the correspo

Re: [PATCH v2 2/2] nvme-pci: Allow PCI bus-level PM to be used if ASPM is disabled

2019-08-08 Thread Bjorn Helgaas
On Thu, Aug 08, 2019 at 04:47:45PM +0200, Rafael J. Wysocki wrote: > On Thu, Aug 8, 2019 at 3:43 PM Bjorn Helgaas wrote: > > On Thu, Aug 08, 2019 at 12:10:06PM +0200, Rafael J. Wysocki wrote: > > > From: Rafael J. Wysocki > > > > > > One of the modifications made by commit d916b1be94b6 ("nvme-pci

Re: [PATCH net-next] taprio: remove unused variable 'entry_list_policy'

2019-08-08 Thread David Miller
From: YueHaibing Date: Thu, 8 Aug 2019 22:26:23 +0800 > net/sched/sch_taprio.c:680:32: warning: > entry_list_policy defined but not used [-Wunused-const-variable=] > > It is not used since commit a3d43c0d56f1 ("taprio: Add > support adding an admin schedule") > > Reported-by: Hulk Robot > Sig

Re: [PATCH 1/1] block: Use bits.h macros to improve readability

2019-08-08 Thread Leonardo Bras
On Fri, 2019-08-02 at 21:18 -0700, Jens Axboe wrote: > On 8/1/19 6:00 PM, Leonardo Bras wrote: > > Applies some bits.h macros in order to improve readability of > > linux/blk_types.h. > > > > Signed-off-by: Leonardo Bras > > --- > > include/linux/blk_types.h | 55 ---

Re: [PATCH] fanotify, inotify, dnotify, security: add security hook for fs notifications

2019-08-08 Thread Paul Moore
On Wed, Jul 31, 2019 at 11:35 AM Aaron Goidel wrote: > As of now, setting watches on filesystem objects has, at most, applied a > check for read access to the inode, and in the case of fanotify, requires > CAP_SYS_ADMIN. No specific security hook or permission check has been > provided to control

Re: [PATCH V37 04/29] Enforce module signatures if the kernel is locked down

2019-08-08 Thread Matthew Garrett
On Thu, Aug 8, 2019 at 3:01 AM Jessica Yu wrote: > If you're confident that a hard dependency is not the right approach, > then perhaps we could add a comment in the Kconfig (You could take a > look at the comment under MODULE_SIG_ALL in init/Kconfig for an > example)? If someone is configuring th

Re: [PATCH v2 4/6] irqchip/irq-pruss-intc: Add helper functions to configure internal mapping

2019-08-08 Thread David Lechner
On 8/8/19 12:09 PM, David Lechner wrote: Then we can provide a vendor resource hook in the remoteproc driver to handle these resources: static int ti_pru_rproc_handle_rsc(struct rproc *rproc, u32 rsc_type, void *rsc,    int offset, int avail) { struct ti_pru_data *pru = rp

[PATCH] mm, vmscan: Do not special-case slab reclaim when watermarks are boosted

2019-08-08 Thread Mel Gorman
Dave Chinner reported a problem pointing a finger at commit 1c30844d2dfe ("mm: reclaim small amounts of memory when an external fragmentation event occurs"). The report is extensive (see https://lore.kernel.org/linux-mm/20190807091858.2857-1-da...@fromorbit.com/) and it's worth recording the most r

Re: [PATCH 09/20] ext4: Initialize timestamps limits

2019-08-08 Thread Deepa Dinamani
> Rather than printing a warning at mount time (which may be confusing > to users for a problem they may never see), it makes sense to only > print such a warning in the vanishingly small case that someone actually > tries to modify the inode timestamp but it doesn't fit, rather than on > the theor

Re: [PATCH v2 00/15] net: phy: adin: add support for Analog Devices PHYs

2019-08-08 Thread David Miller
From: Alexandru Ardelean Date: Thu, 8 Aug 2019 15:30:11 +0300 > This changeset adds support for Analog Devices Industrial Ethernet PHYs. > Particularly the PHYs this driver adds support for: > * ADIN1200 - Robust, Industrial, Low Power 10/100 Ethernet PHY > * ADIN1300 - Robust, Industrial, Low

Re: [PATCH v3 0/2] dt-bindings: net: meson-dwmac: convert to yaml

2019-08-08 Thread David Miller
From: Neil Armstrong Date: Thu, 8 Aug 2019 13:40:59 +0200 > This patchsets converts the Amlogic Meson DWMAC glue bindings over to > YAML schemas using the already converted dwmac bindings. > > The first patch is needed because the Amlogic glue needs a supplementary > reg cell to access the DWMA

Re: [PATCH 1/1] fs/splice.c: Fix old documentation about moving pages

2019-08-08 Thread Leonardo Bras
On Thu, 2019-08-01 at 19:38 -0300, Leonardo Bras wrote: > Since commit 485ddb4b9741 ("1/2 splice: dont steal")' (2007), > the SPLICE_F_MOVE support was removed (became a no-op according > to man pages), and thus disabling steal operation that would make > moving pages possible. > > This fixes the

[PATCH v2] div64.h: Fix description of do_div parameter

2019-08-08 Thread Jonathan Neuschäfer
Contrary to the description, the first parameter (n) should not be passed as a pointer, but directly as an lvalue. This is possible because do_div is a macro. Signed-off-by: Jonathan Neuschäfer Reviewed-by: Geert Uytterhoeven --- v2: - add Geert Uytterhoeven's R-b v1: - https://lore.kernel.org

[PATCH] arch/x86/kernel/cpu/common.c - add proper prototypes

2019-08-08 Thread Valdis Klētnieks
When building withW=1, we get a warning.. CC arch/x86/kernel/cpu/common.o arch/x86/kernel/cpu/common.c:1952:6: warning: no previous prototype for 'arch_smt_update' [-Wmissing-prototypes] 1952 | void arch_smt_update(void) | ^~~ Provide the proper #include so the pro

Re: [PATCH 3/3] pagewalk: use lockdep_assert_held for locking validation

2019-08-08 Thread Matthew Wilcox
On Thu, Aug 08, 2019 at 06:42:40PM +0300, Christoph Hellwig wrote: > Use lockdep to check for held locks instead of using home grown > asserts. > > @@ -319,7 +319,7 @@ int walk_page_range(struct mm_struct *mm, unsigned long > start, > if (!walk.mm) > return -EINVAL; > > -

Re: [PATCH RFC v1 1/2] rcu/tree: Add basic support for kfree_rcu batching

2019-08-08 Thread Paul E. McKenney
On Thu, Aug 08, 2019 at 07:26:10PM +0900, Byungchul Park wrote: > On Wed, Aug 07, 2019 at 05:45:04AM -0400, Joel Fernandes wrote: > > On Tue, Aug 06, 2019 at 04:56:31PM -0700, Paul E. McKenney wrote: > > [snip] > > > > On Tue, Aug 06, 2019 at 05:20:40PM -0400, Joel Fernandes (Google) wrote: > > >

Re: [PATCH RFC v1 1/2] rcu/tree: Add basic support for kfree_rcu batching

2019-08-08 Thread Paul E. McKenney
On Thu, Aug 08, 2019 at 11:23:17PM +0900, Byungchul Park wrote: > On Thu, Aug 8, 2019 at 9:56 PM Joel Fernandes wrote: > > > > On Thu, Aug 08, 2019 at 06:52:32PM +0900, Byungchul Park wrote: > > > On Wed, Aug 07, 2019 at 10:52:15AM -0700, Paul E. McKenney wrote: > > > > > > On Tue, Aug 06, 2019 at

Re: [PATCH v4 2/3] dt-bindings: eeprom: at25: Add Anvo ANV32E61W

2019-08-08 Thread Schrempf Frieder
On 08.08.19 19:26, Krzysztof Kozlowski wrote: > Document the compatible for ANV32E61W EEPROM chip. This chip is actually not an EEPROM, but a SPI nvSRAM. It can be interfaced by the at25 driver similar to an EEPROM. This is not the ideal solution, but it works until there's a proper driver for s

Re: [PATCH] auxdisplay: charlcd: add help text for backlight initial state

2019-08-08 Thread Miguel Ojeda
On Thu, Jul 4, 2019 at 9:34 PM Mans Rullgard wrote: > > While the individual CHARLCD_BL_xxx options have help texts, the > menu itself does not. Fix this. > > Signed-off-by: Mans Rullgard Picked it up and added a bit of extra explanation, thanks! Cheers, Miguel

Re: [PATCH] auxdisplay: panel: need to delete scan_timer when misc_register fails in panel_attach

2019-08-08 Thread Miguel Ojeda
On Mon, Jul 8, 2019 at 2:37 PM zhengbin wrote: > > In panel_attach, if misc_register fails, we need to delete scan_timer, > which was setup in keypad_init->init_scan_timer. > > Reported-by: Hulk Robot > Signed-off-by: zhengbin Picked it up, thanks! Cheers, Miguel

Re: [PATCH] auxdisplay: Fix a typo in cfag12864b-example.c

2019-08-08 Thread Miguel Ojeda
On Tue, Aug 6, 2019 at 4:25 PM Masanari Iida wrote: > > This patch fix a spelling typo in cfag12864b-example.c > > Signed-off-by: Masanari Iida Picked it up, thanks! Cheers, Miguel

Re: [PATCH 1/2] auxdisplay: charlcd: move charlcd.h to drivers/auxdisplay

2019-08-08 Thread Miguel Ojeda
On Tue, Aug 6, 2019 at 9:18 AM Geert Uytterhoeven wrote: > > On Tue, Aug 6, 2019 at 9:16 AM Masahiro Yamada > wrote: > > This header is included in drivers/auxdisplay/. Make it a local header. > > > > Signed-off-by: Masahiro Yamada > > Reviewed-by: Geert Uytterhoeven Picked it up, thanks! Che

Re: [PATCH 2/2] auxdisplay: charlcd: add include guard to charlcd.h

2019-08-08 Thread Miguel Ojeda
On Tue, Aug 6, 2019 at 9:15 AM Masahiro Yamada wrote: > > Add a header include guard just in case. > > Signed-off-by: Masahiro Yamada Picked it up, thanks! Cheers, Miguel

Re: remove sn2, hpsim and ia64 machvecs

2019-08-08 Thread Luck, Tony
On Thu, Aug 08, 2019 at 08:51:23AM +0200, 'Christoph Hellwig' wrote: > On Wed, Aug 07, 2019 at 04:07:37PM -0700, Luck, Tony wrote: > > On Wed, Aug 07, 2019 at 01:26:17PM -0700, Luck, Tony wrote: > > > Ugh! The rule to do the compression was in arch/ia64/hp/sim/boot/Makefile > > > which went away as

Re: [PATCH 0/6] arm64: add support for the Khadas VIM3

2019-08-08 Thread Kevin Hilman
Neil Armstrong writes: > The Khadas VIM3 uses the Amlogic S922X or A311S SoC, both based on the > Amlogic G12B SoC family, on a board with the same form factor as the > VIM/VIM2 models. It ships in two variants; basic and > pro which differ in RAM and eMMC size: > > - 2GB (basic) or 4GB (pro) LPD

Re: Let's talk about the elephant in the room - the Linux kernel's inability to gracefully handle low memory pressure

2019-08-08 Thread ndrw . xf
On 8 August 2019 17:32:28 BST, Michal Hocko wrote: > >> Would it be possible to reserve a fixed (configurable) amount of RAM >for caches, > >I am afraid there is nothing like that available and I would even argue >it doesn't make much sense either. What would you consider to be a >cache? A kern

Re: cleanup the walk_page_range interface

2019-08-08 Thread Linus Torvalds
On Thu, Aug 8, 2019 at 8:42 AM Christoph Hellwig wrote: > > this series is based on a patch from Linus to split the callbacks > passed to walk_page_range and walk_page_vma into a separate structure > that can be marked const, with various cleanups from me on top. The whole series looks good to me

[PATCH] arch/x86/events - make more stuff static

2019-08-08 Thread Valdis Klētnieks
When building with C=2, sparse makes note of a number of things: CHECK arch/x86/events/intel/rapl.c arch/x86/events/intel/rapl.c:637:30: warning: symbol 'rapl_attr_update' was not declared. Should it be static? CHECK arch/x86/events/intel/cstate.c arch/x86/events/intel/cstate.c:449:30: wa

Re: [PATCH v3 1/3] kasan: support backing vmalloc space with real shadow memory

2019-08-08 Thread Mark Rutland
On Thu, Aug 08, 2019 at 02:50:37PM +0100, Mark Rutland wrote: > Hi Daniel, > > This is looking really good! > > I spotted a few more things we need to deal with, so I've suggested some > (not even compile-tested) code for that below. Mostly that's just error > handling, and using helpers to avoid

Re: [GIT PULL for v5.3-rc4] media fixes

2019-08-08 Thread Linus Torvalds
On Thu, Aug 8, 2019 at 8:39 AM Mauro Carvalho Chehab wrote: > > Please pull from: > git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media > media/v5.3-2 > > For a fix at the vivid CEC support. There's no vivid CEC fix there, and you already asked me to pull that tag two weeks ago,

[PATCH RESEND v7 3/3] arm64: kexec_file: add rng-seed support

2019-08-08 Thread Hsin-Yi Wang
Adding "rng-seed" to dtb. It's fine to add this property if original fdt doesn't contain it. Since original seed will be wiped after read, so use a default size 128 bytes here. Signed-off-by: Hsin-Yi Wang Reviewed-by: Stephen Boyd --- arch/arm64/kernel/machine_kexec_file.c | 18

[PATCH RESEND v7 2/3] fdt: add support for rng-seed

2019-08-08 Thread Hsin-Yi Wang
Introducing a chosen node, rng-seed, which is an entropy that can be passed to kernel called very early to increase initial device randomness. Bootloader should provide this entropy and the value is read from /chosen/rng-seed in DT. Signed-off-by: Hsin-Yi Wang Reviewed-by: Stephen Boyd Reviewed-

[PATCH RESEND v7 1/3] arm64: map FDT as RW for early_init_dt_scan()

2019-08-08 Thread Hsin-Yi Wang
Currently in arm64, FDT is mapped to RO before it's passed to early_init_dt_scan(). However, there might be some codes (eg. commit "fdt: add support for rng-seed") that need to modify FDT during init. Map FDT to RO after early fixups are done. Signed-off-by: Hsin-Yi Wang Reviewed-by: Stephen Boyd

[PATCH RESEND v7 0/3] add support for rng-seed

2019-08-08 Thread Hsin-Yi Wang
Introducing a chosen node, rng-seed, which is an entropy that can be passed to kernel called very early to increase initial device randomness. This can be used for adding sufficient initial entropy for stack canary. Especially architectures that lack per-stack canary. Hsin-Yi Wang (3): arm64: ma

Re: [PATCH 2/2] interconnect: qcom: Add OSM L3 interconnect provider support

2019-08-08 Thread Sibi Sankar
Hey Saravana, Thanks for the review! On 8/8/19 2:51 AM, Saravana Kannan wrote: On Wed, Aug 7, 2019 at 4:24 AM Sibi Sankar wrote: On some Qualcomm SoCs, Operating State Manager (OSM) controls the resources of scaling L3 caches. Add a driver to handle bandwidth requests to OSM L3 from CPU/GPU.

Re: [PATCH 1/2] cpufreq: drivers: Enable frequency invariance in qcom-cpufreq-hw

2019-08-08 Thread Quentin Perret
Hi Douglas, On Thursday 08 Aug 2019 at 14:18:57 (+0100), Douglas RAILLARD wrote: > Add calls to arch_set_freq_scale() in qcom-cpufreq-hw driver to enable > frequency invariance. Is there a patch 2/2 ? > > Signed-off-by: Douglas RAILLARD > --- > drivers/cpufreq/qcom-cpufreq-hw.c | 10 +

[PATCH v3 3/7] x86: KVM: clear interrupt shadow on EMULTYPE_SKIP

2019-08-08 Thread Vitaly Kuznetsov
When doing x86_emulate_instruction(EMULTYPE_SKIP) interrupt shadow has to be cleared if and only if the skipping is successful. There are two immediate issues: - In SVM skip_emulated_instruction() we are not zapping interrupt shadow in case kvm_emulate_instruction(EMULTYPE_SKIP) is used to advan

[PATCH v3 5/7] x86: KVM: svm: remove hardcoded instruction length from intercepts

2019-08-08 Thread Vitaly Kuznetsov
Various intercepts hard-code the respective instruction lengths to optimize skip_emulated_instruction(): when next_rip is pre-set we skip kvm_emulate_instruction(vcpu, EMULTYPE_SKIP). The optimization is, however, incorrect: different (redundant) prefixes could be used to enlarge the instruction. W

[PATCH] nds32: remove unneeded clean-files for DTB

2019-08-08 Thread Masahiro Yamada
These patterns are cleaned-up by the top-level Makefile Signed-off-by: Masahiro Yamada --- arch/nds32/boot/dts/Makefile | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/nds32/boot/dts/Makefile b/arch/nds32/boot/dts/Makefile index fff8ade7a84f..f84bd529b6fd 100644 --- a/arch/nds32/boot/

[PATCH v3 7/7] x86: KVM: svm: eliminate hardcoded RIP advancement from vmrun_interception()

2019-08-08 Thread Vitaly Kuznetsov
Just like we do with other intercepts, in vmrun_interception() we should be doing kvm_skip_emulated_instruction() and not just RIP += 3. Also, it is wrong to increment RIP before nested_svm_vmrun() as it can result in kvm_inject_gp(). We can't call kvm_skip_emulated_instruction() after nested_svm_

[PATCH v3 6/7] x86: KVM: svm: eliminate weird goto from vmrun_interception()

2019-08-08 Thread Vitaly Kuznetsov
Regardless of whether or not nested_svm_vmrun_msrpm() fails, we return 1 from vmrun_interception() so there's no point in doing goto. Also, nested_svm_vmrun_msrpm() call can be made from nested_svm_vmrun() where other nested launch issues are handled. Suggested-by: Sean Christopherson Signed-off-

[PATCH v3 4/7] x86: KVM: add xsetbv to the emulator

2019-08-08 Thread Vitaly Kuznetsov
To avoid hardcoding xsetbv length to '3' we need to support decoding it in the emulator. Signed-off-by: Vitaly Kuznetsov --- arch/x86/include/asm/kvm_emulate.h | 3 ++- arch/x86/kvm/emulate.c | 23 ++- arch/x86/kvm/svm.c | 1 + arch/x86/kvm/x86.c

[PATCH v3 2/7] x86: kvm: svm: propagate errors from skip_emulated_instruction()

2019-08-08 Thread Vitaly Kuznetsov
On AMD, kvm_x86_ops->skip_emulated_instruction(vcpu) can, in theory, fail: in !nrips case we call kvm_emulate_instruction(EMULTYPE_SKIP). Currently, we only do printk(KERN_DEBUG) when this happens and this is not ideal. Propagate the error up the stack. On VMX, skip_emulated_instruction() doesn't

[PATCH v3 1/7] x86: KVM: svm: don't pretend to advance RIP in case wrmsr_interception() results in #GP

2019-08-08 Thread Vitaly Kuznetsov
svm->next_rip is only used by skip_emulated_instruction() and in case kvm_set_msr() fails we rightfully don't do that. Move svm->next_rip advancement to 'else' branch to avoid creating false impression that it's always advanced (and make it look like rdmsr_interception()). This is a preparatory ch

[PATCH v3 0/7] x86: KVM: svm: get rid of hardcoded instructions lengths

2019-08-08 Thread Vitaly Kuznetsov
Changes since v2 [Sean Christopherson]: - Add Reviewed-by tags: - PATCH2 replaced with the suggested "x86: kvm: svm: propagate errors from skip_emulated_instruction()" approach. - PATCH5 split into three separating vmrun_interception() from others and implementing the suggested solution. Origi

[PATCH] um: remove meaningless clearing of clean-files

2019-08-08 Thread Masahiro Yamada
Signed-off-by: Masahiro Yamada --- arch/um/kernel/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/um/kernel/Makefile b/arch/um/kernel/Makefile index 2f36d515762e..89afc54f8699 100644 --- a/arch/um/kernel/Makefile +++ b/arch/um/kernel/Makefile @@ -13,7 +13,6 @@ CPPFLAGS_vmlinux.l

[PATCH] arch/x86/events/intel/lbr.c - make variable static

2019-08-08 Thread Valdis Klētnieks
When compiling with C=2, sparse warns: CHECK arch/x86/events/intel/lbr.c arch/x86/events/intel/lbr.c:276:1: warning: symbol 'lbr_from_quirk_key' was not declared. Should it be static? And yes, it can be static. Signed-off-by: Valdis Kletnieks diff --git a/arch/x86/events/intel/lbr.c b/arc

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

2019-08-08 Thread Tim Chen
On 8/7/19 11:47 PM, Aaron Lu wrote: > On Tue, Aug 06, 2019 at 02:19:57PM -0700, Tim Chen wrote: >> +void account_core_idletime(struct task_struct *p, u64 exec) >> +{ >> +const struct cpumask *smt_mask; >> +struct rq *rq; >> +bool force_idle, refill; >> +int i, cpu; >> + >> +rq =

Re: Let's talk about the elephant in the room - the Linux kernel's inability to gracefully handle low memory pressure

2019-08-08 Thread Johannes Weiner
On Thu, Aug 08, 2019 at 04:47:18PM +0200, Vlastimil Babka wrote: > On 8/7/19 10:51 PM, Johannes Weiner wrote: > > From 9efda85451062dea4ea287a886e515efefeb1545 Mon Sep 17 00:00:00 2001 > > From: Johannes Weiner > > Date: Mon, 5 Aug 2019 13:15:16 -0400 > > Subject: [PATCH] psi: trigger the OOM kill

[PATCH v4 2/3] dt-bindings: eeprom: at25: Add Anvo ANV32E61W

2019-08-08 Thread Krzysztof Kozlowski
Document the compatible for ANV32E61W EEPROM chip. Signed-off-by: Krzysztof Kozlowski Reviewed-by: Fabio Estevam --- New patch --- Documentation/devicetree/bindings/eeprom/at25.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/eeprom/at25.txt b/Documen

[PATCH v4 1/3] dt-bindings: vendor-prefixes: Add Anvo-Systems

2019-08-08 Thread Krzysztof Kozlowski
Add vendor prefix for Anvo-Systems Dresden GmbH. Signed-off-by: Krzysztof Kozlowski Reviewed-by: Rob Herring --- Changes since v3: 1. Add Rob's tag, 2. Remove Admatec (not needed anymore). Changes since v2: 1. Use admatecde vendor prefix. 2. Add Anvo-Systems Dresden GmbH. Changes since v1: N

[PATCH v4 3/3] ARM: dts: imx6ul-kontron-n6310: Add Kontron i.MX6UL N6310 SoM and boards

2019-08-08 Thread Krzysztof Kozlowski
Add support for i.MX6UL modules from Kontron Electronics GmbH (before acquisition: Exceet Electronics) and evalkit boards based on it: 1. N6310 SOM: i.MX6 UL System-on-Module, a 25x25 mm solderable module (LGA pads and pin castellations) with 256 MB RAM, 1 MB NOR-Flash, 256 MB NAND and other

Re: [PATCH 1/2 v2] tracing/arm64: Have max stack tracer handle the case of return address after data

2019-08-08 Thread Steven Rostedt
On Thu, 8 Aug 2019 18:11:53 +0100 Will Deacon wrote: > > We could make it more descriptive of what it will do and not the reason > > for why it is done... > > > > > > ARCH_FTRACE_SHIFT_STACK_TRACER > > Acked-by: Will Deacon Thanks Will! Here's the official patch. From: "Steven Rostedt

general protection fault in perf_tp_event_match (2)

2019-08-08 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:1e78030e Merge tag 'mmc-v5.3-rc1' of git://git.kernel.org/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1011831a60 kernel config: https://syzkaller.appspot.com/x/.config?x=4c7b914a2680c9c6 da

Re: [PATCH v2] selftests: kvm: Adding config fragments

2019-08-08 Thread shuah
On 8/8/19 6:31 AM, Naresh Kamboju wrote: selftests kvm all test cases need pre-required kernel configs for the tests to get pass. The KVM tests are skipped without these configs: dev_fd = open(KVM_DEV_PATH, O_RDONLY); if (dev_fd < 0) exit(KSFT_SKIP); Thanks

Re: [PATCH v13 1/6] sched/core: uclamp: Extend CPU's cgroup controller

2019-08-08 Thread Michal Koutný
On Thu, Aug 08, 2019 at 04:10:21PM +0100, Patrick Bellasi wrote: > Not sure to get what you mean here: I'm currently exposing uclamp to > both v1 and v2 hierarchies. cpu controller has different API for v1 and v2 hierarchies. My question reworded is -- are the new knobs exposed in the legacy API

Re: [PATCH v13 2/6] sched/core: uclamp: Propagate parent clamps

2019-08-08 Thread Michal Koutný
On Thu, Aug 08, 2019 at 04:08:10PM +0100, Patrick Bellasi wrote: > Well, if I've got correctly your comment in the previous message, I > would say that at this stage we don't need RCU looks at all. Agreed. > Reason being that cpu_util_update_eff() gets called only from > cpu_uclamp_write() which

Re: [PATCH v12 3/6] mm, thp: introduce FOLL_SPLIT_PMD

2019-08-08 Thread Song Liu
> On Aug 8, 2019, at 9:37 AM, Oleg Nesterov wrote: > > On 08/07, Song Liu wrote: >> >> @@ -399,7 +399,7 @@ static struct page *follow_pmd_mask(struct >> vm_area_struct *vma, >> spin_unlock(ptl); >> return follow_page_pte(vma, address, pmd, flags, &ctx->pgmap); >>

Re: [PATCH 1/2 v2] tracing/arm64: Have max stack tracer handle the case of return address after data

2019-08-08 Thread Will Deacon
On Thu, Aug 08, 2019 at 12:36:32PM -0400, Steven Rostedt wrote: > On Thu, 8 Aug 2019 17:28:26 +0100 > Will Deacon wrote: > > > > + * Note, this may change in the future, and we will need to deal with > > > that > > > + * if it were to happen. > > > + */ > > > +#define ARCH_RET_ADDR_AFTER_LOCAL_V

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