[PATCH v4 20/23] powerpc/syscall: Do not check unsupported scv vector on PPC32

2021-01-25 Thread Christophe Leroy
Only PPC64 has scv. No need to check the 0x7ff0 trap on PPC32. And ignore the scv parameter in syscall_exit_prepare (Save 14 cycles 346 => 332 cycles) Signed-off-by: Christophe Leroy --- arch/powerpc/kernel/entry_32.S | 1 - arch/powerpc/kernel/syscall.c | 7 +-- 2 files changed, 5

[PATCH RESEND V12 2/8] fuse: 32-bit user space ioctl compat for fuse device

2021-01-25 Thread Alessio Balsini
With a 64-bit kernel build the FUSE device cannot handle ioctl requests coming from 32-bit user space. This is due to the ioctl command translation that generates different command identifiers that thus cannot be used for direct comparisons without proper manipulation. Explicitly extract type and

Re: [PATCH v2 2/2] thermal: Move therm_throt there from x86/mce

2021-01-25 Thread Zhang Rui
Hi, Borislav, Thanks for the patch. CC Srinivas. On Mon, 2021-01-25 at 14:05 +0100, Borislav Petkov wrote: > From: Borislav Petkov > > This functionality has nothing to do with MCE, move it to the thermal > framework and untangle it from MCE. > Agreed. just one question, there are many

[PATCH v2 4/7] rbtree, perf: Use new rbtree helpers

2021-01-25 Thread Peter Zijlstra
Reduce rbtree boiler plate by using the new helpers. One noteworthy change is unification of the various (partial) compare functions. We construct a subtree match by forcing the sub-order to always match, see __group_cmp(). Due to 'const' we had to touch cgroup_id(). Cc: Tejun Heo

Re: [PATCH] Bluetooth: drop HCI device reference before return

2021-01-25 Thread Marcel Holtmann
Hi Pan, > Call hci_dev_put() to decrement reference count of HCI device hdev if > fails to duplicate memory. > > Fixes: 0b26ab9dce74 ("Bluetooth: AMP: Handle Accept phylink command status > evt") > Signed-off-by: Pan Bian > --- > net/bluetooth/a2mp.c | 1 + > 1 file changed, 1 insertion(+)

Re: [PATCH v10 05/12] mm: HUGE_VMAP arch support cleanup

2021-01-25 Thread Christophe Leroy
Le 24/01/2021 à 12:40, Christoph Hellwig a écrit : diff --git a/arch/arm64/include/asm/vmalloc.h b/arch/arm64/include/asm/vmalloc.h index 2ca708ab9b20..597b40405319 100644 --- a/arch/arm64/include/asm/vmalloc.h +++ b/arch/arm64/include/asm/vmalloc.h @@ -1,4 +1,12 @@ #ifndef

Re: [PATCH] amdgpu: fix clang build warning

2021-01-25 Thread Alex Deucher
On Mon, Jan 25, 2021 at 7:24 AM Arnd Bergmann wrote: > > From: Arnd Bergmann > > clang warns about the -mhard-float command line arguments > on architectures that do not support this: > > clang: error: argument unused during compilation: '-mhard-float' > [-Werror,-Wunused-command-line-argument]

Re: [PATCH 1/3] Bluetooth: btusb: Refactor gpio reset

2021-01-25 Thread Marcel Holtmann
Hi Abhishek, > Refactor gpio reset to use a common gpio reset function. > > Signed-off-by: Abhishek Pandit-Subedi > Reviewed-by: Miao-chen Chou > --- > > drivers/bluetooth/btusb.c | 59 +-- > 1 file changed, 19 insertions(+), 40 deletions(-) > > diff --git

Re: [PATCH net-next v2 1/2] dt-bindings: net: dsa: add MT7530 GPIO controller binding

2021-01-25 Thread Rob Herring
On Mon, 25 Jan 2021 12:43:21 +0800, DENG Qingfang wrote: > Add device tree binding to support MT7530 GPIO controller. > > Signed-off-by: DENG Qingfang > --- > Changes v1 -> v2: > No changes. > > Documentation/devicetree/bindings/net/dsa/mt7530.txt | 6 ++ > 1 file changed, 6

[PATCH v2] arm64: dts: ti: k3-j7200-main: Add support for higher speed modes in MMCSD subsystems

2021-01-25 Thread Aswath Govindraju
The following speed modes are now supported in J7200 SoC, - HS200 and HS400 modes at 1.8 V card voltage, in MMCSD0 subsystem [1]. - UHS-I speed modes in MMCSD1 subsystem [1]. Set respective tags in sdhci0 and remove no-1-8-v tag from sdhci1 device tree nodes. [1] - section 12.3.6.1.1 MMCSD

Re: [PATCH v2 5/9] ALSA: virtio: handling control and I/O messages for the PCM device

2021-01-25 Thread Guennadi Liakhovetski
On Sun, 24 Jan 2021, Anton Yakovlev wrote: The driver implements a message-based transport for I/O substream operations. Before the start of the substream, the hardware buffer is sliced into I/O messages, the number of which is equal to the current number of periods. The size of each message

[PATCH V2 5/6] x86_32/sysenter: use percpu to get thread.sp0 when sysenter

2021-01-25 Thread Lai Jiangshan
From: Lai Jiangshan TSS_entry2task_stack is used to refer to tss.sp1 which is stored the value of thread.sp0. At the code where TSS_entry2task_stack is used in sysenter, the CR3 is already kernel CR3 and kernel segments is loaded. So that we can directly use percpu for it instead of

[PATCH V2 3/6] x86_32/sysenter: switch to the task stack without emptying the entry stack

2021-01-25 Thread Lai Jiangshan
From: Lai Jiangshan Like the way x86_64 uses the "old" stack, we can save the entry stack pointer to a register and switch to the task stack. So that we have space on the "old" stack to save more things or scratch registers. Signed-off-by: Lai Jiangshan --- arch/x86/entry/entry_32.S | 11

