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

2019-10-03 Thread Paul E. McKenney
On Thu, Oct 03, 2019 at 12:35:30PM -0400, Mathieu Desnoyers wrote: > - On Oct 2, 2019, at 9:43 PM, paulmck paul...@kernel.org wrote: > > > From: "Paul E. McKenney" > > > > Although the rcu_swap_protected() macro follows the example of swap(), > > the interactions with RCU make its update of

[PATCH 5.3 321/344] md: dont report active array_state until after revalidate_disk() completes.

2019-10-03 Thread Greg Kroah-Hartman
From: NeilBrown commit 9d4b45d6af442237560d0bb5502a012baa5234b7 upstream. Until revalidate_disk() has completed, the size of a new md array will appear to be zero. So we shouldn't report, through array_state, that the array is active until that time. udev rules check array_state to see if the

[PATCH 5.3 319/344] ACPI / LPSS: Save/restore LPSS private registers also on Lynxpoint

2019-10-03 Thread Greg Kroah-Hartman
From: Jarkko Nikula commit 57b3006492a4c11b2d4a772b5b2905d544a32037 upstream. My assumption in commit b53548f9d9e4 ("spi: pxa2xx: Remove LPSS private register restoring during resume") that Intel Lynxpoint and compatible based chipsets may not need LPSS private registers saving and restoring

[PATCH 5.3 313/344] 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.3 312/344] btrfs: adjust dirty_metadata_bytes after writeback failure of extent buffer

2019-10-03 Thread Greg Kroah-Hartman
From: Dennis Zhou commit eb5b64f142504a597d67e2109d603055ff765e52 upstream. Before, if a eb failed to write out, we would end up triggering a BUG_ON(). As of f4340622e0226 ("btrfs: extent_io: Move the BUG_ON() in flush_write_bio() one level up"), we no longer BUG_ON(), so we should make life

[PATCH 5.3 309/344] 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.3 310/344] Btrfs: fix use-after-free when using the tree modification log

2019-10-03 Thread Greg Kroah-Hartman
From: Filipe Manana commit efad8a853ad2057f96664328a0d327a05ce39c76 upstream. At ctree.c:get_old_root(), we are accessing a root's header owner field after we have freed the respective extent buffer. This results in an use-after-free that can lead to crashes, and when CONFIG_DEBUG_PAGEALLOC is

[PATCH 5.3 314/344] btrfs: qgroup: Fix reserved data space leak if we have multiple reserve calls

2019-10-03 Thread Greg Kroah-Hartman
From: Qu Wenruo commit d4e204948fe3e0dc8e1fbf3f8f3290c9c2823be3 upstream. [BUG] The following script can cause btrfs qgroup data space leak: mkfs.btrfs -f $dev mount $dev -o nospace_cache $mnt btrfs subv create $mnt/subv btrfs quota en $mnt btrfs quota rescan -w $mnt btrfs qgroup

[PATCH 5.3 258/344] fuse: fix missing unlock_page in fuse_writepage()

2019-10-03 Thread Greg Kroah-Hartman
From: Vasily Averin commit d5880c7a8620290a6c90ced7a0e8bd0ad9419601 upstream. unlock_page() was missing in case of an already in-flight write against the same page. Signed-off-by: Vasily Averin Fixes: ff17be086477 ("fuse: writepage: skip already in flight") Cc: # v3.13 Signed-off-by: Miklos

[PATCH 5.3 288/344] 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 5.3 289/344] gfs2: clear buf_in_tr when ending a transaction in sweep_bh_for_rgrps

2019-10-03 Thread Greg Kroah-Hartman
From: Bob Peterson commit f0b444b349e33ae0d3dd93e25ca365482a5d17d4 upstream. In function sweep_bh_for_rgrps, which is a helper for punch_hole, it uses variable buf_in_tr to keep track of when it needs to commit pending block frees on a partial delete that overflows the transaction created for

[PATCH 5.3 266/344] kvm: x86: Add "significant index" flag to a few CPUID leaves

2019-10-03 Thread Greg Kroah-Hartman
From: Jim Mattson commit a06dcd625d6181747fac7f4c140b5a4c397a778c upstream. According to the Intel SDM, volume 2, "CPUID," the index is significant (or partially significant) for CPUID leaves 0FH, 10H, 12H, 17H, 18H, and 1FH. Add the corresponding flag to these CPUID leaves in do_host_cpuid().

