Re: [PATCH v3 03/20] coresight: etm4x: Skip selector pair 0

On 04/04/2019 04:35, Mathieu Poirier wrote: Resource selector pair 0 is always implemented and reserved. As such it should not be explicitly programmed. Signed-off-by: Mathieu Poirier Reviewed-by: Suzuki K Poulose

[PATCH 4.9 13/91] include/linux/relay.h: fix percpu annotation in struct rchan

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 62461ac2e5b6520b6d65fc6d7d7b4b8df4b848d8 ] The percpu member of this structure is declared as: struct ... ** __percpu member; So its type is: __percpu pointer to

[PATCH 4.9 47/91] media: s5p-g2d: Correct return type for mem2mem buffer helpers

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 30fa627b32230737bc3f678067e2adfecf956987 ] Fix the assigned type of mem2mem buffer handling API. Namely, these functions: v4l2_m2m_next_buf v4l2_m2m_last_buf v4l2_m2m_buf_remove

[PATCH 4.9 18/91] mm/page_ext.c: fix an imbalance with kmemleak

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0c81585499601acd1d0e1cbf424cabfaee60628c ] After offlining a memory block, kmemleak scan will trigger a crash, as it encounters a page ext address that has already been freed during

[PATCH 4.9 29/91] fs: fix guard_bio_eod to check for real EOD errors

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit dce30ca9e3b676fb288c33c1f4725a0621361185 ] guard_bio_eod() can truncate a segment in bio to allow it to do IO on odd last sectors of a device. It already checks if the IO starts

[PATCH 4.9 21/91] ocfs2: fix a panic problem caused by o2cb_ctl

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cc725ef3cb202ef2019a3c67c8913efa05c3cce6 ] In the process of creating a node, it will cause NULL pointer dereference in kernel if o2cb_ctl failed in the interval (mkdir,

[PATCH 4.9 39/91] e1000e: Fix -Wformat-truncation warnings

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 135e7245479addc6b1f5d031e3d7e2ddb3d2b109 ] Provide precision hints to snprintf() since we know the destination buffer size of the RX/TX ring names are IFNAMSIZ + 5 - 1. This fixes

[PATCH 4.9 38/91] mmc: omap: fix the maximum timeout setting

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a6327b5e57fdc679c842588c3be046c0b39cc127 ] When running OMAP1 kernel on QEMU, MMC access is annoyingly noisy: MMC: CTO of 0xff and 0xfe cannot be used! MMC: CTO of

[PATCH 4.9 60/91] bcache: improve sysfs_strtoul_clamp()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 596b5a5dd1bc2fa019fdaaae522ef331deef927f ] Currently sysfs_strtoul_clamp() is defined as, 82 #define sysfs_strtoul_clamp(file, var, min, max) \ 83 do {

[PATCH 4.9 61/91] genirq: Avoid summation loops for /proc/stat

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1136b0728969901a091f0471968b2b76ed14d9ad ] Waiman reported that on large systems with a large amount of interrupts the readout of /proc/stat takes a long time to sum up the interrupt

[PATCH 4.9 62/91] iw_cxgb4: fix srqidx leak during connection abort

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f368ff188ae4b3ef6f740a15999ea0373261b619 ] When an application aborts the connection by moving QP from RTS to ERROR, then iw_cxgb4's modify_rc_qp() RTS->ERROR logic sets the *srqidxp

[PATCH 4.9 64/91] cdrom: Fix race condition in cdrom_sysctl_register

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f25191bb322dec8fa2979ecb8235643aa42470e1 ] The following traceback is sometimes seen when booting an image in qemu: [ 54.608293] cdrom: Uniform CD-ROM driver Revision: 3.20 [

[PATCH 4.9 63/91] fbdev: fbmem: fix memory access if logo is bigger than the screen

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a5399db139cb3ad9b8502d8b1bd02da9ce0b9df0 ] There is no clipping on the x or y axis for logos larger that the framebuffer size. Therefore: a logo bigger than screen size leads to

