[PATCH 5.10 002/126] bpf: Fix fexit trampoline.

2021-04-05 Thread Greg Kroah-Hartman
From: Alexei Starovoitov [ Upstream commit e21aa341785c679dd409c8cb71f864c00fe6c463 ] The fexit/fmod_ret programs can be attached to kernel functions that can sleep. The synchronize_rcu_tasks() will not wait for such tasks to complete. In such case the trampoline image will be freed and when the

[PATCH 5.10 020/126] kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing

2021-04-05 Thread Greg Kroah-Hartman
From: Jens Axboe [ Upstream commit 15b2219facadec583c24523eed40fa45865f859f ] Don't send fake signals to PF_IO_WORKER threads, they don't accept signals. Just treat them like kthreads in this regard, all they need is a wakeup as no forced kernel/user transition is needed. Suggested-by: Linus To

[PATCH 5.10 021/126] vhost: Fix vhost_vq_reset()

2021-04-05 Thread Greg Kroah-Hartman
From: Laurent Vivier [ Upstream commit beb691e69f4dec7bfe8b81b509848acfd1f0dbf9 ] vhost_reset_is_le() is vhost_init_is_le(), and in the case of cross-endian legacy, vhost_init_is_le() depends on vq->user_be. vq->user_be is set by vhost_disable_cross_endian(). But in vhost_vq_reset(), we have:

[PATCH 5.10 024/126] scsi: qla2xxx: Fix broken #endif placement

2021-04-05 Thread Greg Kroah-Hartman
From: Alexey Dobriyan [ Upstream commit 5999b9e5b1f8a2f5417b755130919b3ac96f5550 ] Only half of the file is under include guard because terminating #endif is placed too early. Link: https://lore.kernel.org/r/YE4snvoW1SuwcXAn@localhost.localdomain Reviewed-by: Himanshu Madhani Signed-off-by: Al

[PATCH 5.10 022/126] io_uring: fix ->flags races by linked timeouts

2021-04-05 Thread Greg Kroah-Hartman
From: Pavel Begunkov [ Upstream commit efe814a471e0e58f28f1efaf430c8784a4f36626 ] It's racy to modify req->flags from a not owning context, e.g. linked timeout calling req_set_fail_links() for the master request might race with that request setting/clearing flags while being executed concurrentl

[PATCH 5.10 025/126] staging: comedi: cb_pcidas: fix request_irq() warn

2021-04-05 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 2e5848a3d86f03024ae096478bdb892ab3d79131 ] request_irq() wont accept a name which contains slash so we need to repalce it with something else -- otherwise it will trigger a warning and the entry in /proc/irq/ will not be created since the .name might be used by

[PATCH 5.10 026/126] staging: comedi: cb_pcidas64: fix request_irq() warn

2021-04-05 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit d2d106fe3badfc3bf0dd3899d1c3f210c7203eab ] request_irq() wont accept a name which contains slash so we need to repalce it with something else -- otherwise it will trigger a warning and the entry in /proc/irq/ will not be created since the .name might be used by

[PATCH 5.10 029/126] thermal/core: Add NULL pointer check before using cooling device stats

2021-04-05 Thread Greg Kroah-Hartman
From: Manaf Meethalavalappu Pallikunhi [ Upstream commit 2046a24ae121cd107929655a6aaf3b8c5beea01f ] There is a possible chance that some cooling device stats buffer allocation fails due to very high cooling device max state value. Later cooling device update sysfs can try to access stats data fo

[PATCH 5.10 030/126] locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling

2021-04-05 Thread Greg Kroah-Hartman
From: Waiman Long [ Upstream commit 5de2055d31ea88fd9ae9709ac95c372a505a60fa ] The use_ww_ctx flag is passed to mutex_optimistic_spin(), but the function doesn't use it. The frequent use of the (use_ww_ctx && ww_ctx) combination is repetitive. In fact, ww_ctx should not be used at all if !use_w

[PATCH 5.10 003/126] virtiofs: Fail dax mount if device does not support it

2021-04-05 Thread Greg Kroah-Hartman
From: Vivek Goyal [ Upstream commit 3f9b9efd82a84f27e95d0414f852caf1fa839e83 ] Right now "mount -t virtiofs -o dax myfs /mnt/virtiofs" succeeds even if filesystem deivce does not have a cache window and hence DAX can't be supported. This gives a false sense to user that they are using DAX with

[PATCH 5.10 031/126] locking/ww_mutex: Fix acquire/release imbalance in ww_acquire_init()/ww_acquire_fini()

2021-04-05 Thread Greg Kroah-Hartman
From: Waiman Long [ Upstream commit bee645788e07eea63055d261d2884ea45c2ba857 ] In ww_acquire_init(), mutex_acquire() is gated by CONFIG_DEBUG_LOCK_ALLOC. The dep_map in the ww_acquire_ctx structure is also gated by the same config. However mutex_release() in ww_acquire_fini() is gated by CONFIG_

[PATCH 5.10 032/126] nvmet-tcp: fix kmap leak when data digest in use

2021-04-05 Thread Greg Kroah-Hartman
From: Elad Grupi [ Upstream commit bac04454ef9fada009f0572576837548b190bf94 ] When data digest is enabled we should unmap pdu iovec before handling the data digest pdu. Signed-off-by: Elad Grupi Reviewed-by: Sagi Grimberg Signed-off-by: Christoph Hellwig Signed-off-by: Sasha Levin --- driv

[PATCH 5.10 006/126] fs: nfsd: fix kconfig dependency warning for NFSD_V4