[PATCH 5.3 263/344] 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 5.3 291/344] z3fold: fix memory leak in kmem cache

2019-10-03 Thread Greg Kroah-Hartman
From: Vitaly Wool commit 63398413c00c7836ea87a1fa205c91d2199b25cf upstream. Currently there is a leak in init_z3fold_page() -- it allocates handles from kmem cache even for headless pages, but then they are never used and never freed, so eventually kmem cache may get exhausted. This patch

[PATCH 5.3 298/344] rtw88: pci: Rearrange the memory usage for skb in RX ISR

2019-10-03 Thread Greg Kroah-Hartman
From: Jian-Hong Pan commit ee6db78f5db9bfe426c57a1ec9713827ebccd2d4 upstream. Testing with RTL8822BE hardware, when available memory is low, we frequently see a kernel panic and system freeze. First, rtw_pci_rx_isr encounters a memory allocation failure (trimmed): rx routine starvation

[PATCH 5.3 262/344] KVM: x86: always stop emulation on page fault

2019-10-03 Thread Greg Kroah-Hartman
From: Jan Dakinevich commit 8530a79c5a9f4e29e6ffb35ec1a79d81f4968ec8 upstream. inject_emulated_exception() returns true if and only if nested page fault happens. However, page fault can come from guest page tables walk, either nested or not nested. In both cases we should stop an attempt to

[PATCH 5.3 297/344] KEYS: trusted: correctly initialize digests and fix locking issue

2019-10-03 Thread Greg Kroah-Hartman
From: Roberto Sassu commit 9f75c82246313d4c2a6bc77e947b45655b3b5ad5 upstream. Commit 0b6cf6b97b7e ("tpm: pass an array of tpm_extend_digest structures to tpm_pcr_extend()") modifies tpm_pcr_extend() to accept a digest for each PCR bank. After modification, tpm_pcr_extend() expects that digests

[PATCH 5.3 294/344] 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.3 285/344] alarmtimer: Use EOPNOTSUPP instead of ENOTSUPP

2019-10-03 Thread Greg Kroah-Hartman
From: Thadeu Lima de Souza Cascardo commit f18ddc13af981ce3c7b7f26925f099e7c6929aba upstream. ENOTSUPP is not supposed to be returned to userspace. This was found on an OpenPower machine, where the RTC does not support set_alarm. On that system, a clock_nanosleep(CLOCK_REALTIME_ALARM, ...)

[PATCH 5.3 280/344] 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 5.3 284/344] iommu/arm-smmu-v3: Disable detection of ATS and PRI

2019-10-03 Thread Greg Kroah-Hartman
From: Will Deacon commit b5e86196b83fd68e065a7c811ab8925fb0dc3893 upstream. Detecting the ATS capability of the SMMU at probe time introduces a spinlock into the ->unmap() fast path, even when ATS is not actually in use. Furthermore, the ATC invalidation that exists is broken, as it occurs

[PATCH 5.3 274/344] spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when its not ours

2019-10-03 Thread Greg Kroah-Hartman
From: Vladimir Oltean commit d41f36a6464a85c06ad920703d878e4491d2c023 upstream. The DSPI interrupt can be shared between two controllers at least on the LX2160A. In that case, the driver for one controller might misbehave and consume the other's interrupt. Fix this by actually checking if any

[PATCH 5.3 273/344] spi: ep93xx: Repair SPI CS lookup tables

2019-10-03 Thread Greg Kroah-Hartman
From: Alexander Sverdlin commit 4fbc485324d2975c54201091dfad0a7dd4902324 upstream. The actual device name of the SPI controller being registered on EP93xx is "spi0" (as seen by gpiod_find_lookup_table()). This patch fixes all relevant lookup tables and the following failure (seen on EDB9302):

[PATCH 5.3 278/344] 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 5.3 279/344] staging: erofs: cannot set EROFS_V_Z_INITED_BIT if fill_inode_lazy fails

2019-10-03 Thread Greg Kroah-Hartman
From: Gao Xiang commit 3407a4198faf01c9d7596c45b8606834b8dfc2b7 upstream. As reported by erofs-utils fuzzer, unsupported compressed clustersize will make fill_inode_lazy fail, for such case we cannot set EROFS_V_Z_INITED_BIT since we need return failure for each z_erofs_map_blocks_iter().

