[PATCH 5.1 364/371] blk-throttle: fix zero wait time for iops throttled group

2019-07-24 Thread Greg Kroah-Hartman
From: Konstantin Khlebnikov commit 3a10f999ffd464d01c5a05592a15470a3c4bbc36 upstream. After commit 991f61fe7e1d ("Blk-throttle: reduce tail io latency when iops limit is enforced") wait time could be zero even if group is throttled and cannot issue requests right now. As a result throtl_select_d

[PATCH 5.1 365/371] clk: imx: imx8mm: correct audio_pll2_clk to audio_pll2_out

2019-07-24 Thread Greg Kroah-Hartman
From: Peng Fan commit 5b933e28d8b1fbdc7fbac4bfc569f3b152c3dd59 upstream. There is no audio_pll2_clk registered, it should be audio_pll2_out. Cc: Fixes: ba5625c3e272 ("clk: imx: Add clock driver support for imx8mm") Signed-off-by: Peng Fan Signed-off-by: Shawn Guo Signed-off-by: Greg Kroah-Ha

[PATCH 5.1 371/371] dm bufio: fix deadlock with loop device

2019-07-24 Thread Greg Kroah-Hartman
From: Junxiao Bi commit bd293d071ffe65e645b4d8104f9d8fe15ea13862 upstream. When thin-volume is built on loop device, if available memory is low, the following deadlock can be triggered: One process P1 allocates memory with GFP_FS flag, direct alloc fails, memory reclaim invokes memory shrinker

[PATCH 5.1 369/371] dt-bindings: allow up to four clocks for orion-mdio

2019-07-24 Thread Greg Kroah-Hartman
From: Josua Mayer commit 80785f5a22e9073e2ded5958feb7f220e066d17b upstream. Armada 8040 needs four clocks to be enabled for MDIO accesses to work. Update the binding to allow the extra clock to be specified. Cc: sta...@vger.kernel.org Fixes: 6d6a331f44a1 ("dt-bindings: allow up to three clocks

[PATCH 5.1 346/371] gpu: ipu-v3: ipu-ic: Fix saturation bit offset in TPMEM

2019-07-24 Thread Greg Kroah-Hartman
From: Steve Longerbeam commit 3d1f62c686acdedf5ed9642b763f3808d6a47d1e upstream. The saturation bit was being set at bit 9 in the second 32-bit word of the TPMEM CSC. This isn't correct, the saturation bit is bit 42, which is bit 10 of the second word. Fixes: 1aa8ea0d2bd5d ("gpu: ipu-v3: Add Im

[PATCH 5.1 347/371] parisc: Ensure userspace privilege for ptraced processes in regset functions

2019-07-24 Thread Greg Kroah-Hartman
From: Helge Deller commit 34c32fc603311a72cb558e5e337555434f64c27b upstream. On parisc the privilege level of a process is stored in the lowest two bits of the instruction pointers (IAOQ0 and IAOQ1). On Linux we use privilege level 0 for the kernel and privilege level 3 for user-space. So usersp

[PATCH 5.1 340/371] mm/nvdimm: add is_ioremap_addr and use that to check ioremap address

2019-07-24 Thread Greg Kroah-Hartman
From: Aneesh Kumar K.V commit 9bd3bb6703d8c0a5fb8aec8e3287bd55b7341dcd upstream. Architectures like powerpc use different address range to map ioremap and vmalloc range. The memunmap() check used by the nvdimm layer was wrongly using is_vmalloc_addr() to check for ioremap range which fails for

[PATCH 4.19 011/271] wil6210: fix spurious interrupts in 3-msi

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit e10b0eddd5235aa5aef4e40b970e34e735611a80 ] Interrupt is set in ICM (ICR & ~IMV) rising trigger. As the driver masks the IRQ after clearing it, there can be a race where an additional spurious interrupt is triggered when the driver unmask the IRQ. This can happen in case HW trigge

[PATCH 4.19 010/271] ath10k: add peer id check in ath10k_peer_find_by_id

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 49ed34b835e231aa941257394716bc689bc98d9f ] For some SDIO chip, the peer id is 65535 for MPDU with error status, then test_bit will trigger buffer overflow for peer's memory, if kasan enabled, it will report error. Reason is when station is in disconnecting status, firmware do no

[PATCH 5.1 348/371] parisc: Fix kernel panic due invalid values in IAOQ0 or IAOQ1

2019-07-24 Thread Greg Kroah-Hartman
From: Helge Deller commit 10835c854685393a921b68f529bf740fa7c9984d upstream. On parisc the privilege level of a process is stored in the lowest two bits of the instruction pointers (IAOQ0 and IAOQ1). On Linux we use privilege level 0 for the kernel and privilege level 3 for user-space. So usersp

[PATCH 4.19 018/271] media: ov7740: avoid invalid framesize setting

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 6e4ab830ac6d6a0d7cd7f87dc5d6536369bf24a8 ] If the requested framesize by VIDIOC_SUBDEV_S_FMT is larger than supported framesizes, it causes an out of bounds array access and the resulting framesize is unexpected. Avoid out of bounds array access and select the default framesize.

