[PATCH 4.19 112/142] xen: xlate_mmu: add missing header to fix W=1 warning

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 72791ac854fea36034fa7976b748fde585008e78 ] Add a missing header otherwise compiler warns about missed prototype: drivers/xen/xlate_mmu.c:183:5: warning: no previous prototype for

[PATCH 4.19 111/142] drm/ast: fixed reading monitor EDID not stable issue

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 300625620314194d9e6d4f6dda71f2dc9cf62d9f ] v1: over-sample data to increase the stability with some specific monitors v2: refine to avoid infinite loop v3: remove un-necessary

[PATCH 4.19 094/142] netfilter: add missing error handling code for register functions

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 584eab291c67894cb17cc87544b9d086228ea70f ] register_{netdevice/inetaddr/inet6addr}_notifier may return an error value, this patch adds the code to handle these error paths.

[PATCH 4.19 127/142] hfsplus: do not free node before using

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c7d7d620dcbd2a1c595092280ca943f2fced7bbd ] hfs_bmap_free() frees node via hfs_bnode_put(node). However it then reads node->this when dumping error message on an error path, which

[PATCH 4.19 097/142] KVM: VMX: Update shared MSRs to be saved/restored on MSR_EFER.LMA changes

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f48b4711dd6e1cf282f9dfd159c14a305909c97c ] When guest transitions from/to long-mode by modifying MSR_EFER.LMA, the list of shared MSRs to be saved/restored on guest<->host

[PATCH 4.19 116/142] afs: Fix validation/callback interaction

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ae3b7361dc0ee9a425bf7d77ce211f533500b39b ] When afs_validate() is called to validate a vnode (inode), there are two unhandled cases in the fastpath at the top of the function: (1)

[PATCH 4.19 098/142] KVM: x86: fix empty-body warnings

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 354cb410d87314e2eda344feea84809e4261570a ] We get the following warnings about empty statements when building with 'W=1': arch/x86/kvm/lapic.c:632:53: warning: suggest braces

[PATCH 4.19 118/142] cachefiles: Explicitly cast enumerated type in put_object

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b7e768b7e3522695ed36dcb48ecdcd344bd30a9b ] Clang warns when one enumerated type is implicitly converted to another. fs/cachefiles/namei.c:247:50: warning: implicit conversion from

[PATCH 4.19 128/142] debugobjects: avoid recursive calls with kmemleak

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8de456cf87ba863e028c4dd01bae44255ce3d835 ] CONFIG_DEBUG_OBJECTS_RCU_HEAD does not play well with kmemleak due to recursive calls. fill_pool kmemleak_ignore make_black_object

[PATCH 4.19 130/142] kernel/kcov.c: mark funcs in __sanitizer_cov_trace_pc() as notrace

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 903e8ff86753e6f327bb92166a0665e4ecb8e2e7 ] Since __sanitizer_cov_trace_pc() is marked as notrace, function calls in __sanitizer_cov_trace_pc() shouldn't be traced either.

[PATCH 4.19 119/142] fscache, cachefiles: remove redundant variable cache

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 31ffa563833576bd49a8bf53120568312755e6e2 ] Variable 'cache' is being assigned but is never used hence it is redundant and can be removed. Cleans up clang warning: warning: variable

[PATCH 4.19 135/142] ALSA: fireface: fix reference to wrong register for clock configuration

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Sakamoto commit fa9c98e4b975bb3192ed6af09d9fa282ed3cd8a0 upstream. In an initial commit, 'SYNC_STATUS' register is referred to get clock configuration, however this is wrong,

[PATCH 4.19 139/142] ALSA: hda/realtek: Enable audio jacks of ASUS UX433FN/UX333FA with ALC294

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Jian-Hong Pan commit 0bea4cc8383519f78f3f74caca7bdebdfb346d3b upstream. The ASUS UX433FN and UX333FA with ALC294 cannot detect the headset MIC and output through the internal speaker and the

[PATCH 4.19 140/142] ALSA: hda/realtek - Fix the mute LED regresion on Lenovo X1 Carbon

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Hui Wang commit 6ba189c5c1a4bda70dc1e4826c58b0246068bb8d upstream. Users reported a mute LED regression on Lenovo X1 Carbon, the root cause is we applied the fixup of