Re: System hangs if NVMe/SSD is removed during suspend

2019-10-03 Thread Tejun Heo
Hello, Mika. On Wed, Oct 02, 2019 at 03:21:36PM +0300, Mika Westerberg wrote: > but from that discussion I don't see more generic solution to be > implemented. > > Any ideas we should fix this properly? Yeah, the only fix I can think of is not using freezable wq. It's just not a good idea and

[PATCH 5.3 277/344] 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 5.3 275/344] binfmt_elf: Do not move brk for INTERP-less ET_EXEC

2019-10-03 Thread Greg Kroah-Hartman
From: Kees Cook commit 7be3cb019db1cbd5fd5ffe6d64a23fefa4b6f229 upstream. When brk was moved for binaries without an interpreter, it should have been limited to ET_DYN only. In other words, the special case was an ET_DYN that lacks an INTERP, not just an executable that lacks INTERP. The bug

[PATCH 5.3 260/344] parisc: Disable HP HSC-PCI Cards to prevent kernel crash

2019-10-03 Thread Greg Kroah-Hartman
From: Helge Deller commit 5fa1659105fac63e0f3c199b476025c2e04111ce upstream. The HP Dino PCI controller chip can be used in two variants: as on-board controller (e.g. in B160L), or on an Add-On card ("Card-Mode") to bridge PCI components to systems without a PCI bus, e.g. to a HSC/GSC bus. One

[PATCH 5.3 224/344] drm: fix module name in edid_firmware log message

2019-10-03 Thread Greg Kroah-Hartman
From: Jani Nikula [ Upstream commit ade925995b172f1d7410d1c665b2f47c5e99bef0 ] The module is drm_kms_helper, not drm_kms_firmware. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=204549 Reported-by: Göran Uddeborg Fixes: ac6c35a4d8c7 ("drm: add backwards compatibility support for

[PATCH 5.3 227/344] zd1211rw: remove false assertion from zd_mac_clear()

2019-10-03 Thread Greg Kroah-Hartman
From: Oliver Neukum [ Upstream commit 7a2eb7367fdea72e448d1a847aa857f6caf8ea2f ] The function is called before the lock which is asserted was ever used. Just remove it. Reported-by: syzbot+74c65761783d66a9c...@syzkaller.appspotmail.com Signed-off-by: Oliver Neukum Signed-off-by: Kalle Valo

[PATCH 5.3 229/344] 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 5.3 220/344] ALSA: hda - Add a quirk model for fixing Huawei Matebook X right speaker

2019-10-03 Thread Greg Kroah-Hartman
From: Tomas Espeleta [ Upstream commit a2ef03fe617a8365fb7794531b11ba587509a9b9 ] [ This is rather a revival of the patch Tomas sent in months ago, but applying only with the quirk model option -- tiwai ] Hard coded coefficients to make Huawuei Matebook X right speaker work. The Matebook X

[PATCH 5.3 270/344] media: hantro: Set DMA max segment size

2019-10-03 Thread Greg Kroah-Hartman
From: Francois Buergisser commit c3c3509b86810293df5c524ef61421d8affc8bf0 upstream. The Hantro codec is typically used in platforms with an IOMMU, so we need to set a proper DMA segment size. Devices without an IOMMU will still fallback to default 64KiB segments. Cc: sta...@vger.kernel.org

[PATCH 5.3 259/344] fuse: fix beyond-end-of-page access in fuse_parse_cache()

2019-10-03 Thread Greg Kroah-Hartman
From: Tejun Heo commit e5854b1cdf6cb48a20e01e3bdad0476a4c60a077 upstream. With DEBUG_PAGEALLOC on, the following triggers. BUG: unable to handle page fault for address: 88859367c000 #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page PGD 3001067

[PATCH 5.3 268/344] media: videobuf-core.c: poll_wait needs a non-NULL buf pointer

2019-10-03 Thread Greg Kroah-Hartman
From: Hans Verkuil commit 6f51fdfd8229d5358c2d6e272cf73478866e8ddc upstream. poll_wait uses >done, but buf is NULL. Move the poll_wait to later in the function once buf is correctly set and only call it if it is non-NULL. Signed-off-by: Hans Verkuil Reported-by: Dan Carpenter Fixes:

[PATCH 5.3 256/344] tpm: Wrap the buffer from the caller to tpm_buf in tpm_send()

2019-10-03 Thread Greg Kroah-Hartman
From: Jarkko Sakkinen commit e13cd21ffd50a07b55dcc4d8c38cedf27f28eaa1 upstream. tpm_send() does not give anymore the result back to the caller. This would require another memcpy(), which kind of tells that the whole approach is somewhat broken. Instead, as Mimi suggested, this commit just wraps

[PATCH 5.3 248/344] ARM: dts: am3517-evm: Fix missing video

2019-10-03 Thread Greg Kroah-Hartman
From: Adam Ford commit 24cf23276a54dd2825d3e3965c1b1b453e2a113d upstream. A previous commit removed the panel-dpi driver, which made the video on the AM3517-evm stop working because it relied on the dpi driver for setting video timings. Now that the simple-panel driver is available in

[PATCH 5.3 251/344] blk-mq: add callback of .cleanup_rq

2019-10-03 Thread Greg Kroah-Hartman
From: Ming Lei [ Upstream commit 226b4fc75c78f9c497c5182d939101b260cfb9f3 ] SCSI maintains its own driver private data hooked off of each SCSI request, and the pridate data won't be freed after scsi_queue_rq() returns BLK_STS_RESOURCE or BLK_STS_DEV_RESOURCE. An upper layer driver (e.g. dm-rq)

[PATCH 5.3 239/344] ALSA: firewire-tascam: check intermediate state of clock status and retry

2019-10-03 Thread Greg Kroah-Hartman
From: Takashi Sakamoto commit e1a00b5b253a4f97216b9a33199a863987075162 upstream. 2 bytes in MSB of register for clock status is zero during intermediate state after changing status of sampling clock in models of TASCAM FireWire series. The duration of this state differs depending on cases.

[PATCH 5.3 250/344] 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 5.3 249/344] rcu/tree: Fix SCHED_FIFO params

2019-10-03 Thread Greg Kroah-Hartman
From: Peter Zijlstra [ Upstream commit 130d9c331bc59a8733b47c58ef197a2b1fa3ed43 ] A rather embarrasing mistake had us call sched_setscheduler() before initializing the parameters passed to it. Fixes: 1a763fd7c633 ("rcu/tree: Call setschedule() gp ktread to SCHED_FIFO outside of atomic

[PATCH 5.3 222/344] drm/amd/powerplay/smu7: enforce minimal VBITimeout (v2)

2019-10-03 Thread Greg Kroah-Hartman
From: Ahzo [ Upstream commit f659bb6dae58c113805f92822e4c16ddd3156b79 ] This fixes screen corruption/flickering on 75 Hz displays. v2: make print statement debug only (Alex) Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=102646 Reviewed-by: Evan Quan Signed-off-by: Ahzo

[PATCH 5.3 218/344] 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.3 185/344] 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 5.3 253/344] 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 5.3 245/344] IB/hfi1: Do not update hcrc for a KDETH packet during fault injection

2019-10-03 Thread Greg Kroah-Hartman
From: Kaike Wan commit b2590bdd0b1dfb91737e6cb07ebb47bd74957f7e upstream. When a KDETH packet is subject to fault injection during transmission, HCRC is supposed to be omitted from the packet so that the hardware on the receiver side would drop the packet. When creating pbc, the PbcInsertHcrc

[PATCH 5.3 243/344] 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 5.3 242/344] printk: Do not lose last line in kmsg buffer dump

2019-10-03 Thread Greg Kroah-Hartman
From: Vincent Whitchurch commit c9dccacfccc72c32692eedff4a27a4b0833a2afd upstream. kmsg_dump_get_buffer() is supposed to select all the youngest log messages which fit into the provided buffer. It determines the correct start index by using msg_print_text() with a NULL buffer to calculate the

[PATCH 5.3 241/344] scsi: qla2xxx: Fix Relogin to prevent modifying scan_state flag