Re: [PATCH v16 06/11] mm: introduce memfd_secret system call to create "secret" memory areas

2021-01-25 Thread Michal Hocko
On Thu 21-01-21 14:27:18, Mike Rapoport wrote: > From: Mike Rapoport > > Introduce "memfd_secret" system call with the ability to create memory > areas visible only in the context of the owning process and not mapped not > only to other processes but in the kernel page tables as well. > > The

Re: [PATCH v2 2/2] thermal: Move therm_throt there from x86/mce

2021-01-25 Thread Borislav Petkov
On Mon, Jan 25, 2021 at 09:14:35AM -0800, Srinivas Pandruvada wrote: > Can the handler, processing architectural features via thermal > interrupt, reside in arch/x86 folder or need to be > drivers/thermal/intel? Look at... > > > @@ -718,7 +699,7 @@ void intel_init_thermal(struct cpuinfo_x86 *c)

[PATCH] KVM: x86: allow KVM_REQ_GET_NESTED_STATE_PAGES outside guest mode for VMX

2021-01-25 Thread Paolo Bonzini
VMX also uses KVM_REQ_GET_NESTED_STATE_PAGES for the Hyper-V eVMCS, which may need to be loaded outside guest mode. Therefore we cannot WARN in that case. However, that part of nested_get_vmcs12_pages is _not_ needed at vmentry time. Split it out of KVM_REQ_GET_NESTED_STATE_PAGES handling, so

Re: [PATCH v12 4/5] drm/tegra: dc: Support memory bandwidth management

2021-01-25 Thread Dmitry Osipenko
28.12.2020 18:49, Dmitry Osipenko пишет: > Display controller (DC) performs isochronous memory transfers, and thus, > has a requirement for a minimum memory bandwidth that shall be fulfilled, > otherwise framebuffer data can't be fetched fast enough and this results > in a DC's data-FIFO underflow

[PATCH v2 7/8] cpupower: Remove family arg to decode_pstates()

2021-01-25 Thread Nathan Fontenot
The decode_pstates() routine no longer uses the CPU family and the caleed routines (get_cof() and get_did()) can grab the family from the global cpupower_cpu_info struct. These update removes passing the family arg to all these routines. Signed-off-by: Nathan Fontenot ---

[PATCH v2 4/8] cpupower: Remove unused pscur variable.

2021-01-25 Thread Nathan Fontenot
The pscur variable is set but not uused, just remove it. This may have previsously been set to validate the MSR_AMD_PSTATE_STATUS MSR. With the addition of the CPUPOWER_CAP_AMD_HW_PSTATE cap flag this is no longer needed since the cpuid bit to enable this cap flag also validates that the

[PATCH v3 RFC net-next 13/19] net: mvpp2: add RXQ flow control configurations

2021-01-25 Thread stefanc
From: Stefan Chulski This patch add RXQ flow control configurations. Patch do not enable flow control itself, flow control disabled by default. Signed-off-by: Stefan Chulski --- drivers/net/ethernet/marvell/mvpp2/mvpp2.h | 38 ++- drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c |

Re: [PATCH v4 1/5] clk: qcom: clk-alpha-pll: replace regval with val

2021-01-25 Thread Bjorn Andersson
On Sun 17 Jan 22:43 CST 2021, Vinod Koul wrote: > Driver uses regval variable for holding register values, replace with a > shorter one val > Reviewed-by: Bjorn Andersson Regards, Bjorn > Suggested-by: Stephen Boyd > Signed-off-by: Vinod Koul > --- > drivers/clk/qcom/clk-alpha-pll.c | 20

[PATCH v3 RFC net-next 16/19] net: mvpp2: add PPv23 RX FIFO flow control

2021-01-25 Thread stefanc
From: Stefan Chulski New FIFO flow control feature were added in PPv23. PPv2 FIFO polled by HW and trigger pause frame if FIFO fill level is below threshold. FIFO HW flow control enabled with CM3 RXQ flow control with ethtool. Current FIFO thresholds is: 9KB for port with maximum speed 10Gb/s

[PATCH v3 RFC net-next 11/19] net: mvpp2: add spinlock for FW FCA configuration path

2021-01-25 Thread stefanc
From: Stefan Chulski Spinlock added to MSS shared memory configuration space. Signed-off-by: Stefan Chulski --- drivers/net/ethernet/marvell/mvpp2/mvpp2.h | 5 + drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 3 +++ 2 files changed, 8 insertions(+) diff --git

[PATCH v3 RFC net-next 15/19] net: mvpp2: add BM protection underrun feature support

2021-01-25 Thread stefanc
From: Stefan Chulski Feature double size of BPPI by decreasing number of pools from 16 to 8. Increasing of BPPI size protect BM drop from BPPI underrun. Underrun could occurred due to stress on DDR and as result slow buffer transition from BPPE to BPPI. New BPPI threshold recommended by spec is:

Re: [PATCH v9 00/13] Add Broadcom VK driver

2021-01-25 Thread Greg Kroah-Hartman
On Wed, Jan 20, 2021 at 09:58:14AM -0800, Scott Branden wrote: > This patch series drops previous patches in [1] > that were incorporated by Kees Cook into patch series > "Introduce partial kernel_read_file() support" [2]. > > Remaining patches are contained in this series to add Broadcom VK

Re: [PATCH 3/3] Bluetooth: btusb: Expose reset gpio to debugfs

2021-01-25 Thread Marcel Holtmann
Hi Abhishek, > If btusb has a reset gpio, expose it to userspace so we can toggle the > reset gpio directly. This is useful for testing and error recovery. > > Signed-off-by: Abhishek Pandit-Subedi > Reviewed-by: Miao-chen Chou > --- > > drivers/bluetooth/btusb.c | 46

Re: [PATCH v2] KVM/SVM: add support for SEV attestation command