[PATCH 4.19 131/142] initramfs: clean old path before creating a hardlink

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7c0950d455d6ab610d2990a13120f935b75abf2c ] sys_link() can fail due to the new path already existing. This case ofen occurs when we use a concated initrd, for example: 1) prepare a

[PATCH 4.19 136/142] ALSA: hda/realtek - Fixed headphone issue for ALC700

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit bde1a7459623a66c2abec4d0a841e4b06cc88d9a upstream. If it plugged headphone or headset into the jack, then do the reboot, it will have a chance to cause headphone no sound.

[PATCH 4.14 26/89] s390/cpum_cf: Reject request for sampling in event initialization

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 613a41b0d16e617f46776a93b975a1eeea96417c ] On s390 command perf top fails [root@s35lp76 perf] # ./perf top -F10 --stdio Error: cycles: PMU Hardware doesn't support

[PATCH 4.14 16/89] ARM: OMAP2+: prm44xx: Fix section annotation on omap44xx_prm_enable_io_wakeup

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

[PATCH 4.14 27/89] hwmon: (ina2xx) Fix current value calculation

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 38cd989ee38c16388cde89db5b734f9d55b905f9 ] The current register (04h) has a sign bit at MSB. The comments for this calculation also mention that it's a signed register. However,

[PATCH 4.19 141/142] IB/hfi1: Fix an out-of-bounds access in get_hw_stats

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Piotr Stankiewicz commit 36d842194a57f1b21fbc6a6875f2fa2f9a7f8679 upstream. When running with KASAN, the following trace is produced: [ 62.535888]

[PATCH 4.14 06/89] net/mlx4_core: Correctly set PFC param if global pause is turned off.

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tarick Bedeir [ Upstream commit bd5122cd1e0644d8bd8dd84517c932773e999766 ] rx_ppp and tx_ppp can be set between 0 and 255, so don't clamp to 1. Fixes: 6e8814ceb7e8 ("net/mlx4_en: Fix mixed

[PATCH 4.14 05/89] net: 8139cp: fix a BUG triggered by changing mtu with network traffic

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Su Yanjun [ Upstream commit a5d4a89245ead1f37ed135213653c5beebea4237 ] When changing mtu many times with traffic, a bug is triggered: [ 1035.684037] kernel BUG at

[PATCH 4.19 124/142] ocfs2: fix deadlock caused by ocfs2_defrag_extent()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e21e57445a64598b29a6f629688f9b9a39e7242a ] ocfs2_defrag_extent may fall into deadlock. ocfs2_ioctl_move_extents ocfs2_ioctl_move_extents ocfs2_move_extents

[PATCH 4.14 10/89] rtnetlink: ndo_dflt_fdb_dump() only work for ARPHRD_ETHER devices

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 688838934c231bb08f46db687e57f6d8bf82709c ] kmsan was able to trigger a kernel-infoleak using a gre device [1] nlmsg_populate_fdb_fill() has a hard coded

[PATCH 4.14 31/89] netfilter: xt_hashlimit: fix a possible memory leak in htable_create()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b4e955e9f372035361fbc6f07b21fe2cc6a5be4a ] In the htable_create(), hinfo is allocated by vmalloc() So that if error occurred, hinfo should be freed. Fixes: 11d5f15723c9

[PATCH 4.14 03/89] neighbour: Avoid writing before skb->head in neigh_hh_output()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit e6ac64d4c4d095085d7dd71cbd05704ac99829b2 ] While skb_push() makes the kernel panic if the skb headroom is less than the unaligned hardware header size, it

[PATCH 4.19 117/142] fscache: fix race between enablement and dropping of object

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c5a94f434c82529afda290df3235e4d85873c5b4 ] It was observed that a process blocked indefintely in __fscache_read_or_alloc_page(), waiting for FSCACHE_COOKIE_LOOKING_UP to be cleared

[PATCH 4.19 142/142] bpf: fix off-by-one error in adjust_subprog_starts

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Edward Cree commit afd594240806acc138cf696c09f2f4829d55d02f upstream. When patching in a new sequence for the first insn of a subprog, the start of that subprog does not change (it's the

[PATCH 4.19 122/142] nvme-rdma: fix double freeing of async event data

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6344d02dc8f886b6bbcd922ae1a17e4a41500f2d ] Some error paths in configuration of admin queue free data buffer associated with async request SQE without resetting the data buffer

