[PATCH 4.19 062/149] ARM: OMAP: dts: N950/N9: fix onenand timings

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8443e4843e1c2594bf5664e1d993a1be71d1befb ] Commit a758f50f10cf ("mtd: onenand: omap2: Configure driver from DT") started using DT specified timings for GPMC, and as a result the

[PATCH 4.19 086/149] drm/radeon: check if device is root before getting pci speed caps

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit afeff4c16edaa6275b903f82b0561406259aa3a3 ] Check if the device is root rather before attempting to see what speeds the pcie port supports. Fixes a crash with pci passthrough in a

[PATCH 4.19 006/149] perf script: Fix crash when processing recorded stat data

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8bf8c6da53c2265aea365a1de6038f118f522113 ] While updating perf to work with Python3 and Python2 I noticed that the stat-cpi script was dumping core. $ perf stat -e

[PATCH 4.19 007/149] IB/{hfi1, qib}: Fix WC.byte_len calculation for UD_SEND_WITH_IMM

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 904bba211acc2112fdf866e5a2bc6cd9ecd0de1b ] The work completion length for a receiving a UD send with immediate is short by 4 bytes causing application using this opcode to fail.

[PATCH 4.19 089/149] net: stmmac: Send TSO packets always from Queue 0

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c5acdbee22a1b200dde07effd26fd1f649e9ab8a ] The number of TSO enabled channels in HW can be different than the number of total channels. There is no way to determined, at runtime,

[GIT PULL] Ceph updates for 5.1-rc1

Hi Linus, The following changes since commit 1c163f4c7b3f621efff9b28a47abb36f7378d783: Linux 5.0 (2019-03-03 15:21:29 -0800) are available in the Git repository at: https://github.com/ceph/ceph-client.git tags/ceph-for-5.1-rc1 for you to fetch changes up to

[PATCH 4.19 088/149] net: stmmac: Fallback to Platform Data clock in Watchdog conversion

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4ec5302fa906ec9d86597b236f62315bacdb9622 ] If we don't have DT then stmmac_clk will not be available. Let's add a new Platform Data field so that we can specify the refclk by this

[PATCH 4.19 012/149] iommu/amd: Fix IOMMU page flush when detach device from a domain

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9825bd94e3a2baae1f4874767ae3a7d4c049720e ] When a VM is terminated, the VFIO driver detaches all pass-through devices from VFIO domain by clearing domain id and page table root

[PATCH 4.19 090/149] net: stmmac: Disable EEE mode earlier in XMIT callback

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e2cd682deb231ba6f80524bb84e57e7138261149 ] In stmmac xmit callback we use a different flow for TSO packets but TSO xmit callback is not disabling the EEE mode. Fix this by

[PATCH 4.19 087/149] drm/amdgpu: Transfer fences to dmabuf importer

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6e11ea9de9576a644045ffdc2067c09bc2012eda ] amdgpu only uses shared-fences internally, but dmabuf importers rely on implicit write hazard tracking via the

[PATCH 4.19 077/149] ARM: pxa: ssp: unneeded to free devm_ allocated data

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ba16adeb346387eb2d1ada69003588be96f098fa ] devm_ allocated data will be automatically freed. The free of devm_ allocated data is invalid. Fixes: 1c459de1e645 ("ARM: pxa: ssp: use

[PATCH 4.19 093/149] bpf, selftests: fix handling of sparse CPU allocations

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1bb54c4071f585ebef56ce8fdfe6026fa2cbcddd ] Previously, bpf_num_possible_cpus() had a bug when calculating a number of possible CPUs in the case of sparse CPU allocations, as it was

[PATCH 4.19 094/149] bpf: fix lockdep false positive in percpu_freelist

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a89fac57b5d080771efd4d71feaae19877cf68f0 ] Lockdep warns about false positive: [ 12.492084] e6b28347 (>lock){+...}, at: pcpu_freelist_push+0x2a/0x40 [ 12.492696] but

