[PATCH 4.20 333/352] usb: gadget: udc: net2272: Fix bitwise and boolean operations

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 07c69f1148da7de3978686d3af9263325d9d60bd upstream. (!x & y) strikes again. Fix bitwise and boolean operations by enclosing the expression: intcsr & (1 <<

[PATCH 4.20 335/352] staging: speakup: fix tty-operation NULL derefs

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit a1960e0f1639cb1f7a3d94521760fc73091f6640 upstream. The send_xchar() and tiocmset() tty operations are optional. Add the missing sanity checks to prevent user-space

[PATCH 4.20 308/352] bnxt_en: Disable interrupts when allocating CP rings or NQs.

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Michael Chan [ Upstream commit 5e66e35aab335b83d9ffb220d8a3a13986a7a60e ] When calling firmware to allocate a CP ring or NQ, an interrupt associated with that ring may be generated

[PATCH 4.20 334/352] usb: gadget: musb: fix short isoc packets with inventra dma

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Paul Elder commit c418fd6c01fbc5516a2cd1eaf1df1ec86869028a upstream. Handling short packets (length < max packet size) in the Inventra DMA engine in the MUSB driver causes the MUSB DMA

[PATCH 4.20 311/352] net/mlx5e: Use the inner headers to determine tc/pedit offload limitation on decap flows

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Guy Shattah [ Upstream commit 1651925d403e077e3fc86f961905e27c6810e132 ] In packets that need to be decaped the internal headers have to be checked, not the external ones. Fixes:

[PATCH 4.20 309/352] net: cls_flower: Remove filter from mask before freeing it

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Petr Machata [ Upstream commit c1f7e02979edd7a3a3e69fe04be60b1d650dc8a7 ] In fl_change(), when adding a new rule (i.e. fold == NULL), a driver may reject the new rule, for example due to

[PATCH 4.20 310/352] net: dsa: b53: Fix for failure when irq is not defined in dt

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Arun Parameswaran [ Upstream commit 39841cc1cbb69344539c98a1fa9d858ed124c7ba ] Fixes the issues with non BCM58XX chips in the b53 driver failing, when the irq is not specified in the device

[PATCH 4.20 338/352] scsi: aic94xx: fix module loading

4.20-stable review patch. If anyone has any objections, please let me know. -- From: James Bottomley commit 42caa0edabd6a0a392ec36a5f0943924e4954311 upstream. The aic94xx driver is currently failing to load with errors like sysfs: cannot create duplicate filename

Re: [PATCH 1/2] Provide in-kernel headers for making it easy to extend the kernel

On Mon, Feb 11, 2019 at 10:39:43AM +0900, Masahiro Yamada wrote: > On Fri, Feb 8, 2019 at 6:13 AM Joel Fernandes (Google) > wrote: > > > > Introduce in-kernel headers and other artifacts which are made available > > as an archive through proc (/proc/kheaders.txz file). This archive makes > > it

[PATCH 4.20 340/352] kvm: fix kvm_ioctl_create_device() reference counting (CVE-2019-6974)

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit cfa39381173d5f969daf43582c95ad679189cbc9 upstream. kvm_ioctl_create_device() does the following: 1. creates a device that holds a reference to the VM object (with a borrowed

[PATCH 4.20 349/352] serial: 8250_pci: Make PCI class test non fatal

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit 824d17c57b0abbcb9128fb3f7327fae14761914b upstream. As has been reported the National Instruments serial cards have broken PCI class. The commit 7d8905d06405

[PATCH 4.20 351/352] cacheinfo: Keep the old value if of_property_read_u32 fails

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Huacai Chen commit 3a34c986324c07dde32903f7bb262e6138e77c2a upstream. Commit 448a5a552f336bd7b847b1951 ("drivers: base: cacheinfo: use OF property_read_u32 instead of

[PATCH 4.20 305/352] sctp: walk the list of asoc safely

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman [ Upstream commit ba59fb0273076637f0add4311faa990a5eec27c0 ] In sctp_sendmesg(), when walking the list of endpoint associations, the association can be dropped from the

[PATCH 4.20 342/352] cpu/hotplug: Fix "SMT disabled by BIOS" detection for KVM

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit b284909abad48b07d3071a9fc9b5692b3e64914b upstream. With the following commit: 73d5e2b47264 ("cpu/hotplug: detect SMT disabled by BIOS") ... the hotplug code

[PATCH 4.20 313/352] xfs: eof trim writeback mapping as soon as it is cached

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit aa6ee4ab69293969867ab09b57546d226ace3d7a upstream. The cached writeback mapping is EOF trimmed to try and avoid races between post-eof block management and writeback that

[PATCH 4.20 341/352] KVM: nVMX: unconditionally cancel preemption timer in free_nested (CVE-2019-7221)

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Peter Shier commit ecec76885bcfe3294685dc363fd1273df0d5d65f upstream. Bugzilla: 1671904 There are multiple code paths where an hrtimer may have been started to emulate an L1 VMX preemption

[PATCH 4.20 346/352] perf/core: Dont WARN() for impossible ring-buffer sizes

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Mark Rutland commit 9dff0aa95a324e262ffb03f425d00e4751f3294e upstream. The perf tool uses /proc/sys/kernel/perf_event_mlock_kb to determine how large its ringbuffer mmap should be. This can

[PATCH 4.20 347/352] perf tests evsel-tp-sched: Fix bitwise operator

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 489338a717a0dfbbd5a3fabccf172b78f0ac9015 upstream. Notice that the use of the bitwise OR operator '|' always leads to true in this particular case, which seems a

[PATCH 4.20 339/352] KVM: x86: work around leak of uninitialized stack contents (CVE-2019-7222)

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit 353c0956a618a07ba4bbe7ad00ff29fe70e8412a upstream. Bugzilla: 1671930 Emulation of certain instructions (VMXON, VMCLEAR, VMPTRLD, VMWRITE with memory operand, INVEPT,

[PATCH 4.20 348/352] serial: fix race between flush_to_ldisc and tty_open

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman commit fedb5760648a291e949f2380d383b5b2d2749b5e upstream. There still is a race window after the commit b027e2298bd588 ("tty: fix data race between tty_init_dev and flush

[PATCH 4.19 001/313] devres: Align data[] to ARCH_KMALLOC_MINALIGN

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Brodkin commit a66d972465d15b1d89281258805eb8b47d66bd36 upstream. Initially we bumped into problem with 32-bit aligned atomic64_t on ARC, see [1]. And then during quite lengthly

[PATCH 4.19 012/313] wil6210: fix reset flow for Talyn-mb

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d083b2e2b7db5cca1791643d036e6597af27f49b ] With current reset flow, Talyn sometimes get stuck causing PCIe enumeration to fail. Fix this by removing some reset flow operations that

[PATCH 4.19 011/313] nds32: Fix gcc 8.0 compiler option incompatible.

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4c3d6174e0e17599549f636ec48ddf78627a17fe ] When the kernel configs of ftrace and frame pointer options are choosed, the compiler option of kernel will incompatible. Error

[PATCH 4.19 013/313] wil6210: fix memory leak in wil_find_tx_bcast_2

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 664497400c89a4d40aee51bcf48bbd2e4dc71104 ] A successful call to wil_tx_ring takes skb reference so it will only be freed in wil_tx_complete. Consume the skb in wil_find_tx_bcast_2

[PATCH 4.19 010/313] gpu: ipu-v3: image-convert: Prevent race between run and unprepare

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 819bec35c8c9706185498c9222bd244e0781ad35 ] Prevent possible race by parallel threads between ipu_image_convert_run() and ipu_image_convert_unprepare(). This involves setting

[PATCH 4.19 021/313] dlm: Dont swamp the CPU with callbacks queued during recovery

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 216f0efd19b9cc32207934fd1b87a45f2c4c593e ] Before this patch, recovery would cause all callbacks to be delayed, put on a queue, and afterward they were all queued to the callback