Re: [PATCH] soundwire: cdns: Fix compilation error on arm64

On 4/4/2019 1:42 PM, Jan Kotas wrote: On arm64 the cadence_master.c file doesn't compile. readl and writel are undefined. This patch fixes that by including io.h. Signed-off-by: Jan Kotas Reviewed-by: Mukesh Ojha Cheers, -Mukesh --- drivers/soundwire/cadence_master.c | 1 + 1 file

[PATCH 4.9 53/91] ACPI / video: Refactor and fix dmi_is_desktop()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cecf3e3e0803462335e25d083345682518097334 ] This commit refactors the chassis-type detection introduced by commit 53fa1f6e8a59 ("ACPI / video: Only default only_lcd to true on

[PATCH 4.9 52/91] iwlwifi: pcie: fix emergency path

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c6ac9f9fb98851f47b978a9476594fc3c477a34d ] Allocator swaps the pending requests with 0 when it starts working. This means that relying on it n RX path to decide if to move to

[PATCH 4.9 56/91] ALSA: PCM: check if ops are defined before suspending PCM

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d9c0b2afe820fa3b3f8258a659daee2cc71ca3ef ] BE dai links only have internal PCM's and their substream ops may not be set. Suspending these PCM's will result in their ops->trigger()

[PATCH 4.9 49/91] vfs: fix preadv64v2 and pwritev64v2 compat syscalls with offset == -1

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cc4b1242d7e3b42eed73881fc749944146493e4f ] The preadv2 and pwritev2 syscalls are supposed to emulate the readv and writev syscalls when offset == -1. Therefore the compat code should

[PATCH 4.9 81/91] netfilter: physdev: relax br_netfilter dependency

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8e2f311a68494a6677c1724bdcb10bada21af37c ] Following command: iptables -D FORWARD -m physdev ... causes connectivity loss in some setups. Reason is that iptables userspace will

[PATCH 4.9 80/91] dmaengine: qcom_hidma: assign channel cookie correctly

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 546c0547555efca8ba8c120716c325435e29df1b ] When dma_cookie_complete() is called in hidma_process_completed(), dma_cookie_status() will return DMA_COMPLETE in hidma_tx_status(). Then,

[PATCH 4.9 89/91] dmaengine: tegra: avoid overflow of byte tracking

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e486df39305864604b7e25f2a95d51039517ac57 ] The dma_desc->bytes_transferred counter tracks the number of bytes moved by the DMA channel. This is then used to calculate the information

[PATCH 4.9 88/91] x86/build: Mark per-CPU symbols as absolute explicitly for LLD

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d071ae09a4a1414c1433d5ae9908959a7325b0ad ] Accessing per-CPU variables is done by finding the offset of the variable in the per-CPU block and adding it to the address of the

[PATCH 4.9 71/91] ARM: avoid Cortex-A9 livelock on tight dmb loops

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5388a5b82199facacd3d7ac0d05aca6e8f902fed ] machine_crash_nonpanic_core() does this: while (1) cpu_relax(); because the kernel has crashed, and we have no

[PATCH 4.9 83/91] regulator: act8865: Fix act8600_sudcdc_voltage_ranges setting

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f01a7beb6791f1c419424c1a6958b7d0a289c974 ] The act8600_sudcdc_voltage_ranges setting does not match the datasheet. The problems in below entry: REGULATOR_LINEAR_RANGE(1900,

[PATCH 4.9 85/91] x86/build: Specify elf_i386 linker emulation explicitly for i386 objects

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 927185c124d62a9a4d35878d7f6d432a166b74e3 ] The kernel uses the OUTPUT_FORMAT linker script command in it's linker scripts. Most of the time, the -m option is passed to the linker

[PATCH 4.9 76/91] soc/tegra: fuse: Fix illegal free of IO base address

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 51294bf6b9e897d595466dcda5a3f2751906a200 ] On cases where device tree entries for fuse and clock provider are in different order, fuse driver needs to defer probing. This leads to