[PATCH 4.19 016/271] media: spi: IR LED: add missing of table registration

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 24e4cf770371df6ad49ed873f21618d9878f64c8 ] MODULE_DEVICE_TABLE(of, should be called to complete DT OF mathing mechanism and register it. Before this patch: modinfo drivers/media/rc/ir-spi.ko | grep alias After this patch: modinfo drivers/media/rc/ir-spi.ko | grep alias alias

[PATCH 4.19 002/271] MIPS: fix build on non-linux hosts

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 1196364f21ffe5d1e6d83cafd6a2edb89404a3ae ] calc_vmlinuz_load_addr.c requires SZ_64K to be defined for alignment purposes. It included "../../../../include/linux/sizes.h" to define that size, however "sizes.h" tries to include which assumes linux system headers. These may not e

[PATCH 4.19 023/271] net: stmmac: dwmac4/5: Clear unused address entries

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 0620ec6c62a5a07625b65f699adc5d1b90394ee6 ] In case we don't use a given address entry we need to clear it because it could contain previous values that are no longer valid. Found out while running stmmac selftests. Signed-off-by: Jose Abreu Cc: Joao Pinto Cc: David S. Miller

[PATCH 4.19 017/271] crypto: talitos - fix skcipher failure due to wrong output IV

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 3e03e792865ae48b8cfc69a0b4d65f02f467389f ] Selftests report the following: [2.984845] alg: skcipher: cbc-aes-talitos encryption test failed (wrong output IV) on test vector 0, cfg="in-place" [2.995377] : 3d af ba 42 9d 9e b4 30 b4 22 da 80 2c 9f ac 41 [3.032

[PATCH 4.19 013/271] regmap: debugfs: Fix memory leak in regmap_debugfs_init

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 2899872b627e99b7586fe3b6c9f861da1b4d5072 ] As detected by kmemleak running on i.MX6ULL board: nreferenced object 0xd8366600 (size 64): comm "swapper/0", pid 1, jiffies 4294937370 (age 933.220s) hex dump (first 32 bytes): 64 75 6d 6d 79 2d 69 6f 6d 75 78 63 2d 67 70 72 d

[PATCH 4.19 022/271] net: stmmac: dwmac1000: Clear unused address entries

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 9463c445590091202659cdfdd44b236acadfbd84 ] In case we don't use a given address entry we need to clear it because it could contain previous values that are no longer valid. Found out while running stmmac selftests. Signed-off-by: Jose Abreu Cc: Joao Pinto Cc: David S. Miller

[PATCH 4.19 025/271] signal/pid_namespace: Fix reboot_pid_ns to use send_sig not force_sig

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit f9070dc94542093fd516ae4ccea17ef46a4362c5 ] The locking in force_sig_info is not prepared to deal with a task that exits or execs (as sighand may change). The is not a locking problem in force_sig as force_sig is only built to handle synchronous exceptions. Further the function

[PATCH 4.19 021/271] media: media_device_enum_links32: clean a reserved field

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit f49308878d7202e07d8761238e01bd0e5fce2750 ] In v4l2-compliance utility, test MEDIA_IOC_ENUM_ENTITIES will check whether reserved field of media_links_enum filled with zero. However, for 32 bit program, the reserved field is missing copy from kernel space to user space in media_de

[PATCH 4.19 012/271] ath: DFS JP domain W56 fixed pulse type 3 RADAR detection

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit d8792393a783158cbb2c39939cb897dc5e5299b6 ] Increase pulse width range from 1-2usec to 0-4usec. During data traffic HW occasionally fails detecting radar pulses, so that SW cannot get enough radar reports to achieve the success rate. Tested ath10k hw and fw: * QCA9888(10.

[PATCH 4.19 019/271] media: marvell-ccic: fix DMA s/g desc number calculation

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 0c7aa32966dab0b8a7424e1b34c7f206817953ec ] The commit d790b7eda953 ("[media] vb2-dma-sg: move dma_(un)map_sg here") left dma_desc_nent unset. It previously contained the number of DMA descriptors as returned from dma_map_sg(). We can now (since the commit referred to above) obta

[PATCH 4.19 028/271] xfrm: Fix xfrm sel prefix length validation

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit b38ff4075a80b4da5cb2202d7965332ca0efb213 ] Family of src/dst can be different from family of selector src/dst. Use xfrm selector family to validate address prefix length, while verifying new sa from userspace. Validated patch with this command: ip xfrm state add src 1.1.6.1 dst

[PATCH 4.19 026/271] signal/cifs: Fix cifs_put_tcp_session to call send_sig instead of force_sig

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 72abe3bcf0911d69b46c1e8bdb5612675e0ac42c ] The locking in force_sig_info is not prepared to deal with a task that exits or execs (as sighand may change). The is not a locking problem in force_sig as force_sig is only built to handle synchronous exceptions. Further the function

[PATCH 4.19 027/271] af_key: fix leaks in key_pol_get_resp and dump_sp.

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 7c80eb1c7e2b8420477fbc998971d62a648035d9 ] In both functions, if pfkey_xfrm_policy2msg failed we leaked the newly allocated sk_buff. Free it on error. Fixes: 55569ce256ce ("Fix conversion between IPSEC_MODE_xxx and XFRM_MODE_xxx.") Reported-by: syzbot+4f0529365f7f2208d...@syzka