2019-10-03 Thread Greg Kroah-Hartman
From: Quinn Tran commit 8b5292bcfcacf15182a77a973a98d310e76fd58b upstream. Relogin fails to move forward due to scan_state flag indicating device is not there. Before relogin process, Session delete process accidently modified the scan_state flag. [mkp: typos plus corrected Fixes: sha as

[PATCH 5.3 235/344] ARM: dts: logicpd-torpedo-baseboard: Fix missing video

2019-10-03 Thread Greg Kroah-Hartman
From: Adam Ford commit f9f5518a38684e031d913f40482721ff553f5ba2 upstream. A previous commit removed the panel-dpi driver, which made the Torpedo video stop working because it relied on the dpi driver for setting video timings. Now that the simple-panel driver is available in omap2plus, this

[PATCH 5.3 237/344] 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

Re: [PATCH v5 01/10] mm/memunmap: Use the correct start and end pfn when removing pages from zone

2019-10-03 Thread Aneesh Kumar K.V
On 10/1/19 8:33 PM, David Hildenbrand wrote: On 01.10.19 16:57, David Hildenbrand wrote: On 01.10.19 16:40, David Hildenbrand wrote: From: "Aneesh Kumar K.V" With altmap, all the resource pfns are not initialized. While initializing pfn, altmap reserve space is skipped. Hence when removing

[PATCH 5.3 231/344] btrfs: Detect unbalanced tree with empty leaf before crashing btree operations

2019-10-03 Thread Greg Kroah-Hartman
From: Qu Wenruo [ Upstream commit 62fdaa52a3d00a875da771719b6dc537ca79fce1 ] [BUG] With crafted image, btrfs will panic at btree operations: kernel BUG at fs/btrfs/ctree.c:3894! invalid opcode: [#1] SMP PTI CPU: 0 PID: 1138 Comm: btrfs-transacti Not tainted 5.0.0-rc8+ #9 RIP:

[PATCH 5.3 181/344] 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.3 230/344] btrfs: tree-checker: Add ROOT_ITEM check

2019-10-03 Thread Greg Kroah-Hartman
From: Qu Wenruo [ Upstream commit 259ee7754b6793af8bdd77f9ca818bc41cfe9541 ] This patch will introduce ROOT_ITEM check, which includes: - Key->objectid and key->offset check Currently only some easy check, e.g. 0 as rootid is invalid. - Item size check Root item size is fixed. -

[PATCH 5.3 233/344] media: omap3isp: Set device on omap3isp subdevs

2019-10-03 Thread Greg Kroah-Hartman
From: Sakari Ailus [ Upstream commit e9eb103f027725053a4b02f93d7f2858b56747ce ] The omap3isp driver registered subdevs without the dev field being set. Do that now. Signed-off-by: Sakari Ailus Reviewed-by: Laurent Pinchart Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Sasha Levin ---

[PATCH 5.3 187/344] ARM: dts: exynos: Mark LDO10 as always-on on Peach Pit/Pi Chromebooks

2019-10-03 Thread Greg Kroah-Hartman
From: Marek Szyprowski [ Upstream commit 5b0eeeaa37615df37a9a30929b73e9defe61ca84 ] Commit aff138bf8e37 ("ARM: dts: exynos: Add TMU nodes regulator supply for Peach boards") assigned LDO10 to Exynos Thermal Measurement Unit, but it turned out that it supplies also some other critical parts and

[PATCH 5.3 232/344] kvm: Nested KVM MMUs need PAE root too

2019-10-03 Thread Greg Kroah-Hartman
From: Jiří Paleček [ Upstream commit 1cfff4d9a5d01fa61e5768a6afffc81ae1c8ecb9 ] On AMD processors, in PAE 32bit mode, nested KVM instances don't work. The L0 host get a kernel OOPS, which is related to arch.mmu->pae_root being NULL. The reason for this is that when setting up nested KVM

[PATCH 5.3 190/344] 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.3 221/344] 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 5.3 213/344] mmc: sdhci: Fix incorrect switch to HS mode

2019-10-03 Thread Greg Kroah-Hartman
From: Al Cooper [ Upstream commit c894e33ddc1910e14d6f2a2016f60ab613fd8b37 ] When switching from any MMC speed mode that requires 1.8v (HS200, HS400 and HS400ES) to High Speed (HS) mode, the system ends up configured for SDR12 with a 50MHz clock which is an illegal mode. This happens because

[PATCH 5.3 209/344] block: make rq sector size accessible for block stats