[PATCH 4.14 17/89] ASoC: rsnd: fixup clock start checker

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3ee9a76a8c5a10e1bfb04b81db767c6d562ddaf3 ] commit 4d230d12710646 ("ASoC: rsnd: fixup not to call clk_get/set under non-atomic") fixuped clock start timing. But it exchanged clock

[PATCH 4.19 123/142] ACPI/IORT: Fix iort_get_platform_device_domain() uninitialized pointer value

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ea2412dc21cc790335d319181dddc43682aef164 ] Running the Clang static analyzer on IORT code detected the following error: Logic error: Branch condition evaluates to a garbage value

[PATCH 4.14 14/89] tun: forbid iface creation with rtnl ops

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Dichtel [ Upstream commit 35b827b6d06199841a83839e8bb69c0cd13a28be ] It's not supported right now (the goal of the initial patch was to support 'ip link del' only). Before the patch:

[PATCH 4.14 11/89] sctp: kfree_rcu asoc

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit fb6df5a6234c38a9c551559506a49a677ac6f07a ] In sctp_hash_transport/sctp_epaddr_lookup_transport, it dereferences a transport's asoc under rcu_read_lock while asoc is

[PATCH 4.14 37/89] ARM: dts: at91: sama5d2: use the divided clock for SMC

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4ab7ca092c3c7ac8b16aa28eba723a8868f82f14 ] The SAMA5D2 is different from SAMA5D3 and SAMA5D4, as there are two different clocks for the peripherals in the SoC. The Static Memory

[PATCH 4.14 38/89] Btrfs: send, fix infinite loop due to directory rename dependencies

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a4390aee72713d9e73f1132bcdeb17d72fbbf974 ] When doing an incremental send, due to the need of delaying directory move (rename) operations we can end up in infinite loop at

[PATCH 4.14 51/89] USB: omap_udc: fix rejection of out transfers when DMA is used

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 069caf5950dfa75d0526cd89c439ff9d9d3136d8 ] Commit 387f869d2579 ("usb: gadget: u_ether: conditionally align transfer size") started aligning transfer size only if requested, breaking

[PATCH 4.14 19/89] ARM: dts: logicpd-somlv: Fix interrupt on mmc3_dat1

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3d8b804bc528d3720ec0c39c212af92dafaf6e84 ] The interrupt on mmc3_dat1 is wrong which prevents this from appearing in /proc/interrupts. Fixes: ab8dd3aed011 ("ARM: DTS: Add minimal

[PATCH 4.14 21/89] sysv: return err instead of 0 in __sysv_write_inode

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c4b7d1ba7d263b74bb72e9325262a67139605cde ] Fixes gcc '-Wunused-but-set-variable' warning: fs/sysv/inode.c: In function '__sysv_write_inode': fs/sysv/inode.c:239:6: warning:

[PATCH 4.14 18/89] staging: rtl8723bs: Fix the return value in case of error in rtw_wx_read32()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c3e43d8b958bd6849817393483e805d8638a8ab7 ] We return 0 unconditionally in 'rtw_wx_read32()'. However, 'ret' is set to some error codes in several error handling paths. Return 'ret'

[PATCH 4.14 40/89] RDMA/rdmavt: Fix rvt_create_ah function signature

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4f32fb921b153ae9ea280e02a3e91509fffc03d3 ] rdmavt uses a crazy system that looses the type checking when assinging functions to struct ib_device function pointers. Because of this

[PATCH 4.14 52/89] drm/meson: add support for 1080p25 mode

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 31e1ab494559fb46de304cc6c2aed1528f94b298 ] This essential mode for PAL users is missing, so add it. Fixes: 335e3713afb87 ("drm/meson: Add support for HDMI venc modes and settings")

[PATCH 4.14 59/89] netfilter: nf_tables: deactivate expressions in rule replecement routine

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ca08987885a147643817d02bf260bc4756ce8cd4 ] There is no expression deactivation call from the rule replacement path, hence, chain counter is not decremented. A few steps to reproduce

[PATCH 4.14 58/89] usb: gadget: u_ether: fix unsafe list iteration

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c9287fa657b3328b4549c0ab39ea7f197a3d6a50 ] list_for_each_entry_safe() is not safe for deleting entries from the list if the spin lock, which protects it, is released and reacquired

