[PATCH 5.10 043/199] 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 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 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 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 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 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 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 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 008/199] ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()

2021-01-25 Thread Greg Kroah-Hartman
From: Takashi Iwai commit 217bfbb8b0bfa24619b11ab75c135fec99b99b20 upstream. snd_seq_oss_synth_make_info() didn't check the error code from snd_seq_oss_midi_make_info(), and this leads to the call of strlcpy() with the uninitialized string as the source, which may lead to the access over the

[PATCH 5.10 015/199] btrfs: do not double free backref nodes on error

2021-01-25 Thread Greg Kroah-Hartman
From: Josef Bacik commit 49ecc679ab48b40ca799bf94b327d5284eac9e46 upstream. Zygo reported the following KASAN splat: BUG: KASAN: use-after-free in btrfs_backref_cleanup_node+0x18a/0x420 Read of size 8 at addr 888112402950 by task btrfs/28836 CPU: 0 PID: 28836 Comm: btrfs Tainted: G

[PATCH 5.4 80/86] net_sched: reject silly cell_log in qdisc_get_rtab()

2021-01-25 Thread Greg Kroah-Hartman
From: Eric Dumazet commit e4bedf48aaa5552bc1f49703abd17606e7e6e82a upstream. iproute2 probably never goes beyond 8 for the cell exponent, but stick to the max shift exponent for signed 32bit. UBSAN reported: UBSAN: shift-out-of-bounds in net/sched/sch_api.c:389:22 shift exponent 130 is too

[PATCH 5.4 48/86] selftests: net: fib_tests: remove duplicate log test

2021-01-25 Thread Greg Kroah-Hartman
From: Hangbin Liu [ Upstream commit fd23d2dc180fccfad4b27a8e52ba1bc415d18509 ] The previous test added an address with a specified metric and check if correspond route was created. I somehow added two logs for the same test. Remove the duplicated one. Reported-by: Antoine Tenart Fixes:

[PATCH 5.4 43/86] pinctrl: aspeed: g6: Fix PWMG0 pinctrl setting

2021-01-25 Thread Greg Kroah-Hartman
From: Billy Tsai [ Upstream commit 92ff62a7bcc17d47c0ce8dddfb7a6e1a2e55ebf4 ] The SCU offset for signal PWM8 in group PWM8G0 is wrong, fix it from SCU414 to SCU4B4. Signed-off-by: Billy Tsai Fixes: 2eda1cdec49f ("pinctrl: aspeed: Add AST2600 pinmux support") Reviewed-by: Joel Stanley

[PATCH 5.4 68/86] x86/cpu/amd: Set __max_die_per_package on AMD

2021-01-25 Thread Greg Kroah-Hartman
From: Yazen Ghannam commit 76e2fc63ca40977af893b724b00cc2f8e9ce47a4 upstream. Set the maximum DIE per package variable on AMD using the NodesPerProcessor topology value. This will be used by RAPL, among others, to determine the maximum number of DIEs on the system in order to do per-DIE

[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 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 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 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.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 31/86] 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.4 09/86] btrfs: dont clear ret in btrfs_start_dirty_block_groups

2021-01-25 Thread Greg Kroah-Hartman
From: Josef Bacik commit 34d1eb0e599875064955a74712f08ff14c8e3d5f upstream. If we fail to update a block group item in the loop we'll break, however we'll do btrfs_run_delayed_refs and lose our error value in ret, and thus not clean up properly. Fix this by only running the delayed refs if

[PATCH 5.4 29/86] arm64: make atomic helpers __always_inline

2021-01-25 Thread Greg Kroah-Hartman
From: Arnd Bergmann [ Upstream commit c35a824c31834d947fb99b0c608c1b9f922b4ba0 ] With UBSAN enabled and building with clang, there are occasionally warnings like WARNING: modpost: vmlinux.o(.text+0xc533ec): Section mismatch in reference from the function arch_atomic64_or() to the variable

[PATCH 5.4 28/86] clk: tegra30: Add hda clock default rates to clock driver

