[PATCH v7 13/13] arm64: dts: imx8mq: Add node to G2 hardware

2021-03-29 Thread Benjamin Gaignard
Split VPU node in two: one for G1 and one for G2 since they are different hardware blocks. Add syscon for hardware control block. Remove reg-names property that is useless. Each VPU node only need one interrupt. Change G2 assigned clock to match to the specifications. In the both nodes all the

Re: [PATCH 12/17] ASoC: tegra: tegra20_das: clarify expression

2021-03-29 Thread Thierry Reding
On Fri, Mar 26, 2021 at 04:59:22PM -0500, Pierre-Louis Bossart wrote: > cppcheck warning: > > sound/soc/tegra/tegra20_das.c:64:60: style: Boolean result is used in > bitwise operation. Clarify expression with > parentheses. [clarifyCondition] > reg = otherdap <<

Re: [PATCH 13/17] ASoC: tegra: tegra20_das: align function prototypes

2021-03-29 Thread Thierry Reding
On Fri, Mar 26, 2021 at 04:59:23PM -0500, Pierre-Louis Bossart wrote: > cppcheck warnings: > > sound/soc/tegra/tegra20_das.c:35:40: style:inconclusive: Function > 'tegra20_das_connect_dap_to_dac' argument 1 names different: > declaration 'dap_id' definition 'dap'. [funcArgNamesDifferent] > > int

Re: [PATCH] move_mount: allow to add a mount into an existing group

2021-03-29 Thread Pavel Tikhomirov
On 3/29/21 12:47 AM, Andrei Vagin wrote: On Thu, Mar 25, 2021 at 03:14:44PM +0300, Pavel Tikhomirov wrote: Previously a sharing group (shared and master ids pair) can be only inherited when mount is created via bindmount. This patch adds an ability to add an existing private mount into an

Re: linux-next: build failure after merge of the staging tree

2021-03-29 Thread Alexandru Ardelean
On Mon, 29 Mar 2021 at 09:15, Greg KH wrote: > > On Mon, Mar 29, 2021 at 04:55:25PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > After merging the staging tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > drivers/iio/adc/ti-ads131e08.c: In function

[syzbot] WARNING: suspicious RCU usage in io_sq_thread

2021-03-29 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:81b1d39f Merge tag '5.12-rc4-smb3' of git://git.samba.org/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=156f3d9ed0 kernel config: https://syzkaller.appspot.com/x/.config?x=d4e9addca54f3b44

[syzbot] general protection fault in io_commit_cqring (2)

2021-03-29 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:81b1d39f Merge tag '5.12-rc4-smb3' of git://git.samba.org/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10ce6fe6d0 kernel config: https://syzkaller.appspot.com/x/.config?x=daeff30c2474a60f

[syzbot] WARNING: still has locks held in io_sq_thread

2021-03-29 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:81b1d39f Merge tag '5.12-rc4-smb3' of git://git.samba.org/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10fcce62d0 kernel config: https://syzkaller.appspot.com/x/.config?x=d4e9addca54f3b44

Re: [PATCH 02/17] ASoC: atmel: fix shadowed variable

2021-03-29 Thread Codrin.Ciubotariu
On 26.03.2021 23:59, Pierre-Louis Bossart wrote: > Fix cppcheck warning: > > sound/soc/atmel/atmel-classd.c:51:14: style: Local variable 'pwm_type' > shadows outer variable [shadowVariable] > const char *pwm_type; > ^ > sound/soc/atmel/atmel-classd.c:226:27: note: Shadowed

Re: [PATCH v3 3/3] iio: adc: add ADC driver for the TI TSC2046 controller

