linux-next: Tree for Mar 18

Hi all, News: there will be no linux-next release on Friday this week. Warning: Some of the branches in linux-next are still based on v5.12-rc1, so please be careful if you are trying to bisect a bug. News: if your -next included tree is based on Linus' tree tag v5.12-rc1{,-dontuse} (or

Re: [PATCH 07/10] MIPS: disable CONFIG_IDE in bigsur_defconfig

Hi! On 3/18/21 7:57 AM, Christoph Hellwig wrote: > bigsur_defconfig enables CONFIG_IDE for the tc86c001 ide driver, which > is a Toshiba plug in card that does not make much sense to use on bigsur ^ for Else that doesn't make much sense. :-) > platforms. For all other ATA cards libata

[PATCH] mm: vmalloc: Prevent use after free in _vm_unmap_aliases

From: Vijayanand Jitta A potential use after free can occur in _vm_unmap_aliases where an already freed vmap_area could be accessed, Consider the following scenario: Process 1 Process 2 __vm_unmap_aliases

[PATCH v25 00/13] Introduce Data Access MONitor (DAMON)

From: SeongJae Park Changes from Previous Version (v24) === - Rebase on latest -mm tree (v5.12-rc3-mmots-2021-03-17-22-26) - Ignore 'debugfs_create_{file|dir}()' return values (Greg KH) - Remove 'recording' feature - Remove user space tool and recording

[PATCH 0/2]spi: spi-zynq-qspi: Fix stack violation bug

This patch series fixes kernel-doc warnings and stack violation issues in Zynq qspi driver file --- Branch: for-next --- Amit Kumar Mahapatra (1): spi: spi-zynq-qspi: Fix kernel-doc warning Karen Dombroski (1): spi: spi-zynq-qspi: Fix stack violation bug drivers/spi/spi-zynq-qspi.c | 9

[PATCH 1/2] spi: spi-zynq-qspi: Fix kernel-doc warning

Fix kernel-doc warning. Signed-off-by: Amit Kumar Mahapatra --- drivers/spi/spi-zynq-qspi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/spi/spi-zynq-qspi.c b/drivers/spi/spi-zynq-qspi.c index 5d8a5ee62fa2..1acde9e24973 100644 --- a/drivers/spi/spi-zynq-qspi.c +++

[PATCH 2/2] spi: spi-zynq-qspi: Fix stack violation bug

From: Karen Dombroski When the number of bytes for the op is greater than one, the read could run off the end of the function stack and cause a crash. This patch restores the behaviour of safely reading out of the original opcode location. Kernel panic - not syncing: stack-protector: Kernel

Re: [PATCH 5/5] i2c: stm32f7: indicate the address being accessed on errors

On Fri, Feb 05, 2021 at 09:51:44AM +0100, Alain Volmat wrote: > To help debugging issues, add the address of the slave being > accessed when getting an error. > > Signed-off-by: Alain Volmat Applied to for-next, thanks! signature.asc Description: PGP signature

Re: [RFC PATCH 7/8] dt-bindings: Add bindings documentation for RISC-V idle states

On Tue, Mar 16, 2021 at 9:24 PM Rob Herring wrote: > > On Sun, Mar 7, 2021 at 8:18 PM Anup Patel wrote: > > > > On Sat, Mar 6, 2021 at 4:52 AM Rob Herring wrote: > > > > > > On Sun, Feb 21, 2021 at 03:07:57PM +0530, Anup Patel wrote: > > > > The RISC-V CPU idle states will be described in DT

Re: [GIT PULL v2] Immutable branch between MFD and Platform/X86 due for the v5.13 merge window

Hi, On 3/10/21 11:57 AM, Lee Jones wrote: > Rebased onto -rc2 > > The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15: > > Linux 5.12-rc2 (2021-03-05 17:33:41 -0800) > > are available in the Git repository at: > >

Re: systemd-rfkill regression on 5.11 and later kernels

On Thu, 18 Mar 2021 11:50:37 +0100, Johannes Berg wrote: > > Hi, > > > OK, I took a deeper look again, and actually there are two issues in > > systemd-rfkill code: > > > > * It expects 8 bytes returned from read while it reads a struct > >   rfkill_event record. If the code is rebuilt with

Re: [PATCH] i2c: i2c-scmi: Drop unused ACPI_MODULE_NAME definition

On Fri, Mar 05, 2021 at 07:28:30PM +0100, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The ACPI_MODULE_NAME() definition is only used by the message > printing macros from ACPICA that are not used by the code in > question, so it is redundant. Drop it. > > No functional impact. > >

[PATCH] fs/nilfs2: fix misspellings using codespell tool

From: Liu xuzhi Two typos are found out by codespell tool \ in 2217th and 2254th lines of segment.c: $ codespell ./fs/nilfs2/ ./segment.c:2217 :retured ==> returned ./segment.c:2254: retured ==> returned Fix two typos found by codespell. Signed-off-by: Liu xuzhi --- fs/nilfs2/segment.c |

[PATCH v3 0/2] Add i2c-cp2615