[PATCH 4.19 015/313] ath9k: dynack: use authentication messages for late ack

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3831a2a0010c72e3956020cbf1057a1701a2e469 ] In order to properly support dynack in ad-hoc mode running wpa_supplicant, take into account authentication frames for 'late ack'

[PATCH 4.19 004/313] drm/vgem: Fix vgem_init to get drm device available.

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d5c04dff24870ef07ce6453a3f4e1ffd9cf88d27 ] Modify vgem_init to take platform dev as parent in drm_dev_init. This will make drm device available at "/sys/devices/platform/vgem" in

[PATCH 4.19 017/313] scsi: mpt3sas: Call sas_remove_host before removing the target devices

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit dc730212e8a378763cb182b889f90c8101331332 ] Call sas_remove_host() before removing the target devices in the driver's .remove() callback function(i.e. during driver unload time). So

[PATCH 4.19 018/313] scsi: lpfc: Fix LOGO/PLOGI handling when triggerd by ABTS Timeout event

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 30e196cacefdd9a38c857caed23cefc9621bc5c1 ] After a LOGO in response to an ABTS timeout, a PLOGI wasn't issued to re-establish the login. An nlp_type check in the LOGO completion

Re: [PATCH] net: phy: mdio_bus: add missing device_del() in mdiobus_register() error handling