[PATCH 4.9 72/91] tty: increase the default flip buffer limit to 2*640K

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7ab57b76ebf632bf2231ccabe26bea33868118c6 ] We increase the default limit for buffer memory allocation by a factor of 10 to 640K to prevent data loss when using fast serial

Re: [PATCH v3 02/20] coresight: etm4x: Add kernel configuration for CONTEXTID

On 04/04/2019 04:35, Mathieu Poirier wrote: Set the proper bit in the configuration register when contextID tracing has been requested by user space. That way PE_CONTEXT elements are generated by the tracers when a process is installed on a CPU. Signed-off-by: Mathieu Poirier

[PATCH 4.9 84/91] drm/nouveau: Stop using drm_crtc_force_disable

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 934c5b32a5e43d8de2ab4f1566f91d7c3bf8cb64 ] The correct way for legacy drivers to update properties that need to do a full modeset, is to do a full modeset. Note that we don't need

[PATCH 4.14 001/121] arm64: debug: Dont propagate UNKNOWN FAR into si_code for debug signals

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit b9a4b9d084d978f80eb9210727c81804588b42ff upstream. FAR_EL1 is UNKNOWN for all debug exceptions other than those caused by taking a hardware watchpoint. Unfortunately, if a

[PATCH 4.14 022/121] mm, mempolicy: fix uninit memory access

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2e25644e8da4ed3a27e7b8315aaae74660be72dc ] Syzbot with KMSAN reports (excerpt): == BUG: KMSAN: uninit-value in

[PATCH 4.14 020/121] mm/cma.c: cma_declare_contiguous: correct err handling

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0d3bd18a5efd66097ef58622b898d3139790aa9d ] In case cma_init_reserved_mem failed, need to free the memblock allocated by memblock_reserve or memblock_alloc_range. Quote Catalin's

[PATCH 4.14 017/121] scsi: hisi_sas: Set PHY linkrate when disconnected

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit efdcad62e7b8a02f5ccca57806dce1482ac8 ] When the PHY comes down, we currently do not set the negotiated linkrate: root@(none)$ pwd /sys/class/sas_phy/phy-0:0 root@(none)$ more

[PATCH 4.14 015/121] sysctl: handle overflow for file-max

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 32a5ad9c22852e6bd9e74bdec5934ef9d1480bc5 ] Currently, when writing echo 18446744073709551616 > /proc/sys/fs/file-max /proc/sys/fs/file-max will overflow and be set to 0. That

[PATCH 4.14 005/121] tty/serial: atmel: RS485 HD w/DMA: enable RX after TX is stopped

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Razvan Stefanescu commit 69646d7a3689fbe1a65ae90397d22ac3f1b8d40f upstream. In half-duplex operation, RX should be started after TX completes. If DMA is used, there is a case when the DMA

[PATCH 4.14 019/121] perf c2c: Fix c2c report for empty numa node

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e34c940245437f36d2c492edd1f8237eff391064 ] Ravi Bangoria reported that we fail with an empty NUMA node with the following message: $ lscpu NUMA node0 CPU(s): NUMA node1

[PATCH 4.14 009/121] f2fs: fix to avoid deadlock in f2fs_read_inline_dir()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aadcef64b22f668c1a107b86d3521d9cac915c24 ] As Jiqun Li reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=202883 sometimes, dead lock when make system call

[PATCH 4.14 012/121] net/mlx5: Avoid panic when setting vport mac, getting vport config

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6e77c413e8e73d0f36b5358b601389d75ec4451c ] If we try to set VFs mac address on a VF (not PF) net device, the kernel will be crash. The commands are show as below: $ echo 2 >

[PATCH 4.14 033/121] jbd2: fix invalid descriptor block checksum

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6e876c3dd205d30b0db6850e97a03d75457df007 ] In jbd2_journal_commit_transaction(), if we are in abort mode, we may flush the buffer without setting descriptor block checksum by goto