[PATCH 4.14 56/89] x86/kvm/vmx: fix old-style function declaration

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1e4329ee2c52692ea42cc677fb2133519718b34a ] The inline keyword which is not at the beginning of the function declaration may trigger the following build warnings, so let's fix it:

[PATCH 4.14 55/89] KVM: x86: fix empty-body warnings

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 354cb410d87314e2eda344feea84809e4261570a ] We get the following warnings about empty statements when building with 'W=1': arch/x86/kvm/lapic.c:632:53: warning: suggest braces

[PATCH 4.14 62/89] ixgbe: recognize 1000BaseLX SFP modules as 1Gbps

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a8bf879af7b1999eba36303ce9cc60e0e7dd816c ] Add the two 1000BaseLX enum values to the X550's check for 1Gbps modules, allowing the core driver code to establish a link over this SFP

[PATCH 4.14 63/89] net: hisilicon: remove unexpected free_netdev

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c758940158bf29fe14e9d0f89d5848f227b48134 ] The net device ndev is freed via free_netdev when failing to register the device. The control flow then jumps to the error handling code

[PATCH 4.14 74/89] mm/page_alloc.c: fix calculation of pgdat->nr_zones

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8f416836c0d50b198cad1225132e5abebf8980dc ] init_currently_empty_zone() will adjust pgdat->nr_zones and set it to 'zone_idx(zone) + 1' unconditionally. This is correct in the normal

[PATCH 4.14 76/89] hfsplus: do not free node before using

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c7d7d620dcbd2a1c595092280ca943f2fced7bbd ] hfs_bmap_free() frees node via hfs_bnode_put(node). However it then reads node->this when dumping error message on an error path, which

[PATCH 4.14 39/89] RDMA/mlx5: Fix fence type for IB_WR_LOCAL_INV WR

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 074fca3a18e7e1e0d4d7dcc9d7badc43b90232f4 ] Currently, for IB_WR_LOCAL_INV WR, when the next fence is None, the current fence will be SMALL instead of Normal Fence. Without this

[PATCH 4.14 46/89] ipvs: call ip_vs_dst_notifier earlier than ipv6_dev_notf

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2a31e4bd9ad255ee40809b5c798c4b1c2b09703b ] ip_vs_dst_event is supposed to clean up all dst used in ipvs' destinations when a net dev is going down. But it works only when the dst's

[PATCH 4.14 45/89] bpf: fix check of allowed specifiers in bpf_trace_printk

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1efb6ee3edea57f57f9fb05dba8dcb3f7333f61f ] A format string consisting of "%p" or "%s" followed by an invalid specifier (e.g. "%p%\n" or "%s%") could pass the check which would make

[PATCH 4.14 78/89] ocfs2: fix potential use after free

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 164f7e586739d07eb56af6f6d66acebb11f315c8 ] ocfs2_get_dentry() calls iput(inode) to drop the reference count of inode, and if the reference count hits 0, inode is freed. However, in

[PATCH 4.14 44/89] exportfs: do not read dentry after free

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2084ac6c505a58f7efdec13eba633c6aaa085ca5 ] The function dentry_connected calls dput(dentry) to drop the previously acquired reference to dentry. In this case, dentry can be

[PATCH 4.14 70/89] fscache, cachefiles: remove redundant variable cache

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 31ffa563833576bd49a8bf53120568312755e6e2 ] Variable 'cache' is being assigned but is never used hence it is redundant and can be removed. Cleans up clang warning: warning: variable

[PATCH 4.14 67/89] Revert "xen/balloon: Mark unallocated host memory as UNUSABLE"

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 123664101aa2156d05251704fc63f9bcbf77741a ] This reverts commit b3cf8528bb21febb650a7ecbf080d0647be40b9f. That commit unintentionally broke Xen balloon memory hotplug with

[PATCH 4/6] drm/exynos: plane: Minor cleanup

Use available drm_plane pointer, for consistency. Signed-off-by: Christoph Manszewski --- drivers/gpu/drm/exynos/exynos_drm_plane.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/exynos/exynos_drm_plane.c b/drivers/gpu/drm/exynos/exynos_drm_plane.c