2019-10-03 Thread Greg Kroah-Hartman
From: Hou Tao [ Upstream commit 3d24430694077313c75c6b89f618db09943621e4 ] Currently rq->data_len will be decreased by partial completion or zeroed by completion, so when blk_stat_add() is invoked, data_len will be zero and there will never be samples in poll_cb because blk_mq_poll_stats_bkt()

[PATCH 5.3 184/344] 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

Re: [PATCH] Documentation: networking: device drivers: Remove stray asterisks

2019-10-03 Thread Jonathan Corbet
On Wed, 2 Oct 2019 17:09:55 +0200 Jonathan Neuschäfer wrote: > These asterisks were once references to a line that said: > "* Other names and brands may be claimed as the property of others." > But now, they serve no purpose; they can only irritate the reader. > > Fixes: de3edab4276c

[PATCH 5.3 210/344] raid5: dont set STRIPE_HANDLE to stripe which is in batch list

2019-10-03 Thread Greg Kroah-Hartman
From: Guoqing Jiang [ Upstream commit 6ce220dd2f8ea71d6afc29b9a7524c12e39f374a ] If stripe in batch list is set with STRIPE_HANDLE flag, then the stripe could be set with STRIPE_ACTIVE by the handle_stripe function. And if error happens to the batch_head at the same time,

[PATCH 5.3 216/344] 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.3 208/344] io_uring: fix wrong sequence setting logic

2019-10-03 Thread Greg Kroah-Hartman
From: Jackie Liu [ Upstream commit 8776f3fa15a5cd213c4dfab7ddaf557983374ea6 ] Sqo_thread will get sqring in batches, which will cause ctx->cached_sq_head to be added in batches. if one of these sqes is set with the DRAIN flag, then he will never get a chance to process, and finally sqo_thread

[PATCH 5.3 217/344] mmc: mtk-sd: Re-store SDIO IRQs mask at system resume

2019-10-03 Thread Greg Kroah-Hartman
From: Ulf Hansson [ Upstream commit 1c81d69d4c98aab56c5a7d5a810f84aefdb37e9b ] In cases when SDIO IRQs have been enabled, runtime suspend is prevented by the driver. However, this still means msdc_runtime_suspend|resume() gets called during system suspend/resume, via

[PATCH 5.3 207/344] spi: bcm2835: Work around DONE bit erratum

2019-10-03 Thread Greg Kroah-Hartman
From: Lukas Wunner [ Upstream commit 4c524191c0a21d758b519087c64f84348095e940 ] Commit 3bd7f6589f67 ("spi: bcm2835: Overcome sglist entry length limitation") amended the BCM2835 SPI driver with support for DMA transfers whose buffers are not aligned to 4 bytes and require more than one sglist

[PATCH 5.3 186/344] ASoC: dt-bindings: sun4i-spdif: Fix dma-names warning

2019-10-03 Thread Greg Kroah-Hartman
From: Maxime Ripard [ Upstream commit 1a8e7cdfa4f5872bf0c202d09bff6628aba6b9f6 ] Even though the H6 compatible has been properly added, the exeption for the number of DMA channels hasn't been updated, leading in a validation warning. Fix this. Fixes: b20453031472 ("dt-bindings: sound:

[PATCH 5.3 206/344] tools/power/x86/intel-speed-select: Fix memory leak

2019-10-03 Thread Greg Kroah-Hartman
From: Prarit Bhargava [ Upstream commit 3bc3d30ca324bfc3045a1a7fe1f5fe5ad5d92fd9 ] cpumasks are allocated by calling the alloc_cpu_mask() function and are never free'd. They should be free'd after the commands have run. Fix the memory leaks by calling free_cpu_set(). Signed-off-by: Prarit

[PATCH 5.3 204/344] 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.3 200/344] irqchip/gic-v3-its: Fix LPI release for Multi-MSI devices

2019-10-03 Thread Greg Kroah-Hartman
From: Marc Zyngier [ Upstream commit c9c96e30ecaa0aafa225aa1a5392cb7db17c7a82 ] When allocating a range of LPIs for a Multi-MSI capable device, this allocation extended to the closest power of 2. But on the release path, the interrupts are released one by one. This results in not releasing the

[PATCH 5.3 183/344] libata/ahci: Drop PCS quirk for Denverton and beyond

