[PATCH 4.19 166/211] KVM: x86: set ctxt->have_exception in x86_decode_insn()

2019-10-03 Thread Greg Kroah-Hartman
From: Jan Dakinevich commit c8848cee74ff05638e913582a476bde879c968ad upstream. x86_emulate_instruction() takes into account ctxt->have_exception flag during instruction decoding, but in practice this flag is never set in x86_decode_insn(). Fixes: 6ea6e84309ca ("KVM: x86: inject exceptions

[PATCH 4.19 119/211] libtraceevent: Change users plugin directory

2019-10-03 Thread Greg Kroah-Hartman
From: Tzvetomir Stoyanov [ Upstream commit e97fd1383cd77c467d2aed7fa4e596789df83977 ] To be compliant with XDG user directory layout, the user's plugin directory is changed from ~/.traceevent/plugins to ~/.local/lib/traceevent/plugins/ Suggested-by: Patrick McLean Signed-off-by: Tzvetomir

[PATCH 4.19 154/211] IB/mlx5: Free mpi in mp_slave mode

2019-10-03 Thread Greg Kroah-Hartman
From: Danit Goldberg commit 5d44adebbb7e785939df3db36ac360f5e8b73e44 upstream. ib_add_slave_port() allocates a multiport struct but never frees it. Don't leak memory, free the allocated mpi struct during driver unload. Cc: Fixes: 32f69e4be269 ("{net, IB}/mlx5: Manage port association for

[PATCH 4.19 148/211] iwlwifi: fw: dont send GEO_TX_POWER_LIMIT command to FW version 36

2019-10-03 Thread Greg Kroah-Hartman
From: Luca Coelho commit fddbfeece9c7882cc47754c7da460fe427e3e85b upstream. The intention was to have the GEO_TX_POWER_LIMIT command in FW version 36 as well, but not all 8000 family got this feature enabled. The 8000 family is the only one using version 36, so skip this version entirely. If

[PATCH 4.19 167/211] KVM: x86: Manually calculate reserved bits when loading PDPTRS

2019-10-03 Thread Greg Kroah-Hartman
From: Sean Christopherson commit 16cfacc8085782dab8e365979356ce1ca87fd6cc upstream. Manually generate the PDPTR reserved bit mask when explicitly loading PDPTRs. The reserved bits that are being tracked by the MMU reflect the current paging mode, which is unlikely to be PAE paging in the vast

[PATCH 4.19 140/211] ALSA: hda - Drop unsol event handler for Intel HDMI codecs

2019-10-03 Thread Greg Kroah-Hartman
From: Takashi Iwai [ Upstream commit f2dbe87c5ac1f88e6007ba1f1374f4bd8a197fb6 ] We don't need to deal with the unsol events for Intel chips that are tied with the graphics via audio component notifier. Although the presence of the audio component is checked at the beginning of

[PATCH 4.19 139/211] e1000e: add workaround for possible stalled packet

2019-10-03 Thread Greg Kroah-Hartman
From: Kai-Heng Feng [ Upstream commit e5e9a2ecfe780975820e157b922edee715710b66 ] This works around a possible stalled packet issue, which may occur due to clock recovery from the PCH being too slow, when the LAN is transitioning from K1 at 1G link speed. Bugzilla:

[PATCH 4.19 115/211] ALSA: firewire-motu: add support for MOTU 4pre

2019-10-03 Thread Greg Kroah-Hartman
From: Takashi Sakamoto [ Upstream commit 6af86bdb8ad41f4cf1292d3b10857dc322758328 ] MOTU 4pre was launched in 2012 by MOTU, Inc. This commit allows userspace applications can transmit and receive PCM frames and MIDI messages for this model via ALSA PCM interface and RawMidi/Sequencer

[PATCH 4.19 145/211] btrfs: extent-tree: Make sure we only allocate extents from block groups with the same type

2019-10-03 Thread Greg Kroah-Hartman
From: Qu Wenruo [ Upstream commit 2a28468e525f3924efed7f29f2bc5a2926e7e19a ] [BUG] With fuzzed image and MIXED_GROUPS super flag, we can hit the following BUG_ON(): kernel BUG at fs/btrfs/delayed-ref.c:491! invalid opcode: [#1] PREEMPT SMP NOPTI CPU: 0 PID: 1849 Comm: sync Tainted:

[PATCH 4.19 206/211] CIFS: fix max ea value size

2019-10-03 Thread Greg Kroah-Hartman
From: Murphy Zhou commit 63d37fb4ce5ae7bf1e58f906d1bf25f036fe79b2 upstream. It should not be larger then the slab max buf size. If user specifies a larger size, it passes this check and goes straightly to SMB2_set_info_init performing an insecure memcpy. Signed-off-by: Murphy Zhou

[PATCH 4.19 173/211] ASoC: Intel: Fix use of potentially uninitialized variable

2019-10-03 Thread Greg Kroah-Hartman
From: Amadeusz Sławiński commit 810f3b860850148788fc1ed8a6f5f807199fed65 upstream. If ipc->ops.reply_msg_match is NULL, we may end up using uninitialized mask value. reported by smatch: sound/soc/intel/common/sst-ipc.c:266 sst_ipc_reply_find_msg() error: uninitialized symbol 'mask'.

[PATCH 4.19 184/211] memcg, kmem: do not fail __GFP_NOFAIL charges

2019-10-03 Thread Greg Kroah-Hartman
From: Michal Hocko commit e55d9d9bfb69405bd7615c0f8d229d8fafb3e9b8 upstream. Thomas has noticed the following NULL ptr dereference when using cgroup v1 kmem limit: BUG: unable to handle kernel NULL pointer dereference at 0008 PGD 0 P4D 0 Oops: [#1] PREEMPT SMP PTI CPU: 3 PID:

[PATCH 5.2 001/313] arcnet: provide a buffer big enough to actually receive packets

2019-10-03 Thread Greg Kroah-Hartman
From: Uwe Kleine-König [ Upstream commit 108639aac35eb57f1d0e8333f5fc8c7ff68df938 ] struct archdr is only big enough to hold the header of various types of arcnet packets. So to provide enough space to hold the data read from hardware provide a buffer large enough to hold a packet with maximal

Re: [PATCH] si2157: Add support for Logilink VG0022A.

2019-10-03 Thread Gon Solo
> No, I mean with the first patch you sent to the ML, with the powerup > hack. Boot time: [4.653257] si2168 1-0067: Silicon Labs Si2168-B40 successfully identified [4.653259] si2168 1-0067: firmware version: B 4.0.2 [4.653279] usb 2-1: DVB: registering adapter 0 frontend 0 (Silicon

[PATCH 4.19 198/211] md: only call set_in_sync() when it is expected to succeed.

2019-10-03 Thread Greg Kroah-Hartman
From: NeilBrown commit 480523feae581ab714ba6610388a3b4619a2f695 upstream. Since commit 4ad23a976413 ("MD: use per-cpu counter for writes_pending"), set_in_sync() is substantially more expensive: it can wait for a full RCU grace period which can be 10s of milliseconds. So we should only call it

[PATCH 4.19 174/211] ARM: samsung: Fix system restart on S3C6410

2019-10-03 Thread Greg Kroah-Hartman
From: Lihua Yao commit 16986074035cc0205472882a00d404ed9d213313 upstream. S3C6410 system restart is triggered by watchdog reset. Cc: Fixes: 9f55342cc2de ("ARM: dts: s3c64xx: Fix infinite interrupt in soft mode") Signed-off-by: Lihua Yao Signed-off-by: Krzysztof Kozlowski Signed-off-by: Greg

[PATCH 4.19 181/211] efifb: BGRT: Improve efifb_bgrt_sanity_check

2019-10-03 Thread Greg Kroah-Hartman
From: Hans de Goede commit 51677dfcc17f88ed754143df670ff064eae67f84 upstream. For various reasons, at least with x86 EFI firmwares, the xoffset and yoffset in the BGRT info are not always reliable. Extensive testing has shown that when the info is correct, the BGRT image is always exactly

[PATCH 4.19 172/211] ASoC: Intel: Skylake: Use correct function to access iomem space

2019-10-03 Thread Greg Kroah-Hartman
From: Amadeusz Sławiński commit 17d29ff98fd4b70e9ccdac5e95e18a087e2737ef upstream. For copying from __iomem, we should use __ioread32_copy. reported by sparse: sound/soc/intel/skylake/skl-debug.c:437:34: warning: incorrect type in argument 1 (different address spaces)

[PATCH 4.19 171/211] ASoC: Intel: NHLT: Fix debug print format

2019-10-03 Thread Greg Kroah-Hartman
From: Amadeusz Sławiński commit 855a06da37a773fd073d51023ac9d07988c87da8 upstream. oem_table_id is 8 chars long, so we need to limit it, otherwise it may print some unprintable characters into dmesg. Signed-off-by: Amadeusz Sławiński Link:

[PATCH 4.19 203/211] quota: fix wrong condition in is_quota_modification()

2019-10-03 Thread Greg Kroah-Hartman
From: Chao Yu commit 6565c182094f69e4ffdece337d395eb7ec760efc upstream. Quoted from commit 3da40c7b0898 ("ext4: only call ext4_truncate when size <= isize") " At LSF we decided that if we truncate up from isize we shouldn't trim fallocated blocks that were fallocated with KEEP_SIZE and are

[PATCH 4.19 195/211] Btrfs: fix race setting up and completing qgroup rescan workers

2019-10-03 Thread Greg Kroah-Hartman
From: Filipe Manana commit 13fc1d271a2e3ab8a02071e711add01fab9271f6 upstream. There is a race between setting up a qgroup rescan worker and completing a qgroup rescan worker that can lead to callers of the qgroup rescan wait ioctl to either not wait for the rescan worker to complete or to hang

[PATCH 4.19 210/211] mm/compaction.c: clear total_{migrate,free}_scanned before scanning a new zone

2019-10-03 Thread Greg Kroah-Hartman
From: Yafang Shao [ Upstream commit a94b525241c0fff3598809131d7cfcfe1d572d8c ] total_{migrate,free}_scanned will be added to COMPACTMIGRATE_SCANNED and COMPACTFREE_SCANNED in compact_zone(). We should clear them before scanning a new zone. In the proc triggered compaction, we forgot clearing

[PATCH 4.19 183/211] memcg, oom: dont require __GFP_FS when invoking memcg OOM killer

2019-10-03 Thread Greg Kroah-Hartman
From: Tetsuo Handa commit f9c645621a28e37813a1de96d9cbd89cde94a1e4 upstream. Masoud Sharbiani noticed that commit 29ef680ae7c21110 ("memcg, oom: move out_of_memory back to the charge path") broke memcg OOM called from __xfs_filemap_fault() path. It turned out that try_charge() is retrying

[PATCH 4.19 159/211] ALSA: hda/realtek - PCI quirk for Medion E4254

2019-10-03 Thread Greg Kroah-Hartman
From: Jan-Marek Glogowski [ Upstream commit bd9c10bc663dd2eaac8fe39dad0f18cd21527446 ] The laptop has a combined jack to attach headsets on the right. The BIOS encodes them as two different colored jacks at the front, but otherwise it seems to be configured ok. But any adaption of the pins

[PATCH 4.19 162/211] powerpc/imc: Dont create debugfs files for cpu-less nodes

2019-10-03 Thread Greg Kroah-Hartman
From: Madhavan Srinivasan commit 41ba17f20ea835c489e77bd54e2da73184e22060 upstream. Commit <684d984038aa> ('powerpc/powernv: Add debugfs interface for imc-mode and imc') added debugfs interface for the nest imc pmu devices to support changing of different ucode modes. Primarily adding this

[PATCH 4.19 193/211] btrfs: qgroup: Fix the wrong target io_tree when freeing reserved data space

2019-10-03 Thread Greg Kroah-Hartman
From: Qu Wenruo commit bab32fc069ce8829c416e8737c119f62a57970f9 upstream. [BUG] Under the following case with qgroup enabled, if some error happened after we have reserved delalloc space, then in error handling path, we could cause qgroup data space leakage: >From btrfs_truncate_block() in

[PATCH 5.2 023/313] vrf: Do not attempt to create IPv6 mcast rule if IPv6 is disabled

2019-10-03 Thread Greg Kroah-Hartman
From: David Ahern [ Upstream commit dac91170f8e9c73784af5fad6225e954b795601c ] A user reported that vrf create fails when IPv6 is disabled at boot using 'ipv6.disable=1': https://bugzilla.kernel.org/show_bug.cgi?id=204903 The failure is adding fib rules at create time. Add RTNL_FAMILY_IP6MR

[PATCH 5.2 014/313] selftests: Update fib_tests to handle missing ping6

2019-10-03 Thread Greg Kroah-Hartman
From: David Ahern [ Upstream commit 0360894a05ed52be268e3c4d40b2df9d94975fa6 ] Some distributions (e.g., debian buster) do not install ping6. Re-use the hook in pmtu.sh to detect this and fallback to ping. Fixes: a0e11da78f48 ("fib_tests: Add tests for metrics on routes") Signed-off-by: David

[PATCH 5.2 030/313] ax25: enforce CAP_NET_RAW for raw sockets

2019-10-03 Thread Greg Kroah-Hartman
From: Ori Nimron [ Upstream commit 0614e2b73768b502fc32a75349823356d98aae2c ] When creating a raw AF_AX25 socket, CAP_NET_RAW needs to be checked first. Signed-off-by: Ori Nimron Signed-off-by: Greg Kroah-Hartman Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman ---

[PATCH 5.2 026/313] tcp: better handle TCP_USER_TIMEOUT in SYN_SENT state

2019-10-03 Thread Greg Kroah-Hartman
From: Eric Dumazet [ Upstream commit a66b10c05ee2d744189e9a2130394b070883d289 ] Yuchung Cheng and Marek Majkowski independently reported a weird behavior of TCP_USER_TIMEOUT option when used at connect() time. When the TCP_USER_TIMEOUT is reached, tcp_write_timeout() believes the flow should

[PATCH 5.2 022/313] net_sched: add policy validation for action attributes

2019-10-03 Thread Greg Kroah-Hartman
From: Cong Wang [ Upstream commit 199ce850ce112315cfc68d42b694bcaa27b097b7 ] Similar to commit 8b4c3cdd9dd8 ("net: sched: Add policy validation for tc attributes"), we need to add proper policy validation for TC action attributes too. Cc: David Ahern Cc: Jamal Hadi Salim Signed-off-by: Cong

[PATCH 4.19 189/211] ovl: filter of trusted xattr results in audit

2019-10-03 Thread Greg Kroah-Hartman
From: Mark Salyzyn commit 5c2e9f346b815841f9bed6029ebcb06415caf640 upstream. When filtering xattr list for reading, presence of trusted xattr results in a security audit log. However, if there is other content no errno will be set, and if there isn't, the errno will be -ENODATA and not -EPERM

[PATCH 5.2 024/313] net/mlx5e: Fix traffic duplication in ethtool steering

2019-10-03 Thread Greg Kroah-Hartman
From: Saeed Mahameed [ Upstream commit d22fcc806b84b9818de08b32e494f3c05dd236c7 ] Before this patch, when adding multiple ethtool steering rules with identical classification, the driver used to append the new destination to the already existing hw rule, which caused the hw to forward the

[PATCH 5.2 021/313] ipv4: Revert removal of rt_uses_gateway

2019-10-03 Thread Greg Kroah-Hartman
From: David Ahern [ Upstream commit 77d5bc7e6a6cf8bbeca31aab7f0c5449a5eee762 ] Julian noted that rt_uses_gateway has a more subtle use than 'is gateway set': https://lore.kernel.org/netdev/alpine.lfd.2.21.1909151104060.2...@ja.home.ssi.bg/ Revert that part of the commit referenced in the

[PATCH 4.19 190/211] btrfs: fix allocation of free space cache v1 bitmap pages

2019-10-03 Thread Greg Kroah-Hartman
From: Christophe Leroy commit 3acd48507dc43eeeb0a1fe965b8bad91cab904a7 upstream. Various notifications of type "BUG kmalloc-4096 () : Redzone overwritten" have been observed recently in various parts of the kernel. After some time, it has been made a relation with the use of BTRFS filesystem

[PATCH 5.2 034/313] ASoC: SOF: Intel: hda: Make hdac_device device-managed

2019-10-03 Thread Greg Kroah-Hartman
From: Ranjani Sridharan [ Upstream commit ef9bec27485fefb6b93168fea73fda0dc9638046 ] snd_hdac_ext_bus_device_exit() has been recently modified to no longer free the hdac device. SOF allocates memory for hdac_device and hda_hda_priv with kzalloc. Make them device-managed instead so that they

[PATCH 5.2 006/313] net: qrtr: Stop rx_worker before freeing node

2019-10-03 Thread Greg Kroah-Hartman
From: Bjorn Andersson [ Upstream commit 73f0c11d11329a0d6d205d4312b6e5d2512af7c5 ] As the endpoint is unregistered there might still be work pending to handle incoming messages, which will result in a use after free scenario. The plan is to remove the rx_worker, but until then (and for stable@)

[PATCH 5.2 045/313] media: mtk-cir: lower de-glitch counter for rc-mm protocol

2019-10-03 Thread Greg Kroah-Hartman
From: Sean Young [ Upstream commit 5dd4b89dc098bf22cd13e82a308f42a02c102b2b ] The rc-mm protocol can't be decoded by the mtk-cir since the de-glitch filter removes pulses/spaces shorter than 294 microseconds. Tested on a BananaPi R2. Signed-off-by: Sean Young Acked-by: Sean Wang

[PATCH 5.2 019/313] net: phy: micrel: add Asym Pause workaround for KSZ9021

2019-10-03 Thread Greg Kroah-Hartman
From: Hans Andersson [ Upstream commit 407d8098cb1ab338199f4753162799a488d87d23 ] The Micrel KSZ9031 PHY may fail to establish a link when the Asymmetric Pause capability is set. This issue is described in a Silicon Errata (DS8691D or DS8692D), which advises to always disable the

[PATCH 5.2 050/313] media: vivid: work around high stack usage with clang

2019-10-03 Thread Greg Kroah-Hartman
From: Arnd Bergmann [ Upstream commit 1a03f91c2c2419c3709c4554952c66695575e91c ] Building a KASAN-enabled kernel with clang ends up in a case where too much is inlined into vivid_thread_vid_cap() and the stack usage grows a lot, possibly when the register allocation fails to produce efficient

[PATCH 5.2 049/313] media: vb2: reorder checks in vb2_poll()

2019-10-03 Thread Greg Kroah-Hartman
From: Michael Tretter [ Upstream commit 8d86a15649957c182e90fa2b1267c16699bc12f1 ] When reaching the end of stream, V4L2 clients may expect the V4L2_EOS_EVENT before being able to dequeue the last buffer, which has the V4L2_BUF_FLAG_LAST flag set. If the vb2_poll() function first checks for

[PATCH 5.2 057/313] sched/deadline: Fix bandwidth accounting at all levels after offline migration

2019-10-03 Thread Greg Kroah-Hartman
From: Juri Lelli [ Upstream commit 59d06cea1198d665ba11f7e8c5f45b00ff2e4812 ] If a task happens to be throttled while the CPU it was running on gets hotplugged off, the bandwidth associated with the task is not correctly migrated with it when the replenishment timer fires (offline_migration).

[PATCH 5.2 051/313] media: hdpvr: Add device num check and handling

2019-10-03 Thread Greg Kroah-Hartman
From: Luke Nowakowski-Krijger [ Upstream commit d4a6a9537bc32811486282206ecfb7c53754b74d ] Add hdpvr device num check and error handling We need to increment the device count atomically before we checkout a device to make sure that we do not reach the max count, otherwise we get out-of-bounds

[PATCH 5.2 054/313] sched/fair: Fix imbalance due to CPU affinity

2019-10-03 Thread Greg Kroah-Hartman
From: Vincent Guittot [ Upstream commit f6cad8df6b30a5d2bbbd2e698f74b4cafb9fb82b ] The load_balance() has a dedicated mecanism to detect when an imbalance is due to CPU affinity and must be handled at parent level. In this case, the imbalance field of the parent's sched_group is set. The

[PATCH 5.2 065/313] cpuidle: teo: Allow tick to be stopped if PM QoS is used

2019-10-03 Thread Greg Kroah-Hartman
From: Rafael J. Wysocki [ Upstream commit cab09f3d2d2a0a6cb3dfb678660d67a2c3764f50 ] The TEO goveror prevents the scheduler tick from being stopped (unless stopped already) if there is a PM QoS latency constraint for the given CPU and the target residency of the deepest idle state matching that

[PATCH 5.2 055/313] sched/core: Fix CPU controller for !RT_GROUP_SCHED

2019-10-03 Thread Greg Kroah-Hartman
From: Juri Lelli [ Upstream commit a07db5c0865799ebed1f88be0df50c581fb65029 ] On !CONFIG_RT_GROUP_SCHED configurations it is currently not possible to move RT tasks between cgroups to which CPU controller has been attached; but it is oddly possible to first move tasks around and then make them

[PATCH 5.2 067/313] soc: amlogic: meson-clk-measure: protect measure with a mutex

2019-10-03 Thread Greg Kroah-Hartman
From: Neil Armstrong [ Upstream commit 3a760d986568b67d1f8411dab64608075817b90d ] In order to protect clock measuring when multiple process asks for a measure, protect the main measure function with mutexes. Reviewed-by: Kevin Hilman Reviewed-by: Martin Blumenstingl Signed-off-by: Neil

[PATCH 5.2 062/313] ALSA: i2c: ak4xxx-adda: Fix a possible null pointer dereference in build_adc_controls()

2019-10-03 Thread Greg Kroah-Hartman
From: Jia-Ju Bai [ Upstream commit 2127c01b7f63b06a21559f56a8c81a3c6535bd1a ] In build_adc_controls(), there is an if statement on line 773 to check whether ak->adc_info is NULL: if (! ak->adc_info || ! ak->adc_info[mixer_ch].switch_name) When ak->adc_info is NULL, it is used on

[PATCH 5.2 040/313] ASoC: sgtl5000: Fix charge pump source assignment

2019-10-03 Thread Greg Kroah-Hartman
From: Oleksandr Suvorov [ Upstream commit b6319b061ba279577fd7030a9848fbd6a17151e3 ] If VDDA != VDDIO and any of them is greater than 3.1V, charge pump source can be assigned automatically [1]. [1] https://www.nxp.com/docs/en/data-sheet/SGTL5000.pdf Signed-off-by: Oleksandr Suvorov

[PATCH 5.2 094/313] media: i2c: tda1997x: prevent potential NULL pointer access

2019-10-03 Thread Greg Kroah-Hartman
From: Wolfram Sang [ Upstream commit 2f822f1da08ac5c93e351e79d22920f08fa51baf ] i2c_new_dummy() can fail returning a NULL pointer. This is not checked and the returned pointer is blindly used. Convert to devm_i2c_new_dummy_client() which returns an ERR_PTR and also add a validity check. Using

[PATCH 5.2 089/313] blk-mq: Fix memory leak in blk_mq_init_allocated_queue error handling

2019-10-03 Thread Greg Kroah-Hartman
From: zhengbin [ Upstream commit 73d9c8d4c0017e21e1ff519474ceb1450484dc9a ] If blk_mq_init_allocated_queue->elevator_init_mq fails, need to release the previously requested resources. Fixes: d34849913819 ("blk-mq-sched: allow setting of default IO scheduler") Signed-off-by: zhengbin

[PATCH 5.2 035/313] cpufreq: ap806: Add NULL check after kcalloc

2019-10-03 Thread Greg Kroah-Hartman
From: Hariprasad Kelam [ Upstream commit 3355c91b79394593ebbb197c8e930a91826f4ff3 ] Add NULL check after kcalloc. Fix below issue reported by coccicheck ./drivers/cpufreq/armada-8k-cpufreq.c:138:1-12: alloc with no test, possible model on line 151 Signed-off-by: Hariprasad Kelam

[PATCH 5.2 041/313] firmware: qcom_scm: Use proper types for dma mappings

2019-10-03 Thread Greg Kroah-Hartman
From: Stephen Boyd [ Upstream commit 6e37ccf78a53296c6c7bf426065762c27829eb84 ] We need to use the proper types and convert between physical addresses and dma addresses here to avoid mismatch warnings. This is especially important on systems with a different size for dma addresses and physical

[PATCH 5.2 039/313] ASoC: sgtl5000: Fix of unmute outputs on probe

2019-10-03 Thread Greg Kroah-Hartman
From: Oleksandr Suvorov [ Upstream commit 631bc8f0134ae9620d86a96b8c5f9445d91a2dca ] To enable "zero cross detect" for ADC/HP, change HP_ZCD_EN/ADC_ZCD_EN bits only instead of writing the whole CHIP_ANA_CTRL register. Signed-off-by: Oleksandr Suvorov Reviewed-by: Marcel Ziswiler Reviewed-by:

[PATCH 5.2 078/313] RAS: Fix prototype warnings

2019-10-03 Thread Greg Kroah-Hartman
From: Valdis Klētnieks [ Upstream commit 0a54b809a3a2c31e1055b45b03708eb730222be1 ] When building with C=2 and/or W=1, legitimate warnings are issued about missing prototypes: CHECK drivers/ras/debugfs.c drivers/ras/debugfs.c:4:15: warning: symbol 'ras_debugfs_dir' was not declared.

[PATCH 5.2 074/313] md/raid1: end bio when the device faulty

2019-10-03 Thread Greg Kroah-Hartman
From: Yufen Yu [ Upstream commit eeba6809d8d58908b5ed1b5ceb5fcb09a98a7cad ] When write bio return error, it would be added to conf->retry_list and wait for raid1d thread to retry write and acknowledge badblocks. In narrow_write_error(), the error bio will be split in the unit of badblock shift

[PATCH 5.2 101/313] ARM: xscale: fix multi-cpu compilation

2019-10-03 Thread Greg Kroah-Hartman
From: Arnd Bergmann [ Upstream commit c7b68049943079550d4e6af0f10aa3aabd64131a ] Building a combined ARMv4+XScale kernel produces these and other build failures: /tmp/copypage-xscale-3aa821.s: Assembler messages: /tmp/copypage-xscale-3aa821.s:167: Error: selected processor does not support

[PATCH 5.2 097/313] arm64/efi: Move variable assignments after SECTIONS

2019-10-03 Thread Greg Kroah-Hartman
From: Kees Cook [ Upstream commit 90776dd1c427cbb4d381aa4b13338f1fb1d20f5e ] It seems that LLVM's linker does not correctly handle variable assignments involving section positions that are updated during the SECTIONS parsing. Commit aa69fb62bea1 ("arm64/efi: Mark __efistub_stext_offset as an

[PATCH 5.2 092/313] perf test vfs_getname: Disable ~/.perfconfig to get default output

2019-10-03 Thread Greg Kroah-Hartman
From: Arnaldo Carvalho de Melo [ Upstream commit 4fe94ce1c6ba678b5f12b94bb9996eea4fc99e85 ] To get the expected output we have to ignore whatever changes the user has in its ~/.perfconfig file, so set PERF_CONFIG to /dev/null to achieve that. Before: # egrep 'trace|show_' ~/.perfconfig

[PATCH 5.2 107/313] kasan/arm64: fix CONFIG_KASAN_SW_TAGS && KASAN_INLINE

2019-10-03 Thread Greg Kroah-Hartman
From: Mark Rutland [ Upstream commit 34b5560db40d2941cfbe82eca1641353d5aed1a9 ] The generic Makefile.kasan propagates CONFIG_KASAN_SHADOW_OFFSET into KASAN_SHADOW_OFFSET, but only does so for CONFIG_KASAN_GENERIC. Since commit: 6bd1d0be0e97936d ("arm64: kasan: Switch to using

[PATCH 5.2 115/313] ASoC: uniphier: Fix double reset assersion when transitioning to suspend state

2019-10-03 Thread Greg Kroah-Hartman
From: Kunihiko Hayashi [ Upstream commit c372a35550c8d60f673b20210eea58a06d6d38cb ] When transitioning to supend state, uniphier_aio_dai_suspend() is called and asserts reset lines and disables clocks. However, if there are two or more DAIs, uniphier_aio_dai_suspend() are called multiple

[PATCH 5.2 111/313] ARM: dts: imx7-colibri: disable HS400

2019-10-03 Thread Greg Kroah-Hartman
From: Stefan Agner [ Upstream commit a95fbda08ee20cd063ce5826e0df95a2c22ea8c5 ] Force HS200 by masking bit 63 of the SDHCI capability register. The i.MX ESDHC driver uses SDHCI_QUIRK2_CAPS_BIT63_FOR_HS400. With that the stack checks bit 63 to descide whether HS400 is available. Using

[PATCH 5.2 106/313] media: imx: mipi csi-2: Dont fail if initial state times-out

2019-10-03 Thread Greg Kroah-Hartman
From: Ezequiel Garcia [ Upstream commit 0d5078c7172c46db6c58718d817b9fcf769554b4 ] Not all sensors will be able to guarantee a proper initial state. This may be either because the driver is not properly written, or (probably unlikely) because the hardware won't support it. While the right

[PATCH 5.2 083/313] perf tools: Fix paths in include statements

2019-10-03 Thread Greg Kroah-Hartman
From: Luke Mujica [ Upstream commit 2b75863b0845764529e01014a5c90664d8044cbe ] These paths point to the wrong location but still work because they get picked up by a -I flag that happens to direct to the correct file. Fix paths to lead to the actual file location without help from include

[PATCH 5.2 118/313] ASoC: sun4i-i2s: Dont use the oversample to calculate BCLK

2019-10-03 Thread Greg Kroah-Hartman
From: Maxime Ripard [ Upstream commit 7df8f9a20196072162d9dc8fe99943f2d35f23d5 ] The BCLK divider should be calculated using the parameters that actually make the BCLK rate: the number of channels, the sampling rate and the sample width. We've been using the oversample_rate previously because

[PATCH 5.2 130/313] EDAC/amd64: Support more than two controllers for chip selects handling

2019-10-03 Thread Greg Kroah-Hartman
From: Yazen Ghannam [ Upstream commit d971e28e2ce4696fcc32998c8aced5e47701fffe ] The struct chip_select array that's used for saving chip select bases and masks is fixed at length of two. There should be one struct chip_select for each controller, so this array should be increased to support

[PATCH 5.2 076/313] md: dont set In_sync if array is frozen

2019-10-03 Thread Greg Kroah-Hartman
From: Guoqing Jiang [ Upstream commit 062f5b2ae12a153644c765e7ba3b0f825427be1d ] When a disk is added to array, the following path is called in mdadm. Manage_subdevs -> sysfs_freeze_array -> Manage_add -> sysfs_set_str(, NULL, "sync_action","idle") Then from

[PATCH 5.2 132/313] EDAC/amd64: Recognize DRAM device type ECC capability

2019-10-03 Thread Greg Kroah-Hartman
From: Yazen Ghannam [ Upstream commit f8be8e5680225ac9caf07d4545f8529b7395327f ] AMD Family 17h systems support x4 and x16 DRAM devices. However, the device type is not checked when setting mci.edac_ctl_cap. Set the appropriate capability flag based on the device type. Default to x8 DRAM

[PATCH 5.2 134/313] ARM: at91: move platform-specific asm-offset.h to arch/arm/mach-at91

2019-10-03 Thread Greg Kroah-Hartman
From: Masahiro Yamada [ Upstream commit 9fac85a6db822f2cd92dfe2e83e063b31a94 ] is only generated and included by arch/arm/mach-at91/, so it does not need to reside in the globally visible include/generated/. I renamed it to arch/arm/mach-at91/pm_data-offsets.h since the prefix 'at91_' is

[PATCH 5.2 135/313] soc: renesas: rmobile-sysc: Set GENPD_FLAG_ALWAYS_ON for always-on domain

2019-10-03 Thread Greg Kroah-Hartman
From: Geert Uytterhoeven [ Upstream commit af0bc634728c0bc6a3f66f911f227d5c6396db88 ] Currently the R-Mobile "always-on" PM Domain is implemented by returning -EBUSY from the generic_pm_domain.power_off() callback, and doing nothing in the generic_pm_domain.power_on() callback. However, this

[PATCH 5.2 137/313] PM / devfreq: Fix kernel oops on governor module load

2019-10-03 Thread Greg Kroah-Hartman
From: Ezequiel Garcia [ Upstream commit 7544fd7f384591038646d3cd9efb311ab4509e24 ] A bit unexpectedly (but still documented), request_module may return a positive value, in case of a modprobe error. This is currently causing issues in the devfreq framework. When a request_module exits with a

[PATCH 5.2 141/313] media: cec-notifier: clear cec_adap in cec_notifier_unregister

2019-10-03 Thread Greg Kroah-Hartman
From: Hans Verkuil [ Upstream commit 14d5511691e5290103bc480998bc322e68f139d4 ] If cec_notifier_cec_adap_unregister() is called before cec_unregister_adapter() then everything is OK (and this is the case today). But if it is the other way around, then cec_notifier_unregister() is called first,

[PATCH 5.2 149/313] media: ov9650: add a sanity check

2019-10-03 Thread Greg Kroah-Hartman
From: Mauro Carvalho Chehab [ Upstream commit 093347abc7a4e0490e3c962ecbde2dc272a8f708 ] As pointed by cppcheck: [drivers/media/i2c/ov9650.c:706]: (error) Shifting by a negative value is undefined behaviour [drivers/media/i2c/ov9650.c:707]: (error) Shifting by a negative value

[PATCH 5.2 121/313] ASoC: mchp-i2s-mcc: Fix unprepare of GCLK

2019-10-03 Thread Greg Kroah-Hartman
From: Codrin Ciubotariu [ Upstream commit 988b59467b2b14523a266957affbe9eca3e99fc9 ] If hw_free() gets called after hw_params(), GCLK remains prepared, preventing further use of it. This patch fixes this by unpreparing the clock in hw_free() or if hw_params() gets an error. Fixes: 7e0cdf545a55

Re: [Cocci] [RFC] scripts: Fix coccicheck failed

2019-10-03 Thread Markus Elfring
> Was this patch posted somewhere? Yes, of course. YueHaibing's update suggestions are available also by the usual mailing list archive interfaces. How do you think about to avoid the addition of the SmPL variable “virtual report” to the script “add_namespace.cocci” if you would dare to

[PATCH 5.2 138/313] ARM: OMAP2+: move platform-specific asm-offset.h to arch/arm/mach-omap2

2019-10-03 Thread Greg Kroah-Hartman
From: Masahiro Yamada [ Upstream commit ccf4975dca233b1d6a74752d6ab35c239edc0d58 ] is only generated and included by arch/arm/mach-omap2/, so it does not need to reside in the globally visible include/generated/. I renamed it to arch/arm/mach-omap2/pm-asm-offsets.h since the prefix 'ti-' is

[PATCH 5.2 157/313] x86/mm/pti: Do not invoke PTI functions when PTI is disabled

2019-10-03 Thread Greg Kroah-Hartman
From: Thomas Gleixner [ Upstream commit 990784b57731192b7d90c8d4049e6318d81e887d ] When PTI is disabled at boot time either because the CPU is not affected or PTI has been disabled on the command line, the boot code still calls into pti_finalize() which then unconditionally invokes:

[PATCH 5.2 147/313] perf script: Fix memory leaks in list_scripts()

2019-10-03 Thread Greg Kroah-Hartman
From: Gustavo A. R. Silva [ Upstream commit 3b4acbb92dbda4829e021e5c6d5410658849fa1c ] In case memory resources for *buf* and *paths* were allocated, jump to *out* and release them before return. Signed-off-by: Gustavo A. R. Silva Cc: Alexander Shishkin Cc: Andi Kleen Cc: Gustavo A. R.

[PATCH 5.2 154/313] x86/apic/vector: Warn when vector space exhaustion breaks affinity

2019-10-03 Thread Greg Kroah-Hartman
From: Neil Horman [ Upstream commit 743dac494d61d991967ebcfab92e4f80dc7583b3 ] On x86, CPUs are limited in the number of interrupts they can have affined to them as they only support 256 interrupt vectors per CPU. 32 vectors are reserved for the CPU and the kernel reserves another 22 for

[PATCH 5.2 153/313] sched/cpufreq: Align trace event behavior of fast switching

2019-10-03 Thread Greg Kroah-Hartman
From: Douglas RAILLARD [ Upstream commit 77c84dd1881d0f0176cb678d770bfbda26c54390 ] Fast switching path only emits an event for the CPU of interest, whereas the regular path emits an event for all the CPUs that had their frequency changed, i.e. all the CPUs sharing the same policy. With the

[PATCH 5.2 171/313] ACPI / PCI: fix acpi_pci_irq_enable() memory leak

2019-10-03 Thread Greg Kroah-Hartman
From: Wenwen Wang [ Upstream commit 29b49958cf73b439b17fa29e9a25210809a6c01c ] In acpi_pci_irq_enable(), 'entry' is allocated by kzalloc() in acpi_pci_irq_check_entry() (invoked from acpi_pci_irq_lookup()). However, it is not deallocated if acpi_pci_irq_valid() returns false, leading to a

[PATCH 5.2 117/313] tools headers: Fixup bitsperlong per arch includes

2019-10-03 Thread Greg Kroah-Hartman
From: Arnaldo Carvalho de Melo [ Upstream commit 42fc2e9ef9603a7948aaa4ffd8dfb94b30294ad8 ] We were getting the file by luck, from one of the paths in -I, fix it to get it from the proper place: $ cd tools/include/uapi/asm/ [acme@quaco asm]$ grep include bitsperlong.h #include

[PATCH 5.2 173/313] hwmon: (k10temp) Add support for AMD family 17h, model 70h CPUs

2019-10-03 Thread Greg Kroah-Hartman
From: Marcel Bocu [ Upstream commit 12163cfbfc0f804cc7d27bc20e8d266ce7459260 ] It would seem like model 70h is behaving in the same way as model 30h, so let's just add the new F3 PCI ID to the list of compatible devices. Unlike previous Ryzen/Threadripper, Ryzen gen 3 processors do not need

Re: [PATCH tip/core/rcu 1/9] rcu: Upgrade rcu_swap_protected() to rcu_replace()

2019-10-03 Thread Mathieu Desnoyers
- On Oct 3, 2019, at 9:08 AM, rostedt rost...@goodmis.org wrote: > On Thu, 03 Oct 2019 09:39:17 +0100 > David Howells wrote: > >> paul...@kernel.org wrote: >> >> > +#define rcu_replace(rcu_ptr, ptr, c) >> > \ >> > +({

[PATCH 5.2 126/313] media: mceusb: fix (eliminate) TX IR signal length limit

2019-10-03 Thread Greg Kroah-Hartman
From: A Sun [ Upstream commit 9fc3ce31f5bde660197f35135e90a1cced58aa2c ] Fix and eliminate mceusb's IR length limit for IR signals transmitted to the MCE IR blaster ports. An IR signal TX exceeding 306 pulse/space samples presently causes -EINVAL return error. There's no such limitation nor

[PATCH 5.2 123/313] ACPI / APEI: Release resources if gen_pool_add() fails

2019-10-03 Thread Greg Kroah-Hartman
From: Liguang Zhang [ Upstream commit 6abc7622271dc520f241462e2474c71723638851 ] Destroy ghes_estatus_pool and release memory allocated via vmalloc() on errors in ghes_estatus_pool_init() in order to avoid memory leaks. [ bp: do the labels properly and with descriptive names and massage. ]

[PATCH] usercopy: Add parentheses around assignment in test_copy_struct_from_user

2019-10-03 Thread Nathan Chancellor
Clang warns: lib/test_user_copy.c:96:10: warning: using the result of an assignment as a condition without parentheses [-Wparentheses] if (ret |= test(umem_src == NULL, "kmalloc failed")) ^~~ lib/test_user_copy.c:96:10: note: place

[PATCH 5.2 125/313] s390/kasan: provide uninstrumented __strlen

2019-10-03 Thread Greg Kroah-Hartman
From: Vasily Gorbik [ Upstream commit f45f7b5bdaa4828ce871cf03f7c01599a0de57a5 ] s390 kasan code uses sclp_early_printk to report initialization failures. The code doing that should not be instrumented, because kasan shadow memory has not been set up yet. Even though sclp_early_core.c is

[PATCH 5.2 182/313] x86/cpu: Add Tiger Lake to Intel family

2019-10-03 Thread Greg Kroah-Hartman
From: Gayatri Kammela [ Upstream commit 6e1c32c5dbb4b90eea8f964c2869d0bde050dbe0 ] Add the model numbers/CPUIDs of Tiger Lake mobile and desktop to the Intel family. Suggested-by: Tony Luck Signed-off-by: Gayatri Kammela Signed-off-by: Tony Luck Reviewed-by: Tony Luck Cc: Linus Torvalds

[PATCH 5.2 179/313] irqchip/sifive-plic: set max threshold for ignored handlers

2019-10-03 Thread Greg Kroah-Hartman
From: Christoph Hellwig [ Upstream commit 9ce06497c2722a0f9109e4cc3ce35b7a69617886 ] When running in M-mode, the S-mode plic handlers are still listed in the device tree. Ignore them by setting the maximum threshold. Signed-off-by: Christoph Hellwig Acked-by: Marc Zyngier Signed-off-by:

[PATCH 5.2 180/313] s390/crypto: xts-aes-s390 fix extra run-time crypto self tests finding

2019-10-03 Thread Greg Kroah-Hartman
From: Harald Freudenberger [ Upstream commit 9e323d45ba94262620a073a3f9945ca927c07c71 ] With 'extra run-time crypto self tests' enabled, the selftest for s390-xts fails with alg: skcipher: xts-aes-s390 encryption unexpectedly succeeded on test vector "random: len=0 klen=64";

[PATCH 5.2 176/313] dmaengine: ti: edma: Do not reset reserved paRAM slots

2019-10-03 Thread Greg Kroah-Hartman
From: Peter Ujfalusi [ Upstream commit c5dbe60664b3660f5ac5854e21273ea2e7ff698f ] Skip resetting paRAM slots marked as reserved as they might be used by other cores. Signed-off-by: Peter Ujfalusi Link: https://lore.kernel.org/r/20190823125618.8133-2-peter.ujfal...@ti.com Signed-off-by: Vinod

[PATCH 5.2 194/313] raid5: dont increment read_errors on EILSEQ return

2019-10-03 Thread Greg Kroah-Hartman
From: Nigel Croxon [ Upstream commit b76b4715eba0d0ed574f58918b29c1b2f0fa37a8 ] While MD continues to count read errors returned by the lower layer. If those errors are -EILSEQ, instead of -EIO, it should NOT increase the read_errors count. When RAID6 is set up on dm-integrity target that

[PATCH 5.2 183/313] platform/x86: intel_pmc_core: Do not ioremap RAM

2019-10-03 Thread Greg Kroah-Hartman
From: M. Vefa Bicakci [ Upstream commit 7d505758b1e556cdf65a5e451744fe0ae8063d17 ] On a Xen-based PVH virtual machine with more than 4 GiB of RAM, intel_pmc_core fails initialization with the following warning message from the kernel, indicating that the driver is attempting to ioremap RAM:

[PATCH 5.2 196/313] libertas: Add missing sentinel at end of if_usb.c fw_table

2019-10-03 Thread Greg Kroah-Hartman
From: Kevin Easton [ Upstream commit 764f3f1ecffc434096e0a2b02f1a6cc964a89df6 ] This sentinel tells the firmware loading process when to stop. Reported-and-tested-by: syzbot+98156c174c5a2cad9...@syzkaller.appspotmail.com Signed-off-by: Kevin Easton Signed-off-by: Kalle Valo Signed-off-by:

[PATCH 5.2 162/313] ALSA: firewire-motu: add support for MOTU 4pre

2019-10-03 Thread Greg Kroah-Hartman
From: Takashi Sakamoto [ Upstream commit 6af86bdb8ad41f4cf1292d3b10857dc322758328 ] MOTU 4pre was launched in 2012 by MOTU, Inc. This commit allows userspace applications can transmit and receive PCM frames and MIDI messages for this model via ALSA PCM interface and RawMidi/Sequencer

[PATCH 5.2 184/313] SoC: simple-card-utils: set 0Hz to sysclk when shutdown

2019-10-03 Thread Greg Kroah-Hartman
From: Katsuhiro Suzuki [ Upstream commit 2458adb8f92ad4d07ef7ab27c5bafa1d3f4678d6 ] This patch set 0Hz to sysclk when shutdown the card. Some codecs set rate constraints that derives from sysclk. This mechanism works correctly if machine drivers give fixed frequency. But simple-audio and

[PATCH 5.2 192/313] mmc: core: Add helper function to indicate if SDIO IRQs is enabled

2019-10-03 Thread Greg Kroah-Hartman
From: Ulf Hansson [ Upstream commit bd880b00697befb73eff7220ee20bdae4fdd487b ] To avoid each host driver supporting SDIO IRQs, from keeping track internally about if SDIO IRQs has been claimed, let's introduce a common helper function, sdio_irq_claimed(). The function returns true if SDIO IRQs

[PATCH 5.2 163/313] iommu/amd: Silence warnings under memory pressure

2019-10-03 Thread Greg Kroah-Hartman
From: Qian Cai [ Upstream commit 3d708895325b78506e8daf00ef31549476e8586a ] When running heavy memory pressure workloads, the system is throwing endless warnings, smartpqi :23:00.0: AMD-Vi: IOMMU mapping error in map_sg (io-pages: 5 reason: -12) Hardware name: HPE ProLiant DL385

[PATCH 5.2 166/313] iommu/iova: Avoid false sharing on fq_timer_on

2019-10-03 Thread Greg Kroah-Hartman
From: Eric Dumazet [ Upstream commit 0d87308cca2c124f9bce02383f1d9632c9be89c4 ] In commit 14bd9a607f90 ("iommu/iova: Separate atomic variables to improve performance") Jinyu Qi identified that the atomic_cmpxchg() in queue_iova() was causing a performance loss and moved critical fields so that

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