[PATCH 4.14 80/89] printk: Add console owner and waiter logic to load balance console writes

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit dbdda842fe96f8932bae554f0adf463c27c42bc7 ] This patch implements what I discussed in Kernel Summit. I added lockdep annotation (hopefully correctly), and it hasn't had any splats

[PATCH 4.14 79/89] Revert "printk: Never set console_may_schedule in console_trylock()"

4.14-stable review patch. If anyone has any objections, please let me know. -- This reverts commit c9b8d580b3fb0ab65d37c372aef19a318fda3199. This is just a technical revert to make the printk fix apply cleanly, this patch will be re-picked in about 3 commits. ---

[PATCH 4.14 71/89] nvme: flush namespace scanning work just before removing namespaces

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f6c8e432cb0479255322c5d0335b9f1699a0270c ] nvme_stop_ctrl can be called also for reset flow and there is no need to flush the scan_work as namespaces are not being removed. This can

[PATCH 4.14 85/89] flexfiles: enforce per-mirror stateid only for v4 DSes

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tigran Mkrtchyan commit 320f35b7bf8cccf1997ca3126843535e1b95e9c4 upstream. Since commit bb21ce0ad227 we always enforce per-mirror stateid. However, this makes sense only for v4+ servers.

[PATCH 4.14 68/89] pstore/ram: Correctly calculate usable PRZ bytes

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 89d328f637b9904b6d4c9af73c8a608b8dd4d6f8 ] The actual number of bytes stored in a PRZ is smaller than the bytes requested by platform data, since there is a header on each PRZ.

[PATCH 4.9 03/51] net: 8139cp: fix a BUG triggered by changing mtu with network traffic

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Su Yanjun [ Upstream commit a5d4a89245ead1f37ed135213653c5beebea4237 ] When changing mtu many times with traffic, a bug is triggered: [ 1035.684037] kernel BUG at

[PATCH 4.14 89/89] IB/hfi1: Fix an out-of-bounds access in get_hw_stats

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Piotr Stankiewicz commit 36d842194a57f1b21fbc6a6875f2fa2f9a7f8679 upstream. When running with KASAN, the following trace is produced: [ 62.535888]

[PATCH 4.14 88/89] ALSA: hda/realtek - Fixed headphone issue for ALC700

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit bde1a7459623a66c2abec4d0a841e4b06cc88d9a upstream. If it plugged headphone or headset into the jack, then do the reboot, it will have a chance to cause headphone no sound.

[PATCH 4.14 73/89] ocfs2: fix deadlock caused by ocfs2_defrag_extent()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e21e57445a64598b29a6f629688f9b9a39e7242a ] ocfs2_defrag_extent may fall into deadlock. ocfs2_ioctl_move_extents ocfs2_ioctl_move_extents ocfs2_move_extents

[PATCH 4.9 11/51] ARM: OMAP2+: prm44xx: Fix section annotation on omap44xx_prm_enable_io_wakeup

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

[PATCH 4.9 25/51] ASoC: omap-mcpdm: Add pm_qos handling to avoid under/overruns with CPU_IDLE

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 373a500e34aea97971c9d71e45edad458d3da98f ] We need to block sleep states which would require longer time to leave than the time the DMA must react to the DMA request in order to keep

[PATCH 4.9 00/51] 4.9.146-stable review

This is the start of the stable review cycle for the 4.9.146 release. There are 51 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 Sun Dec 16 11:56:52 UTC 2018. Anything

[PATCH 4.9 28/51] bpf: fix check of allowed specifiers in bpf_trace_printk

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1efb6ee3edea57f57f9fb05dba8dcb3f7333f61f ] A format string consisting of "%p" or "%s" followed by an invalid specifier (e.g. "%p%\n" or "%s%") could pass the check which would make

[PATCH 4.9 33/51] USB: omap_udc: fix USB gadget functionality on Palm Tungsten E

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2c2322fbcab8102b8cadc09d66714700a2da42c2 ] On Palm TE nothing happens when you try to use gadget drivers and plug the USB cable. Fix by adding the board to the vbus sense quirk list.

[PATCH 4.9 15/51] selftests: add script to stress-test nft packet path vs. control plane

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 25d8bcedbf4329895dbaf9dd67baa6f18dad918c ] Start flood ping for each cpu while loading/flushing rulesets to make sure we do not access already-free'd rules from nf_tables evaluation