[PATCH 4.19 003/271] arm64/efi: Mark __efistub_stext_offset as an absolute symbol explicitly

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit aa69fb62bea15126e744af2e02acc0d6cf3ed4da ] After r363059 and r363928 in LLVM, a build using ld.lld as the linker with CONFIG_RANDOMIZE_BASE enabled fails like so: ld.lld: error: relocation R_AARCH64_ABS32 cannot be used against symbol __efistub_stext_offset; recompile with -fPIC

[PATCH 4.19 004/271] scsi: iscsi: set auth_protocol back to NULL if CHAP_A value is not supported

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 5dd6c49339126c2c8df2179041373222362d6e49 ] If the CHAP_A value is not supported, the chap_server_open() function should free the auth_protocol pointer and set it to NULL, or we will leave a dangling pointer around. [ 66.010905] Unsupported CHAP_A value [ 66.011660] Security

[PATCH 4.19 033/271] media: staging: media: davinci_vpfe: - Fix for memory leak if decoder initialization fails.

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 6995a659101bd4effa41cebb067f9dc18d77520d ] Fix to avoid possible memory leak if the decoder initialization got failed.Free the allocated memory for file handle object before return in case decoder initialization fails. Signed-off-by: Shailendra Verma Signed-off-by: Mauro Carval

[PATCH 4.19 031/271] media: mc-device.c: dont memset __user pointer contents

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 518fa4e0e0da97ea2e17c95ab57647ce748a96e2 ] You can't memset the contents of a __user pointer. Instead, call copy_to_user to copy links.reserved (which is zeroed) to the user memory. This fixes this sparse warning: SPARSE:drivers/media/mc/mc-device.c drivers/media/mc/mc-device.c

[PATCH 4.19 038/271] batman-adv: Fix duplicated OGMs on NETDEV_UP

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 9e6b5648bbc4cd48fab62cecbb81e9cc3c6e7e88 ] The state of slave interfaces are handled differently depending on whether the interface is up or not. All active interfaces (IFF_UP) will transmit OGMs. But for B.A.T.M.A.N. IV, also non-active interfaces are scheduling (low TTL) OGMs o

[PATCH 4.19 006/271] wil6210: fix potential out-of-bounds read

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit bfabdd6997323adbedccb13a3fed1967fb8cf8f5 ] Notice that *rc* can evaluate to up to 5, include/linux/netdevice.h: enum gro_result { GRO_MERGED, GRO_MERGED_FREE, GRO_HELD, GRO_NORMAL, GRO_DROP, GRO_CONSUMED, }; typedef enum gro_result

[PATCH 4.19 008/271] ath9k: Check for errors when reading SREV register

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 2f90c7e5d09437a4d8d5546feaae9f1cf48cfbe1 ] Right now, if an error is encountered during the SREV register read (i.e. an EIO in ath9k_regread()), that error code gets passed all the way to __ath9k_hw_init(), where it is visible during the "Chip rev not supported" message. ath

[PATCH 4.19 036/271] crypto: talitos - Align SEC1 accesses to 32 bits boundaries.

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit c9cca7034b34a2d82e9a03b757de2485c294851c ] The MPC885 reference manual states: SEC Lite-initiated 8xx writes can occur only on 32-bit-word boundaries, but reads can occur on any byte boundary. Writing back a header read from a non-32-bit-word boundary will yield unpredictable re

Re: [PATCH v3 1/2] x86/mm: Identify the end of the kernel area to be reserved

2019-07-24 Thread Thomas Gleixner
On Wed, 24 Jul 2019, Greg KH wrote: > On Wed, Jul 24, 2019 at 06:03:41PM +0200, Thomas Gleixner wrote: > > > Gotta love old tool-chains :( > > > > Oh yes. /me does archaeology to find a VM with old stuff > > I can provide a binary if you can't find anything. Found GNU ld (GNU Binutils for Debian

[PATCH 4.19 047/271] crypto: inside-secure - do not rely on the hardware last bit for result descriptors

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 89332590427235680236b9470e851afc49b3caa1 ] When performing a transformation the hardware is given result descriptors to save the result data. Those result descriptors are batched using a 'first' and a 'last' bit. There are cases were more descriptors than needed are given to the

[PATCH 4.19 007/271] ath10k: Do not send probe response template for mesh

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 97354f2c432788e3163134df6bb144f4b6289d87 ] Currently mac80211 do not support probe response template for mesh point. When WMI_SERVICE_BEACON_OFFLOAD is enabled, host driver tries to configure probe response template for mesh, but it fails because the interface type is not NL80211

[PATCH 4.19 009/271] ath6kl: add some bounds checking

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 5d6751eaff672ea77642e74e92e6c0ac7f9709ab ] The "ev->traffic_class" and "reply->ac" variables come from the network and they're used as an offset into the wmi->stream_exist_for_ac[] array. Those variables are u8 so they can be 0-255 but the stream_exist_for_ac[] array only has WMM