Hello Andrew, On Wed, 16 Jan 2019 16:44:39 +0100 Andrew Lunn wrote: > > On Wed, 16 Jan 2019 15:48:29 +0100, Andrew Lunn wrote: > > > > > Reviewed-by: Andrew Lunn > > > > > > However, i wounder if it makes sense to add a label before the > > > existing device_del() at the end of the

[PATCH 4.19 014/313] ath10k: assign n_cipher_suites for WCN3990

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2bd345cd2bfc0bd44528896313c0b45f087bdf67 ] Commit 2ea9f12cefe4 ("ath10k: add new cipher suite support") added a new n_cipher_suites HW param with a fallback value and a warning log.

[PATCH 4.19 020/313] clk: boston: fix possible memory leak in clk_boston_setup()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 46fda5b5067a391912cf73bf3d32c26b6a22ad09 ] Smatch report warnings: drivers/clk/imgtec/clk-boston.c:76 clk_boston_setup() warn: possible memory leak of 'onecell'

[PATCH 4.19 016/313] scsi: lpfc: Correct LCB RJT handling

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b114d9009d386276bfc3352289fc235781ae3353 ] When LCB's are rejected, if beaconing was already in progress, the Reason Code Explanation was not being set. Should have been set to

[PATCH v3 1/2] media: uapi: Add H264 low-level decoder API compound controls.

From: Pawel Osciak Stateless video codecs will require both the H264 metadata and slices in order to be able to decode frames. This introduces the definitions for a new pixel format for H264 slices that have been parsed, as well as the structures used to pass the metadata from the userspace to

Re: [PATCH 4.20 066/352] ASoC: sunxi: sun50i-codec-analog: Add support for cpvdd regulator supply

On Mon, Feb 11, 2019 at 03:14:53PM +0100, Greg Kroah-Hartman wrote: > On the Allwinner A64 SoCs, the audio codec has a built-in headphone > amplifier. This amplifier has a power supply separate from the rest of > the analog audio circuitry, labeled cpvdd. > This patch adds a DAPM widget for this

[PATCH 4.19 008/313] drm/sun4i: Initialize registers in tcon-top driver

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c96d62215fb540e2ae61de44cb7caf4db50958e3 ] It turns out that TCON TOP registers in H6 SoC have non-zero reset value. This may cause issues if bits are not changed during

[PATCH 4.19 009/313] genirq/affinity: Spread IRQs to all available NUMA nodes

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b82592199032bf7c778f861b936287e37ebc9f62 ] If the number of NUMA nodes exceeds the number of MSI/MSI-X interrupts which are allocated for a device, the interrupt affinity spreading

[PATCH 4.19 000/313] 4.19.21-stable review

This is the start of the stable review cycle for the 4.19.21 release. There are 313 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 Wed Feb 13 14:17:25 UTC 2019. Anything

[PATCH 4.19 033/313] Tools: hv: kvp: Fix a warning of buffer overflow with gcc 8.0.1

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4fcba7802c3e15a6e56e255871d6c72f829b9dd8 ] The patch fixes: hv_kvp_daemon.c: In function 'kvp_set_ip_info': hv_kvp_daemon.c:1305:2: note: 'snprintf' output between 41 and 4136

[PATCH 4.19 035/313] vbox: fix link error with gcc -Og

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b8ae30a7020d61e0504529adf45abb08fa5c59f5 ] With the new CONFIG_CC_OPTIMIZE_FOR_DEBUGGING option, we get a link error in the vboxguest driver, when that fails to optimize out the

Re: [PATCH 2/5] genirq/affinity: allow driver to setup managed IRQ's affinity

On Mon, Feb 11, 2019 at 11:54:00AM +0800, Ming Lei wrote: > On Sun, Feb 10, 2019 at 05:30:41PM +0100, Thomas Gleixner wrote: > > On Fri, 25 Jan 2019, Ming Lei wrote: > > > > > This patch introduces callback of .setup_affinity into 'struct > > > irq_affinity', so that: > > > > Please see