[PATCH 4.9 26/51] ASoC: omap-dmic: Add pm_qos handling to avoid overruns with CPU_IDLE

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ffdcc3638c58d55a6fa68b6e5dfd4fb4109652eb ] We need to block sleep states which would require longer time to leave than the time the DMA must react to the DMA request in order to keep

[PATCH 4.9 07/51] rtnetlink: ndo_dflt_fdb_dump() only work for ARPHRD_ETHER devices

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 688838934c231bb08f46db687e57f6d8bf82709c ] kmsan was able to trigger a kernel-infoleak using a gre device [1] nlmsg_populate_fdb_fill() has a hard coded

[PATCH 4.9 34/51] KVM: x86: fix empty-body warnings

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 354cb410d87314e2eda344feea84809e4261570a ] We get the following warnings about empty statements when building with 'W=1': arch/x86/kvm/lapic.c:632:53: warning: suggest braces around

[PATCH 4.9 30/51] USB: omap_udc: use devm_request_irq()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 286afdde1640d8ea8916a0f05e811441fbbf4b9d ] The current code fails to release the third irq on the error path (observed by reading the code), and we get also multiple WARNs with

[PATCH 4.9 35/51] x86/kvm/vmx: fix old-style function declaration

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1e4329ee2c52692ea42cc677fb2133519718b34a ] The inline keyword which is not at the beginning of the function declaration may trigger the following build warnings, so let's fix it:

Re: [PATCH RFC v2 1/8] drm/bridge: dw-hdmi: Add SCDC and TMDS Scrambling support

Am Freitag, 30. November 2018, 14:42:54 CET schrieb Neil Armstrong: > Add support for SCDC Setup for TMDS Clock > 3.4GHz and enable TMDS > Scrambling when supported or mandatory. > > This patch also adds an helper to setup the control bit to support > the high TMDS Bit Period/TMDS Clock-Period

Re: [PATCH RFC v2 6/8] drm/bridge: dw-hdmi: allow ycbcr420 modes for >= 0x200a

Am Freitag, 30. November 2018, 14:42:59 CET schrieb Neil Armstrong: > Now the DW-HDMI Controller supports the HDMI2.0 modes, enable support > for these modes in the connector if the platform supports them. > We limit these modes to DW-HDMI IP version >= 0x200a which > are designed to support

[PATCH 4.9 45/51] ocfs2: fix deadlock caused by ocfs2_defrag_extent()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e21e57445a64598b29a6f629688f9b9a39e7242a ] ocfs2_defrag_extent may fall into deadlock. ocfs2_ioctl_move_extents ocfs2_ioctl_move_extents ocfs2_move_extents

[PATCH 4.4 01/88] ipv6: Check available headroom in ip6_xmit() even without options

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit 66033f47ca60294a95fc85ec3a3cc909dab7b765 ] Even if we send an IPv6 packet without options, MAX_HEADER might not be enough to account for the additional

[PATCH 4.4 03/88] net: phy: dont allow __set_phy_supported to add unsupported modes

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit d2a36971ef595069b7a600d1144c2e0881a930a1 ] Currently __set_phy_supported allows to add modes w/o checking whether the PHY supports them. This is wrong, it

[PATCH 4.4 00/88] 4.4.168-stable review

This is the start of the stable review cycle for the 4.4.168 release. There are 88 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 Sun Dec 16 11:56:41 UTC 2018. Anything

[PATCH 4.9 19/51] ASoC: dapm: Recalculate audio map forcely when card instantiated

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 882eab6c28d23a970ae73b7eb831b169a672d456 ] Audio map are possible in wrong state before card->instantiated has been set to true. Imaging the following examples: time 1: at the

[PATCH 4.9 20/51] hwmon: (w83795) temp4_type has writable permission

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 09aaf6813cfca4c18034fda7a43e68763f34abb1 ] Both datasheet and comments of store_temp_mode() tell us that temp1~4_type is writable, so fix it. Signed-off-by: Yao Wang Signed-off-by:

[PATCH 4.9 50/51] pstore: Convert console write to use ->write_buf

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 70ad35db3321a6d129245979de4ac9d06eed897c ] Maybe I'm missing something, but I don't know why it needs to copy the input buffer to psinfo->buf and then write. Instead we can write