2021-01-25 Thread Greg Kroah-Hartman
From: Peter Geis [ Upstream commit f4eccc7fea203cfb35205891eced1ab51836f362 ] Current implementation defaults the hda clocks to clk_m. This causes hda to run too slow to operate correctly. Fix this by defaulting to pll_p and setting the frequency to the correct rate. This matches upstream t124

[PATCH 5.4 07/86] btrfs: dont get an EINTR during drop_snapshot for reloc

2021-01-25 Thread Greg Kroah-Hartman
From: Josef Bacik commit 18d3bff411c8d46d40537483bdc0b61b33ce0371 upstream. This was partially fixed by f3e3d9cc3525 ("btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree"), however it missed a spot when we restart a trans handle because we need to end the

[PATCH 5.4 24/86] riscv: Fix kernel time_init()

2021-01-25 Thread Greg Kroah-Hartman
From: Damien Le Moal [ Upstream commit 11f4c2e940e2f317c9d8fb5a79702f2a4a02ff98 ] If of_clk_init() is not called in time_init(), clock providers defined in the system device tree are not initialized, resulting in failures for other devices to initialize due to missing clocks. Similarly to other

[PATCH 5.4 25/86] riscv: Fix sifive serial driver

2021-01-25 Thread Greg Kroah-Hartman
From: Damien Le Moal [ Upstream commit 1f1496a923b6ba16679074fe77100e1b53cdb880 ] Setup the port uartclk in sifive_serial_probe() so that the base baud rate is correctly printed during device probe instead of always showing "0". I.e. the probe message is changed from 3800.serial: ttySIF0

[PATCH 5.4 21/86] scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback

2021-01-25 Thread Greg Kroah-Hartman
From: Can Guo [ Upstream commit 35fc4cd34426c242ab015ef280853b7bff101f48 ] Users can initiate resets to specific SCSI device/target/host through IOCTL. When this happens, the SCSI cmd passed to eh_device/target/host _reset_handler() callbacks is initialized with a request whose tag is -1. In

[PATCH 5.4 22/86] 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.4 17/86] drm/i915/gt: Prevent use of engine->wa_ctx after error

2021-01-25 Thread Greg Kroah-Hartman
From: Chris Wilson commit 488751a0ef9b5ce572c47301ce62d54fc6b5a74d upstream. On error we unpin and free the wa_ctx.vma, but do not clear any of the derived flags. During lrc_init, we look at the flags and attempt to dereference the wa_ctx.vma if they are set. To protect the error path where we

[PATCH 4.19 53/58] net_sched: avoid shift-out-of-bounds in tcindex_set_parms()

2021-01-25 Thread Greg Kroah-Hartman
From: Eric Dumazet commit bcd0cf19ef8258ac31b9a20248b05c15a1f4b4b0 upstream. tc_index being 16bit wide, we need to check that TCA_TCINDEX_SHIFT attribute is not silly. UBSAN: shift-out-of-bounds in net/sched/cls_tcindex.c:260:29 shift exponent 255 is too large for 32-bit type 'int' CPU: 0 PID:

[PATCH 4.19 51/58] udp: mask TOS bits in udp_v4_early_demux()

2021-01-25 Thread Greg Kroah-Hartman
From: Guillaume Nault commit 8d2b51b008c25240914984208b2ced57d1dd25a5 upstream. udp_v4_early_demux() is the only function that calls ip_mc_validate_source() with a TOS that hasn't been masked with IPTOS_RT_MASK. This results in different behaviours for incoming multicast UDPv4 packets,

[PATCH 4.19 50/58] kasan: fix incorrect arguments passing in kasan_add_zero_shadow

2021-01-25 Thread Greg Kroah-Hartman
From: Lecopzer Chen commit 5dabd1712cd056814f9ab15f1d68157ceb04e741 upstream. kasan_remove_zero_shadow() shall use original virtual address, start and size, instead of shadow address. Link: https://lkml.kernel.org/r/20210103063847.5963-1-lecop...@gmail.com Fixes: 0207df4fa1a86

[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

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 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 4.19 13/58] scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback

2021-01-25 Thread Greg Kroah-Hartman
From: Can Guo [ Upstream commit 35fc4cd34426c242ab015ef280853b7bff101f48 ] Users can initiate resets to specific SCSI device/target/host through IOCTL. When this happens, the SCSI cmd passed to eh_device/target/host _reset_handler() callbacks is initialized with a request whose tag is -1. In

Re: UBSAN: shift-out-of-bounds in exfat_fill_super

2021-01-25 Thread Matthew Wilcox
On Mon, Jan 25, 2021 at 09:33:14AM -0800, syzbot wrote: > UBSAN: shift-out-of-bounds in fs/exfat/super.c:471:28 > shift exponent 4294967294 is too large for 32-bit type 'int' This is an integer underflow: sbi->dentries_per_clu = 1 << (sbi->cluster_size_bits -

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

2021-01-25 Thread Steven Rostedt
On Mon, 25 Jan 2021 19:19:27 +0100 Oleg Nesterov wrote: > 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

Re: [PATCH v5 12/21] arm64: cpufeature: Add an early command-line cpufeature override facility

2021-01-25 Thread Catalin Marinas
On Mon, Jan 25, 2021 at 10:50:10AM +, Marc Zyngier wrote: > In order to be able to override CPU features at boot time, > let's add a command line parser that matches options of the > form "cpureg.feature=value", and store the corresponding > value into the override val/mask pair. > > No

Re: [PATCH v5 14/21] arm64: Honor VHE being disabled from the command-line

2021-01-25 Thread Catalin Marinas
On Mon, Jan 25, 2021 at 10:50:12AM +, Marc Zyngier wrote: > Finally we can check whether VHE is disabled on the command line, > and not enable it if that's the user's wish. > > Signed-off-by: Marc Zyngier > Acked-by: David Brazdil Acked-by: Catalin Marinas

[PATCH] x86_64: Update the NMI handler nesting logic comment

2021-01-25 Thread Steven Rostedt
From: "Steven Rostedt (VMware)" The NMI handler on x86 needs to deal with nested NMIs becaues if an NMI takes an exception (page fault or breakpoint), the exception handle triggers a iretq which unlatches NMIs in the hardware allowing for another NMI to take place. The current code does a bit

Re: linux-next: Fixes tag needs some work in the block tree

2021-01-25 Thread Paolo Valente
> Il giorno 25 gen 2021, alle ore 10:40, Stephen Rothwell > ha scritto: > > Hi all, > > In commit > > d4fc3640ff36 ("block, bfq: set next_rq to waker_bfqq->next_rq in waker > injection") > > Fixes tag > > Fixes: c5089591c3ba ("block, bfq: detect wakers and unconditionally inject >

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

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] 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 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] mm/filemap: Adding missing mem_cgroup_uncharge() to __add_to_page_cache_locked()

2021-01-25 Thread Matthew Wilcox
On Mon, Jan 25, 2021 at 01:23:58PM -0500, Waiman Long wrote: > 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

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

2021-01-25 Thread Michal Hocko
On Mon 25-01-21 13:23:58, Waiman Long wrote: > On 1/25/21 1:14 PM, Michal Hocko wrote: [...] > > With the proposed simplification by Willy > > Acked-by: Michal Hocko > > Thank for the ack. However, I am a bit confused about what you mean by > simplification. There is another linux-next patch