[PATCH 4.14 011/121] net/mlx5: Avoid panic when setting vport rate

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 24319258660a84dd77f4be026a55b10a12524919 ] If we try to set VFs rate on a VF (not PF) net device, the kernel will be crash. The commands are show as below: $ echo 2 >

[PATCH 4.14 013/121] gpio: gpio-omap: fix level interrupt idling

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d01849f7deba81f4959fd9e51bf20dbf46987d1c ] Tony notes that the GPIO module does not idle when level interrupts are in use, as the wakeup appears to get stuck. After extensive

[PATCH 4.14 037/121] wil6210: check null pointer in _wil_cfg80211_merge_extra_ies

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit de77a53c2d1e8fb3621e63e8e1f0f0c9a1a99ff7 ] ies1 or ies2 might be null when code inside _wil_cfg80211_merge_extra_ies access them. Add explicit check for null and make sure ies1/ies2

Re: [PATCH v4] arm/mach-at91/pm : fix possible object reference leak

On Tue, Apr 02, 2019 at 10:12:38PM +0800, Peng Hao wrote: > > of_find_device_by_node() takes a reference to the struct device > when it finds a match via get_device. When returning error we should > call put_device. > > Reviewed-by: Mukesh Ojha > Signed-off-by: Peng Hao Thanks applied to

[PATCH 4.14 025/121] ocfs2: fix a panic problem caused by o2cb_ctl

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cc725ef3cb202ef2019a3c67c8913efa05c3cce6 ] In the process of creating a node, it will cause NULL pointer dereference in kernel if o2cb_ctl failed in the interval (mkdir,

Re: [PATCH][next] HID: intel-ish-hid: fix spelling mistake "multipe" -> "multiple"

On 4/4/2019 1:28 PM, Colin King wrote: From: Colin Ian King There is a spelling mistake in a dev_err message, fix it. Signed-off-by: Colin Ian King Reviewed-by: Mukesh Ojha Cheers, -Mukesh --- drivers/hid/intel-ish-hid/ishtp-fw-loader.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 4.14 051/121] IB/mlx4: Increase the timeout for CM cache

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2612d723aadcf8281f9bf8305657129bd9f3cd57 ] Using CX-3 virtual functions, either from a bare-metal machine or pass-through from a VM, MAD packets are proxied through the PF driver.

[PATCH 4.14 027/121] fs/file.c: initialize init_files.resize_wait

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5704a06810682683355624923547b41540e2801a ] (Taken from https://bugzilla.kernel.org/show_bug.cgi?id=200647) 'get_unused_fd_flags' in kthread cause kernel crash. It works fine on

[PATCH 4.14 030/121] dm thin: add sanity checks to thin-pool and external snapshot creation

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 70de2cbda8a5d788284469e755f8b097d339c240 ] Invoking dm_get_device() twice on the same device path with different modes is dangerous. Because in that case, upgrade_mode() will alloc

[PATCH 4.14 054/121] efi: cper: Fix possible out-of-bounds access

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 45b14a4ffcc1e0b5caa246638f942cbe7eaea7ad ] When checking a generic status block, we iterate over all the generic data blocks. The loop condition only checks that the start of the

[PATCH 4.14 044/121] serial: 8250_pxa: honor the port number from devicetree

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fe9ed6d2483fda55465f32924fb15bce0fac3fac ] Like the other OF-enabled drivers, use the port number from the firmware if the devicetree specifies an alias: aliases { ...

[PATCH 4.14 048/121] mmc: omap: fix the maximum timeout setting

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a6327b5e57fdc679c842588c3be046c0b39cc127 ] When running OMAP1 kernel on QEMU, MMC access is annoyingly noisy: MMC: CTO of 0xff and 0xfe cannot be used! MMC: CTO of