[PATCH 4.19 037/313] i40e: prevent overlapping tx_timeout recover

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d5585b7b6846a6d0f9517afe57be3843150719da ] If a TX hang occurs, we attempt to recover by incrementally resetting. If we're starved for CPU time, it's possible the reset doesn't

[PATCH 4.19 042/313] ARM: OMAP2+: hwmod: Fix some section annotations

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c10b26abeb53cabc1e6271a167d3f3d396ce0218 ] When building the kernel with Clang, the following section mismatch warnings appears: WARNING: vmlinux.o(.text+0x2d398): Section mismatch

[PATCH 4.19 040/313] usbnet: smsc95xx: fix rx packet alignment

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 810eeb1f41a9a272eedc94ca18c072e75678ede4 ] The smsc95xx driver already takes into account the NET_IP_ALIGN parameter when setting up the receive packet data, which means we do not

[PATCH 4.19 041/313] drm/rockchip: fix for mailbox read size

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fa68d4f8476bea4cdf441062b614b41bb85ef1da ] Some of the functions (like cdn_dp_dpcd_read, cdn_dp_get_edid_block) allow to read 64KiB, but the cdn_dp_mailbox_read_receive, that is

[PATCH 4.19 024/313] crypto: aes_ti - disable interrupts while accessing S-box

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0a6a40c2a8c184a2fb467efacfb1cd338d719e0b ] In the "aes-fixed-time" AES implementation, disable interrupts while accessing the S-box, in order to make cache-timing attacks more

[PATCH 4.19 043/313] drm/amd/display: fix gamma not being applied correctly

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8ce504b9389be846bcdf512ed5be8f661b3bf097 ] [why] Gamma was always being set as identity on SDR monitor, leading to no changes in gamma. This caused nightlight to not apply

[PATCH 4.19 045/313] bpf: libbpf: retry map creation without the name

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 23499442c319412aa8e54e7a939e2eb531bdd77d ] Since commit 88cda1c9da02 ("bpf: libbpf: Provide basic API support to specify BPF obj name"), libbpf unconditionally sets bpf_attr->name

[PATCH 4.19 044/313] drm/amd/display: calculate stream->phy_pix_clk before clock mapping

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 08e1c28dd521c7b08d1b0af0bae9fb22ccc012a4 ] [why] phy_pix_clk is one of the variable used to check if one PLL can be shared with displays having common mode set configuration. As of

[PATCH 4.19 047/313] modpost: validate symbol names also in find_elf_symbol

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5818c683a619c534c113e1f66d24f636defc29bc ] If an ARM mapping symbol shares an address with a valid symbol, find_elf_symbol can currently return the mapping symbol instead, as the

[PATCH 4.19 049/313] soc/tegra: Dont leak device tree node reference

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9eb40fa2cd2d1f6829e7b49bb22692f754b9cfe0 ] of_find_node_by_path() acquires a reference to the node returned by it and that reference needs to be dropped by its caller.

[PATCH 4.19 048/313] perf tools: Add Hygon Dhyana support

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4787eff3fa88f62fede6ed7afa06477ae6bf984d ] The tool perf is useful for the performance analysis on the Hygon Dhyana platform. But right now there is no Hygon support for it to

[PATCH 4.19 025/313] drm/vc4: ->x_scaling[1] should never be set to VC4_SCALING_NONE

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0560054da5673b25d56bea6c57c8d069673af73b ] For the YUV conversion to work properly, ->x_scaling[1] should never be set to VC4_SCALING_NONE, but vc4_get_scaling_mode() might return

[PATCH 4.19 071/313] i2c: sh_mobile: add support for r8a77990 (R-Car E3)

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5eb316e636eb298c204f5b368526d4480b63c0ba ] Add support for the IIC code for the r8a77990 (R-Car E3). It is not considered compatible with existing fallback bindings due to the

[PATCH 4.19 070/313] f2fs: fix wrong return value of f2fs_acl_create

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f6176473a0c7472380eef72ebeb330cf9485bf0a ] When call f2fs_acl_create_masq() failed, the caller f2fs_acl_create() should return -EIO instead of -ENOMEM, this patch makes it