2021-03-29 Thread Oleksij Rempel
On Mon, Mar 22, 2021 at 02:27:22PM +, Jonathan Cameron wrote: > > > > +static DECLARE_TI_TSC2046_8_CHANNELS(tsc2046_adc, 12); > > > > + > > > > +static const struct tsc2046_adc_dcfg tsc2046_adc_dcfg_tsc2046e = { > > > > + .channels = tsc2046_adc_channels, > > > > + .num_channels =

[tip:x86/vmware] BUILD SUCCESS 0b4a285e2c65c2c9449c6eccb87298e385213e7b

2021-03-29 Thread kernel test robot
randconfig-a002-20210329 x86_64 randconfig-a003-20210329 x86_64 randconfig-a006-20210329 x86_64 randconfig-a001-20210329 x86_64 randconfig-a005-20210329 x86_64 randconfig-a004-20210329 i386 randconfig-a003

[tip:locking/core] BUILD SUCCESS bd9a5fc2edb0bdcb0756298daa31ddd6a02f0634

2021-03-29 Thread kernel test robot
allyesconfig mips allmodconfig powerpc allyesconfig powerpc allmodconfig powerpc allnoconfig x86_64 randconfig-a002-20210329 x86_64 randconfig-a003

Re: [PATCH V3 1/5] dt-bindings: Added the yaml bindings for DCC

2021-03-29 Thread schowdhu
On 2021-03-29 12:02, Souradeep Chowdhury wrote: Documentation for Data Capture and Compare(DCC) device tree bindings in yaml format. Resent this patch by adding the review tag Link as follows https://lore.kernel.org/lkml/20210329074909.vpO1kbU39ZSxJpJFZqQc-9i_h5ucqyd4gqZK3a1DQtg@z/

[PATCH net 1/1] xdp: fix xdp_return_frame() kernel BUG throw for page_pool memory model

2021-03-29 Thread Ong Boon Leong
xdp_return_frame() may be called outside of NAPI context to return xdpf back to page_pool. xdp_return_frame() calls __xdp_return() with napi_direct = false. For page_pool memory model, __xdp_return() calls xdp_return_frame_no_direct() unconditionally and below false negative kernel BUG throw

[PATCH 4.4 14/33] ia64: fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign

2021-03-29 Thread Greg Kroah-Hartman
From: Sergei Trofimovich [ Upstream commit 61bf318eac2c13356f7bd1c6a05421ef504ccc8a ] In https://bugs.gentoo.org/769614 Dmitry noticed that `ptrace(PTRACE_GET_SYSCALL_INFO)` does not return error sign properly. The bug is in mismatch between get/set errors: static inline long

[PATCH 4.4 15/33] x86/tlb: Flush global mappings when KAISER is disabled

2021-03-29 Thread Greg Kroah-Hartman
From: Borislav Petkov Jim Mattson reported that Debian 9 guests using a 4.9-stable kernel are exploding during alternatives patching: kernel BUG at /build/linux-dqnRSc/linux-4.9.228/arch/x86/kernel/alternative.c:709! invalid opcode: [#1] SMP Modules linked in: CPU: 1 PID: 1 Comm:

[PATCH 4.4 16/33] squashfs: fix inode lookup sanity checks

2021-03-29 Thread Greg Kroah-Hartman
From: Sean Nyekjaer commit c1b2028315c6b15e8d6725e0d5884b15887d3daa upstream. When mouting a squashfs image created without inode compression it fails with: "unable to read inode lookup table" It turns out that the BLOCK_OFFSET is missing when checking the SQUASHFS_METADATA_SIZE agaist the

[PATCH 4.4 17/33] squashfs: fix xattr id and id lookup sanity checks

2021-03-29 Thread Greg Kroah-Hartman
From: Phillip Lougher commit 8b44ca2b634527151af07447a8090a5f3a043321 upstream. The checks for maximum metadata block size is missing SQUASHFS_BLOCK_OFFSET (the two byte length count). Link: https://lkml.kernel.org/r/2069685113.2081245.1614583677...@webmail.123-reg.co.uk Fixes:

[PATCH 4.4 18/33] bus: omap_l3_noc: mark l3 irqs as IRQF_NO_THREAD

2021-03-29 Thread Greg Kroah-Hartman
From: Grygorii Strashko [ Upstream commit 7d7275b3e866cf8092bd12553ec53ba26864f7bb ] The main purpose of l3 IRQs is to catch OCP bus access errors and identify corresponding code places by showing call stack, so it's important to handle L3 interconnect errors as fast as possible. On RT these

[PATCH 4.4 19/33] macvlan: macvlan_count_rx() needs to be aware of preemption

2021-03-29 Thread Greg Kroah-Hartman
From: Eric Dumazet [ Upstream commit dd4fa1dae9f4847cc1fd78ca468ad69e16e5db3e ] macvlan_count_rx() can be called from process context, it is thus necessary to disable preemption before calling u64_stats_update_begin() syzbot was able to spot this on 32bit arch: WARNING: CPU: 1 PID: 4632 at

[PATCH 4.4 02/33] powerpc/4xx: Fix build errors from mfdcr()

2021-03-29 Thread Greg Kroah-Hartman
From: Michael Ellerman [ Upstream commit eead089311f4d935ab5d1d8fbb0c42ad44699ada ] lkp reported a build error in fsp2.o: CC arch/powerpc/platforms/44x/fsp2.o {standard input}:577: Error: unsupported relocation against base Which comes from: pr_err("GESR0: 0x%08x\n", mfdcr(base +

[PATCH 4.4 20/33] net: dsa: bcm_sf2: Qualify phydev->dev_flags based on port

2021-03-29 Thread Greg Kroah-Hartman
From: Florian Fainelli [ Upstream commit 47142ed6c34d544ae9f0463e58d482289cbe0d46 ] Similar to commit 92696286f3bb37ba50e4bd8d1beb24afb759a799 ("net: bcmgenet: Set phydev->dev_flags only for internal PHYs") we need to qualify the phydev->dev_flags based on whether the port is connected to an

[PATCH 4.4 21/33] e1000e: add rtnl_lock() to e1000_reset_task

2021-03-29 Thread Greg Kroah-Hartman
From: Vitaly Lifshits [ Upstream commit 21f857f0321d0d0ea9b1a758bd55dc63d1cb2437 ] A possible race condition was found in e1000_reset_task, after discovering a similar issue in igb driver via commit 024a8168b749 ("igb: reinit_locked() should be called with rtnl_lock"). Added rtnl_lock() and

[PATCH 4.4 22/33] e1000e: Fix error handling in e1000_set_d0_lplu_state_82571

2021-03-29 Thread Greg Kroah-Hartman
From: Dinghao Liu [ Upstream commit b52912b8293f2c496f42583e65599aee606a0c18 ] There is one e1e_wphy() call in e1000_set_d0_lplu_state_82571 that we have caught its return value but lack further handling. Check and terminate the execution flow just like other e1e_wphy() in this function.

[PATCH 4.4 23/33] net/qlcnic: Fix a use after free in qlcnic_83xx_get_minidump_template

2021-03-29 Thread Greg Kroah-Hartman
From: Lv Yunlong [ Upstream commit db74623a3850db99cb9692fda9e836a56b74198d ] In qlcnic_83xx_get_minidump_template, fw_dump->tmpl_hdr was freed by vfree(). But unfortunately, it is used when extended is true. Fixes: 7061b2bdd620e ("qlogic: Deletion of unnecessary checks before two function

[PATCH 4.4 24/33] can: c_can_pci: c_can_pci_remove(): fix use-after-free

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 0429d6d89f97ebff4f17f13f5b5069c66bde8138 ] There is a UAF in c_can_pci_remove(). dev is released by free_c_can_dev() and is used by pci_iounmap(pdev, priv->base) later. To fix this issue, save the mmio address before releasing dev. Fixes: 5b92da0443c2

Re: [PATCH v2 8/8] pinctrl: stm32: Add STM32H750 MCU pinctrl support

2021-03-29 Thread Alexandre TORGUE
Hi Dillon On 3/12/21 7:24 AM, dillon.min...@gmail.com wrote: From: dillon min This patch adds STM32H750 pinctrl and GPIO support since stm32h750 has the same pin alternate functions with stm32h743, so just reuse the stm32h743's pinctrl driver Signed-off-by: dillon min --- v2: - add

[PATCH 4.4 03/33] atm: eni: dont release is never initialized

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 4deb550bc3b698a1f03d0332cde3df154d1b6c1e ] label err_eni_release is reachable when eni_start() fail. In eni_start() it calls dev->phy->start() in the last step, if start() fail we don't need to call phy->stop(), if start() is never called, we neither need to

[PATCH 4.4 25/33] can: c_can: move runtime PM enable/disable to c_can_platform

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 6e2fe01dd6f98da6cae8b07cd5cfa67abc70d97d ] Currently doing modprobe c_can_pci will make the kernel complain: Unbalanced pm_runtime_enable! this is caused by pm_runtime_enable() called before pm is initialized. This fix is similar to 227619c3ff7c, move

[PATCH 4.4 26/33] can: m_can: m_can_do_rx_poll(): fix extraneous msg loss warning

2021-03-29 Thread Greg Kroah-Hartman
From: Torin Cooper-Bennun [ Upstream commit c0e399f3baf42279f48991554240af8c457535d1 ] Message loss from RX FIFO 0 is already handled in m_can_handle_lost_msg(), with netdev output included. Removing this warning also improves driver performance under heavy load, where m_can_do_rx_poll() may

[PATCH 4.14 02/59] powerpc/4xx: Fix build errors from mfdcr()

2021-03-29 Thread Greg Kroah-Hartman
From: Michael Ellerman [ Upstream commit eead089311f4d935ab5d1d8fbb0c42ad44699ada ] lkp reported a build error in fsp2.o: CC arch/powerpc/platforms/44x/fsp2.o {standard input}:577: Error: unsupported relocation against base Which comes from: pr_err("GESR0: 0x%08x\n", mfdcr(base +

[PATCH 4.14 19/59] nfs: we dont support removing system.nfs4_acl

2021-03-29 Thread Greg Kroah-Hartman
From: J. Bruce Fields [ Upstream commit 4f8be1f53bf615102d103c0509ffa9596f65b718 ] The NFSv4 protocol doesn't have any notion of reomoving an attribute, so removexattr(path,"system.nfs4_acl") doesn't make sense. There's no documented return value. Arguably it could be EOPNOTSUPP but I'm a

[PATCH 4.14 22/59] squashfs: fix inode lookup sanity checks

2021-03-29 Thread Greg Kroah-Hartman
From: Sean Nyekjaer commit c1b2028315c6b15e8d6725e0d5884b15887d3daa upstream. When mouting a squashfs image created without inode compression it fails with: "unable to read inode lookup table" It turns out that the BLOCK_OFFSET is missing when checking the SQUASHFS_METADATA_SIZE agaist the

[PATCH 4.14 21/59] ia64: fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign

2021-03-29 Thread Greg Kroah-Hartman
From: Sergei Trofimovich [ Upstream commit 61bf318eac2c13356f7bd1c6a05421ef504ccc8a ] In https://bugs.gentoo.org/769614 Dmitry noticed that `ptrace(PTRACE_GET_SYSCALL_INFO)` does not return error sign properly. The bug is in mismatch between get/set errors: static inline long

[PATCH 4.14 20/59] ia64: fix ia64_syscall_get_set_arguments() for break-based syscalls

2021-03-29 Thread Greg Kroah-Hartman
From: Sergei Trofimovich [ Upstream commit 0ceb1ace4a2778e34a5414e5349712ae4dc41d85 ] In https://bugs.gentoo.org/769614 Dmitry noticed that `ptrace(PTRACE_GET_SYSCALL_INFO)` does not work for syscalls called via glibc's syscall() wrapper. ia64 has two ways to call syscalls from userspace: via

[PATCH 4.14 24/59] arm64: dts: ls1046a: mark crypto engine dma coherent

2021-03-29 Thread Greg Kroah-Hartman
From: Horia Geantă commit 9c3a16f88385e671b63a0de7b82b85e604a80f42 upstream. Crypto engine (CAAM) on LS1046A platform is configured HW-coherent, mark accordingly the DT node. As reported by Greg and Sascha, and explained by Robin, lack of "dma-coherent" property for an IP that is configured

[PATCH 4.14 23/59] squashfs: fix xattr id and id lookup sanity checks

2021-03-29 Thread Greg Kroah-Hartman
From: Phillip Lougher commit 8b44ca2b634527151af07447a8090a5f3a043321 upstream. The checks for maximum metadata block size is missing SQUASHFS_BLOCK_OFFSET (the two byte length count). Link: https://lkml.kernel.org/r/2069685113.2081245.1614583677...@webmail.123-reg.co.uk Fixes:

[PATCH 4.14 25/59] arm64: dts: ls1012a: mark crypto engine dma coherent

2021-03-29 Thread Greg Kroah-Hartman
From: Horia Geantă commit ba8da03fa7dff59d9400250aebd38f94cde3cb0f upstream. Crypto engine (CAAM) on LS1012A platform is configured HW-coherent, mark accordingly the DT node. Lack of "dma-coherent" property for an IP that is configured HW-coherent can lead to problems, similar to what has been

[PATCH 4.14 26/59] arm64: dts: ls1043a: mark crypto engine dma coherent

2021-03-29 Thread Greg Kroah-Hartman
From: Horia Geantă commit 4fb3a074755b7737c4081cffe0ccfa08c2f2d29d upstream. Crypto engine (CAAM) on LS1043A platform is configured HW-coherent, mark accordingly the DT node. Lack of "dma-coherent" property for an IP that is configured HW-coherent can lead to problems, similar to what has been

[PATCH 4.14 27/59] ARM: dts: at91-sama5d27_som1: fix phy address to 7

2021-03-29 Thread Greg Kroah-Hartman
From: Claudiu Beznea commit 221c3a09ddf70a0a51715e6c2878d8305e95c558 upstream. Fix the phy address to 7 for Ethernet PHY on SAMA5D27 SOM1. No connection established if phy address 0 is used. The board uses the 24 pins version of the KSZ8081RNA part, KSZ8081RNA pin 16 REFCLK as PHYAD bit [2]

[PATCH 4.14 17/59] u64_stats,lockdep: Fix u64_stats_init() vs lockdep

2021-03-29 Thread Greg Kroah-Hartman
From: Peter Zijlstra [ Upstream commit d5b0e0677bfd5efd17c5bbb00156931f0d41cb85 ] Jakub reported that: static struct net_device *rtl8139_init_board(struct pci_dev *pdev) { ... u64_stats_init(>rx_stats.syncp); u64_stats_init(>tx_stats.syncp);

[PATCH 4.14 18/59] drm/radeon: fix AGP dependency

2021-03-29 Thread Greg Kroah-Hartman
From: Christian König [ Upstream commit cba2afb65cb05c3d197d17323fee4e3c9edef9cd ] When AGP is compiled as module radeon must be compiled as module as well. Signed-off-by: Christian König Reviewed-by: Alex Deucher Signed-off-by: Alex Deucher Signed-off-by: Sasha Levin ---

[PATCH 5.4 020/111] net: davicom: Use platform_get_irq_optional()

2021-03-29 Thread Greg Kroah-Hartman
From: Paul Cercueil [ Upstream commit 2e2696223676d56db1a93acfca722c1b96cd552d ] The second IRQ line really is optional, so use platform_get_irq_optional() to obtain it. Signed-off-by: Paul Cercueil Signed-off-by: David S. Miller Signed-off-by: Sasha Levin ---

[PATCH 5.4 023/111] cifs: change noisy error message to FYI

2021-03-29 Thread Greg Kroah-Hartman
From: Paulo Alcantara [ Upstream commit e3d100eae44b42f309c1366efb8397368f1cf8ed ] A customer has reported that their dmesg were being flooded by CIFS: VFS: \\server Cancelling wait for mid xxx cmd: a CIFS: VFS: \\server Cancelling wait for mid yyy cmd: b CIFS: VFS: \\server Cancelling

[PATCH 5.4 022/111] atm: idt77252: fix null-ptr-dereference

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 4416e98594dc04590ebc498fc4e530009535c511 ] this one is similar to the phy_data allocation fix in uPD98402, the driver allocate the idt77105_priv and store to dev_data but later dereference using dev->dev_data, which will cause null-ptr-dereference. fix this

[PATCH 5.4 025/111] sparc64: Fix opcode filtering in handling of no fault loads

2021-03-29 Thread Greg Kroah-Hartman
From: Rob Gardner [ Upstream commit e5e8b80d352ec999d2bba3ea584f541c83f4ca3f ] is_no_fault_exception() has two bugs which were discovered via random opcode testing with stress-ng. Both are caused by improper filtering of opcodes. The first bug can be triggered by a floating point store with a

[PATCH 5.4 024/111] irqchip/ingenic: Add support for the JZ4760

2021-03-29 Thread Greg Kroah-Hartman
From: Paul Cercueil [ Upstream commit 5fbecd2389f48e1415799c63130d0cdce1cf3f60 ] Add support for the interrupt controller found in the JZ4760 SoC, which works exactly like the one in the JZ4770. Signed-off-by: Paul Cercueil Signed-off-by: Marc Zyngier Link:

[PATCH 5.4 026/111] habanalabs: Call put_pid() when releasing control device

2021-03-29 Thread Greg Kroah-Hartman
From: Tomer Tayar [ Upstream commit 27ac5aada024e0821c86540ad18f37edadd77d5e ] The refcount of the "hl_fpriv" structure is not used for the control device, and thus hl_hpriv_put() is not called when releasing this device. This results with no call to put_pid(), so add it explicitly in

[PATCH 5.4 021/111] atm: uPD98402: fix incorrect allocation

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 3153724fc084d8ef640c611f269ddfb576d1dcb1 ] dev->dev_data is set in zatm.c, calling zatm_start() will overwrite this dev->dev_data in uPD98402_start() and a subsequent PRIV(dev)->lock (i.e dev->phy_data->lock) will result in a null-ptr-dereference. I believe

[PATCH 5.4 016/111] nfs: fix PNFS_FLEXFILE_LAYOUT Kconfig default

2021-03-29 Thread Greg Kroah-Hartman
From: Timo Rothenpieler [ Upstream commit a0590473c5e6c4ef17c3132ad08fbad170f72d55 ] This follows what was done in 8c2fabc6542d9d0f8b16bd1045c2eda59bdcde13. With the default being m, it's impossible to build the module into the kernel. Signed-off-by: Timo Rothenpieler Signed-off-by: Anna

[PATCH 5.4 015/111] gpiolib: acpi: Add missing IRQF_ONESHOT

2021-03-29 Thread Greg Kroah-Hartman
From: Yang Li [ Upstream commit 6e5d5791730b55a1f987e1db84b078b91eb49e99 ] fixed the following coccicheck: ./drivers/gpio/gpiolib-acpi.c:176:7-27: ERROR: Threaded IRQ with no primary handler requested without IRQF_ONESHOT Make sure threaded IRQs without a primary handler are always request

[PATCH 5.4 017/111] NFS: Correct size calculation for create reply length

2021-03-29 Thread Greg Kroah-Hartman
From: Frank Sorenson [ Upstream commit ad3dbe35c833c2d4d0bbf3f04c785d32f931e7c9 ] CREATE requests return a post_op_fh3, rather than nfs_fh3. The post_op_fh3 includes an extra word to indicate 'handle_follows'. Without that additional word, create fails when full 64-byte filehandles are in use.

Re: [PATCH v3 01/18] vfs: add fileattr ops

2021-03-29 Thread Miklos Szeredi
On Sun, Mar 28, 2021 at 8:08 PM Al Viro wrote: > > On Thu, Mar 25, 2021 at 08:37:38PM +0100, Miklos Szeredi wrote: > > > +int vfs_fileattr_get(struct dentry *dentry, struct fileattr *fa) > > +{ > > + struct inode *inode = d_inode(dentry); > > + > > + if (d_is_special(dentry)) > > +

[PATCH 5.4 002/111] net: fec: ptp: avoid register access when ipg clock is disabled

2021-03-29 Thread Greg Kroah-Hartman
From: Heiko Thiery [ Upstream commit 6a4d7234ae9a3bb31181f348ade9bbdb55aeb5c5 ] When accessing the timecounter register on an i.MX8MQ the kernel hangs. This is only the case when the interface is down. This can be reproduced by reading with 'phc_ctrl eth0 get'. Like described in the change in

[PATCH 5.4 019/111] net: wan: fix error return code of uhdlc_init()

2021-03-29 Thread Greg Kroah-Hartman
From: Jia-Ju Bai [ Upstream commit 62765d39553cfd1ad340124fe1e280450e8c89e2 ] When priv->rx_skbuff or priv->tx_skbuff is NULL, no error return code of uhdlc_init() is assigned. To fix this bug, ret is assigned with -ENOMEM in these cases. Reported-by: TOTE Robot Signed-off-by: Jia-Ju Bai

[PATCH 5.4 018/111] net: hisilicon: hns: fix error return code of hns_nic_clear_all_rx_fetch()

2021-03-29 Thread Greg Kroah-Hartman
From: Jia-Ju Bai [ Upstream commit 143c253f42bad20357e7e4432087aca747c43384 ] When hns_assemble_skb() returns NULL to skb, no error return code of hns_nic_clear_all_rx_fetch() is assigned. To fix this bug, ret is assigned with -ENOMEM in this case. Reported-by: TOTE Robot Signed-off-by:

[PATCH 5.4 028/111] regulator: qcom-rpmh: Correct the pmic5_hfsmps515 buck

2021-03-29 Thread Greg Kroah-Hartman
From: satya priya [ Upstream commit e610e072c87a30658479a7b4c51e1801cb3f450c ] Correct the REGULATOR_LINEAR_RANGE and n_voltges for pmic5_hfsmps515 buck. Signed-off-by: satya priya Link: https://lore.kernel.org/r/1614155592-14060-4-git-send-email-ska...@codeaurora.org Signed-off-by: Mark

[PATCH 5.10 031/221] irqchip/ingenic: Add support for the JZ4760

2021-03-29 Thread Greg Kroah-Hartman
From: Paul Cercueil [ Upstream commit 5fbecd2389f48e1415799c63130d0cdce1cf3f60 ] Add support for the interrupt controller found in the JZ4760 SoC, which works exactly like the one in the JZ4770. Signed-off-by: Paul Cercueil Signed-off-by: Marc Zyngier Link:

[PATCH 5.10 059/221] static_call: Fix the module key fixup

2021-03-29 Thread Greg Kroah-Hartman
From: Peter Zijlstra [ Upstream commit 50bf8080a94d171e843fc013abec19d8ab9f50ae ] Provided the target address of a R_X86_64_PC32 relocation is aligned, the low two bits should be invariant between the relative and absolute value. Turns out the address is not aligned and things go sideways,

[PATCH 5.10 060/221] static_call: Fix static_call_set_init()

2021-03-29 Thread Greg Kroah-Hartman
From: Peter Zijlstra [ Upstream commit 68b1eddd421d2b16c6655eceb48918a1e896bbbc ] It turns out that static_call_set_init() does not preserve the other flags; IOW. it clears TAIL if it was set. Fixes: 9183c3f9ed710 ("static_call: Add inline static call infrastructure") Reported-by: Sumit Garg

[PATCH 5.10 061/221] KVM: x86: Protect userspace MSR filter with SRCU, and set atomically-ish

2021-03-29 Thread Greg Kroah-Hartman
From: Sean Christopherson [ Upstream commit b318e8decf6b9ef1bcf4ca06fae6d6a2cb5d5c5c ] Fix a plethora of issues with MSR filtering by installing the resulting filter as an atomic bundle instead of updating the live filter one range at a time. The KVM_X86_SET_MSR_FILTER ioctl() isn't truly

[PATCH 5.10 028/221] atm: uPD98402: fix incorrect allocation

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 3153724fc084d8ef640c611f269ddfb576d1dcb1 ] dev->dev_data is set in zatm.c, calling zatm_start() will overwrite this dev->dev_data in uPD98402_start() and a subsequent PRIV(dev)->lock (i.e dev->phy_data->lock) will result in a null-ptr-dereference. I believe

[PATCH 5.10 029/221] atm: idt77252: fix null-ptr-dereference

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 4416e98594dc04590ebc498fc4e530009535c511 ] this one is similar to the phy_data allocation fix in uPD98402, the driver allocate the idt77105_priv and store to dev_data but later dereference using dev->dev_data, which will cause null-ptr-dereference. fix this

[PATCH 5.10 030/221] cifs: change noisy error message to FYI

2021-03-29 Thread Greg Kroah-Hartman
From: Paulo Alcantara [ Upstream commit e3d100eae44b42f309c1366efb8397368f1cf8ed ] A customer has reported that their dmesg were being flooded by CIFS: VFS: \\server Cancelling wait for mid xxx cmd: a CIFS: VFS: \\server Cancelling wait for mid yyy cmd: b CIFS: VFS: \\server Cancelling

[PATCH 5.10 024/221] net: hisilicon: hns: fix error return code of hns_nic_clear_all_rx_fetch()

2021-03-29 Thread Greg Kroah-Hartman
From: Jia-Ju Bai [ Upstream commit 143c253f42bad20357e7e4432087aca747c43384 ] When hns_assemble_skb() returns NULL to skb, no error return code of hns_nic_clear_all_rx_fetch() is assigned. To fix this bug, ret is assigned with -ENOMEM in this case. Reported-by: TOTE Robot Signed-off-by:

[PATCH 5.10 033/221] kbuild: dummy-tools: fix inverted tests for gcc

2021-03-29 Thread Greg Kroah-Hartman
From: Jiri Slaby [ Upstream commit b3d9fc1436808a4ef9927e558b3415e728e710c5 ] There is a test in Kconfig which takes inverted value of a compiler check: * config CC_HAS_INT128 def_bool !$(cc-option,$(m64-flag) -D__SIZEOF_INT128__=0) This results in CC_HAS_INT128 not being in

[PATCH 5.10 063/221] selinux: dont log MAC_POLICY_LOAD record on failed policy load

2021-03-29 Thread Greg Kroah-Hartman
From: Ondrej Mosnacek commit 519dad3bcd809dc1523bf80ab0310ddb3bf00ade upstream. If sel_make_policy_nodes() fails, we should jump to 'out', not 'out1', as the latter would incorrectly log an MAC_POLICY_LOAD audit record, even though the policy hasn't actually been reloaded. The 'out1' jump label

[PATCH 5.10 073/221] gcov: fix clang-11+ support

2021-03-29 Thread Greg Kroah-Hartman
From: Nick Desaulniers commit 60bcf728ee7c60ac2a1f9a0eaceb3a7b3954cd2b upstream. LLVM changed the expected function signatures for llvm_gcda_start_file() and llvm_gcda_emit_function() in the clang-11 release. Users of clang-11 or newer may have noticed their kernels failing to boot due to a

[PATCH 5.10 074/221] ACPI: video: Add missing callback back for Sony VPCEH3U1E

2021-03-29 Thread Greg Kroah-Hartman
From: Chris Chiu commit c1d1e25a8c542816ae8dee41b81a18d30c7519a0 upstream. The .callback of the quirk for Sony VPCEH3U1E was unintetionally removed by the commit 25417185e9b5 ("ACPI: video: Add DMI quirk for GIGABYTE GB-BXBT-2807"). Add it back to make sure the quirk for Sony VPCEH3U1E works as

[PATCH 5.10 076/221] arm64: stacktrace: dont trace arch_stack_walk()

2021-03-29 Thread Greg Kroah-Hartman
From: Mark Rutland commit c607ab4f916d4d5259072eca34055d3f5a795c21 upstream. We recently converted arm64 to use arch_stack_walk() in commit: 5fc57df2f6fd ("arm64: stacktrace: Convert to ARCH_STACKWALK") The core stacktrace code expects that (when tracing the current task) arch_stack_walk()

[PATCH 5.10 056/221] ia64: fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign

2021-03-29 Thread Greg Kroah-Hartman
From: Sergei Trofimovich [ Upstream commit 61bf318eac2c13356f7bd1c6a05421ef504ccc8a ] In https://bugs.gentoo.org/769614 Dmitry noticed that `ptrace(PTRACE_GET_SYSCALL_INFO)` does not return error sign properly. The bug is in mismatch between get/set errors: static inline long

[PATCH 5.10 057/221] static_call: Pull some static_call declarations to the type headers

2021-03-29 Thread Greg Kroah-Hartman
From: Peter Zijlstra [ Upstream commit 880cfed3a012d7863f42251791cea7fe78c39390 ] Some static call declarations are going to be needed on low level header files. Move the necessary material to the dedicated static call types header to avoid inclusion dependency hell. Signed-off-by: Peter

[PATCH 5.10 058/221] static_call: Allow module use without exposing static_call_key

2021-03-29 Thread Greg Kroah-Hartman
From: Josh Poimboeuf [ Upstream commit 73f44fe19d359635a607e8e8daa0da4001c1cfc2 ] When exporting static_call_key; with EXPORT_STATIC_CALL*(), the module can use static_call_update() to change the function called. This is not desirable in general. Not exporting static_call_key however also

[PATCH 5.10 032/221] kbuild: add image_name to no-sync-config-targets

2021-03-29 Thread Greg Kroah-Hartman
From: Masahiro Yamada [ Upstream commit 993bdde94547887faaad4a97f0b0480a6da271c3 ] 'make image_name' needs include/config/auto.conf to show the correct output because KBUILD_IMAGE depends on CONFIG options, but should not attempt to resync the configuration. Signed-off-by: Masahiro Yamada

Re: [PATCH] usb: gadget: aspeed: set port_dev dma mask

2021-03-29 Thread Christoph Hellwig
On Sat, Mar 27, 2021 at 03:17:59PM -0700, Tao Ren wrote: > On Fri, Mar 26, 2021 at 01:05:26PM +0100, Christoph Hellwig wrote: > > On Fri, Mar 26, 2021 at 12:03:03PM +, Robin Murphy wrote: > > > This might happen to work out, but is far from correct. Just wait until > > > you > > > try it on

Re: [PATCH v2 4/4] erofs: add on-disk compression configurations

2021-03-29 Thread Gao Xiang
On Mon, Mar 29, 2021 at 02:43:48PM +0800, Chao Yu wrote: ... > > > > + > > > > +static int erofs_load_compr_cfgs(struct super_block *sb, > > > > +struct erofs_super_block *dsb) > > > > +{ > > > > + struct erofs_sb_info *sbi; > > > > + struct page

[PATCH] locking/mutex: initialize osq lock in __MUTEX_INITIALIZER()

2021-03-29 Thread Nikitas Angelinas
Since __MUTEX_INITIALIZER() is used on memory that is initialized to 0 anyway this change should not have an effect, but it seems better to initialize osq explicitly for completeness, as done in other macros and functions that initialize mutex and rwsem. Signed-off-by: Nikitas Angelinas ---

Re: [PATCH 0/3] iio: adc: ad7923: convert driver resources routines to device-managed counterparts

2021-03-29 Thread Alexandru Ardelean
On Mon, Mar 29, 2021 at 12:48 AM Lucas Stankus wrote: > > Following the initiative proposed by Alexandru, this patch series aims > to convert the ad7923 to use only device-managed routines. > This idea is becoming popular it seems :) Thanks to Lars for pointing out that spi_set_drvdata()

Re: drivers/net/can/spi/mcp251xfd/mcp251xfd-core.c:2267:16: warning: taking address of packed member 'hw_tx_obj' of class or structure 'mcp251xfd_tx_obj_load_buf::(anonymous)' may result in an unalign

2021-03-29 Thread Marc Kleine-Budde
On 27.03.2021 18:16:14, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 0f4498cef9f5cd18d7c6639a2a902ec1edc5be4e > commit: eb79a267c9b3e608e7762a1b221428f37ace3aa3 can: mcp251xfd: rename all > remaining occurrence to

Re: [PATCH] xen/pciback: Fix incorrect type warnings

2021-03-29 Thread Juergen Gross
On 26.03.21 19:14, Muhammad Usama Anjum wrote: Correct enum pci_channel_io_normal should be used instead of putting integer value 1. Fix following smatch warnings: drivers/xen/xen-pciback/pci_stub.c:805:40: warning: incorrect type in argument 2 (different base types)

linux-next: manual merge of the rust tree with the kbuild tree

2021-03-29 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the rust tree got a conflict in: Makefile between commit: b0600f0d9b54 ("kbuild: check the minimum assembler version in Kconfig") from the kbuild tree and commit: 98898dfbdf72 ("Rust support") from the rust tree. I fixed it up (see below) and can

Re: [PATCH 03/17] ASoC: atmel: atmel-i2s: remove useless initialization

2021-03-29 Thread Codrin.Ciubotariu
On 26.03.2021 23:59, Pierre-Louis Bossart wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the > content is safe > > Cppcheck complains: > > sound/soc/atmel/atmel-i2s.c:628:6: style: Redundant initialization for 'err'. > The initialized value is overwritten

Re: [kbuild-all] Re: [PATCH] riscv: Use $(LD) instead of $(CC) to link vDSO

2021-03-29 Thread Rong Chen
Hi Nathan, On 3/27/21 7:58 AM, Nathan Chancellor wrote: On Sat, Mar 27, 2021 at 12:05:34AM +0800, kernel test robot wrote: Hi Nathan, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v5.12-rc4 next-20210326] [If your patch is

Re: [kernel/resource] cf1e4e12c9: WARNING:possible_recursive_locking_detected

2021-03-29 Thread Alistair Popple
Not sure why I didn't hit this in testing but the problem is obvious: I missed that revoke_iomem() calls devmem_is_allowed() which on x86 calls region_intersects(). I guess I must have forgotten to do a boot test with CONFIG_IO_STRICT_DEVMEM. Will put a fix together. - Alistair On Monday, 29

[PATCH 4.4 04/33] atm: lanai: dont run lanai_dev_close if not open

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit a2bd45834e83d6c5a04d397bde13d744a4812dfc ] lanai_dev_open() can fail. When it fail, lanai->base is unmapped and the pci device is disabled. The caller, lanai_init_one(), then tries to run atm_dev_deregister(). This will subsequently call lanai_dev_close() and

[PATCH 4.4 05/33] net: tehuti: fix error return code in bdx_probe()

2021-03-29 Thread Greg Kroah-Hartman
From: Jia-Ju Bai [ Upstream commit 38c26ff3048af50eee3fcd591921357ee5bfd9ee ] When bdx_read_mac() fails, no error return code of bdx_probe() is assigned. To fix this bug, err is assigned with -EFAULT as error return code. Reported-by: TOTE Robot Signed-off-by: Jia-Ju Bai Signed-off-by: David

[PATCH 4.4 06/33] sun/niu: fix wrong RXMAC_BC_FRM_CNT_COUNT count

2021-03-29 Thread Greg Kroah-Hartman
From: Denis Efremov [ Upstream commit 155b23e6e53475ca3b8c2a946299b4d4dd6a5a1e ] RXMAC_BC_FRM_CNT_COUNT added to mp->rx_bcasts twice in a row in niu_xmac_interrupt(). Remove the second addition. Signed-off-by: Denis Efremov Signed-off-by: David S. Miller Signed-off-by: Sasha Levin ---

[PATCH 4.4 07/33] nfs: fix PNFS_FLEXFILE_LAYOUT Kconfig default

2021-03-29 Thread Greg Kroah-Hartman
From: Timo Rothenpieler [ Upstream commit a0590473c5e6c4ef17c3132ad08fbad170f72d55 ] This follows what was done in 8c2fabc6542d9d0f8b16bd1045c2eda59bdcde13. With the default being m, it's impossible to build the module into the kernel. Signed-off-by: Timo Rothenpieler Signed-off-by: Anna

[PATCH 4.4 00/33] 4.4.264-rc1 review

2021-03-29 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.4.264 release. There are 33 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed, 31 Mar 2021 07:55:56 +. Anything

[PATCH 4.4 09/33] atm: uPD98402: fix incorrect allocation

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 3153724fc084d8ef640c611f269ddfb576d1dcb1 ] dev->dev_data is set in zatm.c, calling zatm_start() will overwrite this dev->dev_data in uPD98402_start() and a subsequent PRIV(dev)->lock (i.e dev->phy_data->lock) will result in a null-ptr-dereference. I believe