2021-01-25 Thread Paolo Bonzini
On 04/01/21 16:17, Brijesh Singh wrote: The SEV FW version >= 0.23 added a new command that can be used to query the attestation report containing the SHA-256 digest of the guest memory encrypted through the KVM_SEV_LAUNCH_UPDATE_{DATA, VMSA} commands and sign the report with the Platform

Re: [PATCH V2] x86/entry/64: De-Xen-ify our NMI code further

2021-01-25 Thread Steven Rostedt
On Mon, 25 Jan 2021 12:38:59 -0500 Steven Rostedt wrote: > On triggering an NMI from user space, I see the switch to the thread stack > is done, and "exc_nmi" is called. > > The problem I see with this is that exc_nmi is called with the thread > stack, if it were to take an exception, NMIs

Re: [PATCH v2] bpf: Drop disabled LSM hooks from the sleepable set

2021-01-25 Thread KP Singh
On Mon, Jan 25, 2021 at 7:39 AM Mikko Ylinen wrote: > > Some networking and keys LSM hooks are conditionally enabled > and when building the new sleepable BPF LSM hooks with those > LSM hooks disabled, the following build error occurs: > > BTFIDS vmlinux > FAILED unresolved symbol

linux-next-20210125: drivers/crypto/marvell/octeontx2/ build errors

2021-01-25 Thread Randy Dunlap
on x86_64: ld: drivers/crypto/marvell/octeontx2/otx2_cptpf_main.o: in function `cptpf_flr_wq_handler': otx2_cptpf_main.c:(.text+0x2b): undefined reference to `otx2_mbox_alloc_msg_rsp' ld: drivers/crypto/marvell/octeontx2/otx2_cptpf_main.o: in function `otx2_cptpf_probe':

Re: [PATCH v4 5/5] clk: qcom: gcc: Add clock driver for SM8350

2021-01-25 Thread Bjorn Andersson
On Sun 17 Jan 22:43 CST 2021, Vinod Koul wrote: > From: Vivek Aknurwar > > This adds Global Clock controller (GCC) driver for SM8350 SoC > > Signed-off-by: Vivek Aknurwar > Signed-off-by: Jeevan Shriram > [vkoul: rebase and tidy up for upstream] > Signed-off-by: Vinod Koul Reviewed-by:

Re: [PATCH v5 0/4] Add bus lock VM exit support

2021-01-25 Thread Paolo Bonzini
On 06/11/20 10:03, Chenyi Qiang wrote: This patch series add the support for bus lock VM exit in KVM. It is a sub-feature of bus lock detection. When it is enabled by the VMM, the processor generates a "Bus Lock" VM exit following execution of an instruction if the processor detects that one or

[PATCH v3 1/4] ARM: dts: qcom: msm8974: add gpu support

2021-01-25 Thread Iskren Chernev
From: Brian Masney Add support for the a3xx GPU. opp_table is chosen to include lower frequencies common to all different msm8974 variants. Signed-off-by: Brian Masney [iskren.cher...@gmail.com: change opp-table values in v3] Signed-off-by: Iskren Chernev --- Changes in v3: - change opp-table

[PATCH v3 4/4] ARM: dts: qcom: msm8974-klte: Mark essential regulators

2021-01-25 Thread Iskren Chernev
s1 and l12 regulators are used for the memory and cache on the Samsung S5 (klte). If they are turned off the phone shuts down. So mark them as always-on to prevent that from happening. Signed-off-by: Iskren Chernev Tested-by: Alexey Minnekhanov ---

Re: [PATCH v3] tracing: precise log info for kretprobe addr err

2021-01-25 Thread Oleg Nesterov
On 01/26, Jianlin Lv wrote: > > When trying to create kretprobe with the wrong function symbol in tracefs; > The error is triggered in the register_trace_kprobe() and recorded as > FAIL_REG_PROBE issue, > > Example: > $ cd /sys/kernel/debug/tracing > $ echo 'r:myprobe ERROR_SYMBOL_XXX ret=%x0'

Re: [PATCH] tpm_tis: Add missing start/stop_tpm_chip calls

2021-01-25 Thread Jarkko Sakkinen
On Sat, Jan 23, 2021 at 02:42:47AM +0100, Lukasz Majczak wrote: > There is a missing call to start_tpm_chip before the call to > the tpm_get_timeouts() and tpm_tis_probe_irq_single(). As the current > approach maight work for tpm2, it fails for tpm1.x - in that case > call to tpm_get_timeouts() or

Re: [PATCH v16 10/11] arch, mm: wire up memfd_secret system call where relevant

2021-01-25 Thread Catalin Marinas
On Thu, Jan 21, 2021 at 02:27:22PM +0200, Mike Rapoport wrote: > diff --git a/arch/arm64/include/uapi/asm/unistd.h > b/arch/arm64/include/uapi/asm/unistd.h > index f83a70e07df8..ce2ee8f1e361 100644 > --- a/arch/arm64/include/uapi/asm/unistd.h > +++ b/arch/arm64/include/uapi/asm/unistd.h > @@

Re: [PATCH net-next 2/3] net: constify page_is_pfmemalloc() argument at call sites

2021-01-25 Thread David Rientjes
On Mon, 25 Jan 2021, Alexander Lobakin wrote: > Constify "page" argument for page_is_pfmemalloc() users where applicable. > > Signed-off-by: Alexander Lobakin > --- > drivers/net/ethernet/hisilicon/hns3/hns3_enet.c | 2 +- > drivers/net/ethernet/intel/fm10k/fm10k_main.c | 2 +- >

Re: [PATCH] mm/filemap: Adding missing mem_cgroup_uncharge() to __add_to_page_cache_locked()

2021-01-25 Thread Waiman Long
On 1/25/21 1:14 PM, Michal Hocko wrote: On Mon 25-01-21 17:41:19, Michal Hocko wrote: On Mon 25-01-21 16:25:06, Matthew Wilcox wrote: On Mon, Jan 25, 2021 at 05:03:28PM +0100, Michal Hocko wrote: On Mon 25-01-21 10:57:54, Waiman Long wrote: On 1/25/21 4:28 AM, Michal Hocko wrote: On Sun