[PATCH 4.19 069/313] f2fs: fix race between write_checkpoint and write_begin

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2866fb16d67992195b0526d19e65acb6640fb87f ] The following race could lead to inconsistent SIT bitmap: Task A Task B == ==

[PATCH 4.19 072/313] arm64: io: Ensure calls to delay routines are ordered against prior readX()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6460d32014717686d3b7963595950ba2c6d1bb5e ] A relatively standard idiom for ensuring that a pair of MMIO writes to a device arrive at that device with a specified minimum delay

[PATCH 4.19 029/313] dpaa2-ptp: defer probe when portal allocation failed

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5500598abbfb5b46201b9768bd9ea873a5eeaece ] The fsl_mc_portal_allocate can fail when the requested MC portals are not yet probed by the fsl_mc_allocator. In this situation, the

[PATCH 4.19 031/313] staging:iio:ad2s90: Make probe handle spi_setup failure

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b3a3eafeef769c6982e15f83631dcbf8d1794efb ] Previously, ad2s90_probe ignored the return code from spi_setup, not handling its possible failure. This patch makes ad2s90_probe check if

[PATCH 4.19 022/313] x86/PCI: Fix Broadcom CNB20LE unintended sign extension (redux)

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 53bb565fc5439f2c8c57a786feea5946804aa3e9 ] In the expression "word1 << 16", word1 starts as u16, but is promoted to a signed int, then sign-extended to resource_size_t, which is

[PATCH 4.19 055/313] clk: meson: meson8b: do not use cpu_div3 for cpu_scale_out_sel

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a5ac1ead32c9aac285f6436e09b4f6111996e9b8 ] The cpu_div3 clock (cpu_in divided by 3) generates a signal with a duty cycle of 33%. The CPU clock however requires a clock signal with a

[PATCH 4.19 053/313] staging: erofs: fix the definition of DBG_BUGON

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit eef168789866514e5d4316f030131c9fe65b643f ] It's better not to positively BUG_ON the kernel, however developers need a way to locate issues as soon as possible. DBG_BUGON is

[PATCH 4.19 066/313] staging: pi433: fix potential null dereference

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 64c4c4ca6c129a4191e8e1e91b2d5d9b8d08c518 ] Add a test for successful call to cdev_alloc() to avoid potential null dereference. Issue reported by smatch. Signed-off-by: Michael

[PATCH 4.19 028/313] MIPS: Boston: Disable EG20T prefetch

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5ec17af7ead09701e23d2065e16db6ce4e137289 ] The Intel EG20T Platform Controller Hub used on the MIPS Boston development board supports prefetching memory to optimize DMA transfers.

[PATCH 4.19 068/313] f2fs: avoid build warn of fall_through

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f5d5510e7389fa264337fb524346bac9eb93adc8 ] After merging the f2fs tree, today's linux-next build (x86_64_allmodconfig) produced this warning: In file included from

[PATCH 4.19 076/313] nfsd4: fix crash on writing v4_end_grace before nfsd startup

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 62a063b8e7d1db684db3f207261a466fa3194e72 ] Anatoly Trosinenko reports that this: 1) Checkout fresh master Linux branch (tested with commit e195ca6cb) 2) Copy x84_64-config-4.14 to

[PATCH 4.19 056/313] clk: meson: meson8b: fix the width of the cpu_scale_div clock

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a8662eadd1032018f31e37deda811790b2326662 ] According to the public S805 datasheet HHI_SYS_CPU_CLK_CNTL1[29:20] is the register for the CPU scale_div clock. This matches the code in

[PATCH 4.19 074/313] sunvdc: Do not spin in an infinite loop when vio_ldc_send() returns EAGAIN

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a11f6ca9aef989b56cd31ff4ee2af4fb31a172ec ] __vdc_tx_trigger should only loop on EAGAIN a finite number of times. See commit adddc32d6fde ("sunvnet: Do not spin in an infinite loop

[PATCH 4.19 080/313] Thermal: do not clear passive state during system sleep

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 964f4843a455d2ffb199512b08be8d5f077c4cac ] commit ff140fea847e ("Thermal: handle thermal zone device properly during system sleep") added PM hook to call thermal zone reset during

[PATCH 4.19 083/313] s390/zcrypt: improve special ap message cmd handling

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit be534791011100d204602e2e0496e9e6ce8edf63 ] There exist very few ap messages which need to have the 'special' flag enabled. This flag tells the firmware layer to do some pre- and