[PATCH 4.14 056/121] scsi: fcoe: make use of fip_mode enum complete

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8beb90aaf334a6efa3e924339926b5f93a234dbb ] commit 1917d42d14b7 ("fcoe: use enum for fip_mode") introduces a separate enum for the fip_mode that shall be used during initialisation

[PATCH 4.14 057/121] perf test: Fix failure of evsel-tp-sched test on s390

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 03d309711d687460d1345de8a0363f45b1c8cd11 ] Commit 489338a717a0 ("perf tests evsel-tp-sched: Fix bitwise operator") causes test case 14 "Parse sched tracepoints fields" to fail on

[PATCH 4.14 055/121] scsi: megaraid_sas: return error when create DMA pool failed

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bcf3b67d16a4c8ffae0aa79de5853435e683945c ] when create DMA pool for cmd frames failed, we should return -ENOMEM, instead of 0. In some case in: megasas_init_adapter_fusion()

[PATCH 4.14 070/121] kprobes: Prohibit probing on bsearch()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 02106f883cd745523f7766d90a739f983f19e650 ] Since kprobe breakpoing handler is using bsearch(), probing on this routine can cause recursive breakpoint problem. int3 ->do_int3()

[PATCH 4.14 063/121] media: mtk-jpeg: Correct return type for mem2mem buffer helpers

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1b275e4e8b70dbff9850874b30831c1bd8d3c504 ] Fix the assigned type of mem2mem buffer handling API. Namely, these functions: v4l2_m2m_next_buf v4l2_m2m_last_buf v4l2_m2m_buf_remove

[PATCH 4.14 069/121] ACPI / video: Refactor and fix dmi_is_desktop()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cecf3e3e0803462335e25d083345682518097334 ] This commit refactors the chassis-type detection introduced by commit 53fa1f6e8a59 ("ACPI / video: Only default only_lcd to true on

[PATCH 4.14 041/121] scsi: core: replace GFP_ATOMIC with GFP_KERNEL in scsi_scan.c

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1749ef00f7312679f76d5e9104c5d1e22a829038 ] We had a test-report where, under memory pressure, adding LUNs to the systems would fail (the tests add LUNs strictly in sequence): [

[PATCH 4.14 072/121] ARM: 8833/1: Ensure that NEON code always compiles with Clang

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit de9c0d49d85dc563549972edc5589d195cd5e859 ] While building arm32 allyesconfig, I ran into the following errors: arch/arm/lib/xor-neon.c:17:2: error: You should compile this file

[PATCH 4.14 061/121] media: s5p-g2d: Correct return type for mem2mem buffer helpers

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 30fa627b32230737bc3f678067e2adfecf956987 ] Fix the assigned type of mem2mem buffer handling API. Namely, these functions: v4l2_m2m_next_buf v4l2_m2m_last_buf v4l2_m2m_buf_remove

[PATCH 4.14 092/121] ARM: 8830/1: NOMMU: Toggle only bits in EXC_RETURN we are really care of

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 72cd4064fccaae15ab84d40d4be23667402df4ed ] ARMv8M introduces support for Security extension to M class, among other things it affects exception handling, especially, encoding of

[PATCH 4.14 088/121] ARM: dts: lpc32xx: Remove leading 0x and 0s from bindings notation

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3e3380d0675d5e20b0af067d60cb947a4348bf9b ] Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node

[PATCH 4.14 059/121] media: sh_veu: Correct return type for mem2mem buffer helpers

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 43c145195c7fc3025ee7ecfc67112ac1c82af7c2 ] Fix the assigned type of mem2mem buffer handling API. Namely, these functions: v4l2_m2m_next_buf v4l2_m2m_last_buf v4l2_m2m_buf_remove

[PATCH 4.14 066/121] jbd2: fix race when writing superblock

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 538bcaa6261b77e71d37f5596c33127c1a3ec3f7 ] The jbd2 superblock is lockless now, so there is probably a race condition between writing it so disk and modifing contents of it, which