Re: [PATCH v3] PM / clk: make PM clock layer compatible with clocks that must sleep

2021-01-25 Thread Nicolas Pitre
On Mon, 25 Jan 2021, Rafael J. Wysocki wrote: > On Sun, Jan 24, 2021 at 12:07 AM Nicolas Pitre wrote: > > A note on sparse: > > According to https://lwn.net/Articles/109066/ there are things > > that sparse can't cope with. In particular, pm_clk_op_lock() and > > pm_clk_op_unlock() may or may

[PATCH v3 RFC net-next 10/19] net: mvpp2: add FCA RXQ non occupied descriptor threshold

2021-01-25 Thread stefanc
From: Stefan Chulski RXQ non occupied descriptor threshold would be used by Flow Control Firmware feature to move to the XOFF mode. RXQ non occupied threshold would change interrupt cause that polled by CM3 Firmware. Actual non occupied interrupt masked and won't trigger interrupt.

[PATCH v5 2/2] dt-bindings: pinctrl: Add bindings for Awinic AW9523/AW9523B

2021-01-25 Thread AngeloGioacchino Del Regno
Add bindings for the Awinic AW9523/AW9523B I2C GPIO Expander driver. Signed-off-by: AngeloGioacchino Del Regno --- .../pinctrl/awinic,aw9523-pinctrl.yaml| 139 ++ 1 file changed, 139 insertions(+) create mode 100644

Re: [PATCH v2] Bluetooth: btusb: fix memory leak on suspend and resume

2021-01-25 Thread Marcel Holtmann
Hi Vamshi, > kmemleak report: > unreferenced object 0x9b1127f00500 (size 208): > comm "kworker/u17:2", pid 500, jiffies 4294937470 (age 580.136s) > hex dump (first 32 bytes): >00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >00 60 ed 05 11 9b ff ff 00 00 00 00 00

Re: [PATCH v17 11/26] x86/mm: Update ptep_set_wrprotect() and pmdp_set_wrprotect() for transition from _PAGE_DIRTY to _PAGE_COW

2021-01-25 Thread Borislav Petkov
On Tue, Dec 29, 2020 at 01:30:38PM -0800, Yu-cheng Yu wrote: > When Shadow Stack is introduced, [R/O + _PAGE_DIRTY] PTE is reserved for > shadow stack. Copy-on-write PTEs have [R/O + _PAGE_COW]. > > When a PTE goes from [R/W + _PAGE_DIRTY] to [R/O + _PAGE_COW], it could > become a transient

Re: [PATCH net-next 2/3] net: constify page_is_pfmemalloc() argument at call sites

2021-01-25 Thread Alexander Lobakin
From: David Rientjes Date: Mon, 25 Jan 2021 10:19:48 -0800 (PST) > On Mon, 25 Jan 2021, Alexander Lobakin wrote: > > > Constify "page" argument for page_is_pfmemalloc() users where applicable. > > > > Signed-off-by: Alexander Lobakin > > --- > > drivers/net/ethernet/hisilicon/hns3/hns3_enet.c

Re: [PATCH 2/3] dt-bindings: iio: Add cros ec proximity yaml doc

2021-01-25 Thread Stephen Boyd
Quoting Gwendal Grignou (2021-01-24 12:42:56) > On Sun, Jan 24, 2021 at 9:28 AM Jonathan Cameron wrote: > > On Fri, 22 Jan 2021 14:54:42 -0800 > > Stephen Boyd wrote: > > > + > > > +properties: > > > + compatible: > > > +const: google,cros-ec-proximity > Given we have proximity detection in

Re: [PATCH] Bluetooth: btusb: Add a Kconfig option to disable USB wakeup by default

2021-01-25 Thread Marcel Holtmann
Hi Max, > For the original commit of 9e45524a011107a73bc2cdde8370c61e82e93a4d, > wakeup is always disabled for Realtek Bluetooth devices. > However, there's the capability for Realtek Bluetooth devices to > apply USB wakeup. Otherwise, there's the better power consumption > without USB wakeup

Re: [PATCH] swiotlb: Validate bounce size in the sync/unmap path

2021-01-25 Thread Martin Radev
On Mon, Jan 18, 2021 at 10:14:28AM -0500, Konrad Rzeszutek Wilk wrote: > On Mon, Jan 18, 2021 at 12:44:58PM +0100, Martin Radev wrote: > > On Wed, Jan 13, 2021 at 12:30:17PM +0100, Christoph Hellwig wrote: > > > On Tue, Jan 12, 2021 at 04:07:29PM +0100, Martin Radev wrote: > > > > The size of the

Re: [PATCH] KVM: x86/mmu: consider the hva in mmu_notifer retry

2021-01-25 Thread Sean Christopherson
+Cc the other architectures, I'm guessing this would be a helpful optimization for all archs. Quite a few comments, but they're all little more than nits. Nice! On Mon, Jan 25, 2021, David Stevens wrote: > From: David Stevens > > Use the range passed to mmu_notifer's invalidate_range_start to

[PATCH 5.4 11/86] mmc: core: dont initialize block size from ext_csd if not present

2021-01-25 Thread Greg Kroah-Hartman
From: Peter Collingbourne commit b503087445ce7e45fabdee87ca9e460d5b5b5168 upstream. If extended CSD was not available, the eMMC driver would incorrectly set the block size to 0, as the data_sector_size field of ext_csd was never initialized. This issue was exposed by commit 817046ecddbc

[PATCH 5.4 10/86] btrfs: send: fix invalid clone operations when cloning from the same file and root