[PATCH 4.19 078/313] perf: arm_spe: handle devm_kasprintf() failure

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 754a58db6a556e6e5f5e32f3e84e7d67b5bf9c8e ] devm_kasprintf() may return NULL on failure of internal allocation thus the assignment to 'name' is not safe if unchecked. If NULL is

[PATCH 4.19 058/313] ptp: Fix pass zero to ERR_PTR() in ptp_clock_register

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aea0a897af9e44c258e8ab9296fad417f1bc063a ] Fix smatch warning: drivers/ptp/ptp_clock.c:298 ptp_clock_register() warn: passing zero to 'ERR_PTR' 'err' should be set while

[PATCH 4.19 061/313] iio: adc: meson-saradc: check for devm_kasprintf failure

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aad172b017617994343e36d8659c69e14cd694fd ] devm_kasprintf() may return NULL on failure of internal allocation thus the assignments to init.name are not safe if not checked. On

[PATCH 4.19 062/313] iio: adc: meson-saradc: fix internal clock names

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 50314f98b0ac468218e7c9af8c99f215a35436df ] Before this patch we are registering the internal clocks (for example on Meson8b, where the SAR ADC IP block implements the divider and

[PATCH 4.19 085/313] arm64: ftrace: dont adjust the LR value

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6e803e2e6e367db9a0d6ecae1bd24bb5752011bd ] The core ftrace code requires that when it is handed the PC of an instrumented function, this PC is the address of the instrumented

[PATCH 4.19 060/313] powerpc/32: Add .data..Lubsan_data*/.data..Lubsan_type* sections explicitly

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit beba24ac59133cb36ecd03f9af9ccb11971ee20e ] When both `CONFIG_LD_DEAD_CODE_DATA_ELIMINATION=y` and `CONFIG_UBSAN=y` are set, link step typically produce numberous warnings about

[PATCH 4.19 084/313] mt76x0: dfs: fix IBI_R11 configuration on non-radar channels

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6bf4a8e902aad7df55d7f2b10b850cfa3f880996 ] Fix IBI_R11 configuration on non-radar channels for mt76x0e driver. This patch improve system stability under heavy load. Moreover use

[PATCH 4.19 086/313] drm/v3d: Fix prime imports of buffers from other drivers.

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 62d1a752874962f072de8a779e960fcd2ab4847b ] v3d_bo_get_pages() checks this to decide to map the imported buffer instead of the backing shmem file. The caller was about to set this

[PATCH 4.19 097/313] usb: hub: delay hub autosuspend if USB3 port is still link training

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e86108940e541febf35813402ff29fa6f4a9ac0b ] When initializing a hub we want to give a USB3 port in link training the same debounce delay time before autosuspening the hub as already

[PATCH 4.19 088/313] ARM: mmp/mmp2: dt: enable the clock

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f36797ee43802b367e59f0f9a9805304a4ff0c98 ] The device-tree booted MMP2 needs to enable the timer clock, otherwise it would stop ticking when the boot finishes. It can also use the

[PATCH 4.19 054/313] x86/resctrl: Fixup the user-visible strings

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 723f1a0dd8e26a7523ba068204bee11c95ded38d ] Fix the messages in rdt_last_cmd_printf() and rdt_last_cmd_puts() to make them more meaningful and consistent. [ bp: s/cpu/CPU/;

[PATCH 4.19 098/313] timekeeping: Use proper seqcount initializer

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ce10a5b3954f2514af726beb78ed8d7350c5e41c ] tk_core.seq is initialized open coded, but that misses to initialize the lockdep map when lockdep is enabled. Lockdep splats involving

[PATCH 4.19 063/313] iio: accel: kxcjk1013: Add KIOX010A ACPI Hardware-ID

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7f6232e69539971cf9eaed07a6c14ab4a2361133 ] Various 2-in-1's use KIOX010A and KIOX020A as HIDs for 2 KXCJ91008 accelerometers. The KIOX010A HID is for the one in the base and the

[PATCH 4.19 101/313] media: imx274: select REGMAP_I2C

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4f9d7225c70dd9d3f406b79e60f8dbd2cd5ae743 ] The imx274 driver uses regmap and the build will fail without it. Fixes: drivers/media/i2c/imx274.c:142:21: error: variable