[PATCH 4.4 08/33] NFS: Correct size calculation for create reply length

2021-03-29 Thread Greg Kroah-Hartman
From: Frank Sorenson [ Upstream commit ad3dbe35c833c2d4d0bbf3f04c785d32f931e7c9 ] CREATE requests return a post_op_fh3, rather than nfs_fh3. The post_op_fh3 includes an extra word to indicate 'handle_follows'. Without that additional word, create fails when full 64-byte filehandles are in use.

[PATCH 4.4 28/33] net: cdc-phonet: fix data-interface release on probe failure

2021-03-29 Thread Greg Kroah-Hartman
From: Johan Hovold [ Upstream commit c79a707072fe3fea0e3c92edee6ca85c1e53c29f ] Set the disconnected flag before releasing the data interface in case netdev registration fails to avoid having the disconnect callback try to deregister the never registered netdev (and trigger a WARN_ON()).

[PATCH 4.4 29/33] RDMA/cxgb4: Fix adapter LE hash errors while destroying ipv6 listening server

2021-03-29 Thread Greg Kroah-Hartman
From: Potnuri Bharat Teja [ Upstream commit 3408be145a5d6418ff955fe5badde652be90e700 ] Not setting the ipv6 bit while destroying ipv6 listening servers may result in potential fatal adapter errors due to lookup engine memory hash errors. Therefore always set ipv6 field while destroying ipv6