2021-01-25 Thread Greg Kroah-Hartman
From: Filipe Manana commit 518837e65068c385dddc0a87b3e577c8be7c13b1 upstream. When an incremental send finds an extent that is shared, it checks which file extent items in the range refer to that extent, and for those it emits clone operations, while for others it emits regular write operations

[PATCH 5.4 55/86] x86/mmx: Use KFPU_387 for MMX string operations

2021-01-25 Thread Greg Kroah-Hartman
From: Andy Lutomirski commit 67de8dca50c027ca0fa3b62a488ee5035036a0da upstream. The default kernel_fpu_begin() doesn't work on systems that support XMM but haven't yet enabled CR4.OSFXSR. This causes crashes when _mmx_memcpy() is called too early because LDMXCSR generates #UD when the

[PATCH 5.4 37/86] drm/nouveau/bios: fix issue shadowing expansion ROMs

2021-01-25 Thread Greg Kroah-Hartman
From: Ben Skeggs [ Upstream commit 402a89660e9dc880710b12773076a336c9dab3d7 ] This issue has generally been covered up by the presence of additional expansion ROMs after the ones we're interested in, with header fetches of subsequent images loading enough of the ROM to hide the issue. Noticed

[PATCH 5.4 38/86] drm/nouveau/privring: ack interrupts the same way as RM

2021-01-25 Thread Greg Kroah-Hartman
From: Ben Skeggs [ Upstream commit e05e06cd34f5311f677294a08b609acfbc315236 ] Whatever it is that we were doing before doesn't work on Ampere. Signed-off-by: Ben Skeggs Signed-off-by: Sasha Levin --- drivers/gpu/drm/nouveau/nvkm/subdev/ibus/gf100.c | 10 +++---

[PATCH 5.10 035/199] ASoC: rt711: mutex between calibration and power state changes

2021-01-25 Thread Greg Kroah-Hartman
From: Shuming Fan [ Upstream commit 6108f990c0887d3e8f1db2d13c7012e40a061f28 ] To avoid calibration time-out, this patch adds the mutex between calibration and power state changes Signed-off-by: Shuming Fan Link: https://lore.kernel.org/r/20201217085651.24580-1-shumi...@realtek.com

[PATCH 5.10 020/199] pinctrl: ingenic: Fix JZ4760 support

2021-01-25 Thread Greg Kroah-Hartman
From: Paul Cercueil commit 9a85c09a3f507b925d75cb0c7c8f364467038052 upstream. - JZ4760 and JZ4760B have a similar register layout as the JZ4740, and don't use the new register layout, which was introduced with the JZ4770 SoC and not the JZ4760 or JZ4760B SoCs. - The JZ4740 code path only

[PATCH 5.10 006/199] platform/x86: i2c-multi-instantiate: Dont create platform device for INT3515 ACPI nodes

2021-01-25 Thread Greg Kroah-Hartman
From: Heikki Krogerus commit 9bba96275576da0cf78ede62aeb2fc975ed8a32d upstream. There are several reports about the tps6598x causing interrupt flood on boards with the INT3515 ACPI node, which then causes instability. There appears to be several problems with the interrupt. One problem is that

[PATCH 5.10 041/199] scsi: ufs: Relax the condition of UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL

2021-01-25 Thread Greg Kroah-Hartman
From: Stanley Chu [ Upstream commit 21acf4601cc63cf564c6fc1a74d81b191313c929 ] UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL is intended to skip enabling fWriteBoosterBufferFlushEn while WriteBooster is initializing. Therefore it is better to apply the checking during WriteBooster initialization

[PATCH 5.10 056/199] x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery

2021-01-25 Thread Greg Kroah-Hartman
From: David Woodhouse [ Upstream commit b36b0fe96af13460278bf9b173beced1bd15f85d ] It's useful to be able to test non-vector event channel delivery, to make sure Linux will work properly on older Xen which doesn't have it. It's also useful for those working on Xen and Xen-compatible

[PATCH 5.10 060/199] riscv: defconfig: enable gpio support for HiFive Unleashed

2021-01-25 Thread Greg Kroah-Hartman
From: Sagar Shrikant Kadam [ Upstream commit 0983834a83931606a647c275e5d4165ce4e7b49f ] Ethernet phy VSC8541-01 on HiFive Unleashed has its reset line connected to a gpio, so enable GPIO driver's required to reset the phy. Signed-off-by: Sagar Shrikant Kadam Signed-off-by: Palmer Dabbelt

[PATCH 5.10 091/199] bpf: Reject too big ctx_size_in for raw_tp test run

2021-01-25 Thread Greg Kroah-Hartman
From: Song Liu [ Upstream commit 7ac6ad051150592557520b45773201b987ecfce3 ] syzbot reported a WARNING for allocating too big memory: WARNING: CPU: 1 PID: 8484 at mm/page_alloc.c:4976 __alloc_pages_nodemask+0x5f8/0x730 mm/page_alloc.c:5011 Modules linked in: CPU: 1 PID: 8484 Comm:

[PATCH 5.10 110/199] i2c: sprd: depend on COMMON_CLK to fix compile tests

2021-01-25 Thread Greg Kroah-Hartman
From: Krzysztof Kozlowski [ Upstream commit 9ecd1d2b302b600351fac50779f43fcb680c1a16 ] The I2C_SPRD uses Common Clock Framework thus it cannot be built on platforms without it (e.g. compile test on MIPS with LANTIQ): /usr/bin/mips-linux-gnu-ld: drivers/i2c/busses/i2c-sprd.o: in function

[PATCH 5.10 113/199] drivers: iio: temperature: Add delay after the addressed reset command in mlx90632.c

2021-01-25 Thread Greg Kroah-Hartman
From: Slaveyko Slaveykov commit cf5b1385d748b2f91b0c05bb301fcaf9bdbad385 upstream. After an I2C reset command, the mlx90632 needs some time before responding to other I2C commands. Without that delay, there is a chance that the I2C command(s) after the reset will not be accepted.

[PATCH 5.10 112/199] iio: ad5504: Fix setting power-down state