[PATCH 4.19 106/313] IB/hfi1: Unreserve a reserved request when it is completed

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ca95f802ef5139722acc8d30aeaab6fe5bbe939e ] Currently, When a reserved operation is completed, its entry in the send queue will not be unreserved, which leads to the miscalculation

[PATCH 4.19 102/313] drm/amdgpu/powerplay: fix clock stretcher limits on polaris (v2)

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit de4aaab5cc9770a8c4dc13d9bfb6a83b06bba57e ] Adjust limits for newer polaris variants. v2: fix polaris11 kicker (Jerry) Reviewed-by: Junwei Zhang Signed-off-by: Alex Deucher

[PATCH 4.19 089/313] ARM: dts: aspeed: add missing memory unit-address

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8ef86955fe59f7912a40d57ae4c6d511f0187b4d ] The base aspeed-g5.dtsi already defines a '/memory@8000' node, so '/memory' in the board files create a duplicate node. We're probably

[PATCH 4.19 103/313] tipc: fix node keep alive interval calculation

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f5d6c3e5a359c0507800e7ac68d565c21de9b5a1 ] When setting LINK tolerance, node timer interval will be calculated base on the LINK with lowest tolerance. But when calculated, the old

[PATCH 4.19 099/313] usb: mtu3: fix the issue about SetFeature(U1/U2_Enable)

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a0678e2eed41e81004308693ac84ea95614b0920 ] Fix the issue: device doesn't accept LGO_U1/U2: 1. set SW_U1/U2_ACCEPT_ENABLE to eanble controller to accept LGO_U1/U2 by default; 2.

[PATCH 4.19 104/313] driver core: Move async_synchronize_full call

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c37d721c68ad88925ba0e72f6e14acb829a8c6bb ] Move the async_synchronize_full call out of __device_release_driver and into driver_detach. The idea behind this is that the

[PATCH 4.19 107/313] usb: dwc3: trace: add missing break statement to make compiler happy

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 54d48183d21e03f780053d7129312049cb5dd591 ] The missed break statement in the outer switch makes the code fall through always and thus always same value will be printed. Besides

[PATCH 4.19 108/313] gpio: mt7621: report failure of devm_kasprintf()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 59d646c775d6ae688ee90fda9f2a4270c47b7490 ] kasprintf() may return NULL on failure of internal allocation thus the assigned label is not safe if not explicitly checked. On error

[PATCH 4.19 109/313] gpio: mt7621: pass mediatek_gpio_bank_probe() failure up the stack

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a109c2dbb571b10bb9969285b646f57309c98251 ] The error cases of mediatek_gpio_bank_probe() would go unnoticed (except for the dev_err() messages). The probe function should return an

[PATCH 4.19 110/313] pinctrl: sx150x: handle failure case of devm_kstrdup

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a9d9f6b83f1bb05da849b3540e6d1f70ef1c2343 ] devm_kstrdup() may return NULL if internal allocation failed. Thus using label, name is unsafe without checking. Therefor in the

[PATCH 4.19 113/313] mips: bpf: fix encoding bug for mm_srlv32_op

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 17f6c83fb5ebf7db4fcc94a5be4c22d5a7bfe428 ] For micro-mips, srlv inside POOL32A encoding space should use 0x50 sub-opcode, NOT 0x90. Some early version ISA doc describes the

[PATCH 4.19 111/313] iommu/amd: Fix amd_iommu=force_isolation

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c12b08ebbe16f0d3a96a116d86709b04c1ee8e74 ] The parameter is still there but it's ignored. We need to check its value before deciding to go into passthrough mode for AMD IOMMU v2

[PATCH 4.19 117/313] watchdog: renesas_wdt: dont set divider while watchdog is running

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e990e12741877e9bfac402ca468f4007a75f6e2a ] The datasheet says we must stop the timer before changing the clock divider. This can happen when the restart handler is called while the

[PATCH 4.19 115/313] ARM: dts: Fix up the D-Link DIR-685 MTD partition info

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 738a05e673435afb986b53da43befd83ad87ec3b ] The vendor firmware was analyzed to get the right idea about this flash layout. /proc/mtd contains: dev:size erasesize name mtd0:

[PATCH 4.19 119/313] usb: dwc3: gadget: Disable CSP for stream OUT ep

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 244add8ebfb231c39db9e33b204bd0ce8f24f782 ] In stream mode, when fast-forwarding TRBs, the stream number is not cleared causing the new stream to not get assigned. So we don't want

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