[PATCH 4.4 31/33] can: dev: Move device back to init netns on owning netns delete

2021-03-29 Thread Greg Kroah-Hartman
From: Martin Willi commit 3a5ca857079ea022e0b1b17fc154f7ad7dbc150f upstream. When a non-initial netns is destroyed, the usual policy is to delete all virtual network interfaces contained, but move physical interfaces back to the initial netns. This keeps the physical interface visible on the

[PATCH 4.4 30/33] perf auxtrace: Fix auxtrace queue conflict

2021-03-29 Thread Greg Kroah-Hartman
From: Adrian Hunter [ Upstream commit b410ed2a8572d41c68bd9208555610e4b07d0703 ] The only requirement of an auxtrace queue is that the buffers are in time order. That is achieved by making separate queues for separate perf buffer or AUX area buffer mmaps. That generally means a separate queue

[PATCH 4.4 33/33] mac80211: fix double free in ibss_leave

2021-03-29 Thread Greg Kroah-Hartman
From: Markus Theil commit 3bd801b14e0c5d29eeddc7336558beb3344efaa3 upstream. Clear beacon ie pointer and ie length after free in order to prevent double free. == BUG: KASAN: double-free or invalid-free \ in

[PATCH 4.4 32/33] net: sched: validate stab values

2021-03-29 Thread Greg Kroah-Hartman
From: Eric Dumazet commit e323d865b36134e8c5c82c834df89109a5c60dab upstream. iproute2 package is well behaved, but malicious user space can provide illegal shift values and trigger UBSAN reports. Add stab parameter to red_check_params() to validate user input. syzbot reported: UBSAN:

[PATCH 4.9 01/53] net: fec: ptp: avoid register access when ipg clock is disabled

2021-03-29 Thread Greg Kroah-Hartman
From: Heiko Thiery [ Upstream commit 6a4d7234ae9a3bb31181f348ade9bbdb55aeb5c5 ] When accessing the timecounter register on an i.MX8MQ the kernel hangs. This is only the case when the interface is down. This can be reproduced by reading with 'phc_ctrl eth0 get'. Like described in the change in

[PATCH 4.9 10/53] net: wan: fix error return code of uhdlc_init()

2021-03-29 Thread Greg Kroah-Hartman
From: Jia-Ju Bai [ Upstream commit 62765d39553cfd1ad340124fe1e280450e8c89e2 ] When priv->rx_skbuff or priv->tx_skbuff is NULL, no error return code of uhdlc_init() is assigned. To fix this bug, ret is assigned with -ENOMEM in these cases. Reported-by: TOTE Robot Signed-off-by: Jia-Ju Bai

[PATCH 4.4 27/33] mac80211: fix rate mask reset

2021-03-29 Thread Greg Kroah-Hartman
From: Johannes Berg [ Upstream commit 1944015fe9c1d9fa5e9eb7ffbbb5ef8954d6753b ] Coverity reported the strange "if (~...)" condition that's always true. It suggested that ! was intended instead of ~, but upon further analysis I'm convinced that what really was intended was a comparison to

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