2021-01-25 Thread Greg Kroah-Hartman
From: Lars-Peter Clausen commit efd597b2839a9895e8a98fcb0b76d2f545802cd4 upstream. The power-down mask of the ad5504 is actually a power-up mask. Meaning if a bit is set the corresponding channel is powered up and if it is not set the channel is powered down. The driver currently has this the

[PATCH v2 0/8] cpupower: Updates and cleanup to support AMD Family 0x19

2021-01-25 Thread Nathan Fontenot
Updates to the cpupower command to add support for AMD family 0x19 and cleanup the code to remove many of the family checks to hopefully make any future family updates easier. The first couple of patches are simple updates to rename the structs in the msr_pstate union to better reflect current

Re: [PATCH] mmc: brcmstb: Fix sdhci_pltfm_suspend link error

2021-01-25 Thread Florian Fainelli
+Nicolas, On 1/25/2021 4:50 AM, Arnd Bergmann wrote: > From: Arnd Bergmann > > sdhci_pltfm_suspend() is only available when CONFIG_PM_SLEEP > support is built into the kernel, which caused a regression > in a recent bugfix: > > ld.lld: error: undefined symbol: sdhci_pltfm_suspend

[PATCH v2 3/8] cpupower: Add CPUPOWER_CAP_AMD_HW_PSTATE cpuid caps flag

2021-01-25 Thread Nathan Fontenot
Add a check in get_cpu_info() for the ability to read frequencies from hardware and set the CPUPOWER_CAP_AMD_HW_PSTATE cpuid flag. The cpuid flag is set when CPUID_8007_EDX[7] is set, which is all families >= 10h. The check excludes family 14h because HW pstate reporting was not implemented on

Re: [PATCH] bpf: Drop disabled LSM hooks from the sleepable set

2021-01-25 Thread KP Singh
On Mon, Jan 25, 2021 at 7:55 AM Mikko Ylinen wrote: > > On Sat, Jan 23, 2021 at 12:50:21AM +0100, KP Singh wrote: > > On Fri, Jan 22, 2021 at 11:33 PM KP Singh wrote: > > > > > > On Fri, Jan 22, 2021 at 1:32 PM Mikko Ylinen > > > wrote: > > > > > > > > Networking LSM hooks are conditionally

Re: [PATCH v4 1/3] arm64: Improve kernel address detection of __is_lm_address()

2021-01-25 Thread Catalin Marinas
On Mon, Jan 25, 2021 at 04:09:57PM +, Vincenzo Frascino wrote: > On 1/25/21 2:59 PM, Catalin Marinas wrote: > > On Mon, Jan 25, 2021 at 02:36:34PM +, Vincenzo Frascino wrote: > >> On 1/25/21 1:02 PM, Mark Rutland wrote: > >>> On Fri, Jan 22, 2021 at 03:56:40PM +, Vincenzo Frascino

Re: [PATCH] hwmon: (dell-smm) Add XPS 15 L502X to fan control blacklist

2021-01-25 Thread Tom Hebb
On Mon, Jan 25, 2021 at 2:05 AM Pali Rohár wrote: > > On Saturday 23 January 2021 18:46:08 Thomas Hebb wrote: > > It has been reported[0] that the Dell XPS 15 L502X exhibits similar > > freezing behavior to the other systems[1] on this blacklist. The issue > > was exposed by a prior change of

Re: [PATCH] smackfs: restrict bytes count in smackfs write functions

2021-01-25 Thread Casey Schaufler
On 1/24/2021 6:36 AM, Sabyrzhan Tasbolatov wrote: > syzbot found WARNINGs in several smackfs write operations where > bytes count is passed to memdup_user_nul which exceeds > GFP MAX_ORDER. Check count size if bigger SMK_LONGLABEL, > for smk_write_syslog if bigger than PAGE_SIZE - 1. > >

Re: [PATCH RFC v1 0/3] Introduce vfio-pci-core subsystem

2021-01-25 Thread Jason Gunthorpe
On Mon, Jan 25, 2021 at 05:20:35PM +0100, Cornelia Huck wrote: > I think you cut out an important part of Alex' comment, so let me > repost it here: Yes, I've already respnded to this. > I'm missing the bigger picture of how this api is supposed to work out, > a driver with a lot of TODOs does

Re: hppa64-linux-ld: mm/hugetlb.o(.text+0x50dc): cannot reach printk

2021-01-25 Thread Nick Desaulniers
I suspect that adding some more sections here makes the distance between other sections too large to encode? IIRC, arm (32b) linker can emit "range extending thunks" to help jump large distances. Not sure what to make of this report; I wouldn't have expected this GCC randconfig to generate code

Re: [PATCH] sched/fair: Rate limit calls to update_blocked_averages() for NOHZ

2021-01-25 Thread Dietmar Eggemann
On 25/01/2021 18:30, Vincent Guittot wrote: > On Mon, 25 Jan 2021 at 11:45, Dietmar Eggemann > wrote: >> >> On 22/01/2021 20:10, Joel Fernandes wrote: >>> Hi Vincent, >>> >>> Thanks for reply. Please see the replies below: >>> >>> On Fri, Jan 22, 2021 at 05:56:22PM +0100, Vincent Guittot wrote:

Re: [PATCH v3 1/5] selftests/x86: Simplify the code to get vdso base address in sgx

2021-01-25 Thread Jarkko Sakkinen
What the short summary is saying now, is that this commit would make the existing code to use vDSO base address. It's already doing that. You could instead just "Use getauxval() to simplify the code". Also, I'd prefer to properly use upper and lower case letter, e.g. vDSO instead of vdso.

Re: [PATCH v1 5/5] driver core: Set fw_devlink=on by default