[PATCH 4.19 049/271] net: axienet: Fix race condition causing TX hang

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 7de44285c1f69ccfbe8be1d6a16fcd956681fee6 ] It is possible that the interrupt handler fires and frees up space in the TX ring in between checking for sufficient TX ring space and stopping the TX queue in axienet_start_xmit. If this happens, the queue wake from the interrupt handle

[PATCH 4.19 048/271] net: fec: Do not use netdev messages too early

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit a19a0582363b9a5f8ba812f34f1b8df394898780 ] When a valid MAC address is not found the current messages are shown: fec 2188000.ethernet (unnamed net_device) (uninitialized): Invalid MAC address: 00:00:00:00:00:00 fec 2188000.ethernet (unnamed net_device) (uninitialized): Using ra

[PATCH 4.19 062/271] gpio: omap: ensure irq is enabled before wakeup

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit c859e0d479b3b4f6132fc12637c51e01492f31f6 ] Documentation states: NOTE: There must be a correlation between the wake-up enable and interrupt-enable registers. If a GPIO pin has a wake-up configured on it, it must also have the corresponding interrupt enabled (on one of th

[PATCH 4.19 059/271] media: fdp1: Support M3N and E3 platforms

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 4e8c120de9268fc26f583268b9d22e7d37c4595f ] New Gen3 R-Car platforms incorporate the FDP1 with an updated version register. No code change is required to support these targets, but they will currently report an error stating that the device can not be identified. Update the drive

[PATCH 4.19 055/271] perf test 6: Fix missing kvm module load for s390

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 53fe307dfd309e425b171f6272d64296a54f4dff ] Command # perf test -Fv 6 fails with error running test 100 'kvm-s390:kvm_s390_create_vm' failed to parse event 'kvm-s390:kvm_s390_create_vm', err -1, str 'unknown tracepoint' event syntax error: 'kvm-s390:kvm_s390_creat

[PATCH 4.19 040/271] media: wl128x: Fix some error handling in fm_v4l2_init_video_device()

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 69fbb3f47327d959830c94bf31893972b8c8f700 ] X-Originating-IP: [10.175.113.25] X-CFilter-Loop: Reflected The fm_v4l2_init_video_device() forget to unregister v4l2/video device in the error path, it could lead to UAF issue, eg, BUG: KASAN: use-after-free in atomic64_read include

[PATCH 4.19 066/271] selinux: fix empty write to keycreate file

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 464c258aa45b09f16aa0f05847ed8895873262d9 ] When sid == 0 (we are resetting keycreate_sid to the default value), we should skip the KEY__CREATE check. Before this patch, doing a zero-sized write to /proc/self/keycreate would check if the current task can create unlabeled keys (wh

[PATCH 4.19 057/271] irqchip/meson-gpio: Add support for Meson-G12A SoC

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit c64a9e804ccf86eb202bfd1c6a8c5233c75a0431 ] The Meson-G12A SoC uses the same GPIO interrupt controller IP block as the other Meson SoCs, A totle of 100 pins can be spied on, which is the sum of: - 223:100 undefined (no interrupt) - 99:97 3 pins on bank GPIOE - 96:77 20 pins o

[PATCH 4.19 056/271] perf report: Fix OOM error in TUI mode on s390

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 8a07aa4e9b7b0222129c07afff81634a884b2866 ] Debugging a OOM error using the TUI interface revealed this issue on s390: [tmricht@m83lp54 perf]$ cat /proc/kallsyms |sort 0001119b7158 B radix_tree_node_cachep 0001119b8000 B __bss_stop 0001119b8000 B _end 03ff800

[PATCH 4.19 051/271] RAS/CEC: Fix pfn insertion

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 6d8e294bf5f0e85c34e8b14b064e2965f53f38b0 ] When inserting random PFNs for debugging the CEC through (debugfs)/ras/cec/pfn, depending on the return value of pfn_set(), multiple values get inserted per a single write. That is because simple_attr_write() interprets a retval of 0 as

[PATCH 4.19 063/271] regmap: fix bulk writes on paged registers

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit db057679de3e9e6a03c1bcd5aee09b0d25fd9f5b ] On buses like SlimBus and SoundWire which does not support gather_writes yet in regmap, A bulk write on paged register would be silently ignored after programming page. This is because local variable 'ret' value in regmap_raw_write_impl(

[PATCH 4.19 068/271] ASoC: meson: axg-tdm: fix sample clock inversion

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit cb36ff785e868992e96e8b9e5a0c2822b680a9e2 ] The content of SND_SOC_DAIFMT_FORMAT_MASK is a number, not a bitfield, so the test to check if the format is i2s is wrong. Because of this the clock setting may be wrong. For example, the sample clock gets inverted in DSP B mode, when it

[PATCH 4.19 069/271] rcu: Force inlining of rcu_read_lock()

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 6da9f775175e516fc7229ceaa9b54f8f56aa7924 ] When debugging options are turned on, the rcu_read_lock() function might not be inlined. This results in lockdep's print_lock() function printing "rcu_read_lock+0x0/0x70" instead of rcu_read_lock()'s caller. For example: [ 10.579995]