[PATCH 4.19 091/149] irqchip/gic-v3-its: Fix ITT_entry_size accessor

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 56841070ccc87b463ac037d2d1f2beb8e5e35f0c ] According to ARM IHI 0069C (ID070116), we should use GITS_TYPER's bits [7:4] as ITT_entry_size instead of [8:4]. Although this is pretty

[PATCH 4.19 000/149] 4.19.29-stable review

This is the start of the stable review cycle for the 4.19.29 release. There are 149 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Thu Mar 14 17:02:30 UTC 2019. Anything

[PATCH 4.19 096/149] bpf: Fix syscalls stackmap lookup potential deadlock

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7c4cd051add3d00bbff008a133c936c515eaa8fe ] The map_lookup_elem used to not acquiring spinlock in order to optimize the reader. It was true until commit 557c0c6e7df8 ("bpf: convert

[PATCH 4.19 080/149] DTS: CI20: Fix bugs in ci20s device tree.

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1ca1c87f91d9dc50d6a38e2177b2032996e7901c ] According to the Schematic, the hardware of ci20 leads to uart3, but not to uart2. Uart2 is miswritten in the original code.

[PATCH 4.19 017/149] IB/ipoib: Fix for use-after-free in ipoib_cm_tx_start

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6ab4aba00f811a5265acc4d3eb1863bb3ca60562 ] The following BUG was reported by kasan: BUG: KASAN: use-after-free in ipoib_cm_tx_start+0x430/0x1390 [ib_ipoib] Read of size 80 at

[PATCH 4.19 097/149] drm/sun4i: tcon: Prepare and enable TCON channel 0 clock at init

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b14e945bda8ae227d1bf2b1837c0c4a61721cd1a ] When initializing clocks, a reference to the TCON channel 0 clock is obtained. However, the clock is never prepared and enabled later.

[PATCH 4.19 078/149] arm64: dts: add msm8996 compatible to gicv3

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2a81efb0de0e33f2d2c83154af0bd3ce389b3269 ] Add compatible to gicv3 node to enable quirk required to restrict writing to GICR_WAKER register which is restricted on msm8996 SoC in

[PATCH 4.19 079/149] batman-adv: release station info tidstats

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7d652669b61d702c6e62a39579d17f6881670ab6 ] With the addition of TXQ stats in the per-tid statistics the struct station_info grew significantly. This resulted in stack size warnings

[PATCH 4.19 013/149] clk: ti: Fix error handling in ti_clk_parse_divider_data()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 303aef8b84272d73999a3207dd05bbe10ed89dc5 ] The ti_clk_parse_divider_data() function is only called from _get_div_table_from_setup(). That function doesn't look at the return value

[PATCH 4.19 109/149] perf trace: Support multiple "vfs_getname" probes

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6ab3bc240ade47a0f52bc16d97edd9accbe0024e ] With a suitably defined "probe:vfs_getname" probe, 'perf trace' can "beautify" its output, so syscalls like open() or openat() can print

[PATCH 4.19 034/149] nfs: Fix NULL pointer dereference of dev_name

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 80ff00172407e0aad4b10b94ef0816fc3e7813cb ] There is a NULL pointer dereference of dev_name in nfs_parse_devname() The oops looks something like: BUG: unable to handle kernel