2021-01-25 Thread Saravana Kannan
t devices and probe them like normal > > device drivers so that the driver core is aware of the devices and their > > status. See [1] for an example of such a case. > > > > [1] - > > https://lore.kernel.org/lkml/CAGETcx9PiX==mlxb9po8myyk6u2vhpvwtmsa5nkd-ywh5xh...@mail.gm

[PATCH 1/2] pinctrl: Add driver for Awinic AW9523/B I2C GPIO Expander

2021-01-25 Thread AngeloGioacchino Del Regno
The Awinic AW9523(B) is a multi-function I2C gpio expander in a TQFN-24L package, featuring PWM (max 37mA per pin, or total max power 3.2Watts) for LED driving capability. It has two ports with 8 pins per port (for a total of 16 pins), configurable as either PWM with 1/256 stepping or GPIO

[PATCH v5 1/2] pinctrl: Add driver for Awinic AW9523/B I2C GPIO Expander

2021-01-25 Thread AngeloGioacchino Del Regno
The Awinic AW9523(B) is a multi-function I2C gpio expander in a TQFN-24L package, featuring PWM (max 37mA per pin, or total max power 3.2Watts) for LED driving capability. It has two ports with 8 pins per port (for a total of 16 pins), configurable as either PWM with 1/256 stepping or GPIO

Re: [PATCH v5 trivial/resend] dt-bindings: net: btusb: DT fix s/interrupt-name/interrupt-names/

2021-01-25 Thread Marcel Holtmann
Hi Geert, > The standard DT property name is "interrupt-names". > > Fixes: fd913ef7ce619467 ("Bluetooth: btusb: Add out-of-band wakeup support") > Signed-off-by: Geert Uytterhoeven > Acked-by: Rob Herring > Reviewed-by: Brian Norris > Acked-by: Rajat Jain > --- > Who takes this patch, before

[PATCH 2/2] dt-bindings: pinctrl: Add bindings for Awinic AW9523/AW9523B

2021-01-25 Thread AngeloGioacchino Del Regno
Add bindings for the Awinic AW9523/AW9523B I2C GPIO Expander driver. Signed-off-by: AngeloGioacchino Del Regno --- .../pinctrl/awinic,aw9523-pinctrl.yaml| 139 ++ 1 file changed, 139 insertions(+) create mode 100644

[PATCH v3 RFC net-next 06/19] net: mvpp2: always compare hw-version vs MVPP21

2021-01-25 Thread stefanc
From: Stefan Chulski Currently we have PP2v1 and PP2v2 hw-versions, with some different handlers depending upon condition hw_version = MVPP21/MVPP22. In a future there will be also PP2v3. Let's use now the generic "if equal/notEqual MVPP21" for all cases instead of "if MVPP22". This patch does

Re: [PATCH] percpu: fix clang modpost warning in pcpu_build_alloc_info()

2021-01-25 Thread Nick Desaulniers
On Mon, Jan 25, 2021 at 3:07 AM Arnd Bergmann wrote: > > On Tue, Jan 5, 2021 at 1:55 AM Dennis Zhou wrote: > > > > On Mon, Jan 04, 2021 at 04:46:51PM -0700, Nathan Chancellor wrote: > > > On Thu, Dec 31, 2020 at 09:28:52PM +, Dennis Zhou wrote: > > > > > > > > Hi Nathan, > > > > > > > > Hi

[PATCH v3 RFC net-next 07/19] net: mvpp2: increase BM pool size to 2048 buffers

2021-01-25 Thread stefanc
From: Stefan Chulski BM pool size increased to support Firmware Flow Control. Minimum depletion thresholds to support FC is 1024 buffers. BM pool size increased to 2048 to have some 1024 buffers space between depletion thresholds and BM pool size. Jumbo frames require a 9888B buffer, so memory

Re: [PATCH v3 0/2] arm64: dts: meson: add support for Beelink GS-King-X

2021-01-25 Thread Kevin Hilman
On Tue, 19 Jan 2021 14:57:32 +, Christian Hewitt wrote: > This series adds bindings and device-tree for the Beelink (AZW) GS-King-X, > which like GT-King and GT-King Pro is based on the W400 reference design. > > Changes since v2: > - shorten audio card name to GSKING-X > - add Neil's

[PATCH 4.19 35/58] serial: mvebu-uart: fix tx lost characters at power off

2021-01-25 Thread Greg Kroah-Hartman
From: Pali Rohár commit 54ca955b5a4024e2ce0f206b03adb7109bc4da26 upstream. Commit c685af1108d7 ("serial: mvebu-uart: fix tx lost characters") fixed tx lost characters at low baud rates but started causing tx lost characters when kernel is going to power off or reboot. TX_EMP tells us when

[PATCH 4.19 14/58] scsi: qedi: Correct max length of CHAP secret

2021-01-25 Thread Greg Kroah-Hartman
From: Nilesh Javali [ Upstream commit d50c7986fbf0e2167279e110a2ed5bd8e811c660 ] The CHAP secret displayed garbage characters causing iSCSI login authentication failure. Correct the CHAP password max length. Link: https://lore.kernel.org/r/20201217105144.8055-1-njav...@marvell.com Reviewed-by:

[PATCH 5.10 036/199] SUNRPC: Handle TCP socket sends with kernel_sendpage() again

2021-01-25 Thread Greg Kroah-Hartman
From: Chuck Lever [ Upstream commit 4a85a6a3320b4a622315d2e0ea91a1d2b013bce4 ] Daire Byrne reports a ~50% aggregrate throughput regression on his Linux NFS server after commit da1661b93bf4 ("SUNRPC: Teach server to use xprt_sock_sendmsg for socket sends"), which replaced kernel_send_page()

[PATCH 5.10 039/199] dm integrity: select CRYPTO_SKCIPHER

2021-01-25 Thread Greg Kroah-Hartman
From: Anthony Iliopoulos [ Upstream commit f7b347acb5f6c29d9229bb64893d8b6a2c7949fb ] The integrity target relies on skcipher for encryption/decryption, but certain kernel configurations may not enable CRYPTO_SKCIPHER, leading to compilation errors due to unresolved symbols. Explicitly select