2019-10-03 Thread Greg Kroah-Hartman
From: Dan Williams [ Upstream commit c312ef176399e04fc5f7f2809d9a589751fbf6d9 ] The Linux ahci driver has historically implemented a configuration fixup for platforms / platform-firmware that fails to enable the ports prior to OS hand-off at boot. The fixup was originally implemented way back

[PATCH 5.3 203/344] platform/x86: intel_pmc_core_pltdrv: Module removal warning fix

2019-10-03 Thread Greg Kroah-Hartman
From: M. Vefa Bicakci [ Upstream commit 0b43e41e93815ecd9616759cf5d64d3a7be8e6fb ] Prior to this commit, removing the intel_pmc_core_pltdrv module would cause the following warning: Device 'intel_pmc_core.0' does not have a release() function, it is broken and must be fixed. See

[PATCH 5.3 196/344] kprobes: Prohibit probing on BUG() and WARN() address

2019-10-03 Thread Greg Kroah-Hartman
From: Masami Hiramatsu [ Upstream commit e336b4027775cb458dc713745e526fa1a1996b2a ] Since BUG() and WARN() may use a trap (e.g. UD2 on x86) to get the address where the BUG() has occurred, kprobes can not do single-step out-of-line that instruction. So prohibit probing on such address. Without

[PATCH 5.3 199/344] 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.3 197/344] x86/mm: Fix cpumask_of_node() error condition

2019-10-03 Thread Greg Kroah-Hartman
From: Peter Zijlstra [ Upstream commit bc04a049f058a472695aa22905d57e2b1f4c77d9 ] When CONFIG_DEBUG_PER_CPU_MAPS=y we validate that the @node argument of cpumask_of_node() is a valid node_id. It however forgets to check for negative numbers. Fix this by explicitly casting to unsigned int.

[PATCH 5.3 182/344] ASoC: Intel: Haswell: Adjust machine device private context

2019-10-03 Thread Greg Kroah-Hartman
From: Cezary Rojewski [ Upstream commit ca964edf0ddbfec2cb10b3d251d09598e7ca9b13 ] Apart from Haswell machines, all other devices have their private data set to snd_soc_acpi_mach instance. Changes for HSW/ BDW boards introduced with series: https://patchwork.kernel.org/cover/10782035/ added

[PATCH 5.3 191/344] closures: fix a race on wakeup from closure_sync

2019-10-03 Thread Greg Kroah-Hartman
From: Kent Overstreet [ Upstream commit a22a9602b88fabf10847f238ff81fde5f906fef7 ] The race was when a thread using closure_sync() notices cl->s->done == 1 before the thread calling closure_put() calls wake_up_process(). Then, it's possible for that thread to return and exit just before

[PATCH 5.3 195/344] 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.3 192/344] 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

[PATCH 5.3 193/344] hwmon: (acpi_power_meter) Change log level for unsafe software power cap

2019-10-03 Thread Greg Kroah-Hartman
From: Wang Shenran [ Upstream commit 6e4d91aa071810deac2cd052161aefb376ecf04e ] At boot time, the acpi_power_meter driver logs the following error level message: "Ignoring unsafe software power cap". Having read about it from a few sources, it seems that the error message can be quite

[PATCH 5.3 146/344] libperf: Fix alignment trap with xyarray contents in perf stat

2019-10-03 Thread Greg Kroah-Hartman
From: Gerald BAEZA [ Upstream commit d9c5c083416500e95da098c01be092b937def7fa ] Following the patch 'perf stat: Fix --no-scale', an alignment trap happens in process_counter_values() on ARMv7 platforms due to the attempt to copy non 64 bits aligned double words (pointed by 'count') via a NEON

[PATCH 5.3 150/344] 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.3 141/344] media: dvb-frontends: use ida for pll number

2019-10-03 Thread Greg Kroah-Hartman
From: Sean Young [ Upstream commit c268e7adea52be0093de1164c425f3c8d8927770 ] KASAN: global-out-of-bounds Read in dvb_pll_attach Syzbot reported global-out-of-bounds Read in dvb_pll_attach, while accessing id[dvb_pll_devcount], because dvb_pll_devcount was 65, that is more than size of 'id'