For a hardware project, I need the I2C master of SiLabs' CP2615 chip to be visible from under Linux. This patchset adds i2c-cp2615, a driver which sets up an i2c_adapter for said chip. Changes in v3: * Fixed SPDX header * Added I2C_AQ_NO_REP_START adapter quirk to i2c.h * Added I2C_AQ_NO_ZERO_LEN

[PATCH v3 2/2] Adding i2c-cp2615: i2c support for Silicon Labs' CP2615 Digital Audio Bridge

Create an i2c_adapter for CP2615's I2C master interface by implementing parts of the CP2615's I/O Protocol (IOP) Signed-off-by: Bence Csókás --- drivers/i2c/busses/Kconfig | 10 ++ drivers/i2c/busses/Makefile | 1 + drivers/i2c/busses/i2c-cp2615.c | 279

[PATCH v3 1/2] i2c: Add I2C_AQ_NO_REP_START adapter quirk

This quirk signifies that the adapter cannot do a repeated START, it always issues a STOP condition after transfers. Signed-off-by: Bence Csókás --- include/linux/i2c.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/linux/i2c.h b/include/linux/i2c.h index

Re: [PATCH 1/2] selftests: add a kselftest for SLUB debugging functionality

On Tue, Mar 16, 2021 at 01:41PM +0100, glit...@gmail.com wrote: > From: Oliver Glitta > > SLUB has resiliency_test() function which is hidden behind #ifdef > SLUB_RESILIENCY_TEST that is not part of Kconfig, so nobody > runs it. Kselftest should proper replacement for it. > > Try changing byte

Re: [PATCH v4 1/5] mm,memory_hotplug: Allocate memmap from the added memory range

On Thu, Mar 18, 2021 at 12:24:16PM +0100, David Hildenbrand wrote: > I don't follow. 2MB == 2MB. And if there would be difference then we would > be in the problem I brought up: vmemmap code allocating too much via the > altmap, which can be very bad because might be populating more vmemmap than >

[PATCH net-next v1 3/3] net: phy: mscc: coma mode disabled for VSC8584

This patch releases coma mode for VSC8584 as done for VSC8514 in commit ca0d7fd0a58d ("net: phy: mscc: coma mode disabled for VSC8514") Fixes: a5afc1678044a ("net: phy: mscc: add support for VSC8584 PHYY.") Signed-off-by: Bjarni Jonasson --- drivers/net/phy/mscc/mscc_main.c | 1 + 1 file

Re: [PATCH v2 2/4] leds: simatic-ipc-leds: add new driver for Siemens Industial PCs

Hei hei, > Enrico Weigelt, metux IT consult hat am 18.03.2021 11:27 > geschrieben: > > > On 15.03.21 11:48, Andy Shevchenko wrote: > > Hi, > > > I have a question, why we can't provide a GPIO driver which is already > > in the kernel and, with use of the patch series I sent, to convert > >

[PATCH V5 1/2] backlight: qcom-wled: Fix FSC update issue for WLED5

Currently, for WLED5, the FSC (Full scale current) setting is not updated properly due to driver toggling the wrong register after an FSC update. On WLED5 we should only toggle the MOD_SYNC bit after a brightness update. For an FSC update we need to toggle the SYNC bits instead. Fix it by

[PATCH V5 0/2] Fix WLED FSC Sync and brightness Sync settings

This patch series has the following two WLED fixes 1. As per the current implementation, for WLED5, after the FSC (Full Scale Current) update the driver is incorrectly toggling the MOD_SYNC register instead of toggling the SYNC register. The patch 1/2 fixes this by toggling the SYNC

[tip: sched/core] sched: Fix various typos

The following commit has been merged into the sched/core branch of tip: Commit-ID: 7aacb8c62f621e9f6f1b5f11bb19eb37ddbf00e2 Gitweb: https://git.kernel.org/tip/7aacb8c62f621e9f6f1b5f11bb19eb37ddbf00e2 Author:Ingo Molnar AuthorDate:Thu, 18 Mar 2021 13:38:50 +01:00

A potential data race in drivers/iio/adc/berlin2-adc.ko

Hi, berlin2_adc_probe [1] registers two interrupt handlers: berlin2_adc_irq [2] and berlin2_adc_tsen_irq [3]. The interrupt handlers operate with the same data, for example, modify priv->data with different masks: priv->data &= BERLIN2_SM_ADC_MASK; and priv->data &= BERLIN2_SM_TSEN_MASK; If

Re: [PATCH RFC 1/2] x86/apic: Do not make an exception for PIC_CASCADE_IR when marking legacy irqs in irq_matrix

Thomas Gleixner writes: > On Fri, Feb 19 2021 at 12:31, Vitaly Kuznetsov wrote: >> Trying to offline/online CPU0 seems to work only once: >> >> # echo 0 > /sys/devices/system/cpu/cpu0/online >> # echo 1 > /sys/devices/system/cpu/cpu0/online >> # echo 0 > /sys/devices/system/cpu/cpu0/online >>

Re: [PATCH 2/5] iommu/vt-d: Remove WO permissions on second-level paging entries