[PATCH 5.10 049/199] HID: logitech-dj: add the G602 receiver

2021-01-25 Thread Greg Kroah-Hartman
From: Filipe Laíns [ Upstream commit e400071a805d6229223a98899e9da8c6233704a1 ] Tested. The device gets correctly exported to userspace and I can see mouse and keyboard events. Signed-off-by: Filipe Laíns Signed-off-by: Jiri Kosina Signed-off-by: Sasha Levin ---

[PATCH 5.10 033/199] drm/i915: Check for rq->hwsp validity after acquiring RCU lock

2021-01-25 Thread Greg Kroah-Hartman
From: Chris Wilson commit 45db630e5f7ec83817c57c8ae387fe219bd42adf upstream. Since we allow removing the timeline map at runtime, there is a risk that rq->hwsp points into a stale page. To control that risk, we hold the RCU read lock while reading *rq->hwsp, but we missed a couple of important

[PATCH 5.10 061/199] drm/amdgpu/psp: fix psp gfx ctrl cmds

2021-01-25 Thread Greg Kroah-Hartman
From: Victor Zhao [ Upstream commit f14a5c34d143f6627f0be70c0de1d962f3a6ff1c ] psp GFX_CTRL_CMD_ID_CONSUME_CMD different for windows and linux, according to psp, linux cmds are not correct. v2: only correct GFX_CTRL_CMD_ID_CONSUME_CMD. Signed-off-by: Victor Zhao Reviewed-by: Emily.Deng

[PATCH 5.10 094/199] RDMA/cma: Fix error flow in default_roce_mode_store

2021-01-25 Thread Greg Kroah-Hartman
From: Neta Ostrovsky [ Upstream commit 7c7b3e5d9aeed31d35c5dab0bf9c0fd4c8923206 ] In default_roce_mode_store(), we took a reference to cma_dev, but didn't return it with cma_dev_put in the error flow. Fixes: 1c15b4f2a42f ("RDMA/core: Modify enum ib_gid_type and enum rdma_network_type") Link:

[PATCH 5.10 119/199] x86/mmx: Use KFPU_387 for MMX string operations

2021-01-25 Thread Greg Kroah-Hartman
From: Andy Lutomirski commit 67de8dca50c027ca0fa3b62a488ee5035036a0da upstream. The default kernel_fpu_begin() doesn't work on systems that support XMM but haven't yet enabled CR4.OSFXSR. This causes crashes when _mmx_memcpy() is called too early because LDMXCSR generates #UD when the

[PATCH 5.10 118/199] irqchip/mips-cpu: Set IPI domain parent chip

2021-01-25 Thread Greg Kroah-Hartman
From: Mathias Kresin commit 599b3063adf4bf041a87a69244ee36aded0d878f upstream. Since commit 55567976629e ("genirq/irqdomain: Allow partial trimming of irq_data hierarchy") the irq_data chain is valided. The irq_domain_trim_hierarchy() function doesn't consider the irq + ipi domain hierarchy as

[PATCH 5.10 128/199] io_uring: fix short read retries for non-reg files

2021-01-25 Thread Greg Kroah-Hartman
From: Pavel Begunkov commit 9a173346bd9e16ab19c7addb8862d95a5cea9feb upstream. Sockets and other non-regular files may actually expect short reads to happen, don't retry reads for them. Because non-reg files don't set FMODE_BUF_RASYNC and so it won't do second/retry do_read, we can filter out

[PATCH 5.10 155/199] sh: Remove unused HAVE_COPY_THREAD_TLS macro

2021-01-25 Thread Greg Kroah-Hartman
From: Jinyang He commit 19170492735be935747b0545b7eed8bb40cc1209 upstream. Fixes: e1cc9d8d596e ("sh: switch to copy_thread_tls()") Signed-off-by: Jinyang He Signed-off-by: Rich Felker Signed-off-by: Greg Kroah-Hartman --- arch/sh/Kconfig |1 - 1 file changed, 1 deletion(-) ---

[PATCH 5.10 121/199] proc_sysctl: fix oops caused by incorrect command parameters

2021-01-25 Thread Greg Kroah-Hartman
From: Xiaoming Ni commit 697edcb0e4eadc41645fe88c991fe6a206b1a08d upstream. The process_sysctl_arg() does not check whether val is empty before invoking strlen(val). If the command line parameter () is incorrectly configured and val is empty, oops is triggered. For example:

[PATCH 5.10 153/199] drm/i915/hdcp: Update CP property in update_pipe

2021-01-25 Thread Greg Kroah-Hartman
From: Anshuman Gupta commit b3c95d0bdb0855b1f28370629e9eebec6bceac17 upstream. When crtc state need_modeset is true it is not necessary it is going to be a real modeset, it can turns to be a fastset instead of modeset. This turns content protection property to be DESIRED and hdcp update_pipe

[PATCH 5.10 172/199] ipv6: create multicast route with RTPROT_KERNEL

2021-01-25 Thread Greg Kroah-Hartman
From: Matteo Croce commit a826b04303a40d52439aa141035fca5654ccaccd upstream. The ff00::/8 multicast route is created without specifying the fc_protocol field, so the default RTPROT_BOOT value is used: $ ip -6 -d route unicast ::1 dev lo proto kernel scope global metric 256 pref medium

[PATCH 5.10 156/199] locking/lockdep: Cure noinstr fail

2021-01-25 Thread Greg Kroah-Hartman
From: Peter Zijlstra commit 0afda3a888dccf12557b41ef42eee942327d122b upstream. When the compiler doesn't feel like inlining, it causes a noinstr fail: vmlinux.o: warning: objtool: lock_is_held_type()+0xb: call to lockdep_enabled() leaves .noinstr.text section Fixes: 4d004099a668 ("lockdep:

  1   2   3   4   5   6   7   8   9   10   >