[PATCH 4.9 46/51] hfs: do not free node before using

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ce96a407adef126870b3f4a1b73529dd8aa80f49 ] hfs_bmap_free() frees the node via hfs_bnode_put(node). However, it then reads node->this when dumping error message on an error path,

[PATCH 4.9 23/51] Btrfs: send, fix infinite loop due to directory rename dependencies

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a4390aee72713d9e73f1132bcdeb17d72fbbf974 ] When doing an incremental send, due to the need of delaying directory move (rename) operations we can end up in infinite loop at

[PATCH 4.9 42/51] xen: xlate_mmu: add missing header to fix W=1 warning

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 72791ac854fea36034fa7976b748fde585008e78 ] Add a missing header otherwise compiler warns about missed prototype: drivers/xen/xlate_mmu.c:183:5: warning: no previous prototype for

[PATCH 4.9 44/51] fscache, cachefiles: remove redundant variable cache

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 31ffa563833576bd49a8bf53120568312755e6e2 ] Variable 'cache' is being assigned but is never used hence it is redundant and can be removed. Cleans up clang warning: warning: variable

[PATCH 4.9 18/51] ASoC: omap-abe-twl6040: Fix missing audio card caused by deferred probing

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 76836fd354922ebe4798a64fda01f8dc6a8b0984 ] The machine driver fails to probe in next-20181113 with: [2.539093] omap-abe-twl6040 sound: ASoC: CODEC DAI twl6040-legacy not

[PATCH 4.9 37/51] cachefiles: Fix page leak in cachefiles_read_backing_file while vmscan is active

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9a24ce5b66f9c8190d63b15f4473600db4935f1f ] [Description] In a heavily loaded system where the system pagecache is nearing memory limits and fscache is enabled, pages can be leaked

[PATCH 4.9 39/51] ixgbe: recognize 1000BaseLX SFP modules as 1Gbps

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a8bf879af7b1999eba36303ce9cc60e0e7dd816c ] Add the two 1000BaseLX enum values to the X550's check for 1Gbps modules, allowing the core driver code to establish a link over this SFP

[PATCH 4.9 22/51] objtool: Fix segfault in .cold detection with -ffunction-sections

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 22566c1603030f0a036ad564634b064ad1a55db2 ] Because find_symbol_by_name() traverses the same lists as read_symbols(), changing sym->name in place without copying it affects the result

[PATCH 4.4 24/88] USB: omap_udc: fix omap_udc_start() on 15xx machines

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6ca6695f576b8453fe68865e84d25946d63b10ad ] On OMAP 15xx machines there are no transceivers, and omap_udc_start() always fails as it forgot to adjust the default return value.

[PATCH 4.4 17/88] Btrfs: send, fix infinite loop due to directory rename dependencies

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a4390aee72713d9e73f1132bcdeb17d72fbbf974 ] When doing an incremental send, due to the need of delaying directory move (rename) operations we can end up in infinite loop at

[PATCH 4.4 21/88] bpf: fix check of allowed specifiers in bpf_trace_printk

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1efb6ee3edea57f57f9fb05dba8dcb3f7333f61f ] A format string consisting of "%p" or "%s" followed by an invalid specifier (e.g. "%p%\n" or "%s%") could pass the check which would make

[PATCH 4.4 12/88] sysv: return err instead of 0 in __sysv_write_inode

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c4b7d1ba7d263b74bb72e9325262a67139605cde ] Fixes gcc '-Wunused-but-set-variable' warning: fs/sysv/inode.c: In function '__sysv_write_inode': fs/sysv/inode.c:239:6: warning:

[PATCH 4.4 28/88] ixgbe: recognize 1000BaseLX SFP modules as 1Gbps

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a8bf879af7b1999eba36303ce9cc60e0e7dd816c ] Add the two 1000BaseLX enum values to the X550's check for 1Gbps modules, allowing the core driver code to establish a link over this SFP

[PATCH 4.4 30/88] drm/ast: fixed reading monitor EDID not stable issue

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 300625620314194d9e6d4f6dda71f2dc9cf62d9f ] v1: over-sample data to increase the stability with some specific monitors v2: refine to avoid infinite loop v3: remove un-necessary

  1   2   3   4   5   6   7   8   9   10   >