[PATCH 4.14 090/121] soc: qcom: gsbi: Fix error handling in gsbi_probe()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8cd09a3dd3e176c62da67efcd477a44a8d87185e ] If of_platform_populate() fails in gsbi_probe(), gsbi->hclk is left undisabled. Found by Linux Driver Verification project

[PATCH 4.14 091/121] mt7601u: bump supported EEPROM version

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3bd1505fed71d834f45e87b32ff07157fdda47e0 ] As reported by Michael eeprom 0d is supported and work with the driver. Dump of /sys/kernel/debug/ieee80211/phy1/mt7601u/eeprom_param

[PATCH 4.14 079/121] genirq: Avoid summation loops for /proc/stat

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1136b0728969901a091f0471968b2b76ed14d9ad ] Waiman reported that on large systems with a large amount of interrupts the readout of /proc/stat takes a long time to sum up the

[PATCH 4.14 094/121] bpf: fix missing prototype warnings

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 116bfa96a255123ed209da6544f74a4f2eaca5da ] Compiling with W=1 generates warnings: CC kernel/bpf/core.o kernel/bpf/core.c:721:12: warning: no previous prototype for

[PATCH v2 3/3] usb: musb: jz4740: obtain USB PHY from devicetree

Fall back to devm_usb_get_phy() if devicetree is not available. Signed-off-by: Paul Cercueil --- Notes: v2: Change "usb-phy" DT property to "phys" drivers/usb/musb/jz4740.c | 17 +++-- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/drivers/usb/musb/jz4740.c

[RFC 1/2] mm/vmemmap: Enable vmem_altmap based base page mapping for vmemmap

vmemmap_populate_basepages() is used for vmemmap mapping across platforms. On arm64 it is used for ARM64_16K_PAGES and ARM64_64K_PAGES configs. When applicable enable it's allocation from device memory range through struct vmem_altpamp. Individual archs should enable this when appropriate. Hence

Re: [PATCH 6/6] arm64/mm: Enable ZONE_DEVICE

On 04/04/2019 06:04, Dan Williams wrote: On Wed, Apr 3, 2019 at 9:42 PM Anshuman Khandual wrote: On 04/03/2019 07:28 PM, Robin Murphy wrote: [ +Dan, Jerome ] On 03/04/2019 05:30, Anshuman Khandual wrote: Arch implementation for functions which create or destroy vmemmap mapping

[RFC 2/2] arm64/mm: Enable ZONE_DEVICE for all page configs

Now that vmemmap_populate_basepages() supports struct vmem_altmap based allocations, ZONE_DEVICE can be functional across all page size configs. Now vmemmap_populate_baepages() takes in actual struct vmem_altmap for allocation and remove_pagetable() should accommodate such new PTE level vmemmap

[PATCH 4.14 105/121] cpu/hotplug: Mute hotplug lockdep during init

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ce48c457b95316b9a01b5aa9d4456ce820df94b4 ] Since we've had: commit cb538267ea1e ("jump_label/lockdep: Assert we hold the hotplug lock for _cpuslocked() operations") we've been

[PATCH 4.14 084/121] platform/x86: intel_pmc_core: Fix PCH IP sts reading

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0e68eeea9894feeba2edf7ec63e4551b87f39621 ] A previous commit "platform/x86: intel_pmc_core: Make the driver PCH family agnostic " provided better abstraction to this driver but has

[PATCH 4.14 096/121] backlight: pwm_bl: Use gpiod_get_value_cansleep() to get initial state

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cec2b18832e26bc866bef2be22eff4e25bbc4034 ] gpiod_get_value() gives out a warning if access to the underlying gpiochip requires sleeping, which is common for I2C based chips:

[PATCH 4.14 081/121] fbdev: fbmem: fix memory access if logo is bigger than the screen

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a5399db139cb3ad9b8502d8b1bd02da9ce0b9df0 ] There is no clipping on the x or y axis for logos larger that the framebuffer size. Therefore: a logo bigger than screen size leads to