Hi, On Mon, Mar 08, 2021 at 11:47:46AM -0800, Raj, Ashok wrote: > That is the primary motivation, given that we have moved to 1st level for > general IOVA, first level doesn't have a WO mapping. I didn't know enough > about the history to determine if a WO without a READ is very useful. I > guess

Re: [PATCH 3/3] KVM: SVM: allow to intercept all exceptions for debug

On Tue, Mar 16, 2021 at 12:51:20PM +0200, Maxim Levitsky wrote: > I agree but what is wrong with that? > This is a debug feature, and it only can be enabled by the root, > and so someone might actually want this case to happen > (e.g to see if a SEV guest can cope with extra #VC exceptions).

[PATCH] scsi: aha1542: remove unneeded semicolon

Fix the following coccicheck warnings: ./drivers/scsi/aha1542.c:569:2-3: Unneeded semicolon. ./drivers/scsi/aha1542.c:554:2-3: Unneeded semicolon. ./drivers/scsi/aha1542.c:519:2-3: Unneeded semicolon. ./drivers/scsi/aha1542.c:508:3-4: Unneeded semicolon. ./drivers/scsi/aha1542.c:407:2-3: Unneeded

Re: [PATCH 1/1] leds: lgm: Improve Kconfig help

Hi Pavel, On 18/3/2021 3:55 pm, Pavel Machek wrote: > Hi! > > > Remove unnecessary Kconfig symbol LEDS_BLINK > > Improve Kconfig help text to make it more useful. > > > > Signed-off-by: Rahul Tanwar > > > +++ b/drivers/leds/blink/Kconfig > > @@ -1,21 +1,19 @@ > > -menuconfig LEDS_BLINK

Re: [PATCH v3] iommu: Check dev->iommu in iommu_dev_xxx functions

On Wed, Mar 03, 2021 at 05:36:11PM +, Shameer Kolothum wrote: > The device iommu probe/attach might have failed leaving dev->iommu > to NULL and device drivers may still invoke these functions resulting > in a crash in iommu vendor driver code. > > Hence make sure we check that. > > Fixes: 

RE: [PATCH 2/4] phy: cadence-torrent: Group reset APIs and clock APIs

> -Original Message- > From: Kishon Vijay Abraham I > Sent: Wednesday, March 10, 2021 9:25 PM > To: Kishon Vijay Abraham I ; Vinod Koul > ; Rob Herring ; Philipp Zabel > ; Swapnil Kashinath Jakhade > > Cc: linux-kernel@vger.kernel.org; devicet...@vger.kernel.org; Lokesh Vutla > ;

Re: systemd-rfkill regression on 5.11 and later kernels

On Thu, 18 Mar 2021 10:36:19 +0100, Johannes Berg wrote: > > Hi Takashi, > > Oh yay :-( > > > we've received a bug report about rfkill change that was introduced in > > 5.11. While the systemd-rfkill expects the same size of both read and > > write, the kernel rfkill write cuts off to the old

[PATCH] RDMA/include: Mundane typo fixes throughout the file

s/proviee/provide/ s/undelying/underlying/ s/quesiton/question/ s/drivr/driver/ Signed-off-by: Bhaskar Chowdhury --- include/rdma/rdma_vt.h | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/include/rdma/rdma_vt.h b/include/rdma/rdma_vt.h index

Re: [PATCH v5 2/5] mm,compaction: Let isolate_migratepages_{range,block} return error codes

On Thu 18-03-21 10:50:38, Vlastimil Babka wrote: > On 3/17/21 3:59 PM, Michal Hocko wrote: > > On Wed 17-03-21 15:38:35, Oscar Salvador wrote: > >> On Wed, Mar 17, 2021 at 03:12:29PM +0100, Michal Hocko wrote: > >> > > Since isolate_migratepages_block will stop returning the next pfn to be > >> >

Re: [PATCH v2 2/4] leds: simatic-ipc-leds: add new driver for Siemens Industial PCs

On 15.03.21 10:57, Henning Schild wrote: Hi, diff --git a/drivers/leds/simple/simatic-ipc-leds.c b/drivers/leds/simple/simatic-ipc-leds.c new file mode 100644 index ..0f7e6320e10d --- /dev/null +++ b/drivers/leds/simple/simatic-ipc-leds.c @@ -0,0 +1,210 @@ +//

[tip: timers/core] time/debug: Remove dentry pointer for debugfs

The following commit has been merged into the timers/core branch of tip: Commit-ID: 44511ab344c755d1f216bf421e92fbc2777e87fe Gitweb: https://git.kernel.org/tip/44511ab344c755d1f216bf421e92fbc2777e87fe Author:Greg Kroah-Hartman AuthorDate:Tue, 16 Feb 2021 16:50:20 +01:00

Re: [RFC PATCH v3 0/3] blk-mq: Avoid use-after-free for accessing old requests

On Mar 05, 2021 / 23:14, John Garry wrote: > This series aims to tackle the various UAF reports, like: > [0] > https://lore.kernel.org/linux-block/8376443a-ec1b-0cef-8244-ed584b96f...@huawei.com/ > [1] >

Re: [PATCH v4 1/6] soc/tegra: Add devm_tegra_core_dev_init_opp_table()

On 18-03-21, 13:27, Dmitry Osipenko wrote: > 14.03.2021 19:48, Dmitry Osipenko пишет: > > Add common helper which initializes OPP table for Tegra SoC core devices. > > > > Tested-by: Peter Geis # Ouya T30 > > Tested-by: Paul Fertser # PAZ00 T20 > > Tested-by: Nicolas Chauvet # PAZ00 T20 and

Re: [PATCH v2 0/4] Misc vSVA fixes for VT-d

On Tue, Mar 02, 2021 at 02:13:56AM -0800, Jacob Pan wrote: > Hi Baolu et al, > > This is a collection of SVA-related fixes. > > ChangeLog: > > v2: > - For guest SVA, call pasid_set_wpe directly w/o checking host CR0.wp > (Review comments by Kevin T.) > - Added fixes tag > >

Re: [PATCH v5] printk: Userspace format enumeration support

On Wed 2021-03-17 11:03:20, Rasmus Villemoes wrote: > On 17/03/2021 09.40, Petr Mladek wrote: > > On Tue 2021-03-16 14:28:12, Chris Down wrote: > >> Rasmus Villemoes writes: > >>> I think it's pointless renaming the symbol to _printk, with all the > >>> churn and reduced readability that involves

[PATCH] sh: kernel: Fix a typo

s/archtecture/architecture/ Signed-off-by: Bhaskar Chowdhury --- arch/sh/kernel/relocate_kernel.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/sh/kernel/relocate_kernel.S b/arch/sh/kernel/relocate_kernel.S index d9bf2b727b42..deda2f60a8f2 100644 ---

Re: [PATCH v7 1/3] dmaengine: ptdma: Initial driver for the AMD PTDMA

>> +#include >> +#include >> +#include >> +#include >> +#include >> +#include >> +#include >> +#include >> +#include > > why do you need sched.h here? > >> + >> +#include "ptdma.h" >> + >> +/* Ever-increasing value to produce unique unit numbers */ >> +static atomic_t pt_ordinal; > >

Re: [PATCH v7 2/3] dmaengine: ptdma: register PTDMA controller as a DMA resource

>> + dma_dev->dst_addr_widths = PT_DMA_WIDTH(dma_get_mask(pt->dev)); >> + dma_dev->directions = DMA_MEM_TO_MEM; >> + dma_dev->residue_granularity = DMA_RESIDUE_GRANULARITY_DESCRIPTOR; >> + dma_cap_set(DMA_MEMCPY, dma_dev->cap_mask); >> + dma_cap_set(DMA_INTERRUPT,

Re: [PATCH 2/5] i2c: stm32f7: support DT binding i2c-analog-filter

On Fri, Feb 05, 2021 at 09:51:41AM +0100, Alain Volmat wrote: > Replace driver internally coded enabling/disabling of the > analog-filter with the DT binding "i2c-analog-filter". > > Signed-off-by: Alain Volmat Applied to for-next, thanks! signature.asc Description: PGP signature

Re: [PATCH 3/5] i2c: stm32f7: add support for DNF i2c-digital-filter binding

On Fri, Feb 05, 2021 at 09:51:42AM +0100, Alain Volmat wrote: > Add the support for the i2c-digital-filter binding, allowing to enable > the digital filter via the device-tree and indicate its value in the DT. > > Signed-off-by: Alain Volmat Applied to for-next, thanks! signature.asc

Re: fuse: kernel BUG at mm/truncate.c:763!

On Thu, Mar 18, 2021 at 11:59:59AM +0100, Miklos Szeredi wrote: > [CC linux-mm] > > On Thu, Mar 18, 2021 at 10:25 AM Luis Henriques wrote: > > > > (I thought Vlastimil was already on CC...) > > > > On Mon, Mar 15, 2021 at 11:06:59AM +, Matthew Wilcox wrote: > > > On Mon, Mar 15, 2021 at

[PATCH] drm/meson: Fix few typo

s/initialy/initially/ s/desined/designed/ Signed-off-by: Bhaskar Chowdhury --- drivers/gpu/drm/meson/meson_venc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/meson/meson_venc.c b/drivers/gpu/drm/meson/meson_venc.c index 5e2236ec189f..3c55ed003359

Re: next: arm64: compiler_types.h:320:38: error: call to '__compiletime_assert_417' declared with attribute error: BUILD_BUG_ON failed: KMALLOC_MIN_SIZE > 16 | KMALLOC_SHIFT_HIGH < 10

This is a new test. +Oliver Glitta, who authored test_slub.c. On Thu, 18 Mar 2021 at 12:26, Naresh Kamboju wrote: > > While building arm64 kernel modules the following kernel warnings / > errors noticed on > linux next 20210318 tag the gcc version is 7.3.0. I will check latest &

Re: [PATCH RESEND] gcc-plugins: avoid errors with -std=gnu++11 on old gcc

On Thu, 18 Mar 2021 11:41:29 -, David Laight said: > That gcc bug just implies you need a space after "xxx". > That is easily fixable in the sources. It's not quite that simple. In file included from /usr/lib/gcc/x86_64-linux-gnu/5/plugin/include/tm.h:27, from

Re: [PATCH v4 1/5] mm,memory_hotplug: Allocate memmap from the added memory range

On 18.03.21 13:03, Oscar Salvador wrote: On Thu, Mar 18, 2021 at 12:24:16PM +0100, David Hildenbrand wrote: I don't follow. 2MB == 2MB. And if there would be difference then we would be in the problem I brought up: vmemmap code allocating too much via the altmap, which can be very bad because

Re: [PATCH 0/3] static_call() vs __exit fixes

On Thu, 18 Mar 2021 at 17:10, Peter Zijlstra wrote: > > Hi, > > After more poking a new set of patches to fix static_call() vs __exit > functions. These patches replace the patch I posted yesterday: > > https://lkml.kernel.org/r/yfh6br61b5gk8...@hirez.programming.kicks-ass.net > > Since I've

Re: fuse: kernel BUG at mm/truncate.c:763!

On Thu, Mar 18, 2021 at 11:55:43AM +, Matthew Wilcox wrote: > On Thu, Mar 18, 2021 at 11:29:28AM +, Luis Henriques wrote: > > On Thu, Mar 18, 2021 at 02:03:02PM +0300, Kirill A. Shutemov wrote: > > > On Thu, Mar 18, 2021 at 11:59:59AM +0100, Miklos Szeredi wrote: > > > > > [16247.536348]

RE: [RFC PATCH v1 0/4] vfio: Add IOPF support for VFIO passthrough

> From: Shenming Lu > Sent: Thursday, March 18, 2021 7:54 PM > > On 2021/3/18 17:07, Tian, Kevin wrote: > >> From: Shenming Lu > >> Sent: Thursday, March 18, 2021 3:53 PM > >> > >> On 2021/2/4 14:52, Tian, Kevin wrote:>>> In reality, many > > devices allow I/O faulting only in selective

Re: [PATCH] scsi: ses: Fix crash caused by kfree an invalid pointer

On 2020/11/29 7:27, James Bottomley wrote: ---8>8>8><8<8<8 From: James Bottomley Subject: [PATCH] scsi: ses: don't attach if enclosure has no components An enclosure with no components can't usefully be operated by the driver (since effectively it has nothing to manage), so report the

Re: [PATCH v23 22/28] x86/cet/shstk: User-mode shadow stack support

> Subject: Re: [PATCH v23 22/28] x86/cet/shstk: User-mode shadow stack support ^ Add On Tue, Mar 16, 2021 at 08:10:48AM -0700, Yu-cheng Yu wrote: > Introduce basic shadow stack

[PATCH net-next v1 1/3] net: phy: mscc: Applying LCPLL reset to VSC8584

Introduced LCPLL reset in commit d15e08d9fb82 ("net: phy: mscc: adding LCPLL reset to VSC8514"). Now applying this reset to the VSC8584 phy familiy. Fixes: a5afc1678044a ("net: phy: mscc: add support for VSC8584 PHYY.") Signed-off-by: Bjarni Jonasson --- drivers/net/phy/mscc/mscc_main.c | 6

[PATCH net-next v1 2/3] net: phy: mscc: improved serdes calibration applied to VSC8584

Introduced 'FOJI' serdes calibration in commit 85e97f0b984e ("net: phy: mscc: improved serdes calibration applied to VSC8514") Now including the VSC8584 family. Fixes: a5afc1678044a ("net: phy: mscc: add support for VSC8584 PHYY.") Signed-off-by: Bjarni Jonasson ---

[PATCH net-next v1 0/3] Fixes applied to VCS8584 family

Three different fixes applied to VSC8584 family: 1. LCPLL reset 2. Serdes calibration 3. Coma mode disabled The same fixes has already been applied to VSC8514 and most of the functionality can be reused for the VSC8584. Bjarni Jonasson (3): net: phy: mscc: Applying LCPLL reset to VSC8584

Re: [v5,0/2] Add check for max clock rate in mode_valid

Hi, Rex: For this series, applied to mediatek-drm-next [1], thanks. [1] https://git.kernel.org/pub/scm/linux/kernel/git/chunkuang.hu/linux.git/log/?h=mediatek-drm-next Regards, Chun-Kuang. Rex-BC Chen 於 2021年3月18日 週四 下午1:41寫道： > > Changes in v5: > fix build error > > Changes in v4: >

Re: [PATCH] drm/amdgpu/ttm: Fix memory leak userptr pages

On Thu, 18 Mar 2021 at 08:49, Christian König wrote: > > Am 17.03.21 um 17:08 schrieb Daniel Gomez: > > If userptr pages have been pinned but not bounded, > > they remain uncleared. > > > > Signed-off-by: Daniel Gomez > > Good catch, not sure if that can ever happen in practice but better save >

Re: [PATCH] virtio_net: replace if (cond) BUG() with BUG_ON()

On Wed, Mar 17, 2021 at 01:57:15PM +0800, Jiapeng Chong wrote: > Fix the following coccicheck warnings: > > ./drivers/net/virtio_net.c:1551:2-5: WARNING: Use BUG_ON instead of if > condition followed by BUG. > > Reported-by: Abaci Robot > Signed-off-by: Jiapeng Chong > --- >

Re: [PATCH] [RFC] arm64: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION

On Wed, Mar 17, 2021 at 5:18 PM Catalin Marinas wrote: > > On Wed, Mar 17, 2021 at 02:37:57PM +, Catalin Marinas wrote: > > On Thu, Feb 25, 2021 at 12:20:56PM +0100, Arnd Bergmann wrote: > > > diff --git a/arch/arm64/kernel/vmlinux.lds.S > > > b/arch/arm64/kernel/vmlinux.lds.S > > > index

RE: A problem of Intel IOMMU hardware ？

> From: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) > > > > > -Original Message- > > From: Tian, Kevin [mailto:kevin.t...@intel.com] > > Sent: Thursday, March 18, 2021 4:27 PM > > To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) > > ; Nadav Amit > > Cc:

Re: [PATCH RFC 1/2] x86/apic: Do not make an exception for PIC_CASCADE_IR when marking legacy irqs in irq_matrix

Thomas Gleixner writes: > On Wed, Mar 17 2021 at 22:40, Thomas Gleixner wrote: >> af174783b925 ("x86: I/O APIC: Never configure IRQ2") >> >> has a very nice explanation why. >> >> Back then the logic was quite different. All legacy PIC interrupts >> (0-15) were bound to the legacy vectors at

Re: [PATCH v5 5/5] mm,page_alloc: Drop unnecessary checks from pfn_range_valid_contig

On Thu 18-03-21 09:44:19, Oscar Salvador wrote: > On Wed, Mar 17, 2021 at 04:03:06PM +0100, Michal Hocko wrote: > > > alloc_contig_pages() vs. alloc_contig_range(). The patches are active for > > > virtio-mem and CMA AFAIKS. > > > > yeah, I meant to say "are not actually fully active". > > We

Re: systemd-rfkill regression on 5.11 and later kernels

Hi Takashi, Oh yay :-( > we've received a bug report about rfkill change that was introduced in > 5.11. While the systemd-rfkill expects the same size of both read and > write, the kernel rfkill write cuts off to the old 8 bytes while read > gives 9 bytes, hence it leads the error: >   

[PATCH] ARM: boot: dts: Fix a typo

s/conlicts/conflicts/ Signed-off-by: Bhaskar Chowdhury --- arch/arm/boot/dts/sama5d3.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/sama5d3.dtsi b/arch/arm/boot/dts/sama5d3.dtsi index 7c979652f330..d1841bffe3c5 100644 ---

Re: [PATCH v5 4/5] mm: Make alloc_contig_range handle in-use hugetlb pages

On Thu, Mar 18, 2021 at 10:29:57AM +0100, Michal Hocko wrote: > On Thu 18-03-21 09:54:01, Oscar Salvador wrote: > [...] > > @@ -2287,10 +2288,12 @@ static int alloc_and_dissolve_huge_page(struct > > hstate *h, struct page *old_page) > > goto unlock; > > } else if

[PATCH v25 10/13] Documentation: Add documents for DAMON

From: SeongJae Park This commit adds documents for DAMON under `Documentation/admin-guide/mm/damon/` and `Documentation/vm/damon/`. Signed-off-by: SeongJae Park --- Documentation/admin-guide/mm/damon/guide.rst | 159 + Documentation/admin-guide/mm/damon/index.rst | 15 ++

[PATCH v25 12/13] mm/damon: Add user space selftests

From: SeongJae Park This commit adds a simple user space tests for DAMON. The tests are using kselftest framework. Signed-off-by: SeongJae Park --- tools/testing/selftests/damon/Makefile| 7 + .../selftests/damon/_chk_dependency.sh| 28 +++

[PATCH v25 11/13] mm/damon: Add kunit tests

From: SeongJae Park This commit adds kunit based unit tests for the core and the virtual address spaces monitoring primitives of DAMON. Signed-off-by: SeongJae Park Reviewed-by: Brendan Higgins --- mm/damon/Kconfig | 36 + mm/damon/core-test.h | 253

[PATCH v25 08/13] mm/damon/dbgfs: Export kdamond pid to the user space

From: SeongJae Park For CPU usage accounting, knowing pid of the monitoring thread could be helpful. For example, users could use cpuaccount cgroups with the pid. This commit therefore exports the pid of currently running monitoring thread to the user space via 'kdamond_pid' file in the

[PATCH v25 13/13] MAINTAINERS: Update for DAMON

From: SeongJae Park This commit updates MAINTAINERS file for DAMON related files. Signed-off-by: SeongJae Park --- MAINTAINERS | 12 1 file changed, 12 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index b2baeb5e4a68..4665a5699cf6 100644 --- a/MAINTAINERS +++

[PATCH v25 07/13] mm/damon: Implement a debugfs-based user space interface

From: SeongJae Park DAMON is designed to be used by kernel space code such as the memory management subsystems, and therefore it provides only kernel space API. That said, letting the user space control DAMON could provide some benefits to them. For example, it will allow user space to analyze

[PATCH v25 09/13] mm/damon/dbgfs: Support multiple contexts

From: SeongJae Park In some use cases, users would want to run multiple monitoring context. For example, if a user wants a high precision monitoring and dedicating multiple CPUs for the job is ok, because DAMON creates one monitoring thread per one context, the user can split the monitoring

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

On 3/18/21 10:21 AM, Fabrice Gasnier wrote: > On 3/14/21 10:08 AM, William Breathitt Gray wrote: >> 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:

Re: [PATCH V1] arm64: dts: imx8mp: fix FEC can't work when attached to generic phy driver

On Thu, Mar 04, 2021 at 07:40:13PM +0800, Joakim Zhang wrote: > Some users report that FEC can't work on i.MX8MP EVK board, it brings > inconvenience. The root cause should be FEC controller attached to > generic phy driver, as Realtek phy driver is built as module in the > defconfig file

Re: [PATCH 4/5] ARM: dts: stm32: enable the analog filter for all I2C nodes in stm32mp151

On Fri, Feb 05, 2021 at 09:51:43AM +0100, Alain Volmat wrote: > Enable the analog filter for all I2C nodes of the stm32mp151. > > Signed-off-by: Alain Volmat I usually don't take DTS patches, but they can go in now via arm-soc as I applied the patches to the driver. signature.asc

Re: [RFC] scripts: kernel-doc: avoid warnings due to initial commented lines in file

On Mon, Mar 15, 2021 at 8:25 PM Jonathan Corbet wrote: > > Aditya writes: > > >> The opening comment mark /** is used for kernel-doc comments [1] > >> > >> [1] > >> https://www.kernel.org/doc/html/latest/doc-guide/kernel-doc.html#how-to-format-kernel-doc-comments > >> > > > > Hi Markus! > >

[PATCH v4 5/5] mm: memcontrol: move PageMemcgKmem to the scope of CONFIG_MEMCG_KMEM

The page only can be marked as kmem when CONFIG_MEMCG_KMEM is enabled. So move PageMemcgKmem() to the scope of the CONFIG_MEMCG_KMEM. As a bonus, on !CONFIG_MEMCG_KMEM build some code can be compiled out. Signed-off-by: Muchun Song Acked-by: Roman Gushchin Reviewed-by: Shakeel Butt Acked-by:

Re: systemd-rfkill regression on 5.11 and later kernels

On Thu, 2021-03-18 at 12:11 +0100, Takashi Iwai wrote: > > That said, we can "fix" this like this, and hope we'll not get this > > again? And if we do get it again ... well, we keep renaming the structs > > and add "struct rfkill_event_v3" next time? > > Yeah, that's a dilemma. An oft-seen trick

Re: [PATCH v23 16/28] mm: Fixup places that call pte_mkwrite() directly

On Thu, Mar 18, 2021 at 10:47:40AM +0100, Borislav Petkov wrote: > As with the previous one, I guess this one needs a mm person ACK. I > mean, it is pretty obvious but still... And that needs to happen for all mm patches in here. -- Regards/Gruss, Boris.

next: arm64: compiler_types.h:320:38: error: call to '__compiletime_assert_417' declared with attribute error: BUILD_BUG_ON failed: KMALLOC_MIN_SIZE > 16 | KMALLOC_SHIFT_HIGH < 10

While building arm64 kernel modules the following kernel warnings / errors noticed on linux next 20210318 tag the gcc version is 7.3.0. I will check latest gcc version builds and keep you updated. In file included from :0:0: In function 'resiliency_test', inlined from 'test_slub_init

Re: [PATCH v2 2/4] leds: simatic-ipc-leds: add new driver for Siemens Industial PCs

On 15.03.21 12:19, Pavel Machek wrote: But I still don't like the naming. simantic-ipc: prefix is useless. Having 6 status leds is not good, either. Do we have some standard naming policy those kinds of LEDs ? In this case, they seem to be assigned to certain specific functions (by physical

[PATCH net-next] /net/hsr: fix misspellings using codespell tool

From: Xiong Zhenwu A typo is found out by codespell tool in 111th line of hsr_debugfs.c: $ codespell ./net/hsr/ net/hsr/hsr_debugfs.c:111: Debufs ==> Debugfs Fix typos found by codespell. Signed-off-by: Xiong Zhenwu --- net/hsr/hsr_debugfs.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH v3 0/6] Some cleanups for huge_memory

Hi all, This series contains cleanups to rework some function logics to make it more readable, use helper function and so on. More details can be found in the respective changelogs. Thanks! v2->v3: use ALIGN/ALIGN_DOWN too against HPAGE_PMD_SIZE per Peter. v1->v2: rename

[PATCH v3 4/6] mm/huge_memory.c: remove redundant PageCompound() check

The !PageCompound() check limits the page must be head or tail while !PageHead() further limits it to page head only. So !PageHead() check is equivalent here. Signed-off-by: Miaohe Lin --- mm/huge_memory.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/huge_memory.c

[PATCH v3 6/6] mm/huge_memory.c: use helper function migration_entry_to_page()

It's more recommended to use helper function migration_entry_to_page() to get the page via migration entry. We can also enjoy the PageLocked() check there. Signed-off-by: Miaohe Lin --- mm/huge_memory.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mm/huge_memory.c

[PATCH v3 3/6] mm/huge_memory.c: rework the function do_huge_pmd_numa_page() slightly

The current code that checks if migrating misplaced transhuge page is needed is pretty hard to follow. Rework it and add a comment to make its logic more clear and improve readability. Signed-off-by: Miaohe Lin --- mm/huge_memory.c | 11 +-- 1 file changed, 5 insertions(+), 6

[PATCH v3 1/6] mm/huge_memory.c: rework the function vma_adjust_trans_huge()

The current implementation of vma_adjust_trans_huge() contains some duplicated codes. Add helper function to get rid of these codes to make it more succinct. Signed-off-by: Miaohe Lin --- mm/huge_memory.c | 44 +++- 1 file changed, 19 insertions(+), 25

[PATCH v3 2/6] mm/huge_memory.c: make get_huge_zero_page() return bool

It's guaranteed that huge_zero_page will not be NULL if huge_zero_refcount is increased successfully. When READ_ONCE(huge_zero_page) is returned, there must be a huge_zero_page and it can be replaced with returning 'true' when we do not care about the value of huge_zero_page. We can thus make it

[PATCH v3 5/6] mm/huge_memory.c: remove unused macro TRANSPARENT_HUGEPAGE_DEBUG_COW_FLAG

The commit 4958e4d86ecb ("mm: thp: remove debug_cow switch") forgot to remove TRANSPARENT_HUGEPAGE_DEBUG_COW_FLAG macro. Remove it here. Signed-off-by: Miaohe Lin --- include/linux/huge_mm.h | 3 --- 1 file changed, 3 deletions(-) diff --git a/include/linux/huge_mm.h b/include/linux/huge_mm.h

Re: [PATCH v3] ASoC: Intel: sof_rt5682: Add ALC1015Q-VB speaker amp support

On 3/17/21 8:21 PM, Jack Yu wrote: This patch adds jsl_rt5682_rt1015p which supports the RT5682 headset codec and ALC1015Q-VB speaker amplifier combination on JasperLake platform. This driver also supports ALC1015Q-CG if running in auto-mode. Following table shows the audio interface support

Re: [PATCH 2/3] mm/slub: Add Support for free path information of an object.

On 3/16/21 11:37 AM, Maninder Singh wrote: > Adding support for inforamtion of free path along with allocation > path of an object: > > slab kmalloc-64 start c8ab0140 data offset 64 pointer offset 0 size 64 > allocated at meminfo_proc_show+0x40/0x4fc > [ 20.192078]

[RFC PATCH] ata: add lun validity check on ata_sas_queuecmd

Hi all, After executing rescan-scsi-bus.sh -r -m, the system adds 255 more disks. The reason is as follows: 1. Execute the rescan-scsi-bus.sh script to scan all targets. 2. The REPORT_LUNS failed due to some errors on the device of sdb(LUN0). 3. Do a sequential scan on the target which sdb

Re: [PATCH 1/2] devtmpfs: fix placement of complete() call

On Thu, Mar 18, 2021 at 01:44:04PM +0100, Rasmus Villemoes wrote: > On 12/03/2021 11.30, Rasmus Villemoes wrote: > > Calling complete() from within the __init function is wrong - > > theoretically, the init process could proceed all the way to freeing > > the init mem before the devtmpfsd thread

Re: [PATCH v1 1/5] mfd: intel_quark_i2c_gpio: revert "Constify static struct resources"

On Tue, Mar 02, 2021 at 09:59:03PM +0100, Rikard Falkeborn wrote: > On Tue, Mar 02, 2021 at 03:56:16PM +0200, Andy Shevchenko wrote: > > The structures are used as place holders, so they are modified at run-time. > > Obviously they may not be constants. > > > > BUG: unable to handle page fault

[PATCH] drm/radeon/ttm: Fix memory leak userptr pages

If userptr pages have been pinned but not bounded, they remain uncleared. Signed-off-by: Daniel Gomez --- drivers/gpu/drm/radeon/radeon_ttm.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c b/drivers/gpu/drm/radeon/radeon_ttm.c index

[PATCH] arm64: dts: ls1028a: fix optee node

Don't enable the optee node in the SoC include. It is an optional component and actually, if enabled, breaks boards which doesn't have it. This reverts commit 48787485f8de ("arm64: dts: ls1028a: enable optee node") and enables the node per board, assuming the intend of the original author was to

[PATCH] usb: cdnsp: Fixes issue with dequeuing requests after disabling endpoint

From: Pawel Laszczak Patch fixes the bug: BUG: kernel NULL pointer dereference, address: 0050 PGD 0 P4D 0 Oops: 0002 [#1] SMP PTI CPU: 0 PID: 4137 Comm: uvc-gadget Tainted: G OE 5.10.0-next-20201214+ #3 Hardware name: ASUS All Series/Q87T, BIOS 0908 07/22/2014 RIP:

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