2021-04-05 Thread Greg Kroah-Hartman
From: Julian Braha [ Upstream commit 7005227369079963d25fb2d5d736d0feb2c44cf6 ] When NFSD_V4 is enabled and CRYPTO is disabled, Kbuild gives the following warning: WARNING: unmet direct dependencies detected for CRYPTO_SHA256 Depends on [n]: CRYPTO [=n] Selected by [y]: - NFSD_V4 [=y] &&

[PATCH 5.10 007/126] rpc: fix NULL dereference on kmalloc failure

2021-04-05 Thread Greg Kroah-Hartman
From: J. Bruce Fields [ Upstream commit 0ddc942394013f08992fc379ca04cffacbbe3dae ] I think this is unlikely but possible: svc_authenticate sets rq_authop and calls svcauth_gss_accept. The kmalloc(sizeof(*svcdata), GFP_KERNEL) fails, leaving rq_auth_data NULL, and returning SVC_DENIED. This ca

[PATCH 5.10 027/126] ASoC: rt5659: Update MCLK rate in set_sysclk()

2021-04-05 Thread Greg Kroah-Hartman
From: Sameer Pujar [ Upstream commit dbf54a9534350d6aebbb34f5c1c606b81a4f35dd ] Simple-card/audio-graph-card drivers do not handle MCLK clock when it is specified in the codec device node. The expectation here is that, the codec should actually own up the MCLK clock and do necessary setup in the

[PATCH 5.10 008/126] iomap: Fix negative assignment to unsigned sis->pages in iomap_swapfile_activate

2021-04-05 Thread Greg Kroah-Hartman
From: Ritesh Harjani [ Upstream commit 5808fecc572391867fcd929662b29c12e6d08d81 ] In case if isi.nr_pages is 0, we are making sis->pages (which is unsigned int) a huge value in iomap_swapfile_activate() by assigning -1. This could cause a kernel crash in kernel v4.18 (with below signature). Or c

[PATCH 5.10 009/126] ASoC: rt1015: fix i2c communication error

2021-04-05 Thread Greg Kroah-Hartman
From: Jack Yu [ Upstream commit 9e0bdaa9fcb8c64efc1487a7fba07722e7bc515e ] Remove 0x100 cache re-sync to solve i2c communication error. Signed-off-by: Jack Yu Link: https://lore.kernel.org/r/20210222090057.29532-1-jack...@realtek.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

RE: [PATCH net-next 1/2] net: stmmac: enable 2.5Gbps link speed

