[PATCH v2] ASoC: Intel: Skylake: skl-topology: fix -frame-larger-than

2021-03-14 Thread Nick Desaulniers
Fixes: sound/soc/intel/skylake/skl-topology.c:3613:13: warning: stack frame size of 1304 bytes in function 'skl_tplg_complete' [-Wframe-larger-than=] struct snd_ctl_elem_value is 1224 bytes in my configuration. Heap allocate it, then free it within the current frame. Signed-off-by: Nick Desaulni

[PATCH v3] iommu/tegra-smmu: Add pagetable mappings to debugfs

2021-03-14 Thread Nicolin Chen
This patch dumps all active mapping entries from pagetable to a debugfs directory named "mappings". Ataching an example: SWGROUP: hc ASID: 0 reg: 0x250 PTB_ASID: 0xe0080004 as->pd_dma: 0x80004000 { [1023] 0xf008000b (1) { PTE RANGE | ATTR | PHYS

Re: [PATCH][next] bus: mhi: core: remove redundant initialization of variables state and ee

2021-03-14 Thread Loic Poulain
On Thu, 11 Mar 2021 at 12:18, Colin King wrote: > > From: Colin Ian King > > The variables state and ee are being initialized with values that > are never read and are being updated later with a new values. The > initializations are redundant and can be removed. > > Addresses-Coverity: ("Unused v

[BUG] net: rds: rds_send_probe memory leak

2021-03-14 Thread Fatih Yildirim
Hi Santosh, I've been working on a memory leak bug reported by syzbot. https://syzkaller.appspot.com/bug?id=39b72114839a6dbd66c1d2104522698a813f9ae2 It seems that memory allocated in rds_send_probe function is not freed. Let me share my observations. rds_message is allocated at the beginning of

Re: [PATCH] virtio-mmio: read[wl]()/write[wl] are already little-endian

2021-03-14 Thread Michael S. Tsirkin
On Sat, Mar 13, 2021 at 06:10:29PM +0100, Laurent Vivier wrote: > Le 11/03/2021 à 16:44, Michael S. Tsirkin a écrit : > > On Tue, Mar 09, 2021 at 11:43:13PM +0100, Laurent Vivier wrote: > >> read[wl]()/write[wl] already access memory in little-endian mode. > > > > But then they convert it to CPU r

Re: [PATCH 05/23] ASoC: cx2070x: remove useless assignment

2021-03-14 Thread Takashi Iwai
On Fri, 12 Mar 2021 19:22:28 +0100, Pierre-Louis Bossart wrote: > > Cppcheck warning: > > sound/soc/codecs/cx2072x.c:830:26: style: Variable > 'reg1.r.rx_data_one_line' is reassigned a value before the old one has > been used. [redundantAssignment] > > reg1.r.rx_data_one_line = 1; >

Re: [PATCH 05/23] ASoC: cx2070x: remove useless assignment

2021-03-14 Thread Takashi Iwai
On Fri, 12 Mar 2021 19:22:28 +0100, Pierre-Louis Bossart wrote: > > Cppcheck warning: > > sound/soc/codecs/cx2072x.c:830:26: style: Variable > 'reg1.r.rx_data_one_line' is reassigned a value before the old one has > been used. [redundantAssignment] > > reg1.r.rx_data_one_line = 1; >

Re: [PATCH 06/23] ASoC: cx2070x: remove duplicate else branch

2021-03-14 Thread Takashi Iwai
On Fri, 12 Mar 2021 19:22:29 +0100, Pierre-Louis Bossart wrote: > > cppcheck warning: > > sound/soc/codecs/cx2072x.c:1436:10: style:inconclusive: Found > duplicate branches for 'if' and 'else'. [duplicateBranch] > } else if (type & 0x4) { > ^ > sound/soc/codecs/cx2072x.c:1439:5: note:

Re: [PATCH] staging: octeon-usb: fixed precedence issue

2021-03-14 Thread Greg KH
A: http://en.wikipedia.org/wiki/Top_post Q: Were do I find info about this thing called top-posting? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I includ

Re: [BUG] net: rds: rds_send_probe memory leak

2021-03-14 Thread Greg KH
On Sun, Mar 14, 2021 at 11:23:10AM +0300, Fatih Yildirim wrote: > Hi Santosh, > > I've been working on a memory leak bug reported by syzbot. > https://syzkaller.appspot.com/bug?id=39b72114839a6dbd66c1d2104522698a813f9ae2 > > It seems that memory allocated in rds_send_probe function is not freed.

Re: [PATCH v1 0/4] ALSA: hda/cirrus: Make CS8409 driver more generic by using fixups

2021-03-14 Thread Takashi Iwai
On Sat, 13 Mar 2021 12:34:06 +0100, Vitaly Rodionov wrote: > > This series of patches will address comments by Pierre-Louis Bossart, > cleans up patch_cirrus.c source, reducing checkpatch.pl warnings from 19 to 0, > fixing an issue reported by Canonical: BugLink: > https://bugs.launchpad.net/bugs

[PATCH v6 0/3] mm, vsprintf: dump full information of page flags in pGp

2021-03-14 Thread Yafang Shao
The existed pGp shows the names of page flags only, rather than the full information including section, node, zone, last cpuipid and kasan tag. While it is not easy to parse these information manually because there are so many flavors. We'd better interpret them in printf. To be compitable with th

[PATCH v6 1/3] mm, slub: use pGp to print page flags

2021-03-14 Thread Yafang Shao
As pGp has been already introduced in printk, we'd better use it to make the output human readable. Before this change, the output is, [ 6155.716018] INFO: Slab 0x4027dd4f objects=33 used=3 fp=0x8cd1579c flags=0x17c0010200 While after this change, the output is, [ 8846.517809

[PATCH v6 3/3] vsprintf: dump full information of page flags in pGp

2021-03-14 Thread Yafang Shao
Currently the pGp only shows the names of page flags, rather than the full information including section, node, zone, last cpupid and kasan tag. While it is not easy to parse these information manually because there're so many flavors. Let's interpret them in pGp as well. To be compitable with the

[PATCH v6 2/3] mm, slub: don't combine pr_err with INFO

2021-03-14 Thread Yafang Shao
It is strange to combine "pr_err" with "INFO", so let's remove the prefix completely. This patch is motivated by David's comment[1]. - before the patch [ 8846.517809] INFO: Slab 0xf42a2c60 objects=33 used=3 fp=0x60d32ca8 flags=0x17c0010200(slab|head) - after the patch [ 6343.

[GIT PULL] KVM fixes for 5.12-rc3

2021-03-14 Thread Paolo Bonzini
Linus, The following changes since commit 9e46f6c6c959d9bb45445c2e8f04a75324a0dfd0: KVM: SVM: Clear the CR4 register on reset (2021-03-02 14:39:11 -0500) are available in the Git repository at: https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus for you to fetch changes up to 35

Re: linux-next: Tree for Mar 10 (lib/test_printf.c)

2021-03-14 Thread Yafang Shao
On Wed, Mar 10, 2021 at 5:52 PM Petr Mladek wrote: > > On Tue 2021-03-09 21:57:48, Randy Dunlap wrote: > > On 3/9/21 8:02 PM, Stephen Rothwell wrote: > > > Hi all, > > > > > > > on i386 (at least): > > > > ../lib/test_printf.c: In function 'page_flags_test': > > ../lib/test_printf.c:595:17: error:

[PATCH 4/4] staging:r8188eu: use ieee80211_is_ctl instead IsFrameTypeCtrl

2021-03-14 Thread Ivan Safonov
IsFrameTypeCtrl() duplicate ieee80211_is_ctl(). Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/hal/rtl8188e_rxdesc.c | 8 +--- drivers/staging/rtl8188eu/include/wifi.h| 8 2 files changed, 5 insertions(+), 11 deletions(-) diff --git a/drivers/staging/rtl8188eu/ha

[PATCH 3/4] staging:r8188eu: replace cap_* definitions with native kernel WLAN_CAPABILITY_*

2021-03-14 Thread Ivan Safonov
cap_* definitions duplicate WLAN_CAPABILITY_*. Remove cap_* definitions, improve code consistency. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/core/rtw_ieee80211.c | 6 +++--- drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 6 +++--- drivers/staging/rtl8188eu/include/wifi.h

[PATCH 2/4] staging:r8188eu: remove unused definitions from wifi.h

2021-03-14 Thread Ivan Safonov
These definitions are not used and will not be useful in the future. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/include/wifi.h | 92 1 file changed, 92 deletions(-) diff --git a/drivers/staging/rtl8188eu/include/wifi.h b/drivers/staging/rtl8188eu/include

[PATCH 0/4] staging:r8188eu: remove unnecessary definitions from wifi.h

2021-03-14 Thread Ivan Safonov
wifi.h contains unnecessary definitions. Some of them are not used at all, some can be replaced with native definitions. Ivan Safonov (4): staging:r8188eu: replace get_(d|s)a with ieee80211_get_(D|S)A staging:r8188eu: remove unused definitions from wifi.h staging:r8188eu: replace cap_* defin

[PATCH 1/4] staging:r8188eu: replace get_(d|s)a with ieee80211_get_(D|S)A

2021-03-14 Thread Ivan Safonov
get_da()/get_sa() duplicate native ieee80211_get_(D|S)A functions. Remove get_(d|s)a, use ieee80211_get_(D|S)A instead. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 6 +-- drivers/staging/rtl8188eu/core/rtw_recv.c | 4 +- .../staging/rtl8188eu/hal/rtl8188

Re: [Linux-stm32] [PATCH v9 22/33] counter: Internalize sysfs interface code

2021-03-14 Thread William Breathitt Gray
On Sun, Mar 14, 2021 at 04:56:44PM +0900, William Breathitt Gray wrote: > On Fri, Mar 12, 2021 at 04:02:42PM +0100, Fabrice Gasnier wrote: > > On 3/9/21 2:19 PM, William Breathitt Gray wrote: > > > +static ssize_t enums_available_show(const u32 *const enums, > > > + cons

[PATCH v3 0/3] Move kernel mapping outside the linear mapping

2021-03-14 Thread Alexandre Ghiti
I decided to split sv48 support in small series to ease the review. This patchset pushes the kernel mapping (modules and BPF too) to the last 4GB of the 64bit address space, this allows to: - implement relocatable kernel (that will come later in another patchset) that requires to move the kernel

Re: [PATCH v10 1/2] scsi: ufs: Enable power management for wlun

2021-03-14 Thread Adrian Hunter
On 10/03/21 5:04 am, Asutosh Das (asd) wrote: > On 3/9/2021 7:56 AM, Asutosh Das (asd) wrote: >> On 3/8/2021 9:17 AM, Rafael J. Wysocki wrote: >>> On Mon, Mar 8, 2021 at 5:21 PM Rafael J. Wysocki wrote: On Sat, Mar 6, 2021 at 5:17 PM Alan Stern wrote: > > On Fri, Mar 05, 2

[PATCH v3 1/3] riscv: Move kernel mapping outside of linear mapping

2021-03-14 Thread Alexandre Ghiti
This is a preparatory patch for relocatable kernel and sv48 support. The kernel used to be linked at PAGE_OFFSET address therefore we could use the linear mapping for the kernel mapping. But the relocated kernel base address will be different from PAGE_OFFSET and since in the linear mapping, two d

[PATCH v3 2/3] Documentation: riscv: Add documentation that describes the VM layout

2021-03-14 Thread Alexandre Ghiti
This new document presents the RISC-V virtual memory layout and is based one the x86 one: it describes the different limits of the different regions of the virtual address space. Signed-off-by: Alexandre Ghiti --- Documentation/riscv/index.rst | 1 + Documentation/riscv/vm-layout.rst | 63 +

[PATCH v3 3/3] riscv: Prepare ptdump for vm layout dynamic addresses

2021-03-14 Thread Alexandre Ghiti
This is a preparatory patch for sv48 support that will introduce dynamic PAGE_OFFSET. Dynamic PAGE_OFFSET implies that all zones (vmalloc, vmemmap, fixaddr...) whose addresses depend on PAGE_OFFSET become dynamic and can't be used to statically initialize the array used by ptdump to identify the d

Re: [PATCH v7 1/3] block: add blk_mq_is_queue_frozen()

2021-03-14 Thread Christoph Hellwig
On Fri, Mar 12, 2021 at 02:06:41PM -0500, Mike Snitzer wrote: > This is returning a frozen state that is immediately stale. I don't > think any code calling this is providing the guarantees you think it > does due to the racey nature of this state once the mutex is dropped. The code only uses it

Re: [PATCH] firewire: Use bitwise instead of arithmetic operator for flags

2021-03-14 Thread Stefan Richter
On Mar 09 Jiapeng Chong wrote: > Fix the following coccicheck warnings: > > ./drivers/firewire/core-device.c:973:22-23: WARNING: sum of probable > bitmasks, consider |. > > ./drivers/firewire/core-device.c:954:22-23: WARNING: sum of probable > bitmasks, consider |. > > Reported-by: Abaci Robot

[linux-stable-rc CI] Test report for 5.10.24-rc1 /arm64

2021-03-14 Thread hulkrobot
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-5.10.y Arch: arm64 Version: 5.10.24-rc1 Commit: 7496dbd02b27316275e097a4e52cebcd2ca5a5c0 Compiler: gcc version 7.3.0 (GCC) Fail

Re: [PATCH v7 2/3] block: add bdev_interposer

2021-03-14 Thread Christoph Hellwig
On Fri, Mar 12, 2021 at 06:44:54PM +0300, Sergei Shtepa wrote: > bdev_interposer allows to redirect bio requests to another devices. I think this warrants a somewhat more detailed description. The code itself looks pretty good to me now, a bunch of nitpicks and a question below: > +static noinli

[PATCH v7 0/2] hwspinlock: add sun6i hardware spinlock support

2021-03-14 Thread Wilken Gottwalt
Most of the Allwinner sun6i compatible devices contain a spinlock unit which can be used to sync access to devices shared between the ARM cores and the embedded companion core. According to the datasheets at least 32 spinlocks are supported. The implementation supports 32, 64, 128 and 256 spinlock

[PATCH v7 1/2] dt-bindings: hwlock: add sun6i_hwspinlock

2021-03-14 Thread Wilken Gottwalt
Adds documentation on how to use the sun6i_hwspinlock driver for sun6i compatible series SoCs. Signed-off-by: Wilken Gottwalt --- Changes in v7: - changed dt documentation to the name of the compatible string Changes in v6: - fixed formating and name issues in dt documentation Changes in v5

Re: [PATCH v7 3/3] dm: add DM_INTERPOSED_FLAG

2021-03-14 Thread Christoph Hellwig
On Fri, Mar 12, 2021 at 06:44:55PM +0300, Sergei Shtepa wrote: > DM_INTERPOSED_FLAG allow to create DM targets on "the fly". > Underlying block device opens without a flag FMODE_EXCL. > DM target receives bio from the original device via > bdev_interposer. This is more of a philopical comment, but

[PATCH v7 2/2] hwspinlock: add sun6i hardware spinlock support

2021-03-14 Thread Wilken Gottwalt
Adds the sun6i_hwspinlock driver for the hardware spinlock unit found in most of the sun6i compatible SoCs. This unit provides at least 32 spinlocks in hardware. The implementation supports 32, 64, 128 or 256 32bit registers. A lock can be taken by reading a register and released by writing a 0 to

[PATCH] iio:dac:max517: Use devm_iio_device_register()

2021-03-14 Thread Mugilraj Dhavachelvan
Use devm_iio_device_register() to avoid remove function and drop explicit call to iio_device_unregister(). Signed-off-by: Mugilraj Dhavachelvan --- drivers/iio/dac/max517.c | 9 + 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/drivers/iio/dac/max517.c b/drivers/iio/dac/max

[linux-stable-rc CI] Test report for 5.4.106-rc1 /x86

2021-03-14 Thread hulkrobot
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-5.4.y Arch: x86 Version: 5.4.106-rc1 Commit: 2bcbae06b8fb9030973ee996e1b8ed43f3bfd4ab Compiler: gcc version 7.3.0 (GCC) All tes

Re: [PATCH V4] clk: imx: Fix reparenting of UARTs not associated with stdout

2021-03-14 Thread Ahmad Fatoum
On 13.03.21 16:16, Ahmad Fatoum wrote: >> +/* i.MX boards use device trees now. For build tests without CONFIG_OF, do >> nothing */ >> +#ifdef CONFIG_OF >> if (imx_keep_uart_clocks) { >> int i; >> >> -imx_uart_clocks = clks; >> -for (i = 0; imx_uart_clo

Re: [PATCH net-next] mfd: Add Renesas Synchronization Management Unit (SMU) support

2021-03-14 Thread Pavel Machek
Hi! On Sat 2021-03-13 11:42:27, min.li...@renesas.com wrote: > From: Min Li > > Add support for ClockMatrix(TM) and 82P33xxx families of timing > and synchronization devices. The access interface can be either > SPI or I2C. Currently, it will create 2 types of MFD devices, > which are to be used

Re: [PATCH] net: mellanox: mlx5: fix error return code of mlx5e_stats_flower()

2021-03-14 Thread Roi Dayan
On 2021-03-12 12:47 AM, Saeed Mahameed wrote: On Tue, 2021-03-09 at 11:44 +0200, Roi Dayan wrote: On 2021-03-09 10:32 AM, Jia-Ju Bai wrote: On 2021/3/9 16:24, Roi Dayan wrote: On 2021-03-09 10:20 AM, Roi Dayan wrote: On 2021-03-06 3:47 PM, Jia-Ju Bai wrote: When mlx5e_tc_get_count

Re: [PATCH v2 1/5] thermal/drivers/core: Use a char pointer for the cooling device name

2021-03-14 Thread Ido Schimmel
On Fri, Mar 12, 2021 at 06:03:12PM +0100, Daniel Lezcano wrote: > diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c > index 996c038f83a4..9ef8090eb645 100644 > --- a/drivers/thermal/thermal_core.c > +++ b/drivers/thermal/thermal_core.c > @@ -960,10 +960,7 @@ __thermal_coo

Re: [PATCH] powerpc/syscall: Force inlining of __prep_irq_for_enabled_exit()

2021-03-14 Thread Michael Ellerman
On Wed, 24 Feb 2021 06:34:22 + (UTC), Christophe Leroy wrote: > As reported by kernel test robot, a randconfig with high amount of > debuging options can lead to build failure for undefined reference > to replay_soft_interrupts() on ppc32. > > This is due to gcc not seeing that __prep_irq_for_

Re: [PATCH] powerpc: Fix missing declaration of [en/dis]able_kernel_vsx()

2021-03-14 Thread Michael Ellerman
On Tue, 9 Mar 2021 08:39:39 + (UTC), Christophe Leroy wrote: > Add stub instances of enable_kernel_vsx() and disable_kernel_vsx() > when CONFIG_VSX is not set, to avoid following build failure. > > CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.o > In file included from >

Re: [PATCH] powerpc/603: Fix protection of user pages mapped with PROT_NONE

2021-03-14 Thread Michael Ellerman
On Mon, 1 Feb 2021 06:29:50 + (UTC), Christophe Leroy wrote: > On book3s/32, page protection is defined by the PP bits in the PTE > which provide the following protection depending on the access > keys defined in the matching segment register: > - PP 00 means RW with key 0 and N/A with key 1. >

Re: [PATCH] powerpc: Force inlining of mmu_has_feature to fix build failure

2021-03-14 Thread Michael Ellerman
On Sat, 27 Feb 2021 16:30:48 + (UTC), Christophe Leroy wrote: > The test robot has managed to generate a random config leading > to following build failure: > > LD .tmp_vmlinux.kallsyms1 > powerpc64-linux-ld: arch/powerpc/mm/pgtable.o: in function > `ptep_set_access_flags': > pgtable.c

Re: [PATCH v2 00/43] powerpc/32: Switch to interrupt entry/exit in C

2021-03-14 Thread Michael Ellerman
On Tue, 9 Mar 2021 12:09:25 + (UTC), Christophe Leroy wrote: > This series aims at porting interrupt entry/exit in C on PPC32, using > the work already merged for PPC64. > > First two patches are a fix and an optimisation of unrecoverable_exception() > function. > > Six following patches do

Re: [syzbot] BUG: unable to handle kernel access to user memory in sock_ioctl

2021-03-14 Thread Dmitry Vyukov
On Wed, Mar 10, 2021 at 7:53 PM Dmitry Vyukov wrote: > > On Wed, Mar 10, 2021 at 7:28 PM syzbot > wrote: > > > > Hello, > > > > syzbot found the following issue on: > > > > HEAD commit:0d7588ab riscv: process: Fix no prototype for arch_dup_tas.. > > git tree: > > git://git.kernel.org/p

[PATCH] backlight: qcom-wled: Use sink_addr for sync toggle

2021-03-14 Thread Marijn Suijten
From: Obeida Shamoun WLED3_SINK_REG_SYNC is, as the name implies, a sink register offset. Therefore, use the sink address as base instead of the ctrl address. This fixes the sync toggle on wled4, which can be observed by the fact that adjusting brightness now works. It has no effect on wled3 be

[syzbot] KASAN: slab-out-of-bounds Read in riscv_intc_irq

2021-03-14 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:0d7588ab riscv: process: Fix no prototype for arch_dup_tas.. git tree: git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes console output: https://syzkaller.appspot.com/x/log.txt?x=15a35756d0 kernel config: ht

[GIT PULL] Please pull powerpc/linux.git powerpc-5.12-3 tag

2021-03-14 Thread Michael Ellerman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Linus, Please pull some more powerpc fixes for 5.12: The following changes since commit fbda7904302499dd7ffc073a3c84eb7c9275db0a: Merge tag 'powerpc-5.12-2' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux (2021-03-07 13:24:44

Re: [PATCH v2 net-next 0/6] skbuff: micro-optimize flow dissection

2021-03-14 Thread Alexander Lobakin
From: David Miller Date: Sat, 13 Mar 2021 18:10:00 -0800 (PST) > None of these apply to net-next as per the patchwork automated checks. Any > idea why? No unfortunately. That'why I sent a follow-up mail. All of them successfully apply to pure net-next on my machine. Can it be a Git version con

Re: [PATCH RFC] net: sched: implement TCQ_F_CAN_BYPASS for lockless qdisc

2021-03-14 Thread Marc Kleine-Budde
Cc += linux-...@vger.kernel.org On 3/14/21 1:03 AM, Vladimir Oltean wrote: > On Sat, Mar 13, 2021 at 10:47:47AM +0800, Yunsheng Lin wrote: >> Currently pfifo_fast has both TCQ_F_CAN_BYPASS and TCQ_F_NOLOCK >> flag set, but queue discipline by-pass does not work for lockless >> qdisc because skb is

Re: [PATCH v1 0/4] ALSA: hda/cirrus: Make CS8409 driver more generic by using fixups

2021-03-14 Thread Vitaly Rodionov
On 14/03/2021 8:36 am, Takashi Iwai wrote: On Sat, 13 Mar 2021 12:34:06 +0100, Vitaly Rodionov wrote: This series of patches will address comments by Pierre-Louis Bossart, cleans up patch_cirrus.c source, reducing checkpatch.pl warnings from 19 to 0, fixing an issue reported by Canonical: BugLin

[PATCH net] net: hdlc_x25: Prevent racing between "x25_close" and "x25_xmit"/"x25_rx"

2021-03-14 Thread Xie He
"x25_close" is called by "hdlc_close" in "hdlc.c", which is called by hardware drivers' "ndo_stop" function. "x25_xmit" is called by "hdlc_start_xmit" in "hdlc.c", which is hardware drivers' "ndo_start_xmit" function. "x25_rx" is called by "hdlc_rcv" in "hdlc.c", which receives HDLC frames from "ne

Panic after upgrading to 5.11.6 stable

2021-03-14 Thread David R
I attempted to upgrade my home server to 5.11 today. The system panics soon after boot with the following :- In iptables by the looks of the stack. 5.10.23 works fine. Can provide config (and boot logs from 5.10.23) if required. Cheers David

Re: Panic after upgrading to 5.11.6 stable

2021-03-14 Thread David R
On 14/03/2021 10:30, David R wrote: > I attempted to upgrade my home server to 5.11 today. The system panics > soon after boot with the following :- > > > > In iptables by the looks of the stack. > > 5.10.23 works fine. > > Can provide config (and boot logs from 5.10.23) if required. > > Cheers > D

Re: [PATCH 2/3] net: ethernet: actions: Add Actions Semi Owl Ethernet MAC driver

2021-03-14 Thread Cristian Ciocaltea
On Sun, Mar 14, 2021 at 05:36:32AM +0100, Andrew Lunn wrote: > > > > + if (phy->interface != PHY_INTERFACE_MODE_RMII) { > > > > + netdev_err(netdev, "unsupported phy mode: %s\n", > > > > + phy_modes(phy->interface)); > > > > + phy_disconnec

Re: [PATCH 1/1] media: i2c: Add support for ov5693 sensor

2021-03-14 Thread Jacopo Mondi
Hi Daniel, On Fri, Mar 12, 2021 at 10:32:39AM +, Daniel Scally wrote: > The OV5693 is a 5 Mpx CMOS image sensor, connected via MIPI CSI-2. The > chip is capable of a single lane configuration, but currently only two > lanes are supported. > > Most of the sensor's features are supported, with t

Re: [syzbot] KASAN: slab-out-of-bounds Read in riscv_intc_irq

2021-03-14 Thread Dmitry Vyukov
On Sun, Mar 14, 2021 at 11:14 AM syzbot wrote: > > Hello, > > syzbot found the following issue on: > > HEAD commit:0d7588ab riscv: process: Fix no prototype for arch_dup_tas.. > git tree: git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git > fixes > console output: https://syz

Re: [PATCH v2 1/5] thermal/drivers/core: Use a char pointer for the cooling device name

2021-03-14 Thread Daniel Lezcano
Hi Ido, On 14/03/2021 10:53, Ido Schimmel wrote: > On Fri, Mar 12, 2021 at 06:03:12PM +0100, Daniel Lezcano wrote: >> diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c >> index 996c038f83a4..9ef8090eb645 100644 >> --- a/drivers/thermal/thermal_core.c >> +++ b/drivers/t

Re: [PATCH v2] ASoC: Intel: Skylake: skl-topology: fix -frame-larger-than

2021-03-14 Thread Andy Shevchenko
On Sun, Mar 14, 2021 at 10:08 AM Nick Desaulniers wrote: > > Fixes: > sound/soc/intel/skylake/skl-topology.c:3613:13: warning: stack frame > size of 1304 bytes in function 'skl_tplg_complete' > [-Wframe-larger-than=] > > struct snd_ctl_elem_value is 1224 bytes in my configuration. > > Heap allocat

Re: Panic after upgrading to 5.11.6 stable

2021-03-14 Thread Pablo Neira Ayuso
On Sun, Mar 14, 2021 at 10:30:55AM +, David R wrote: > I attempted to upgrade my home server to 5.11 today. The system panics > soon after boot with the following :- > > In iptables by the looks of the stack. > > 5.10.23 works fine. > > Can provide config (and boot logs from 5.10.23) if requ

[PATCH] mfd: rn5t618: Do not cache various USB related registers

2021-03-14 Thread Andreas Kemnade
These register get reset to their OTP defaults after USB plugging. And while at it, also add a missing register for detecting the charger type. Signed-off-by: Andreas Kemnade --- drivers/mfd/rn5t618.c | 3 +++ include/linux/mfd/rn5t618.h | 1 + 2 files changed, 4 insertions(+) diff --git

Re: [syzbot] BUG: unable to handle kernel access to user memory in sock_ioctl

2021-03-14 Thread Dmitry Vyukov
On Sun, Mar 14, 2021 at 11:01 AM Dmitry Vyukov wrote: > > On Wed, Mar 10, 2021 at 7:28 PM syzbot > > wrote: > > > > > > Hello, > > > > > > syzbot found the following issue on: > > > > > > HEAD commit:0d7588ab riscv: process: Fix no prototype for > > > arch_dup_tas.. > > > git tree: >

Re: Panic after upgrading to 5.11.6 stable

2021-03-14 Thread David R
On 14/03/2021 10:53, Pablo Neira Ayuso wrote: > On Sun, Mar 14, 2021 at 10:30:55AM +, David R wrote: >> I attempted to upgrade my home server to 5.11 today. The system panics >> soon after boot with the following :- >> >> In iptables by the looks of the stack. >> >> 5.10.23 works fine. >> >> Ca

Re: [PATCH] clk: socfpga: fix iomem pointer cast on 64-bit

2021-03-14 Thread Krzysztof Kozlowski
On 13/03/2021 22:10, Stephen Boyd wrote: > Quoting Krzysztof Kozlowski (2021-03-11 06:48:33) >> Pointers should be cast to unsigned long instead of integer. This fixes >> warning when compile testing on ARM64: >> >> drivers/clk/socfpga/clk-gate.c: In function ‘socfpga_clk_recalc_rate’: >> driv

[PATCH v2] clk: socfpga: fix iomem pointer cast on 64-bit

2021-03-14 Thread Krzysztof Kozlowski
Pointers should be cast with uintptr_t instead of integer. This fixes warning when compile testing on ARM64: drivers/clk/socfpga/clk-gate.c: In function ‘socfpga_clk_recalc_rate’: drivers/clk/socfpga/clk-gate.c:102:7: warning: cast from pointer to integer of different size [-Wpointer-to-int-

Re: [PATCH] iio:dac:max517: Use devm_iio_device_register()

2021-03-14 Thread Alexandru Ardelean
On Sun, Mar 14, 2021 at 11:34 AM Mugilraj Dhavachelvan wrote: > > Use devm_iio_device_register() to avoid remove function and > drop explicit call to iio_device_unregister(). > > Signed-off-by: Mugilraj Dhavachelvan > --- > drivers/iio/dac/max517.c | 9 + > 1 file changed, 1 insertion(+)

[syzbot] KASAN: use-after-free Read in disk_part_iter_next (2)

2021-03-14 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:280d542f Merge tag 'drm-fixes-2021-03-05' of git://anongit.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15ade5aed0 kernel config: https://syzkaller.appspot.com/x/.config?x=952047a9dbff6a6a das

[PATCH v3 net-next 2/6] skbuff: make __skb_header_pointer()'s data argument const

2021-03-14 Thread Alexander Lobakin
The function never modifies the input buffer, so 'data' argument can be marked as const. This implies one harmless cast-away. Signed-off-by: Alexander Lobakin --- include/linux/skbuff.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/include/linux/skbuff.h b/include/lin

[PATCH v3 net-next 0/6] skbuff: micro-optimize flow dissection

2021-03-14 Thread Alexander Lobakin
This little number makes all of the flow dissection functions take raw input data pointer as const (1-5) and shuffles the branches in __skb_header_pointer() according to their hit probability. The result is +20 Mbps per flow/core with one Flow Dissector pass per packet. This affects RPS (with soft

[PATCH v3 net-next 1/6] flow_dissector: constify bpf_flow_dissector's data pointers

2021-03-14 Thread Alexander Lobakin
BPF Flow dissection programs are read-only and don't touch input buffers. Mark 'data' and 'data_end' in struct bpf_flow_dissector as const in preparation for global input constifying. Signed-off-by: Alexander Lobakin --- include/net/flow_dissector.h | 4 ++-- 1 file changed, 2 insertions(+), 2 d

[PATCH v3 net-next 3/6] flow_dissector: constify raw input data argument

2021-03-14 Thread Alexander Lobakin
Flow Dissector code never modifies the input buffer, neither skb nor raw data. Make 'data' argument const for all of the Flow dissector's functions. Signed-off-by: Alexander Lobakin --- include/linux/skbuff.h | 15 ++--- include/net/flow_dissector.h | 2 +- net/core/flow_dissector

[PATCH v3 net-next 5/6] ethernet: constify eth_get_headlen()'s data argument

2021-03-14 Thread Alexander Lobakin
It's used only for flow dissection, which now takes constant data pointers. Signed-off-by: Alexander Lobakin --- include/linux/etherdevice.h | 2 +- net/ethernet/eth.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/include/linux/etherdevice.h b/include/linux/ethe

[PATCH v3 net-next 4/6] linux/etherdevice.h: misc trailing whitespace cleanup

2021-03-14 Thread Alexander Lobakin
Caught by the text editor. Fix it separately from the actual changes. Signed-off-by: Alexander Lobakin --- include/linux/etherdevice.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/etherdevice.h b/include/linux/etherdevice.h index 2e5debc0373c..bcb2f81baafb 10

[PATCH v3 net-next 6/6] skbuff: micro-optimize {,__}skb_header_pointer()

2021-03-14 Thread Alexander Lobakin
{,__}skb_header_pointer() helpers exist mainly for preventing accesses-beyond-end of the linear data. In the vast majorify of cases, they bail out on the first condition. All code going after is mostly a fallback. Mark the most common branch as 'likely' one to move it in-line. Also, skb_copy_bits()

[PATCH v3 4/5] thermal/drivers/cpuidle_cooling: Use device name instead of auto-numbering

2021-03-14 Thread Daniel Lezcano
Currently the naming of a cooling device is just a cooling technique followed by a number. When there are multiple cooling devices using the same technique, it is impossible to clearly identify the related device as this one is just a number. For instance: thermal-idle-0 thermal-idle-1 thermal

[PATCH v3 2/5] thermal/drivers/cpufreq_cooling: Use device name instead of auto-numbering

2021-03-14 Thread Daniel Lezcano
Currently the naming of a cooling device is just a cooling technique followed by a number. When there are multiple cooling devices using the same technique, it is impossible to clearly identify the related device as this one is just a number. For instance: thermal-cpufreq-0 thermal-cpufreq-1 e

[PATCH v3 5/5] thermal/drivers/cpufreq_cooling: Remove unused list

2021-03-14 Thread Daniel Lezcano
There is a list with the purpose of grouping the cpufreq cooling device together as described in the comments but actually it is unused, the code evolved since 2012 and the list was no longer needed. Delete the remaining unused list related code. Signed-off-by: Daniel Lezcano Reviewed-by: Lukasz

[PATCH v3 3/5] thermal/drivers/devfreq_cooling: Use device name instead of auto-numbering

2021-03-14 Thread Daniel Lezcano
Currently the naming of a cooling device is just a cooling technique followed by a number. When there are multiple cooling devices using the same technique, it is impossible to clearly identify the related device as this one is just a number. For instance: thermal-devfreq-0 thermal-devfreq-1 e

[PATCH v3 1/5] thermal/drivers/core: Use a char pointer for the cooling device name

2021-03-14 Thread Daniel Lezcano
We want to have any kind of name for the cooling devices as we do no longer want to rely on auto-numbering. Let's replace the cooling device's fixed array by a char pointer to be allocated dynamically when registering the cooling device, so we don't limit the length of the name. Rework the error p

[PATCH v6] selftests/x86: Use getauxval() to simplify the code in sgx

2021-03-14 Thread Tianjia Zhang
Simplify the sgx code implemntation by using library function getauxval() instead of a custom function to get the base address of vDSO. Signed-off-by: Tianjia Zhang Reviewed-by: Jarkko Sakkinen Acked-by: Shuah Khan --- tools/testing/selftests/sgx/main.c | 24 1 file ch

[PATCH net v2] net: hdlc_x25: Prevent racing between "x25_close" and "x25_xmit"/"x25_rx"

2021-03-14 Thread Xie He
"x25_close" is called by "hdlc_close" in "hdlc.c", which is called by hardware drivers' "ndo_stop" function. "x25_xmit" is called by "hdlc_start_xmit" in "hdlc.c", which is hardware drivers' "ndo_start_xmit" function. "x25_rx" is called by "hdlc_rcv" in "hdlc.c", which receives HDLC frames from "ne

Re: [PATCH 0/6] usbip fixes to crashes found by syzbot

2021-03-14 Thread Tetsuo Handa
On 2021/03/13 9:48, Tetsuo Handa wrote: > On 2021/03/12 14:44, Tetsuo Handa wrote: >> And what you are missing in your [PATCH 4,5,6/6] is >> >> diff --git a/drivers/usb/usbip/vhci_sysfs.c >> b/drivers/usb/usbip/vhci_sysfs.c >> index c4457026d5ad..3c64bd06ab53 100644 >> --- a/drivers/usb/usbi

ERROR: modpost: "__aeabi_unwind_cpp_pr0" undefined!

2021-03-14 Thread kernel test robot
config: arm-randconfig-r024-20210314 (attached as .config) compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project dfd27ebbd0eb137c9a439b7c537bb87ba903efd3) reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin

Re: [PATCH v4 3/3] x86/sgx: Add a basic NUMA allocation scheme to sgx_alloc_epc_page()

2021-03-14 Thread Jarkko Sakkinen
On Sat, Mar 13, 2021 at 06:01:19PM +0200, Jarkko Sakkinen wrote: > Background > == > > EPC section is covered by one or more SRAT entries that are associated with > one and only one PXM (NUMA node). The motivation behind this patch is to > provide basic elements of building allocation sche

[GIT PULL] x86/urgent for v5.12-rc3

2021-03-14 Thread Borislav Petkov
Hi Linus, please pull the accumulated x86/urgent pile for v5.12-rc3. Thx. --- The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15: Linux 5.12-rc2 (2021-03-05 17:33:41 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tip/

Re: [PATCH 0/4] Expose and manage PCI device reset

2021-03-14 Thread Leon Romanovsky
On Fri, Mar 12, 2021 at 11:04:48PM +0530, ameynarkhed...@gmail.com wrote: > From: Amey Narkhede > > PCI and PCIe devices may support a number of possible reset mechanisms > for example Function Level Reset (FLR) provided via Advanced Feature or > PCIe capabilities, Power Management reset, bus rese

Re: [BUG] net: rds: rds_send_probe memory leak

2021-03-14 Thread Fatih Yildirim
On Sun, 2021-03-14 at 09:36 +0100, Greg KH wrote: > On Sun, Mar 14, 2021 at 11:23:10AM +0300, Fatih Yildirim wrote: > > Hi Santosh, > > > > I've been working on a memory leak bug reported by syzbot. > > https://syzkaller.appspot.com/bug?id=39b72114839a6dbd66c1d2104522698a813f9ae2 > > > > It seems

[GIT PULL] efi/urgent for v5.12-rc3

2021-03-14 Thread Borislav Petkov
Hi Linus, please pull a single (forwarded) EFI urgent fix for v5.12-rc3. Thx. --- The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15: Linux 5.12-rc2 (2021-03-05 17:33:41 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/

[PATCH] hwmon: corsair-psu: add support for critical values

2021-03-14 Thread Wilken Gottwalt
Adds support for reading the critical values of the temperature sensors and the rail sensors (voltage and current) once and caches them. Updates the naming of the constants following a more clear scheme. Also updates the documentation and fixes a typo. The new sensors output of a Corsair HX850i wi

[GIT PULL] perf/urgent for v5.12-rc3

2021-03-14 Thread Borislav Petkov
Hi Linus, please pull there perf urgent fixes for v5.12-rc3. Thx. --- The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15: Linux 5.12-rc2 (2021-03-05 17:33:41 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git

Re: [BUG] net: rds: rds_send_probe memory leak

2021-03-14 Thread Greg KH
On Sun, Mar 14, 2021 at 03:19:05PM +0300, Fatih Yildirim wrote: > On Sun, 2021-03-14 at 09:36 +0100, Greg KH wrote: > > On Sun, Mar 14, 2021 at 11:23:10AM +0300, Fatih Yildirim wrote: > > > Hi Santosh, > > > > > > I've been working on a memory leak bug reported by syzbot. > > > https://syzkaller.a

Re: [PATCH v3 1/5] thermal/drivers/core: Use a char pointer for the cooling device name

2021-03-14 Thread Ido Schimmel
On Sun, Mar 14, 2021 at 12:13:29PM +0100, Daniel Lezcano wrote: > We want to have any kind of name for the cooling devices as we do no > longer want to rely on auto-numbering. Let's replace the cooling > device's fixed array by a char pointer to be allocated dynamically > when registering the cooli

Re: [PATCH 2/5] mm/page_alloc: Add a bulk page allocator

2021-03-14 Thread Mel Gorman
On Sat, Mar 13, 2021 at 07:33:43PM +, Matthew Wilcox wrote: > On Sat, Mar 13, 2021 at 04:56:31PM +, Chuck Lever III wrote: > > IME lists are indeed less CPU-efficient, but I wonder if that > > expense is insignificant compared to serialization primitives like > > disabling and re-enabling I

[PATCH 1/4] habanalabs/gaudi: unsecure TPC cfg status registers

2021-03-14 Thread Oded Gabbay
From: Ofir Bitton Unsecure relevant registers as TPC engine need access to TPC status. Signed-off-by: Ofir Bitton Reviewed-by: Oded Gabbay Signed-off-by: Oded Gabbay --- drivers/misc/habanalabs/gaudi/gaudi_security.c | 8 1 file changed, 8 deletions(-) diff --git a/drivers/misc/hab

[PATCH 2/4] habanalabs/gaudi: Update async events header

2021-03-14 Thread Oded Gabbay
From: Ofir Bitton Update with latest version from the Firmware team. Signed-off-by: Ofir Bitton Reviewed-by: Oded Gabbay Signed-off-by: Oded Gabbay --- drivers/misc/habanalabs/gaudi/gaudi.c | 2 +- .../include/gaudi/gaudi_async_events.h| 2 +- .../gaudi/gaudi_async_ids_map_

[PATCH 4/4] habanalabs: support dynamic PLL numbering

2021-03-14 Thread Oded Gabbay
From: Ohad Sharabi As part of the effort remove hard-coded assumptions from the F/W-driver communication, introduce support for dynamic pll numbering. Signed-off-by: Ohad Sharabi Reviewed-by: Oded Gabbay Signed-off-by: Oded Gabbay --- drivers/misc/habanalabs/common/firmware_if.c | 22 ++

[PATCH 3/4] habanalabs: avoid soft lockup bug upon mapping error

2021-03-14 Thread Oded Gabbay
From: farah kassabri Add a little sleep between page unmappings in case mapping of large number of host pages failed, in order to avoid soft lockup bug during the rollback. Signed-off-by: farah kassabri Reviewed-by: Oded Gabbay Signed-off-by: Oded Gabbay --- drivers/misc/habanalabs/common/me

  1   2   3   4   5   6   >