[PATCH 5.3 149/344] 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.3 148/344] EDAC/amd64: Decode syndrome before translating address

2019-10-03 Thread Greg Kroah-Hartman
From: Yazen Ghannam [ Upstream commit 8a2eaab7daf03b23ac902481218034ae2fae5e16 ] AMD Family 17h systems currently require address translation in order to report the system address of a DRAM ECC error. This is currently done before decoding the syndrome information. The syndrome information does

[PATCH 5.3 145/344] cpufreq: imx-cpufreq-dt: Add i.MX8MN support

2019-10-03 Thread Greg Kroah-Hartman
From: Anson Huang [ Upstream commit 75c000c4bcbe2b0eb82baf90c7dd75c7380cc3fd ] i.MX8MN has different speed grading definition as below, it has 4 bits to define speed grading, add support for it. SPEED_GRADE[3:0]MHz 2300 00012200 00102100

[PATCH 5.3 179/344] nvme-multipath: fix ana log nsid lookup when nsid is not found

2019-10-03 Thread Greg Kroah-Hartman
From: Anton Eidelman [ Upstream commit e01f91dff91c7b16a6e3faf2565017d497a73f83 ] ANA log parsing invokes nvme_update_ana_state() per ANA group desc. This updates the state of namespaces with nsids in desc->nsids[]. Both ctrl->namespaces list and desc->nsids[] array are sorted by nsid. Hence

[PATCH 5.3 177/344] x86/mm/pti: Handle unaligned address gracefully in pti_clone_pagetable()

2019-10-03 Thread Greg Kroah-Hartman
From: Song Liu [ Upstream commit 825d0b73cd7526b0bb186798583fae810091cbac ] pti_clone_pmds() assumes that the supplied address is either: - properly PUD/PMD aligned or - the address is actually mapped which means that independently of the mapping level (PUD/PMD/PTE) the next higher

[PATCH 5.3 163/344] media: aspeed-video: address a protential usage of an unitialized var

2019-10-03 Thread Greg Kroah-Hartman
From: Mauro Carvalho Chehab [ Upstream commit 31b8b0bd6e55c3ea5a08bb8141fa5d3c90600e3b ] While this might not occur in practice, if the device is doing the right thing, it would be teoretically be possible to have both hsync_counter and vsync_counter negatives. If this ever happen, ctrl will

[PATCH 5.3 164/344] 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.3 168/344] 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.3 178/344] nvmet: fix data units read and written counters in SMART log

2019-10-03 Thread Greg Kroah-Hartman
From: Tom Wu [ Upstream commit 3bec2e3754becebd4c452999adb49bc62c575ea4 ] In nvme spec 1.3 there is a definition for data write/read counters from SMART log, (See section 5.14.1.2): This value is reported in thousands (i.e., a value of 1 corresponds to 1000 units of 512 bytes

[PATCH 5.3 166/344] ASoC: es8316: fix headphone mixer volume table

2019-10-03 Thread Greg Kroah-Hartman
From: Katsuhiro Suzuki [ Upstream commit f972d02fee2496024cfd6f59021c9d89d54922a6 ] This patch fix setting table of Headphone mixer volume. Current code uses 4 ... 7 values but these values are prohibited. Correct settings are the following: -12dB 0001 -10.5dB 0010 -9dB 0011

[PATCH 5.3 173/344] arm64: Use correct ll/sc atomic constraints

2019-10-03 Thread Greg Kroah-Hartman
From: Andrew Murray [ Upstream commit 580fa1b874711d633f9b145bb0e83ebf3787 ] The A64 ISA accepts distinct (but overlapping) ranges of immediates for: * add arithmetic instructions ('I' machine constraint) * sub arithmetic instructions ('J' machine constraint) * 32-bit logical

[PATCH 5.3 144/344] 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.3 169/344] arm64: dts: meson: fix boards regulators states format

2019-10-03 Thread Greg Kroah-Hartman
From: Neil Armstrong [ Upstream commit f9717178b9be9477877d4c3776c61ff56d854ddf ] This fixes the following DT schemas check errors: meson-gxbb-odroidc2.dt.yaml: gpio-regulator-tf_io: states:0: Additional items are not allowed (180, 1 were unexpected) meson-gxbb-odroidc2.dt.yaml:

<    5   6   7   8   9   10   11   12   13   14   >