[PATCH 4.19 053/149] proc: fix /proc/net/* after setns(2)

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1fde6f21d90f8ba5da3cb9c54ca991ed72696c43 ] /proc entries under /proc/net/* can't be cached into dcache because setns(2) can change current net namespace.

[PATCH 4.19 108/149] perf symbols: Filter out hidden symbols from labels

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 59a17706915fe5ea6f711e1f92d4fb706bce07fe ] When perf is built with the annobin plugin (RHEL8 build) extra symbols are added to its binary: # nm perf | grep annobin | head -10

[PATCH 4.19 112/149] Revert "scsi: libfc: Add WARN_ON() when deleting rports"

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d8f6382a7d026989029e2e50c515df954488459b ] This reverts commit bbc0f8bd88abefb0f27998f40a073634a3a2db89. It added a warning whose intent was to check whether the rport was still

Re: [PATCH] tpm: Make timeout logic simpler and more robust

On Tue, 2019-03-12 at 12:59 -0400, Mimi Zohar wrote: > On Tue, 2019-03-12 at 07:42 -0700, James Bottomley wrote: > > On Tue, 2019-03-12 at 14:50 +0200, Jarkko Sakkinen wrote: > > > On Mon, Mar 11, 2019 at 05:27:43PM -0700, James Bottomley wrote: > > > > On Mon, 2019-03-11 at 16:54 -0700, Calvin

[PATCH 4.19 113/149] i2c: omap: Use noirq system sleep pm ops to idle device for suspend

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c6e2bd956936d925748581e4d0294f10f1d92f2c ] We currently get the following error with pixcir_ts driver during a suspend resume cycle: omap_i2c 4802a000.i2c: controller timed out

[PATCH 4.19 115/149] nvme: lock NS list changes while handling command effects

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e7ad43c3eda6a1690c4c3c341f95dc1c6898da83 ] If a controller supports the NS Change Notification, the namespace scan_work is automatically triggered after attaching a new namespace.

Re: general protection fault in skb_put

On Mon, Mar 11, 2019 at 7:10 PM James Smart wrote: > > On 3/11/2019 9:40 AM, Dmitry Vyukov wrote: > > On Mon, Mar 11, 2019 at 5:20 PM 'James Smart' via syzkaller-bugs > > wrote: > >> > >> On 3/11/2019 6:20 AM, syzbot wrote: > >>> syzbot has bisected this bug to: > >>> > >>> commit

[PATCH 4.19 067/149] ARM: dts: meson8m2: mxiii-plus: mark the SD card detection GPIO active-low

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8615f5596335db0978cea593dcd0070dc5f8b116 ] After commit 89a5e15bcba87d ("gpio/mmc/of: Respect polarity in the device tree") SD cards are not detected anymore. The CD GPIO is

[PATCH 4.19 098/149] dmaengine: at_xdmac: Fix wrongfull report of a channel as in use

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit dc3f595b6617ebc0307e0ce151e8f2f2b2489b95 ] atchan->status variable is used to store two different information: - pass channel interrupts status from interrupt handler to tasklet;

[PATCH 4.19 100/149] vsock/virtio: reset connected sockets on device removal

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 85965487abc540368393a15491e6e7fcd230039d ] When the virtio transport device disappear, we should reset all connected sockets in order to inform the users. Signed-off-by: Stefano

[PATCH 4.19 104/149] netfilter: nf_nat: skip nat clash resolution for same-origin entries

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 ] It is possible that two concurrent packets originating from the same socket of a connection-less protocol (e.g. UDP) can end up having

[PATCH 4.19 064/149] ARM: dts: sun8i: h3: Add ethernet0 alias to Beelink X2

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cc4bddade114b696ab27c1a77cfc7040151306da ] Because "ethernet0" alias is missing, U-Boot doesn't generate board specific MAC address. Effect of this is random MAC address every boot

[PATCH 4.19 117/149] fs: ratelimit __find_get_block_slow() failure message.

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 43636c804df0126da669c261fc820fb22f62bfc2 ] When something let __find_get_block_slow() hit all_mapped path, it calls printk() for 100+ times per a second. But there is no need to

[PATCH 4.19 105/149] s390/qeth: release cmd buffer in error paths

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5065b2dd3e5f9247a6c9d67974bc0472bf561b9d ] Whenever we fail before/while starting an IO, make sure to release the IO buffer. Usually qeth_irq() would do this for us, but if the IO

[PATCH 4.19 132/149] ARM: dts: exynos: Add minimal clkout parameters to Exynos3250 PMU

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit a66352e005488ecb4b534ba1af58a9f671eba9b8 upstream. Add minimal parameters needed by the Exynos CLKOUT driver to Exynos3250 PMU node. This fixes the following warning

[PATCH 4.19 119/149] qed: Consider TX tcs while deriving the max num_queues for PF.

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fb1faab74ddef9ec2d841d54e5d0912a097b3abe ] Max supported queues is derived incorrectly in the case of multi-CoS. Need to consider TCs while calculating num_queues for PF.

[PATCH 4.19 055/149] mm, memory_hotplug: is_mem_section_removable do not pass the end of a zone

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit efad4e475c312456edb3c789d0996d12ed744c13 ] Patch series "mm, memory_hotplug: fix uninitialized pages fallouts", v2. Mikhail Zaslonko has posted fixes for the two bugs quite some

[PATCH 4.19 102/149] selftests: netfilter: fix config fragment CONFIG_NF_TABLES_INET

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 952b72f89ae23b316da8c1021b18d0c388ad6cc4 ] In selftests the config fragment for netfilter was added as NF_TABLES_INET=y and this patch correct it as CONFIG_NF_TABLES_INET=y

[PATCH 4.19 106/149] s390/qeth: fix use-after-free in error path

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit afa0c5904ba16d59b0454f7ee4c807dae350f432 ] The error path in qeth_alloc_qdio_buffers() that takes care of cleaning up the Output Queues is buggy. It first frees the queue, but then

[PATCH 4.19 137/149] gfs2: Fix missed wakeups in find_insert_glock

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Gruenbacher commit 605b0487f0bc1ae9963bf52ece0f5c8055186f81 upstream. Mark Syms has reported seeing tasks that are stuck waiting in find_insert_glock. It turns out that struct

Re: [PATCH 02/25] leds: core: Add support for composing LED class device names

On 3/12/19 12:28 PM, Jacek Anaszewski wrote: > Hi Dan, > > On 3/12/19 6:15 PM, Dan Murphy wrote: >> On 3/10/19 1:28 PM, Jacek Anaszewski wrote: >>> Add public led_compose_name() API for composing LED class device >>> name basing on fwnode_handle data. The function composes device name >>>

[PATCH 4.19 133/149] ARM: dts: exynos: Fix max voltage for buck8 regulator on Odroid XU3/XU4

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit a3238924a820c1d7c977b632b769f3b5690cba09 upstream. The maximum voltage value for buck8 regulator on Odroid XU3/XU4 boards is set too low. Increase it to the 2000mV as

[PATCH 4.19 139/149] staging: erofs: fix fast symlink w/o xattr when fs xattr is on

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Gao Xiang commit 7077fffcb0b0b65dc75e341306aeef4d0e7f2ec6 upstream. Currently, this will hit a BUG_ON for these symlinks as follows: - kernel message [ cut here ]

[PATCH 4.19 134/149] drm: disable uncached DMA optimization for ARM and arm64

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e02f5c1bb2283cfcee68f2f0feddcc06150f13aa ] The DRM driver stack is designed to work with cache coherent devices only, but permits an optimization to be enabled in some cases, where

[PATCH 4.19 073/149] wlcore: sdio: Fixup power on/off sequence

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 13e62626c578d9889ebbda7c521be5adff9bef8e ] During "wlan-up", we are programming the FW into the WiFi-chip. However, re-programming the FW doesn't work, unless a power cycle of the

[PATCH 4.19 138/149] staging: erofs: add error handling for xattr submodule

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Gao Xiang commit cadf1ccf1b0021d0b7a9347e102ac5258f9f98c8 upstream. This patch enhances the missing error handling code for xattr submodule, which improves the stability for the rare cases.

[PATCH 4.19 142/149] staging: erofs: keep corrupted fs from crashing kernel in erofs_namei()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Gao Xiang commit 419d6efc50e94bcf5d6b35cd8c71f79edadec564 upstream. As Al pointed out, " ... and while we are at it, what happens to unsigned int nameoff =

[PATCH 4.19 141/149] staging: erofs: fix race of initializing xattrs of a inode at the same time

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Gao Xiang commit 62dc45979f3f8cb0ea67302a93bff686f0c46c5a upstream. In real scenario, there could be several threads accessing xattrs of the same xattr-uninitialized inode, and

[PATCH 4.19 063/149] ARM: dts: omap4-droid4: Fix typo in cpcap IRQ flags

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ef4a55b9197a8f844ea0663138e902dcce3e2f36 ] We're now getting the following error: genirq: Setting trigger mode 1 for irq 230 failed (regmap_irq_set_type+0x0/0x15c) cpcap-usb-phy

[PATCH 4.19 060/149] autofs: fix error return in autofs_fill_super()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f585b283e3f025754c45bbe7533fc6e5c4643700 ] In autofs_fill_super() on error of get inode/make root dentry the return should be ENOMEM as this is the only failure case of the called

[PATCH 4.19 054/149] x86_64: increase stack size for KASAN_EXTRA

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a8e911d13540487942d53137c156bd7707f66e5d ] If the kernel is configured with KASAN_EXTRA, the stack size is increasted significantly because this option sets "-fstack-reuse" to

[PATCH 4.19 129/149] arm64: dts: hikey: Give wifi some time after power-on

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kiszka commit 83b944174ad79825ae84a47af1a0354485b24602 upstream. Somewhere along recent changes to power control of the wl1835, power-on became very unreliable on the hikey, failing like

[PATCH 4.19 123/149] Input: wacom_serial4 - add support for Wacom ArtPad II tablet

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Jason Gerecke commit 44fc95e218a09d7966a9d448941fdb003f6bb69f upstream. Tablet initially begins communicating at 9600 baud, so this command should be used to connect to the device: $

[PATCH 4.19 125/149] iscsi_ibft: Fix missing break in switch statement

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit df997abeebadaa4824271009e2d2b526a70a11cb upstream. Add missing break statement in order to prevent the code from falling through to case ISCSI_BOOT_TGT_NAME, which

Re: [RFC] simple_lmk: Introduce Simple Low Memory Killer for Android

On Tue, Mar 12, 2019 at 10:17:43AM -0700, Tim Murray wrote: > Knowing whether a SIGKILL'd process has finished reclaiming is as far > as I know not possible without something like procfds. That's where > the 100ms timeout in lmkd comes in. lowmemorykiller and lmkd both > attempt to wait up to

[PATCH 4.19 146/149] perf/x86/intel: Make cpuc allocations consistent

4.19-stable review patch. If anyone has any objections, please let me know. -- From: "Peter Zijlstra (Intel)" commit d01b1f96a82e5dd7841a1d39db3abfdaf95f70ab upstream The cpuc data structure allocation is different between fake and real cpuc's; use the same code to init/free

[PATCH 4.19 121/149] blk-iolatency: fix IO hang due to negative inflight counter

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8c772a9bfc7c07c76f4a58b58910452fbb20843b ] Our test reported the following stack, and vmcore showed that ->inflight counter is -1. [c9003fcc38d0] __schedule at 8173d95d

[PATCH 4.19 128/149] arm64: dts: zcu100-revC: Give wifi some time after power-on

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kiszka commit 35a4f89cd4731ac6ec985cd29ddc1630903006b7 upstream. Somewhere along recent changes to power control of the wl1831, power-on became very unreliable on the Ultra96, failing

[PATCH 4.14 015/135] geneve: correctly handle ipv6.disable module parameter

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Benc [ Upstream commit cf1c9ccba7308e48a68fa77f476287d9d614e4c7 ] When IPv6 is compiled but disabled at runtime, geneve_sock_add returns -EAFNOSUPPORT. For metadata based tunnels, this

[PATCH 4.14 014/135] bnxt_en: Drop oversize TX packets to prevent errors.

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Chan [ Upstream commit 2b3c6885386020b1b9d92d45e8349637e27d1f66 ] There have been reports of oversize UDP packets being sent to the driver to be transmitted, causing error conditions.

[PATCH 4.19 092/149] relay: check return of create_buf_file() properly

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2c1cf00eeacb784781cf1c9896b8af001246d339 ] If create_buf_file() returns an error, don't try to reference it later as a valid dentry pointer. This problem was exposed when debugfs

[PATCH 4.19 148/149] x86: Add TSX Force Abort CPUID/MSR

4.19-stable review patch. If anyone has any objections, please let me know. -- From: "Peter Zijlstra (Intel)" commit 52f64909409c17adf54fcf5f9751e0544ca3a6b4 upstream Skylake systems will receive a microcode update to address a TSX errata. This microcode will (by default)

[PATCH 4.19 095/149] bpf: fix potential deadlock in bpf_prog_register

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e16ec34039c701594d55d08a5aa49ee3e1abc821 ] Lockdep found a potential deadlock between cpu_hotplug_lock, bpf_event_mutex, and cpuctx_mutex: [ 13.007000] WARNING: possible circular

[PATCH 4.19 076/149] bpf: sock recvbuff must be limited by rmem_max in bpf_setsockopt()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c9e4576743eeda8d24dedc164d65b78877f9a98c ] When sock recvbuff is set by bpf_setsockopt(), the value must by limited by rmem_max. It is the same with sendbuff. Fixes: 8c4b4c7e9ff0

[PATCH 4.14 016/135] hv_netvsc: Fix IP header checksum for coalesced packets

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Haiyang Zhang [ Upstream commit bf48648d650db1146b75b9bd358502431e86cf4f ] Incoming packets may have IP header checksum verified by the host. They may not have IP header checksum computed

[PATCH 4.19 081/149] usb: phy: fix link errors

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f2105d42597f4d10e431b195d69e96dccaf9b012 ] Fix link errors when CONFIG_FSL_USB2_OTG is enabled and USB_OTG_FSM is set to module then the following link error occurs.

[PATCH 4.14 000/135] 4.14.106-stable review

This is the start of the stable review cycle for the 4.14.106 release. There are 135 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Thu Mar 14 17:02:27 UTC 2019. Anything

[PATCH 4.14 017/135] net: dsa: mv88e6xxx: Fix u64 statistics

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andrew Lunn [ Upstream commit 6e46e2d821bb22b285ae8187959096b65d063b0d ] The switch maintains u64 counters for the number of octets sent and received. These are kept as two u32's which need

[PATCH 4.14 018/135] netlabel: fix out-of-bounds memory accesses

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paul Moore [ Upstream commit 5578de4834fe0f2a34fedc7374be691443396d1f ] There are two array out-of-bounds memory accesses, one in cipso_v4_map_lvl_valid(), the other in netlbl_bitmap_walk().

[PATCH 4.14 005/135] staging: comedi: ni_660x: fix missing break in switch statement

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 479826cc86118e0d87e5cefb3df5b748e0480924 upstream. Add missing break statement in order to prevent the code from falling through to the default case and return

[PATCH 4.14 007/135] staging: android: ion: fix sys heap pools gfp_flags

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Qing Xia commit 9bcf065e28122588a6cbee08cf847826dacbb438 upstream. In the first loop, gfp_flags will be modified to high_order_gfp_flags, and there will be no chance to change back to

Re: [PATCH RFC 00/39] x86/KVM: Xen HVM guest support

On 2/22/19 4:59 PM, Paolo Bonzini wrote: > On 21/02/19 12:45, Joao Martins wrote: >> On 2/20/19 9:09 PM, Paolo Bonzini wrote: >>> On 20/02/19 21:15, Joao Martins wrote: 2. PV Driver support (patches 17 - 39) We start by redirecting hypercalls from the backend to routines

[PATCH 4.14 004/135] USB: serial: ftdi_sio: add ID for Hjelmslund Electronics USB485

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mans Rullgard commit 8d7fa3d4ea3f0ca69554215e87411494e6346fdc upstream. This adds the USB ID of the Hjelmslund Electronics USB485 Iso stick. Signed-off-by: Mans Rullgard Cc: stable

[PATCH 4.19 084/149] irqchip/mmp: Only touch the PJ4 IRQ & FIQ bits on enable/disable

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2380a22b60ce6f995eac806e69c66e397b59d045 ] Resetting bit 4 disables the interrupt delivery to the "secure processor" core. This breaks the keyboard on a OLPC XO 1.75 laptop, where

[PATCH 4.19 083/149] irqchip/gic-v3-its: Gracefully fail on LPI exhaustion

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 45725e0fc3e7fe52fedb94f59806ec50e9618682 ] In the unlikely event that we cannot find any available LPI in the system, we should gracefully return an error instead of carrying on

[PATCH 4.14 002/135] USB: serial: option: add Telit ME910 ECM composition

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniele Palmas commit 6431866b6707d27151be381252d6eef13025cfce upstream. This patch adds Telit ME910 family ECM composition 0x1102. Signed-off-by: Daniele Palmas Cc: stable Signed-off-by:

[PATCH 4.14 030/135] mpls: Return error for RTA_GATEWAY attribute

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit be48220edd48ca0d569782992840488a52373a24 ] MPLS does not support nexthops with an MPLS address family. Specifically, it does not handle RTA_GATEWAY attribute.

[PATCH 4.14 010/135] net-sysfs: Fix mem leak in netdev_register_kobject

4.14-stable review patch. If anyone has any objections, please let me know. -- From: YueHaibing [ Upstream commit 895a5e96dbd6386c8e78e5b78e067dcc67b7f0ab ] syzkaller report this: BUG: memory leak unreferenced object 0x88837a71a500 (size 256): comm "syz-executor.2", pid

[PATCH 4.19 099/149] vsock/virtio: fix kernel panic after device hot-unplug

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 22b5c0b63f32568e130fa2df4ba23efce3eb495b ] virtio_vsock_remove() invokes the vsock_core_exit() also if there are opened sockets for the AF_VSOCK protocol family. In this way the

[PATCH 4.14 029/135] ipv6: Return error for RTA_VIA attribute

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit e3818541b49fb88650ba339d33cc53e4095da5b3 ] IPv6 currently does not support nexthops outside of the AF_INET6 family. Specifically, it does not handle RTA_VIA

[PATCH 4.19 110/149] MIPS: Loongson: Introduce and use loongson_llsc_mb()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e02e07e3127d8aec1f4bcdfb2fc52a2d99b4859e ] On the Loongson-2G/2H/3A/3B there is a hardware flaw that ll/sc and lld/scd is very weak ordering. We should add sync instructions "before

[PATCH 4.14 020/135] net: nfc: Fix NULL dereference on nfc_llcp_build_tlv fails

4.14-stable review patch. If anyone has any objections, please let me know. -- From: YueHaibing [ Upstream commit 58bdd544e2933a21a51eecf17c3f5f94038261b5 ] KASAN report this: BUG: KASAN: null-ptr-deref in nfc_llcp_build_gb+0x37f/0x540 [nfc] Read of size 3 at addr

[PATCH 4.14 034/135] net: dsa: mv88e6xxx: Fix statistics on mv88e6161

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andrew Lunn [ Upstream commit a6da21bb0eae459a375d5bd48baed821d14301d0 ] Despite what the datesheet says, the silicon implements the older way of snapshoting the statistics. Change the op.

[PATCH 4.14 022/135] net: sit: fix memory leak in sit_init_net()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mao Wenan [ Upstream commit 07f12b26e21ab359261bf75cfcb424fdc7daeb6d ] If register_netdev() is failed to register sitn->fb_tunnel_dev, it will go to err_reg_dev and forget to free

[PATCH 4.14 021/135] net: phy: phylink: fix uninitialized variable in phylink_get_mac_state

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit d25ed413d5e51644e18f66e34eec049f17a7abcb ] When debugging an issue I found implausible values in state->pause. Reason in that state->pause isn't initialized

[PATCH 4.19 114/149] drm/amdgpu: use spin_lock_irqsave to protect vm_manager.pasid_idr

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0a5f49cbf9d6ad3721c16f8a6d823363ea7a160f ] amdgpu_vm_get_task_info is called from interrupt handler and sched timeout workqueue, we should use irq version spin_lock to avoid

[PATCH 4.14 024/135] xen-netback: dont populate the hash cache on XenBus disconnect

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Igor Druzhinin [ Upstream commit a2288d4e355992d369c50c45d017a85f6061ff71 ] Occasionally, during the disconnection procedure on XenBus which includes hash cache deinitialization there might

Re: [RFC] simple_lmk: Introduce Simple Low Memory Killer for Android

On Tue, Mar 12, 2019 at 9:58 AM Michal Hocko wrote: > > On Tue 12-03-19 09:37:41, Sultan Alsawaf wrote: > > I have not had a chance to look at PSI yet, but > > unless a PSI-enabled solution allows allocations to reach the same point as > > when > > the OOM killer is invoked (which is

[PATCH 4.14 045/135] perf core: Fix perf_proc_update_handler() bug

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1a51c5da5acc6c188c917ba572eebac5f8793432 ] The perf_proc_update_handler() handles /proc/sys/kernel/perf_event_max_sample_rate syctl variable. When the PMU IRQ handler timing

[PATCH 4.19 116/149] nvme-pci: fix rapid add remove sequence

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5c959d73dba6495ec01d04c206ee679d61ccb2b0 ] A surprise removal may fail to tear down request queues if it is racing with the initial asynchronous probe. If that happens, the remove

[PATCH 4.19 118/149] qed: Fix EQ full firmware assert.

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 660492bcf4a7561b5fdc13be0ae0b0c0a8c120be ] When slowpath messages are sent with high rate, the resulting events can lead to a FW assert in case they are not handled fast enough

[PATCH 4.14 027/135] net: avoid use IPCB in cipso_v4_error

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nazarov Sergey [ Upstream commit 3da1ed7ac398f34fff1694017a07054d69c5f5c5 ] Extract IP options in cipso_v4_error and use __icmp_send. Signed-off-by: Sergey Nazarov Acked-by: Paul Moore

[PATCH 4.14 019/135] net: netem: fix skb length BUG_ON in __skb_to_sgvec

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sheng Lan [ Upstream commit 5845f706388a4cde0f6b80f9e5d33527e942b7d9 ] It can be reproduced by following steps: 1. virtio_net NIC is configured with gso/tso on 2. configure nginx as http

[PATCH 4.14 047/135] IB/{hfi1, qib}: Fix WC.byte_len calculation for UD_SEND_WITH_IMM

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 904bba211acc2112fdf866e5a2bc6cd9ecd0de1b ] The work completion length for a receiving a UD send with immediate is short by 4 bytes causing application using this opcode to fail.

[PATCH 4.14 046/135] perf tools: Handle TOPOLOGY headers with no CPU

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1497e804d1a6e2bd9107ddf64b0310449f4673eb ] This patch fixes an issue in cpumap.c when used with the TOPOLOGY header. In some configurations, some NUMA nodes may have no CPU (empty

[PATCH 4.14 048/135] iommu/amd: Call free_iova_fast with pfn in map_sg

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 51d8838d66d3249508940d8f59b07701f2129723 ] In the error path of map_sg, free_iova_fast is being called with address instead of the pfn. This results in a bad value getting into the

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