2021-04-05 Thread Voon, Weifeng
> On Fri, Apr 02, 2021 at 07:45:04AM +, Voon, Weifeng wrote: > > > > + /* 2.5G mode only support 2500baseT full duplex only */ > > > > + if (priv->plat->has_gmac4 && priv->plat->speed_2500_en) { > > > > + phylink_set(mac_supported, 2500baseT_Full); > > > > +

[PATCH 5.10 044/126] rtw88: coex: 8821c: correct antenna switch function

2021-04-05 Thread Greg Kroah-Hartman
From: Guo-Feng Fan [ Upstream commit adba838af159914eb98fcd55bfd3a89c9a7d41a8 ] This patch fixes a defect that uses incorrect function to access registers. Use 8 and 32 bit access function to access 8 and 32 bit long data respectively. Signed-off-by: Guo-Feng Fan Signed-off-by: Ping-Ke Shih S

[PATCH 5.10 045/126] netdevsim: dev: Initialize FIB module after debugfs

2021-04-05 Thread Greg Kroah-Hartman
From: Ido Schimmel [ Upstream commit f57ab5b75f7193e194c83616cd104f41c8350f68 ] Initialize the dummy FIB offload module after debugfs, so that the FIB module could create its own directory there. Signed-off-by: Amit Cohen Signed-off-by: Ido Schimmel Signed-off-by: David S. Miller Signed-off-

[PATCH 5.10 046/126] iwlwifi: pcie: dont disable interrupts for reg_lock

2021-04-05 Thread Greg Kroah-Hartman
From: Johannes Berg [ Upstream commit 874020f8adce535cd318af1768ffe744251b6593 ] The only thing we do touching the device in hard interrupt context is, at most, writing an interrupt ACK register, which isn't racing in with anything protected by the reg_lock. Thus, avoid disabling interrupts her

[PATCH 5.10 048/126] net: ethernet: aquantia: Handle error cleanup of start on open

2021-04-05 Thread Greg Kroah-Hartman
From: Nathan Rossi [ Upstream commit 8a28af7a3e85ddf358f8c41e401a33002f7a9587 ] The aq_nic_start function can fail in a variety of cases which leaves the device in broken state. An example case where the start function fails is the request_threaded_irq which can be interrupted, resulting in a E

[PATCH 5.10 047/126] ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr()

2021-04-05 Thread Greg Kroah-Hartman
From: Shuah Khan [ Upstream commit 09078368d516918666a0122f2533dc73676d3d7e ] ieee80211_find_sta_by_ifaddr() must be called under the RCU lock and the resulting pointer is only valid under RCU lock as well. Fix ath10k_wmi_tlv_op_pull_peer_stats_info() to hold RCU lock before it calls ieee80211_

[PATCH 5.10 049/126] appletalk: Fix skb allocation size in loopback case

2021-04-05 Thread Greg Kroah-Hartman
From: Doug Brown [ Upstream commit 39935dccb21c60f9bbf1bb72d22ab6fd14ae7705 ] If a DDP broadcast packet is sent out to a non-gateway target, it is also looped back. There is a potential for the loopback device to have a longer hardware header length than the original target route's device, which

[PATCH 5.10 023/126] scsi: st: Fix a use after free in st_open()

2021-04-05 Thread Greg Kroah-Hartman
From: Lv Yunlong [ Upstream commit c8c165dea4c8f5ad67b1240861e4f6c5395fa4ac ] In st_open(), if STp->in_use is true, STp will be freed by scsi_tape_put(). However, STp is still used by DEBC_printk() after. It is better to DEBC_printk() before scsi_tape_put(). Link: https://lore.kernel.org/r/2021

[PATCH 5.10 028/126] ASoC: rt711: add snd_soc_component remove callback

2021-04-05 Thread Greg Kroah-Hartman
From: Bard Liao [ Upstream commit 899b12542b0897f92de9ba30944937c39ebb246d ] We do some IO operations in the snd_soc_component_set_jack callback function and snd_soc_component_set_jack() will be called when soc component is removed. However, we should not access SoundWire registers when the bus

[PATCH 5.10 004/126] ext4: shrink race window in ext4_should_retry_alloc()

2021-04-05 Thread Greg Kroah-Hartman
From: Eric Whitney [ Upstream commit efc61345274d6c7a46a0570efbc916fcbe3e927b ] When generic/371 is run on kvm-xfstests using 5.10 and 5.11 kernels, it fails at significant rates on the two test scenarios that disable delayed allocation (ext3conv and data_journal) and force actual block allocati

[PATCH 5.10 005/126] ext4: fix bh ref count on error paths

2021-04-05 Thread Greg Kroah-Hartman
From: Zhaolong Zhang [ Upstream commit c915fb80eaa6194fa9bd0a4487705cd5b0dda2f1 ] __ext4_journalled_writepage should drop bhs' ref count on error paths Signed-off-by: Zhaolong Zhang Link: https://lore.kernel.org/r/1614678151-70481-1-git-send-email-zhangzl2...@126.com Signed-off-by: Theodore T

[PATCH 5.10 000/126] 5.10.28-rc1 review

2021-04-05 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.28 release. There are 126 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed, 07 Apr 2021 08:50:09 +. Anything re

[PATCH 5.10 034/126] static_call: Align static_call_is_init() patching condition

2021-04-05 Thread Greg Kroah-Hartman
From: Peter Zijlstra [ Upstream commit 698bacefe993ad2922c9d3b1380591ad489355e9 ] The intent is to avoid writing init code after init (because the text might have been freed). The code is needlessly different between jump_label and static_call and not obviously correct. The existing code relies

[PATCH 5.10 043/126] ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL pointer

2021-04-05 Thread Greg Kroah-Hartman
From: Wen Gong [ Upstream commit 0d96968315d7ffbd70d608b29e9bea084210b96d ] When function return fail to __ath11k_mac_register after success called ieee80211_register_hw, then it set wiphy->dev.parent to NULL by SET_IEEE80211_DEV(ar->hw, NULL) in end of __ath11k_mac_register, then cfg80211_get_d

[PATCH 5.10 051/126] net: ipa: fix register write command validation

2021-04-05 Thread Greg Kroah-Hartman
From: Alex Elder [ Upstream commit 2d65ed76924bc772d3974b0894d870b1aa63b34a ] In ipa_cmd_register_write_valid() we verify that values we will supply to a REGISTER_WRITE IPA immediate command will fit in the fields that need to hold them. This patch fixes some issues in that function and ipa_cmd

[PATCH 5.10 052/126] net: wan/lmc: unregister device when no matching device is found

2021-04-05 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 62e69bc419772638369eff8ff81340bde8aceb61 ] lmc set sc->lmc_media pointer when there is a matching device. However, when no matching device is found, this pointer is NULL and the following dereference will result in a null-ptr-deref. To fix this issue, unregist

[PATCH 5.10 050/126] net: ipa: remove two unused register definitions

2021-04-05 Thread Greg Kroah-Hartman
From: Alex Elder [ Upstream commit d5bc5015eb9d64cbd14e467db1a56db1472d0d6c ] We do not support inter-EE channel or event ring commands. Inter-EE interrupts are disabled (and never re-enabled) for all channels and event rings, so we have no need for the GSI registers that clear those interrupt

[PATCH 5.10 035/126] ext4: do not iput inode under running transaction in ext4_rename()