[PATCH 4.19 074/271] blkcg, writeback: dead memcgs shouldnt contribute to writeback ownership arbitration

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 6631142229005e1b1c311a09efe9fb3cfdac8559 ] wbc_account_io() collects information on cgroup ownership of writeback pages to determine which cgroup should own the inode. Pages can stay associated with dead memcgs but we want to avoid attributing IOs to dead blkcgs as much as possi

[PATCH 4.19 073/271] block: null_blk: fix race condition for null_del_dev

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 7602843fd873cae43a444b83b14dfdd114a9659c ] Dulicate call of null_del_dev() will trigger null pointer error like below. The reason is a race condition between nullb_device_power_store() and nullb_group_drop_item(). CPU#0 CPU#1

[PATCH 4.19 042/271] cpupower : frequency-set -r option misses the last cpu in related cpu list

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 04507c0a9385cc8280f794a36bfff567c8cc1042 ] To set frequency on specific cpus using cpupower, following syntax can be used : cpupower -c #i frequency-set -f #f -r While setting frequency using cpupower frequency-set command, if we use '-r' option, it is expected to set frequency

[PATCH 4.19 044/271] perf jvmti: Address gcc string overflow warning for strncpy()

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 279ab04dbea1370d2eac0f854270369ccaef8a44 ] We are getting false positive gcc warning when we compile with gcc9 (9.1.1): CC jvmti/libjvmti.o In file included from /usr/include/string.h:494, from jvmti/libjvmti.c:5: In function ‘strncpy’,

[PATCH 4.19 070/271] x86/cpufeatures: Add FDP_EXCPTN_ONLY and ZERO_FCS_FDS

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit cbb99c0f588737ec98c333558922ce47e9a95827 ] Add the CPUID enumeration for Intel's de-feature bits to accommodate passing these de-features through to kvm guests. These de-features are (from SDM vol 1, section 8.1.8): - X86_FEATURE_FDP_EXCPTN_ONLY: If CPUID.(EAX=07H,ECX=0H):EBX[b

[PATCH 4.19 077/271] sched/fair: Fix "runnable_avg_yN_inv" not used warnings

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 509466b7d480bc5d22e90b9fbe6122ae0e2fbe39 ] runnable_avg_yN_inv[] is only used in kernel/sched/pelt.c but was included in several other places because they need other macros all came from kernel/sched/sched-pelt.h which was generated by Documentation/scheduler/sched-pelt. As the r

[PATCH 4.19 037/271] tua6100: Avoid build warnings.

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 621ccc6cc5f8d6730b740d31d4818227866c93c9 ] Rename _P to _P_VAL and _R to _R_VAL to avoid global namespace conflicts: drivers/media/dvb-frontends/tua6100.c: In function ‘tua6100_set_params’: drivers/media/dvb-frontends/tua6100.c:79: warning: "_P" redefined #define _P 32 In file

[PATCH 4.19 041/271] net: hns3: set ops to null when unregister ad_dev

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 594a81b39525f0a17e92c2e0b167ae1400650380 ] The hclge/hclgevf and hns3 module can be unloaded independently, when hclge/hclgevf unloaded firstly, the ops of ae_dev should be set to NULL, otherwise it will cause an use-after-free problem. Fixes: 38caee9d3ee8 ("net: hns3: Add suppo

[PATCH 4.19 043/271] arm64: mm: make CONFIG_ZONE_DMA32 configurable

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 0c1f14ed12262f45a3af1d588e4d7bd12438b8f5 ] This change makes CONFIG_ZONE_DMA32 defuly y and allows users to overwrite it only when CONFIG_EXPERT=y. For the SoCs that do not need CONFIG_ZONE_DMA32, this is the first step to manage all available memory by a single zone(normal zone

[PATCH 4.19 088/271] nvme-pci: properly report state change failure in nvme_reset_work

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit cee6c269b016ba89c62e34d6bccb103ee2c7de4f ] If the state change to NVME_CTRL_CONNECTING fails, the dmesg is going to be like: [ 293.689160] nvme nvme0: failed to mark controller CONNECTING [ 293.689160] nvme nvme0: Removing after probe failure status: 0 Even it prints the

[PATCH 4.19 079/271] x86/atomic: Fix smp_mb__{before,after}_atomic()

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 69d927bba39517d0980462efc051875b7f4db185 ] Recent probing at the Linux Kernel Memory Model uncovered a 'surprise'. Strongly ordered architectures where the atomic RmW primitive implies full memory ordering and smp_mb__{before,after}_atomic() are a simple barrier() (such as x86) f

[PATCH 4.19 089/271] nvme-pci: set the errno on ctrl state change error

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit e71afda49335620e3d9adf56015676db33a3bd86 ] This patch removes the confusing assignment of the variable result at the time of declaration and sets the value in error cases next to the places where the actual error is happening. Here we also set the result value to -ENODEV when we

[PATCH 4.19 050/271] s390/qdio: handle PENDING state for QEBSM devices

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 04310324c6f482921c071444833e70fe861b73d9 ] When a CQ-enabled device uses QEBSM for SBAL state inspection, get_buf_states() can return the PENDING state for an Output Queue. get_outbound_buffer_frontier() isn't prepared for this, and any PENDING buffer will permanently stall all f