[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

[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] 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

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 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 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 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

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

[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

[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.

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 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

[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

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 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 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] 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 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

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

2021-01-25 Thread Steven Rostedt
On Mon, 25 Jan 2021 09:51:45 -0800 Andy Lutomirski wrote: > > The problem I see with this is that exc_nmi is called with the thread > > stack, if it were to take an exception, NMIs would be enabled allowing for > > a nested NMI to run. From what I can tell, I don't see anything stopping > > that

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

2021-01-25 Thread Rafael J. Wysocki
On Sun, Jan 24, 2021 at 12:07 AM Nicolas Pitre wrote: > > The clock API splits its interface into sleepable ant atomic contexts: > > - clk_prepare/clk_unprepare for stuff that might sleep > > - clk_enable_clk_disable for anything that may be done in atomic context > > The code handling runtime PM

Re: [PATCH v3] checkpatch: add warning for avoiding .L prefix symbols in assembly files

2021-01-25 Thread Nick Desaulniers
On Sat, Jan 23, 2021 at 1:01 PM Joe Perches wrote: > > On Sun, 2021-01-24 at 00:34 +0530, Aditya Srivastava wrote: > > objtool requires that all code must be contained in an ELF symbol. > > Symbol names that have a '.L' prefix do not emit symbol table entries, as > > they have special meaning for

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

2021-01-25 Thread Michal Hocko
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 24-01-21 23:24:41,

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: (subset) [PATCH v3 0/6] Clock and reset improvements for Tegra ALSA drivers

2021-01-25 Thread Mark Brown
On Wed, 20 Jan 2021 03:31:48 +0300, Dmitry Osipenko wrote: > This series improves the handling of clock and reset controls of > NVIDA Tegra ALSA drivers. Tegra HDA and AHUB drivers aren't handling > resets properly, which needs to be fixed in order to unblock other patches > related to fixes of

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

2021-01-25 Thread Andy Lutomirski
> On Jan 25, 2021, at 9:39 AM, Steven Rostedt wrote: > > On Mon, 25 Jan 2021 15:45:06 +0800 > Lai Jiangshan wrote: > >> From: Lai Jiangshan >> >> The commit 929bacec21478("x86/entry/64: De-Xen-ify our NMI code") simplified >> the NMI code by changing paravirt code into native code and

Re: [PATCH] regulator: pf8x00: set ramp_delay for bucks

2021-01-25 Thread Mark Brown
On Mon, 25 Jan 2021 17:13:41 +0100, Christoph Fritz wrote: > This patch sets ramp_delay for bucks to the max value given by the > datasheet. Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/1] regulator: pf8x00: set ramp_delay for bucks

[PATCH v3 2/4] ARM: dts: qcom: msm8974-klte: add support for GPU

2021-01-25 Thread Iskren Chernev
From: Samuel Pascua Enable adreno and opp_table dt nodes. Signed-off-by: Samuel Pascua Signed-off-by: Iskren Chernev --- arch/arm/boot/dts/qcom-msm8974-samsung-klte.dts | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/qcom-msm8974-samsung-klte.dts

Re: linux-next: manual merge of the bpf-next tree with the net-next tree

2021-01-25 Thread Arjun Roy
On Sun, Jan 24, 2021 at 4:12 PM Stephen Rothwell wrote: > > Hi all, > > Today's linux-next merge of the bpf-next tree got a conflict in: > > net/ipv4/tcp.c > > between commit: > > 7eeba1706eba ("tcp: Add receive timestamp support for receive zerocopy.") > > from the net-next tree and commit:

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: [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] 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

[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 ---

[PATCH v3 3/4] ARM: dts: qcom: msm8974-klte: add support for display

2021-01-25 Thread Iskren Chernev
From: Samuel Pascua Add initial support for the display found on the Samsung Galaxy 5 (klte) phone. This is based on work from Jonathan Marek & Brian Masney. Signed-off-by: Samuel Pascua Signed-off-by: Iskren Chernev --- .../boot/dts/qcom-msm8974-samsung-klte.dts| 58 +++

Re: [STABLE BACKPORT v2 4.4.y, 4.9.y and 4.14.y] compiler.h: Raise minimum version of GCC to 5.1 for arm64

2021-01-25 Thread Nick Desaulniers
On Mon, Jan 25, 2021 at 6:34 AM Greg KH wrote: > > On Mon, Jan 25, 2021 at 01:24:25PM +, Will Deacon wrote: > > commit dca5244d2f5b94f1809f0c02a549edf41ccd5493 upstream. > > > > GCC versions >= 4.9 and < 5.1 have been shown to emit memory references > > beyond the stack pointer, resulting in

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

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 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

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 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

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 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 0/5] Amlogic Meson Always-On ARC remote-processor support

2021-01-25 Thread Kevin Hilman
Martin Blumenstingl writes: > Amlogic Meson6/8/8b/8m2 come with an ARC core in the Always-On (AO) > power-domain. This is typically used for waking up the ARM CPU after > powering it down for system suspend. > > The exact ARC core used on Meson6 and earlier is not known. I believe > it is an

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 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

[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:

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