[PATCH 4.14 111/121] regulator: act8865: Fix act8600_sudcdc_voltage_ranges setting

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f01a7beb6791f1c419424c1a6958b7d0a289c974 ] The act8600_sudcdc_voltage_ranges setting does not match the datasheet. The problems in below entry: REGULATOR_LINEAR_RANGE(1900,

[PATCH 4.14 076/121] bcache: fix input overflow to cache set sysfs file io_error_halflife

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a91fbda49f746119828f7e8ad0f0aa2ab0578f65 ] Cache set sysfs entry io_error_halflife is used to set c->error_decay. c->error_decay is in type unsigned int, and it is converted by

[PATCH 4.14 083/121] e1000e: fix cyclic resets at link up with active tx

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0f9e980bf5ee1a97e2e401c846b2af989eb21c61 ] I'm seeing series of e1000e resets (sometimes endless) at system boot if something generates tx traffic at this time. In my case this is

[PATCH 4.14 108/121] dmaengine: qcom_hidma: initialize tx flags in hidma_prep_dma_*

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 875aac8a46424e5b73a9ff7f40b83311b609e407 ] In async_tx_test_ack(), it uses flags in struct dma_async_tx_descriptor to check the ACK status. As hidma reuses the descriptor in a free

[PATCH 4.14 102/121] soc/tegra: fuse: Fix illegal free of IO base address

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 51294bf6b9e897d595466dcda5a3f2751906a200 ] On cases where device tree entries for fuse and clock provider are in different order, fuse driver needs to defer probing. This leads to

[PATCH 4.14 101/121] hwrng: virtio - Avoid repeated init of completion

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aef027db48da56b6f25d0e54c07c8401ada6ce21 ] The virtio-rng driver uses a completion called have_data to wait for a virtio read to be fulfilled by the hypervisor. The completion is

[PATCH 4.14 106/121] dmaengine: imx-dma: fix warning comparison of distinct pointer types

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9227ab5643cb8350449502dd9e3168a873ab0e3b ] The warning got introduced by commit 930507c18304 ("arm64: add basic Kconfig symbols for i.MX8"). Since it got enabled for arm64. The

[PATCH 4.14 103/121] HID: intel-ish: ipc: handle PIMR before ish_wakeup also clear PISR busy_clear bit

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2edefc056e4f0e6ec9508dd1aca2c18fa320efef ] Host driver should handle interrupt mask register earlier than wake up ish FW else there will be conditions when FW interrupt comes, host

[PATCH 4.14 095/121] cgroup/pids: turn cgroup_subsys->free() into cgroup_subsys->release() to fix the accounting

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 51bee5abeab2058ea5813c5615d6197a23dbf041 ] The only user of cgroup_subsys->free() callback is pids_cgrp_subsys which needs pids_free() to uncharge the pid. However, ->free() is

Re: [PATCH 0/8] v4.19.0 Added Color Management Module

Hi Kalakodima, Thank you for the patch. On Wed, Apr 03, 2019 at 06:44:36PM +0530, venkatarajesh.kalakod...@in.bosch.com wrote: > From: kalakodima venkata rajesh > > This patchset adds rcar- display unit color management module (CMM) > function feature, Which allows correction and adjustment

Re: [PATCH] serial: sh-sci: Fix HSCIF RX sampling point calculation

Hi Geert, On Mon, Apr 01, 2019 at 01:25:10PM +0200, Geert Uytterhoeven wrote: > There are several issues with the formula used for calculating the > deviation from the intended rate: > 1. While min_err and last_stop are signed, srr and baud are unsigned. > Hence the signed values are

[PATCH 4.14 115/121] selinux: do not override context on context mounts

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 53e0c2aa9a59a48e3798ef193d573ade85aa80f5 ] Ignore all selinux_inode_notifysecctx() calls on mounts with SBLABEL_MNT flag unset. This is achived by returning -EOPNOTSUPP for this