[PATCH 4.19 090/271] lightnvm: pblk: fix freeing of merged pages

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 510fd8ea98fcb586c01aef93d87c060a159ac30a ] bio_add_pc_page() may merge pages when a bio is padded due to a flush. Fix iteration over the bio to free the correct pages in case of a merge. Signed-off-by: Heiner Litz Reviewed-by: Javier González Signed-off-by: Matias Bjørling Si

[PATCH 4.19 054/271] perf cs-etm: Properly set the value of old and head in snapshot mode

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit e45c48a9a4d20ebc7b639a62c3ef8f4b08007027 ] This patch adds the necessary intelligence to properly compute the value of 'old' and 'head' when operating in snapshot mode. That way we can get the latest information in the AUX buffer and be compatible with the generic AUX ring buffe

[PATCH 4.19 091/271] arm64: Do not enable IRQs for ct_user_exit

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 9034f6251572a4744597c51dea5ab73a55f2b938 ] For el0_dbg and el0_error, DAIF bits get explicitly cleared before calling ct_user_exit. When context tracking is disabled, DAIF gets set (almost) immediately after. When context tracking is enabled, among the first things done is disab

[PATCH 4.19 092/271] ipsec: select crypto ciphers for xfrm_algo

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 597179b0ba550bd83fab1a9d57c42a9343c58514 ] kernelci.org reports failed builds on arc because of what looks like an old missed 'select' statement: net/xfrm/xfrm_algo.o: In function `xfrm_probe_algs': xfrm_algo.c:(.text+0x1e8): undefined reference to `crypto_has_ahash' I don't se

[PATCH 4.19 053/271] ipset: Fix memory accounting for hash types on resize

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 11921796f4799ca9c61c4b22cc54d84aa69f8a35 ] If a fresh array block is allocated during resize, the current in-memory set size should be increased by the size of the block, not replaced by it. Before the fix, adding entries to a hash set type, leading to a table resize, caused an

[PATCH 4.19 094/271] media: s5p-mfc: Make additional clocks optional

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit e08efef8fe7db87206314c19b341612c719f891a ] Since the beginning the second clock ('special', 'sclk') was optional and it is not available on some variants of Exynos SoCs (i.e. Exynos5420 with v7 of MFC hardware). However commit 1bce6fb3edf1 ("[media] s5p-mfc: Rework clock handlin

[PATCH 4.19 096/271] ntp: Limit TAI-UTC offset

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit d897a4ab11dc8a9fda50d2eccc081a96a6385998 ] Don't allow the TAI-UTC offset of the system clock to be set by adjtimex() to a value larger than 10 seconds. This prevents an overflow in the conversion to int, prevents the CLOCK_TAI clock from getting too far ahead of the CLOCK_R

[PATCH 4.19 098/271] acpi/arm64: ignore 5.1 FADTs that are reported as 5.0

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 2af22f3ec3ca452f1e79b967f634708ff01ced8a ] Some Qualcomm Snapdragon based laptops built to run Microsoft Windows are clearly ACPI 5.1 based, given that that is the first ACPI revision that supports ARM, and introduced the FADT 'arm_boot_flags' field, which has a non-zero field on

[PATCH 4.19 101/271] media: coda: increment sequence offset for the last returned frame

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit b3b7d96817cdb8b6fc353867705275dce8f41ccc ] If no more frames are decoded in bitstream end mode, and a previously decoded frame has been returned, the firmware still increments the frame number. To avoid a sequence number mismatch after decoder restart, increment the sequence_offs

[PATCH 4.19 099/271] media: coda: fix mpeg2 sequence number handling

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 56d159a4ec6d8da7313aac6fcbb95d8fffe689ba ] Sequence number handling assumed that the BIT processor frame number starts counting at 1, but this is not true for the MPEG-2 decoder, which starts at 0. Fix the sequence counter offset detection to handle this. Signed-off-by: Philipp

[PATCH 4.19 100/271] media: coda: fix last buffer handling in V4L2_ENC_CMD_STOP

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit f3775f89852d167990b0d718587774cf00d22ac2 ] coda_encoder_cmd() is racy, as the last scheduled picture run worker can still be in-flight while the ENC_CMD_STOP command is issued. Depending on the exact timing the sequence numbers might already be changed, but the last buffer might

[PATCH 4.19 102/271] media: vimc: cap: check v4l2_fill_pixfmt return value

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 77ae46e11df5c96bb4582633851f838f5d954df4 ] v4l2_fill_pixfmt() returns -EINVAL if the pixelformat used as parameter is invalid or if the user is trying to use a multiplanar format with the singleplanar API. Currently, the vimc_cap_try_fmt_vid_cap() returns such value, but vimc_cap

[PATCH 4.19 080/271] perf evsel: Make perf_evsel__name() accept a NULL argument

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit fdbdd7e8580eac9bdafa532746c865644d125e34 ] In which case it simply returns "unknown", like when it can't figure out the evsel->name value. This makes this code more robust and fixes a problem in 'perf trace' where a NULL evsel was being passed to a routine that only used the evs