2021-04-05 Thread Greg Kroah-Hartman
From: zhangyi (F) [ Upstream commit 5dccdc5a1916d4266edd251f20113a5c495f ] In ext4_rename(), when RENAME_WHITEOUT failed to add new entry into directory, it ends up dropping new created whiteout inode under the running transaction. After commit <9b88f9fb0d2> ("ext4: Do not iput inode under r

[PATCH 5.10 053/126] net: 9p: advance iov on empty read

2021-04-05 Thread Greg Kroah-Hartman
From: Jisheng Zhang [ Upstream commit d65614a01d24704b016635abf5cc028a54e45a62 ] I met below warning when cating a small size(about 80bytes) txt file on 9pfs(msize=2097152 is passed to 9p mount option), the reason is we miss iov_iter_advance() if the read count is 0 for zerocopy case, so we didn

Re: [PATCH v3 13/25] x86/sgx: Add helpers to expose ECREATE and EINIT to KVM

2021-04-05 Thread Borislav Petkov
On Fri, Mar 19, 2021 at 08:23:08PM +1300, Kai Huang wrote: > + /* > + * @secs is an untrusted, userspace-provided address. It comes from > + * KVM and is assumed to be a valid pointer which points somewhere in > + * userspace. This can fault and call SGX or other fault handlers

[PATCH 5.10 055/126] ACPI: tables: x86: Reserve memory occupied by ACPI tables

2021-04-05 Thread Greg Kroah-Hartman
From: Rafael J. Wysocki commit 1a1c130ab7575498eed5bcf7220037ae09cd1f8a upstream. The following problem has been reported by George Kennedy: Since commit 7fef431be9c9 ("mm/page_alloc: place pages to tail in __free_pages_core()") the following use after free occurs intermittently when ACPI ta

[PATCH 5.10 054/126] bpf: Remove MTU check in __bpf_skb_max_len

2021-04-05 Thread Greg Kroah-Hartman
From: Jesper Dangaard Brouer commit 6306c1189e77a513bf02720450bb43bd4ba5d8ae upstream. Multiple BPF-helpers that can manipulate/increase the size of the SKB uses __bpf_skb_max_len() as the max-length. This function limit size against the current net_device MTU (skb->dev->mtu). When a BPF-prog g

[PATCH 5.10 056/126] ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()

2021-04-05 Thread Greg Kroah-Hartman
From: Vitaly Kuznetsov commit 8c182bd7befae6af49c5fd612893f55d6ccb upstream. Commit 496121c02127 ("ACPI: processor: idle: Allow probing on platforms with one ACPI C-state") broke CPU0 hotplug on certain systems, e.g. I'm observing the following on AWS Nitro (e.g r5b.xlarge but other instance

[PATCH 5.10 057/126] ALSA: usb-audio: Apply sample rate quirk to Logitech Connect

2021-04-05 Thread Greg Kroah-Hartman
From: Ikjoon Jang commit 625bd5a616ceda4840cd28f82e957c8ced394b6a upstream. Logitech ConferenceCam Connect is a compound USB device with UVC and UAC. Not 100% reproducible but sometimes it keeps responding STALL to every control transfer once it receives get_freq request. This patch adds 046d:0

[PATCH 5.10 058/126] ALSA: hda: Re-add dropped snd_poewr_change_state() calls

2021-04-05 Thread Greg Kroah-Hartman
From: Takashi Iwai commit c8f79808cd8eb5bc8d14de129bd6d586d3fce0aa upstream. The card power state change via snd_power_change_state() at the system suspend/resume seems dropped mistakenly during the PM code rewrite. The card power state doesn't play much role nowadays but it's still referred in

[PATCH 5.10 059/126] ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks

2021-04-05 Thread Greg Kroah-Hartman
From: Takashi Iwai commit 66affb7bb0dc0905155a1b2475261aa704d1ddb5 upstream. The recently added PM prepare and complete callbacks don't have the sanity check whether the card instance has been properly initialized, which may potentially lead to Oops. This patch adds the azx_is_pm_ready() call i

[PATCH 5.10 060/126] ALSA: hda/realtek: fix a determine_headset_type issue for a Dell AIO

2021-04-05 Thread Greg Kroah-Hartman
From: Hui Wang commit febf22565549ea7111e7d45e8f2d64373cc66b11 upstream. We found a recording issue on a Dell AIO, users plug a headset-mic and select headset-mic from UI, but can't record any sound from headset-mic. The root cause is the determine_headset_type() returns a wrong type, e.g. users

[PATCH 5.10 061/126] ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook

2021-04-05 Thread Greg Kroah-Hartman
From: Hui Wang commit e54f30befa7990b897189b44a56c1138c6bfdbb5 upstream. We found the alc_update_headset_mode() is not called on some machines when unplugging the headset, as a result, the mode of the ALC_HEADSET_MODE_UNPLUGGED can't be set, then the current_headset_type is not cleared, if users

[PATCH 5.10 036/126] io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with MSG_WAITALL

2021-04-05 Thread Greg Kroah-Hartman
From: Stefan Metzmacher [ Upstream commit 0031275d119efe16711cd93519b595e6f9b4b330 ] Without that it's not safe to use them in a linked combination with others. Now combinations like IORING_OP_SENDMSG followed by IORING_OP_SPLICE should be possible. We already handle short reads and writes for

[PATCH 5.10 062/126] ALSA: hda/realtek: fix mute/micmute LEDs for HP 640 G8

2021-04-05 Thread Greg Kroah-Hartman
From: Jeremy Szu commit 417eadfdd9e25188465280edf3668ed163fda2d0 upstream. The HP EliteBook 640 G8 Notebook PC is using ALC236 codec which is using 0x02 to control mute LED and 0x01 to control micmute LED. Therefore, add a quirk to make it works. Signed-off-by: Jeremy Szu Cc: Link: https://lo

[PATCH 5.10 063/126] xtensa: fix uaccess-related livelock in do_page_fault

2021-04-05 Thread Greg Kroah-Hartman
From: Max Filippov commit 7b9acbb6aad4f54623dcd4bd4b1a60fe0c727b09 upstream. If a uaccess (e.g. get_user()) triggers a fault and there's a fault signal pending, the handler will return to the uaccess without having performed a uaccess fault fixup, and so the CPU will immediately execute the uacc

[PATCH 5.10 064/126] xtensa: move coprocessor_flush to the .text section

2021-04-05 Thread Greg Kroah-Hartman
From: Max Filippov commit ab5eb336411f18fd449a1fb37d36a55ec422603f upstream. coprocessor_flush is not a part of fast exception handlers, but it uses parts of fast coprocessor handling code that's why it's in the same source file. It uses call0 opcode to invoke those parts so there are no limitat

[PATCH 5.10 065/126] KVM: SVM: load control fields from VMCB12 before checking them

2021-04-05 Thread Greg Kroah-Hartman
From: Paolo Bonzini commit a58d9166a756a0f4a6618e4f593232593d6df134 upstream. Avoid races between check and use of the nested VMCB controls. This for example ensures that the VMRUN intercept is always reflected to the nested hypervisor, instead of being processed by the host. Without this patc

[PATCH 5.10 067/126] PM: runtime: Fix race getting/putting suppliers at probe

2021-04-05 Thread Greg Kroah-Hartman
From: Adrian Hunter commit 9dfacc54a8661bc8be6e08cffee59596ec59f263 upstream. pm_runtime_put_suppliers() must not decrement rpm_active unless the consumer is suspended. That is because, otherwise, it could suspend suppliers for an active consumer. That can happen as follows: static int driver

[PATCH 5.10 068/126] PM: runtime: Fix ordering in pm_runtime_get_suppliers()

2021-04-05 Thread Greg Kroah-Hartman
From: Adrian Hunter commit c0c33442f7203704aef345647e14c2fb86071001 upstream. rpm_active indicates how many times the supplier usage_count has been incremented. Consequently it must be updated after pm_runtime_get_sync() of the supplier, not before. Fixes: 4c06c4e6cf63 ("driver core: Fix possib

[PATCH 5.10 069/126] tracing: Fix stack trace event size

2021-04-05 Thread Greg Kroah-Hartman
From: Steven Rostedt (VMware) commit 9deb193af69d3fd6dd8e47f292b67c805a787010 upstream. Commit cbc3b92ce037 fixed an issue to modify the macros of the stack trace event so that user space could parse it properly. Originally the stack trace format to user space showed that the called stack was a

[PATCH 5.10 070/126] s390/vdso: copy tod_steering_delta value to vdso_data page

2021-04-05 Thread Greg Kroah-Hartman
From: Heiko Carstens commit 72bbc226ed2ef0a46c165a482861fff00dd6d4e1 upstream. When converting the vdso assembler code to C it was forgotten to actually copy the tod_steering_delta value to vdso_data page. Which in turn means that tod clock steering will not work correctly. Fix this by simply

[PATCH 5.10 037/126] net: mvpp2: fix interrupt mask/unmask skip condition

2021-04-05 Thread Greg Kroah-Hartman
[ Upstream commit 7867299cde34e9c2d2c676f2a384a9d5853b914d ] The condition should be skipped if CPU ID equal to nthreads. The patch doesn't fix any actual issue since nthreads = min_t(unsigned int, num_present_cpus(), MVPP2_MAX_THREADS). On all current Armada platforms, the number of CPU's is less

[PATCH 5.10 038/126] flow_dissector: fix TTL and TOS dissection on IPv4 fragments

2021-04-05 Thread Greg Kroah-Hartman
From: Davide Caratti [ Upstream commit d2126838050ccd1dadf310ffb78b2204f3b032b9 ] the following command: # tc filter add dev $h2 ingress protocol ip pref 1 handle 101 flower \ $tcflags dst_ip 192.0.2.2 ip_ttl 63 action drop doesn't drop all IPv4 packets that match the configured TTL / dest

[PATCH 5.10 039/126] can: dev: move driver related infrastructure into separate subdir

2021-04-05 Thread Greg Kroah-Hartman
From: Marc Kleine-Budde [ Upstream commit 3e77f70e734584e0ad1038e459ed3fd2400f873a ] This patch moves the CAN driver related infrastructure into a separate subdir. It will be split into more files in the coming patches. Reviewed-by: Vincent Mailhol Link: https://lore.kernel.org/r/202104193

[PATCH 5.10 040/126] net: introduce CAN specific pointer in the struct net_device

2021-04-05 Thread Greg Kroah-Hartman
From: Oleksij Rempel [ Upstream commit 4e096a18867a5a989b510f6999d9c6b6622e8f7b ] Since 20dd3850bcf8 ("can: Speed up CAN frame receiption by using ml_priv") the CAN framework uses per device specific data in the AF_CAN protocol. For this purpose the struct net_device->ml_priv is used. Later the

[PATCH 5.10 041/126] can: tcan4x5x: fix max register value

2021-04-05 Thread Greg Kroah-Hartman
[ Upstream commit 6e1caaf8ed22eb700cc47ec353816eee33186c1c ] This patch fixes the max register value for the regmap. Reviewed-by: Dan Murphy Tested-by: Sean Nyekjaer Link: https://lore.kernel.org/r/20201215231746.1132907-12-...@pengutronix.de Signed-off-by: Marc Kleine-Budde Signed-off-by: Sas

[PATCH 5.10 042/126] brcmfmac: clear EAP/association status bits on linkdown events

2021-04-05 Thread Greg Kroah-Hartman
From: Luca Pesce [ Upstream commit e862a3e4088070de352fdafe9bd9e3ae0a95a33c ] This ensure that previous association attempts do not leave stale statuses on subsequent attempts. This fixes the WARN_ON(!cr->bss)) from __cfg80211_connect_result() when connecting to an AP after a previous connectio

[PATCH 5.10 073/126] drm/amdkfd: dqm fence memory corruption

2021-04-05 Thread Greg Kroah-Hartman
From: Qu Huang commit e92049ae4548ba09e53eaa9c8f6964b07ea274c9 upstream. Amdgpu driver uses 4-byte data type as DQM fence memory, and transmits GPU address of fence memory to microcode through query status PM4 message. However, query status PM4 message definition and microcode processing are all

[PATCH] rtl8xxxu: Simplify locking of a skb list accesses

2021-04-05 Thread Christophe JAILLET
The 'c2hcmd_lock' spinlock is only used to protect some __skb_queue_tail() and __skb_dequeue() calls. Use the lock provided in the skb itself and call skb_queue_tail() and skb_dequeue(). These functions already include the correct locking. Signed-off-by: Christophe JAILLET --- drivers/net/wirele

[PATCH 5.10 082/126] KVM: x86/mmu: change TDP MMU yield function returns to match cond_resched

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit e28a436ca4f65384cceaf3f4da0e00aa74244e6a ] Currently the TDP MMU yield / cond_resched functions either return nothing or return true if the TLBs were not flushed. These are confusing semantics, especially when making control flow decisions in calling functions.

[PATCH 5.10 083/126] KVM: x86/mmu: Merge flush and non-flush tdp_mmu_iter_cond_resched

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit e139a34ef9d5627a41e1c02210229082140d1f92 ] The flushing and non-flushing variants of tdp_mmu_iter_cond_resched have almost identical implementations. Merge the two functions and add a flush parameter. Signed-off-by: Ben Gardon Message-Id: <20210202185734.1680

[PATCH 5.10 084/126] KVM: x86/mmu: Rename goal_gfn to next_last_level_gfn

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit 74953d3530280dc53256054e1906f58d07bfba44 ] The goal_gfn field in tdp_iter can be misleading as it implies that it is the iterator's final goal. It is really a target for the lowest gfn mapped by the leaf level SPTE the iterator will traverse towards. Change the

[PATCH 5.10 085/126] KVM: x86/mmu: Ensure forward progress when yielding in TDP MMU iter

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit ed5e484b79e8a9b8be714bd85b6fc70bd6dc99a7 ] In some functions the TDP iter risks not making forward progress if two threads livelock yielding to one another. This is possible if two threads are trying to execute wrprot_gfn_range. Each could write protect an entr

[PATCH 5.10 087/126] kvm: x86/mmu: Add existing trace points to TDP MMU

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit 33dd3574f5fef57c2c6caccf98925d63aa2a8d09 ] The TDP MMU was initially implemented without some of the usual tracepoints found in mmu.c. Correct this discrepancy by adding the missing trace points to the TDP MMU. Tested: ran the demand paging selftest on an Inte

[PATCH 5.10 088/126] KVM: x86/mmu: Add lockdep when setting a TDP MMU SPTE

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit 3a9a4aa5657471a02ffb7f9b7f3b7a468b3f257b ] Add lockdep to __tdp_mmu_set_spte to ensure that SPTEs are only modified under the MMU lock. No functional change intended. Reviewed-by: Peter Feiner Reviewed-by: Sean Christopherson Acked-by: Paolo Bonzini Signed

[PATCH 5.10 090/126] KVM: x86/mmu: Protect TDP MMU page table memory with RCU

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit 7cca2d0b7e7d9f3cd740d41afdc00051c9b508a0 ] In order to enable concurrent modifications to the paging structures in the TDP MMU, threads must be able to safely remove pages of page table memory while other threads are traversing the same memory. To ensure thread

[PATCH 5.10 074/126] drm/amdgpu: fix offset calculation in amdgpu_vm_bo_clear_mappings()

2021-04-05 Thread Greg Kroah-Hartman
From: Nirmoy Das commit 5e61b84f9d3ddfba73091f9fbc940caae1c9eb22 upstream. Offset calculation wasn't correct as start addresses are in pfn not in bytes. CC: sta...@vger.kernel.org Signed-off-by: Nirmoy Das Reviewed-by: Christian König Signed-off-by: Alex Deucher Signed-off-by: Greg Kroah-Har

[PATCH 5.10 091/126] KVM: x86/mmu: Ensure TLBs are flushed when yielding during GFN range zap

2021-04-05 Thread Greg Kroah-Hartman
From: Sean Christopherson [ Upstream commit a835429cda91621fca915d80672a157b47738afb ] When flushing a range of GFNs across multiple roots, ensure any pending flush from a previous root is honored before yielding while walking the tables of the current root. Note, kvm_tdp_mmu_zap_gfn_range() no

[PATCH 5.10 094/126] KVM: x86/mmu: Fix braces in kvm_recover_nx_lpages

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit 8d1a182ea791f0111b0258c8f3eb8d77af0a8386 ] No functional change intended. Fixes: 29cf0f5007a2 ("kvm: x86/mmu: NX largepage recovery for TDP MMU") Signed-off-by: Ben Gardon Message-Id: <20210202185734.1680553-10-bgar...@google.com> Signed-off-by: Paolo Bonzini

[PATCH 5.10 093/126] KVM: x86/mmu: Dont redundantly clear TDP MMU pt memory

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit 734e45b329d626d2c14e2bcf8be3d069a33c3316 ] The KVM MMU caches already guarantee that shadow page table memory will be zeroed, so there is no reason to re-zero the page in the TDP MMU page fault handler. No functional change intended. Reviewed-by: Peter Feiner

[PATCH 5.10 089/126] KVM: x86/mmu: Factor out handling of removed page tables

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit a066e61f13cf4b17d043ad8bea0cdde2b1e5ee49 ] Factor out the code to handle a disconnected subtree of the TDP paging structure from the code to handle the change to an individual SPTE. Future commits will build on this to allow asynchronous page freeing. No funct

[PATCH 5.10 096/126] KVM: x86/mmu: Use atomic ops to set SPTEs in TDP MMU map

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit 9a77daacc87dee9fd63e31243f21894132ed8407 ] To prepare for handling page faults in parallel, change the TDP MMU page fault handler to use atomic operations to set SPTEs so that changes are not lost if multiple threads attempt to modify the same SPTE. Reviewed-b

[PATCH 5.10 099/126] extcon: Add stubs for extcon_register_notifier_all() functions

2021-04-05 Thread Greg Kroah-Hartman
From: Krzysztof Kozlowski [ Upstream commit c9570d4a5efd04479b3cd09c39b571eb031d94f4 ] Add stubs for extcon_register_notifier_all() function for !CONFIG_EXTCON case. This is useful for compile testing and for drivers which use EXTCON but do not require it (therefore do not depend on CONFIG_EXTC

[PATCH 5.10 092/126] KVM: x86/mmu: Add comment on __tdp_mmu_set_spte

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit fe43fa2f407b9d513f7bcf18142e14e1bf1508d6 ] __tdp_mmu_set_spte is a very important function in the TDP MMU which already accepts several arguments and will take more in future commits. To offset this complexity, add a comment to the function describing each of t

[PATCH 5.10 097/126] KVM: x86: compile out TDP MMU on 32-bit systems

2021-04-05 Thread Greg Kroah-Hartman
From: Paolo Bonzini [ Upstream commit 897218ff7cf19290ec2d69652ce673d8ed6fedeb ] The TDP MMU assumes that it can do atomic accesses to 64-bit PTEs. Rather than just disabling it, compile it out completely so that it is possible to use for example 64-bit xchg. To limit the number of stubs, wrap

[PATCH 5.10 100/126] extcon: Fix error handling in extcon_dev_register

2021-04-05 Thread Greg Kroah-Hartman
From: Dinghao Liu [ Upstream commit d3bdd1c3140724967ca4136755538fa7c05c2b4e ] When devm_kcalloc() fails, we should execute device_unregister() to unregister edev->dev from system. Fixes: 046050f6e623e ("extcon: Update the prototype of extcon_register_notifier() with enum extcon") Signed-off-b

[PATCH 5.10 098/126] KVM: x86/mmu: Ensure TLBs are flushed for TDP MMU during NX zapping

2021-04-05 Thread Greg Kroah-Hartman
From: Sean Christopherson [ Upstream commit 048f49809c526348775425420fb5b8e84fd9a133 ] Honor the "flush needed" return from kvm_tdp_mmu_zap_gfn_range(), which does the flush itself if and only if it yields (which it will never do in this particular scenario), and otherwise expects the caller to

[PATCH 5.10 101/126] firmware: stratix10-svc: reset COMMAND_RECONFIG_FLAG_PARTIAL to 0

2021-04-05 Thread Greg Kroah-Hartman
From: Richard Gong [ Upstream commit 2e8496f31d0be8f43849b2980b069f3a9805d047 ] Clean up COMMAND_RECONFIG_FLAG_PARTIAL flag by resetting it to 0, which aligns with the firmware settings. Fixes: 36847f9e3e56 ("firmware: stratix10-svc: correct reconfig flag and timeout values") Signed-off-by: Ri

[PATCH 5.10 102/126] usb: dwc3: pci: Enable dis_uX_susphy_quirk for Intel Merrifield

2021-04-05 Thread Greg Kroah-Hartman
From: Andy Shevchenko [ Upstream commit b522f830d35189e0283fa4d5b4b3ef8d7a78cfcb ] It seems that on Intel Merrifield platform the USB PHY shouldn't be suspended. Otherwise it can't be enabled by simply change the cable in the connector. Enable corresponding quirk for the platform in question.

[PATCH 5.10 075/126] drm/amdgpu: check alignment on CPU page for bo map

2021-04-05 Thread Greg Kroah-Hartman
From: Xℹ Ruoyao commit e3512fb67093fabdf27af303066627b921ee9bd8 upstream. The page table of AMDGPU requires an alignment to CPU page so we should check ioctl parameters for it. Return -EINVAL if some parameter is unaligned to CPU page, instead of corrupt the page table sliently. Reviewed-by: C

[PATCH 5.10 105/126] usbip: vhci_hcd fix shift out-of-bounds in vhci_hub_control()

2021-04-05 Thread Greg Kroah-Hartman
From: Shuah Khan commit 1cc5ed25bdade86de2650a82b2730108a76de20c upstream. Fix shift out-of-bounds in vhci_hub_control() SetPortFeature handling. UBSAN: shift-out-of-bounds in drivers/usb/usbip/vhci_hcd.c:605:42 shift exponent 768 is too large for 32-bit type 'int' Reported-by: syzbot+3dea30b0

[PATCH 5.10 104/126] firewire: nosy: Fix a use-after-free bug in nosy_ioctl()

2021-04-05 Thread Greg Kroah-Hartman
From: Zheyu Ma [ Upstream commit 829933ef05a951c8ff140e814656d73e74915faf ] For each device, the nosy driver allocates a pcilynx structure. A use-after-free might happen in the following scenario: 1. Open nosy device for the first time and call ioctl with command NOSY_IOC_START, then a new

[PATCH 5.10 106/126] USB: quirks: ignore remote wake-up on Fibocom L850-GL LTE modem

2021-04-05 Thread Greg Kroah-Hartman
From: Vincent Palatin commit 0bd860493f81eb2a46173f6f5e44cc38331c8dbd upstream. This LTE modem (M.2 card) has a bug in its power management: there is some kind of race condition for U3 wake-up between the host and the device. The modem firmware sometimes crashes/locks when both events happen at

[PATCH 5.10 095/126] KVM: x86/mmu: Factor out functions to add/remove TDP MMU pages

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit a9442f594147f95307f691cfba0c31e25dc79b9d ] Move the work of adding and removing TDP MMU pages to/from "secondary" data structures to helper functions. These functions will be built on in future commits to enable MMU operations to proceed (mostly) in parallel.

[PATCH 5.10 107/126] usb: musb: Fix suspend with devices connected for a64

2021-04-05 Thread Greg Kroah-Hartman
From: Tony Lindgren commit 92af4fc6ec331228aca322ca37c8aea7b150a151 upstream. Pinephone running on Allwinner A64 fails to suspend with USB devices connected as reported by Bhushan Shah . Reverting commit 5fbf7a253470 ("usb: musb: fix idling for suspend after disconnect interrupt") fixes the issu

[PATCH 5.10 103/126] video: hyperv_fb: Fix a double free in hvfb_probe

2021-04-05 Thread Greg Kroah-Hartman
From: Lv Yunlong [ Upstream commit 37df9f3fedb6aeaff5564145e8162aab912c9284 ] Function hvfb_probe() calls hvfb_getmem(), expecting upon return that info->apertures is either NULL or points to memory that should be freed by framebuffer_release(). But hvfb_getmem() is freeing the memory and leavi

[PATCH 5.10 109/126] cdc-acm: fix BREAK rx code path adding necessary calls

2021-04-05 Thread Greg Kroah-Hartman
From: Oliver Neukum commit 08dff274edda54310d6f1cf27b62fddf0f8d146e upstream. Counting break events is nice but we should actually report them to the tty layer. Fixes: 5a6a62bdb9257 ("cdc-acm: add TIOCMIWAIT") Signed-off-by: Oliver Neukum Link: https://lore.kernel.org/r/20210311133714.31881-1-

[PATCH 5.10 108/126] usb: xhci-mtk: fix broken streams issue on 0.96 xHCI

2021-04-05 Thread Greg Kroah-Hartman
From: Chunfeng Yun commit 6f978a30c9bb12dab1302d0f06951ee290f5e600 upstream. The MediaTek 0.96 xHCI controller on some platforms does not support bulk stream even HCCPARAMS says supporting, due to MaxPSASize is set a default value 1 by mistake, here use XHCI_BROKEN_STREAMS quirk to fix it. Fixe

[PATCH 5.10 110/126] USB: cdc-acm: untangle a circular dependency between callback and softint

2021-04-05 Thread Greg Kroah-Hartman
From: Oliver Neukum commit 6069e3e927c8fb3a1947b07d1a561644ea960248 upstream. We have a cycle of callbacks scheduling works which submit URBs with thos callbacks. This needs to be blocked, stopped and unblocked to untangle the circle. The issue leads to faults like: [ 55.068392] Unable to ha

[PATCH 5.10 066/126] KVM: SVM: ensure that EFER.SVME is set when running nested guest or on nested vmexit

2021-04-05 Thread Greg Kroah-Hartman
From: Paolo Bonzini commit 3c346c0c60ab06a021d1c0884a0ef494bc4ee3a7 upstream. Fixing nested_vmcb_check_save to avoid all TOC/TOU races is a bit harder in released kernels, so do the bare minimum by avoiding that EFER.SVME is cleared. This is problematic because svm_set_efer frees the data struc

[PATCH 5.10 071/126] s390/vdso: fix tod_steering_delta type

2021-04-05 Thread Greg Kroah-Hartman
From: Heiko Carstens commit b24bacd67ffddd9192c4745500fd6f73dbfe565e upstream. The s390 specific vdso function __arch_get_hw_counter() is supposed to consider tod clock steering. If a tod clock steering event happens and the tod clock is set to a new value __arch_get_hw_counter() will not retur

[PATCH 5.10 033/126] io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls

2021-04-05 Thread Greg Kroah-Hartman
From: Stefan Metzmacher [ Upstream commit 76cd979f4f38a27df22efb5773a0d567181a9392 ] We never want to generate any SIGPIPE, -EPIPE only is much better. Signed-off-by: Stefan Metzmacher Link: https://lore.kernel.org/r/38961085c3ec49fd21550c7788f214d1ff02d2d4.1615908477.git.me...@samba.org Sign

[PATCH 5.10 086/126] KVM: x86/mmu: Yield in TDU MMU iter even if no SPTES changed

2021-04-05 Thread Greg Kroah-Hartman
From: Ben Gardon [ Upstream commit 1af4a96025b33587ca953c7ef12a1b20c6e70412 ] Given certain conditions, some TDP MMU functions may not yield reliably / frequently enough. For example, if a paging structure was very large but had few, if any writable entries, wrprot_gfn_range could traverse many

[PATCH 5.10 076/126] reiserfs: update reiserfs_xattrs_initialized() condition

2021-04-05 Thread Greg Kroah-Hartman
From: Tetsuo Handa commit 5e46d1b78a03d52306f21f77a4e4a144b6d31486 upstream. syzbot is reporting NULL pointer dereference at reiserfs_security_init() [1], for commit ab17c4f02156c4f7 ("reiserfs: fixup xattr_root caching") is assuming that REISERFS_SB(s)->xattr_root != NULL in reiserfs_xattr_jcre

[PATCH 5.10 077/126] drm/imx: fix memory leak when fails to init

2021-04-05 Thread Greg Kroah-Hartman
From: Pan Bian commit 69c3ed7282a143439bbc2d03dc00d49c68fcb629 upstream. Put DRM device on initialization failure path rather than directly return error code. Fixes: a67d5088ceb8 ("drm/imx: drop explicit drm_mode_config_cleanup") Signed-off-by: Pan Bian Signed-off-by: Philipp Zabel Signed-off

[PATCH 5.10 078/126] drm/tegra: dc: Restore coupling of display controllers

2021-04-05 Thread Greg Kroah-Hartman
From: Thierry Reding commit a31500fe7055451ed9043c8fff938dfa6f70ee37 upstream. Coupling of display controllers used to rely on runtime PM to take the companion controller out of reset. Commit fd67e9c6ed5a ("drm/tegra: Do not implement runtime PM") accidentally broke this when runtime PM was remo

[PATCH 5.10 079/126] drm/tegra: sor: Grab runtime PM reference across reset

2021-04-05 Thread Greg Kroah-Hartman
From: Thierry Reding commit ac097aecfef0bb289ca53d2fe0b73fc7e1612a05 upstream. The SOR resets are exclusively shared with the SOR power domain. This means that exclusive access can only be granted temporarily and in order for that to work, a rigorous sequence must be observed. To ensure that a s

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