[PATCH 4.19 011/187] net/mlx5: Avoid panic when setting vport mac, getting vport config

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6e77c413e8e73d0f36b5358b601389d75ec4451c ] If we try to set VFs mac address on a VF (not PF) net device, the kernel will be crash. The commands are show as below: $ echo 2 >

[PATCH 4.14 113/121] drm/nouveau: Stop using drm_crtc_force_disable

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 934c5b32a5e43d8de2ab4f1566f91d7c3bf8cb64 ] The correct way for legacy drivers to update properties that need to do a full modeset, is to do a full modeset. Note that we don't need

[PATCH 4.19 013/187] include/linux/relay.h: fix percpu annotation in struct rchan

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 62461ac2e5b6520b6d65fc6d7d7b4b8df4b848d8 ] The percpu member of this structure is declared as: struct ... ** __percpu member; So its type is: __percpu pointer to

[PATCH 4.14 114/121] x86/build: Specify elf_i386 linker emulation explicitly for i386 objects

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 927185c124d62a9a4d35878d7f6d432a166b74e3 ] The kernel uses the OUTPUT_FORMAT linker script command in it's linker scripts. Most of the time, the -m option is passed to the linker

[PATCH 4.19 017/187] libbpf: force fixdep compilation at the start of the build

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8e2688876c7f7073d925e1f150e86b8ed3338f52 ] libbpf targets don't explicitly depend on fixdep target, so when we do 'make -j$(nproc)', there is a high probability, that some objects

[PATCH 4.14 120/121] drm/dp/mst: Configure no_stop_bit correctly for remote i2c xfers

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c978ae9bde582e82a04c63a4071701691dd8b35c ] We aren't supposed to force a stop+start between every i2c msg when performing multi message transfers. This should eg. cause the DDC

Re: [PATCH v1] mfd: Add support for Merrifield Basin Cove PMIC

On Thu, 04 Apr 2019, Andy Shevchenko wrote: > On Thu, Apr 04, 2019 at 10:03:14AM +0100, Lee Jones wrote: > > On Thu, 04 Apr 2019, Andy Shevchenko wrote: > > > On Thu, Apr 04, 2019 at 08:03:57AM +0100, Lee Jones wrote: > > > > On Thu, 04 Apr 2019, Lee Jones wrote: > > > > > On Tue, 02 Apr 2019,

[PATCH 4.14 119/121] dmaengine: tegra: avoid overflow of byte tracking

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e486df39305864604b7e25f2a95d51039517ac57 ] The dma_desc->bytes_transferred counter tracks the number of bytes moved by the DMA channel. This is then used to calculate the

[PATCH 4.19 003/187] tty/serial: atmel: Add is_half_duplex helper

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Razvan Stefanescu commit f3040983132bf3477acd45d2452a906e67c2fec9 upstream. Use a helper function to check that a port needs to use half duplex communication, replacing several occurrences of

[PATCH 4.19 007/187] f2fs: fix to adapt small inline xattr space in __find_inline_xattr()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2c28aba8b2e2a51749fa66e01b68e1cd5b53e022 ] With below testcase, we will fail to find existed xattr entry: 1. mkfs.f2fs -O extra_attr -O flexible_inline_xattr /dev/zram0 2. mount -t

[PATCH 4.19 031/187] mm/slab.c: kmemleak no scan alien caches

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 92d1d07daad65c300c7d0b68bbef8867e9895d54 ] Kmemleak throws endless warnings during boot due to in __alloc_alien_cache(), alc = kmalloc_node(memsize, gfp, node);

[PATCH 4.19 020/187] iio: adc: fix warning in Qualcomm PM8xxx HK/XOADC driver

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e0f0ae838a25464179d37f355d763f9ec139fc15 ] The pm8xxx_get_channel() implementation is unclear, and causes gcc to suddenly generate odd warnings. The trigger for the warning (at

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