[PATCH 4.19 097/271] timer_list: Guard procfs specific code

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit a9314773a91a1d3b36270085246a6715a326ff00 ] With CONFIG_PROC_FS=n the following warning is emitted: kernel/time/timer_list.c:361:36: warning: unused variable 'timer_list_sops' [-Wunused-const-variable] static const struct seq_operations timer_list_sops = { Add #ifdef guard ar

[PATCH 4.19 093/271] ipvs: defer hook registration to avoid leaks

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit cf47a0b882a4e5f6b34c7949d7b293e9287f1972 ] syzkaller reports for memory leak when registering hooks [1] As we moved the nf_unregister_net_hooks() call into __ip_vs_dev_cleanup(), defer the nf_register_net_hooks() call, so that hooks are allocated and freed from same pernet_opera

[PATCH 4.19 095/271] media: i2c: fix warning same module names

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit b2ce5617dad254230551feda3599f2cc68e53ad8 ] When building with CONFIG_VIDEO_ADV7511 and CONFIG_DRM_I2C_ADV7511 enabled as loadable modules, we see the following warning: drivers/gpu/drm/bridge/adv7511/adv7511.ko drivers/media/i2c/adv7511.ko Rework so that the file is named a

[PATCH 4.19 076/271] sched/core: Add __sched tag for io_schedule()

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit e3b929b0a184edb35531153c5afcaebb09014f9d ] Non-inline io_schedule() was introduced in: commit 10ab56434f2f ("sched/core: Separate out io_schedule_prepare() and io_schedule_finish()") Keep in line with io_schedule_timeout(), otherwise "/proc//wchan" will report io_schedule()

[PATCH 4.19 075/271] xfrm: fix sa selector validation

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit b8d6d0079757cbd1b69724cfd1c08e2171c68cee ] After commit b38ff4075a80, the following command does not work anymore: $ ip xfrm state add src 10.125.0.2 dst 10.125.0.1 proto esp spi 34 reqid 1 \ mode tunnel enc 'cbc(aes)' 0xb0abdba8b782ad9d364ec81e3a7d82a1 auth-trunc \ 'hmac(sha

[PATCH 4.19 045/271] net: stmmac: dwmac4: fix flow control issue

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit ee326fd01e79dfa42014d55931260b68b9fa3273 ] Current dwmac4_flow_ctrl will not clear GMAC_RX_FLOW_CTRL_RFE/GMAC_RX_FLOW_CTRL_RFE bits, so MAC hw will keep flow control on although expecting flow control off by ethtool. Add codes to fix it. Fixes: 477286b53f55 ("stmmac: add GMAC4 c

[PATCH 4.19 072/271] net: hns3: fix for skb leak when doing selftest

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 8f9eed1a8791b83eb1c54c261d68424717e4111e ] If hns3_nic_net_xmit does not return NETDEV_TX_BUSY when doing a loopback selftest, the skb is not freed in hns3_clean_tx_ring or hns3_nic_net_xmit, which causes skb not freed problem. This patch fixes it by freeing skb when hns3_nic_ne

[PATCH 4.19 046/271] net: stmmac: modify default value of tx-frames

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit d2facb4b3983425f6776c24dd678a82dbe673773 ] the default value of tx-frames is 25, it's too late when passing tstamp to stack, then the ptp4l will fail: ptp4l -i eth0 -f gPTP.cfg -m ptp4l: selected /dev/ptp0 as PTP clock ptp4l: port 1: INITIALIZING to LISTENING on INITIALIZE ptp4l

[PATCH 4.19 071/271] qed: iWARP - Fix tc for MPA ll2 connection

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit cb94d52b93c74fe1f2595734fabeda9f8ae891ee ] The driver needs to assign a lossless traffic class for the MPA ll2 connection to ensure no packets are dropped when returning from the driver as they will never be re-transmitted by the peer. Fixes: ae3488ff37dc ("qed: Add ll2 connecti

Re: [RFC][Patch v11 2/2] virtio-balloon: page_hinting: reporting to the host

2019-07-24 Thread Nitesh Narayan Lal
On 7/24/19 3:47 PM, Michael S. Tsirkin wrote: > On Wed, Jul 10, 2019 at 03:51:58PM -0400, Nitesh Narayan Lal wrote: >> Enables the kernel to negotiate VIRTIO_BALLOON_F_HINTING feature with the >> host. If it is available and page_hinting_flag is set to true, page_hinting >> is enabled and its cal

[PATCH 4.19 067/271] x86/cpu: Add Ice Lake NNPI to Intel family

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit e32d045cd4ba06b59878323e434bad010e78e658 ] Add the CPUID model number of Ice Lake Neural Network Processor for Deep Learning Inference (ICL-NNPI) to the Intel family list. Ice Lake NNPI uses model number 0x9D and this will be documented in a future version of Intel Software Devel

[PATCH 4.19 064/271] bpf: silence warning messages in core

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit aee450cbe482a8c2f6fa5b05b178ef8b8ff107ca ] Compiling kernel/bpf/core.c with W=1 causes a flood of warnings: kernel/bpf/core.c:1198:65: warning: initialized field overwritten [-Woverride-init] 1198 | #define BPF_INSN_3_TBL(x, y, z) [BPF_##x | BPF_##y | BPF_##z] = true |

Re: [PATCH RFC v1 1/2] dt-bindings: mmc: Document the Amlogic Meson SDHC MMC host controller

2019-07-24 Thread Rob Herring
On Mon, 8 Jul 2019 19:33:29 +0200, Martin Blumenstingl wrote: > This documents the devicetree bindings for the SDHC MMC host controller > found in Meson6, Meson8, Meson8b and Meson8m2 SoCs. It can use a > bus-width of 1/4/8-bit and it supports eMMC spec 4.4x/4.5x including > HS200 mode (up to 100M

[PATCH 4.19 065/271] media: s5p-mfc: fix reading min scratch buffer size on MFC v6/v7

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit be22203aec440c1761ce8542c2636ac6c8951e3a ] MFC v6 and v7 has no register to read min scratch buffer size, so it has to be read conditionally only if hardware supports it. This fixes following NULL pointer exception on SoCs with MFC v6/v7: 8<--- cut here --- Unable to handle kern

[PATCH 4.19 058/271] media: uvcvideo: Fix access to uninitialized fields on probe error

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 11a087f484bf15ff65f0a9f277aa5a61fd07ed2a ] We need to check whether this work we are canceling actually is initialized. Signed-off-by: Oliver Neukum Reported-by: syzbot+2e1ef9188251d9cc7...@syzkaller.appspotmail.com Signed-off-by: Laurent Pinchart Signed-off-by: Mauro Carvalho

[PATCH 4.19 061/271] gpio: omap: fix lack of irqstatus_raw0 for OMAP4

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 64ea3e9094a1f13b96c33244a3fb3a0f45690bd2 ] Commit 384ebe1c2849 ("gpio/omap: Add DT support to GPIO driver") added the register definition tables to the gpio-omap driver. Subsequently to that commit, commit 4e962e8998cc ("gpio/omap: remove cpu_is_omap() checks from *_runtime_r

[PATCH 4.19 035/271] crypto: talitos - properly handle split ICV.

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit eae55a586c3c8b50982bad3c3426e9c9dd7a0075 ] The driver assumes that the ICV is as a single piece in the last element of the scatterlist. This assumption is wrong. This patch ensures that the ICV is properly handled regardless of the scatterlist layout. Fixes: 9c4a79653b35 ("cryp

[PATCH 4.19 000/271] 4.19.61-stable review

2019-07-24 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.19.61 release. There are 271 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 Fri 26 Jul 2019 07:13:35 PM UTC. Anything re

[PATCH 4.19 005/271] dmaengine: imx-sdma: fix use-after-free on probe error path

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 2b8066c3deb9140fdf258417a51479b2aeaa7622 ] If probe() fails anywhere beyond the point where sdma_get_firmware() is called, then a kernel oops may occur. Problematic sequence of events: 1. probe() calls sdma_get_firmware(), which schedules the firmware callback to run when fir

[PATCH 4.19 032/271] media: saa7164: fix remove_proc_entry warning

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 50710eeefbc1ed25375942aad0c4d1eb4af0f330 ] if saa7164_proc_create() fails, saa7164_fini() will trigger a warning, name 'saa7164' WARNING: CPU: 1 PID: 6311 at fs/proc/generic.c:672 remove_proc_entry+0x1e8/0x3a0 ? remove_proc_entry+0x1e8/0x3a0 ? try_stop_module+0x7b/0x240 ?

[PATCH 4.19 060/271] iommu: Fix a leak in iommu_insert_resv_region

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit ad0834dedaa15c3a176f783c0373f836e44b4700 ] In case we expand an existing region, we unlink this latter and insert the larger one. In that case we should free the original region after the insertion. Also we can immediately return. Fixes: 6c65fb318e8b ("iommu: iommu_get_group_res

[PATCH 4.19 039/271] locking/lockdep: Fix merging of hlocks with non-zero references

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit d9349850e188b8b59e5322fda17ff389a1c0cd7d ] The sequence static DEFINE_WW_CLASS(test_ww_class); struct ww_acquire_ctx ww_ctx; struct ww_mutex ww_lock_a; struct ww_mutex ww_lock_b; struct ww_mutex ww_lock_c; struct mutex lock_c;

[PATCH 4.19 034/271] net: phy: Check against net_device being NULL

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 82c76aca81187b3d28a6fb3062f6916450ce955e ] In general, we don't want MAC drivers calling phy_attach_direct with the net_device being NULL. Add checks against this in all the functions calling it: phy_attach() and phy_connect_direct(). Signed-off-by: Ioana Ciornei Suggested-by:

[PATCH 4.19 030/271] perf annotate TUI browser: Do not use member from variable within its own initialization

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit da2019633f0b5c105ce658aada333422d8cb28fe ] Some compilers will complain when using a member of a struct to initialize another member, in the same struct initialization. For instance: debian:8 Debian clang version 3.5.0-10 (tags/RELEASE_350/final) (based on LLVM 3.5.0)

[PATCH 4.19 052/271] net: sfp: add mutex to prevent concurrent state checks

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 2158e856f56bb762ef90f3ec244d41a519826f75 ] sfp_check_state can potentially be called by both a threaded IRQ handler and delayed work. If it is concurrently called, it could result in incorrect state management. Add a st_mutex to protect the state - this lock gets taken outside of

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