Re: [PATCH v3 1/3] fbdev: Fix recursive dependencies wrt BACKLIGHT_CLASS_DEVICE

On 12/16/24 08:42, Thomas Zimmermann wrote: Do not select BACKLIGHT_CLASS_DEVICE from FB_BACKLIGHT. The latter only controls backlight support within fbdev core code and data structures. Make fbdev drivers depend on BACKLIGHT_CLASS_DEVICE and let users select it explicitly. Fixes warnings about

Re: [PATCH v2 1/3] fbdev: Fix recursive dependencies wrt BACKLIGHT_CLASS_DEVICE

On 12/12/24 11:04, Thomas Zimmermann wrote: Do not select BACKLIGHT_CLASS_DEVICE from FB_BACKLIGHT. The latter only controls backlight support within fbdev core code and data structures. Make fbdev drivers depend on BACKLIGHT_CLASS_DEVICE and let users select it explicitly. Fixes warnings about

Re: [PATCH v6] mm/memblock: Add memblock_alloc_or_panic interface

Xi Ruoyao wrote on Sunday, 22 December 2024 13:51: > > On Sun, 2024-12-22 at 13:43 +0800, Guo Weikang wrote: > > Before SLUB initialization, various subsystems used memblock_alloc to > > allocate memory. In most cases, when memory allocation fails, an immediate > > panic is required. To simplify t

Re: [PATCH v6] mm/memblock: Add memblock_alloc_or_panic interface

On Sun, 2024-12-22 at 13:43 +0800, Guo Weikang wrote: > Before SLUB initialization, various subsystems used memblock_alloc to > allocate memory. In most cases, when memory allocation fails, an immediate > panic is required. To simplify this behavior and reduce repetitive checks, > introduce `memblo

[PATCH v6] mm/memblock: Add memblock_alloc_or_panic interface

Before SLUB initialization, various subsystems used memblock_alloc to allocate memory. In most cases, when memory allocation fails, an immediate panic is required. To simplify this behavior and reduce repetitive checks, introduce `memblock_alloc_or_panic`. This function ensures that memory allocati

[PATCH v5] mm/memblock: Add memblock_alloc_or_panic interface

Before SLUB initialization, various subsystems used memblock_alloc to allocate memory. In most cases, when memory allocation fails, an immediate panic is required. To simplify this behavior and reduce repetitive checks, introduce `memblock_alloc_or_panic`. This function ensures that memory allocati

Re: [PATCH v2 4/5] powerpc: kvm: drop 32-bit book3s

On Dec 21, 2024, at 3:42 PM, Arnd Bergmann wrote: > > From: Arnd Bergmann > > Support for KVM on 32-bit Book III-s implementations was added in 2010 > and supports PowerMac, CHRP, and embedded platforms using the Freescale G4 > (mpc74xx), e300 (mpc83xx) and e600 (mpc86xx) CPUs from 2003 to 2009

[PATCH v4] mm/memblock: Add memblock_alloc_or_panic interface

Before SLUB initialization, various subsystems used memblock_alloc to allocate memory. In most cases, when memory allocation fails, an immediate panic is required. To simplify this behavior and reduce repetitive checks, introduce `memblock_alloc_or_panic`. This function ensures that memory allocati

Re: [PATCH v2] mm/memblock: Add memblock_alloc_or_panic interface

Geert Uytterhoeven wrote on Saturday, 21 December 2024 at 22:10 > > Hi Guo, > > On Sat, Dec 21, 2024 at 11:43 AM Guo Weikang > wrote: > > Before SLUB initialization, various subsystems used memblock_alloc to > > allocate memory. In most cases, when memory allocation fails, an immediate > > panic

[PATCH v2 5/5] x86: kvm drop 32-bit host support

From: Arnd Bergmann There are very few 32-bit machines that support KVM, the main exceptions are the "Yonah" Generation Xeon-LV and Core Duo from 2006 and the Atom Z5xx "Silverthorne" from 2008 that were all released just before their 64-bit counterparts. The main usecase for KVM in x86-32 kerne

[PATCH v2 4/5] powerpc: kvm: drop 32-bit book3s

From: Arnd Bergmann Support for KVM on 32-bit Book III-s implementations was added in 2010 and supports PowerMac, CHRP, and embedded platforms using the Freescale G4 (mpc74xx), e300 (mpc83xx) and e600 (mpc86xx) CPUs from 2003 to 2009. Earlier 603/604/750 machines might work but would be even mor

[PATCH v2 3/5] powerpc: kvm: drop 32-bit booke

From: Arnd Bergmann KVM on PowerPC BookE was introduced in 2008 and supported IBM 44x, Freescale e500v2 (32-bit mpc85xx, QuorIQ P1/P2), e500mc (32bit QorIQ P2/P3/P4), e5500 (64-bit QorIQ P5/T1) and e6500 (64-bit QorIQ T2/T4). Support for 44x was dropped in 2014 as it was seeing very little use,

[PATCH v2 2/5] riscv: kvm: drop 32-bit host support

From: Arnd Bergmann KVM support on RISC-V includes both 32-bit and 64-bit host mode, but in practice, all RISC-V SoCs that may use this are 64-bit: As of linux-6.13, there is no mainline Linux support for any specific 32-bit SoC in arch/riscv/, although the generic qemu model should work. The a

[PATCH v2 1/5] mips: kvm: drop support for 32-bit hosts

From: Arnd Bergmann KVM support on MIPS was added in 2012 with both 32-bit and 64-bit mode included, but there is only one CPU implementation that actually includes the required VZ support with the Warrior P5600 core. Support for the one SoC using this core did not fully get merged into mainline,

[PATCH v2 0/5] KVM: drop 32-bit host support on all architectures

From: Arnd Bergmann I've updated my RFC patches based on the feedback, changing mainly the powerpc code. I submitted a patch to remove KVM support for x86-32 hosts earlier this month, but there were still concerns that this might be useful for testing 32-bit host in general, as that remains sup

[PATCH v2 2/9] cxl: Constify 'struct bin_attribute'

The sysfs core now allows instances of 'struct bin_attribute' to be moved into read-only memory. Make use of that to protect them against accidental or malicious modifications. Signed-off-by: Thomas Weißschuh Acked-by: Andrew Donnellan --- drivers/misc/cxl/sysfs.c | 8 1 file changed,

[PATCH v2 1/9] ocxl: Constify 'struct bin_attribute'

The sysfs core now allows instances of 'struct bin_attribute' to be moved into read-only memory. Make use of that to protect them against accidental or malicious modifications. Signed-off-by: Thomas Weißschuh Acked-by: Andrew Donnellan --- drivers/misc/ocxl/sysfs.c | 4 ++-- 1 file changed, 2 i

[PATCH v2 9/9] misc: ds1682: Constify 'struct bin_attribute'

The sysfs core now allows instances of 'struct bin_attribute' to be moved into read-only memory. Make use of that to protect them against accidental or malicious modifications. Signed-off-by: Thomas Weißschuh --- drivers/misc/ds1682.c | 8 1 file changed, 4 insertions(+), 4 deletions(-)

[PATCH v2 5/9] misc: c2port: Constify 'struct bin_attribute'

The sysfs core now allows instances of 'struct bin_attribute' to be moved into read-only memory. Make use of that to protect them against accidental or malicious modifications. Signed-off-by: Thomas Weißschuh --- drivers/misc/c2port/core.c | 12 ++-- 1 file changed, 6 insertions(+), 6 de

[PATCH v2 8/9] misc: eeprom/max6875: Constify 'struct bin_attribute'

The sysfs core now allows instances of 'struct bin_attribute' to be moved into read-only memory. Make use of that to protect them against accidental or malicious modifications. Signed-off-by: Thomas Weißschuh --- drivers/misc/eeprom/max6875.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletion

[PATCH v2 6/9] misc: pch_phub: Constify 'struct bin_attribute'

The sysfs core now allows instances of 'struct bin_attribute' to be moved into read-only memory. Make use of that to protect them against accidental or malicious modifications. Signed-off-by: Thomas Weißschuh --- drivers/misc/pch_phub.c | 8 1 file changed, 4 insertions(+), 4 deletions(

[PATCH v2 7/9] misc: eeprom/idt_89hpesx: Constify 'struct bin_attribute'

The sysfs core now allows instances of 'struct bin_attribute' to be moved into read-only memory. Make use of that to protect them against accidental or malicious modifications. Signed-off-by: Thomas Weißschuh --- drivers/misc/eeprom/idt_89hpesx.c | 6 +++--- 1 file changed, 3 insertions(+), 3 de

[PATCH v2 3/9] misc: sram: constify 'struct bin_attribute'

The sysfs core now allows instances of 'struct bin_attribute' to be moved into read-only memory. Make use of that to protect them against accidental or malicious modifications. Signed-off-by: Thomas Weißschuh --- drivers/misc/sram.c | 8 1 file changed, 4 insertions(+), 4 deletions(-)

[PATCH v2 0/9] misc: constify 'struct bin_attribute'

The sysfs core now allows instances of 'struct bin_attribute' to be moved into read-only memory. Make use of that to protect them against accidental or malicious modifications. Signed-off-by: Thomas Weißschuh --- Changes in v2: - Fix NULL deref in c2port_bin_attr_size() (0day CI) - Add Ack for cx

[PATCH v2 4/9] misc: c2port: Calculate bin_attribute size through group callback

Modifying the size of the global bin_attribute instance can be racy. Instead use the new .bin_size callback to do so safely. For this to work move the initialization of c2dev->ops before the call to device_create() as the size callback will need access to it. Signed-off-by: Thomas Weißschuh ---

Re: [PATCH v2] mm/memblock: Add memblock_alloc_or_panic interface

Hi Guo, On Sat, Dec 21, 2024 at 11:43 AM Guo Weikang wrote: > Before SLUB initialization, various subsystems used memblock_alloc to > allocate memory. In most cases, when memory allocation fails, an immediate > panic is required. To simplify this behavior and reduce repetitive checks, > introduce

[PATCH v3] mm/memblock: Add memblock_alloc_or_panic interface

Before SLUB initialization, various subsystems used memblock_alloc to allocate memory. In most cases, when memory allocation fails, an immediate panic is required. To simplify this behavior and reduce repetitive checks, introduce `memblock_alloc_or_panic`. This function ensures that memory allocati

[PATCH v2] mm/memblock: Add memblock_alloc_or_panic interface

Before SLUB initialization, various subsystems used memblock_alloc to allocate memory. In most cases, when memory allocation fails, an immediate panic is required. To simplify this behavior and reduce repetitive checks, introduce `memblock_alloc_or_panic`. This function ensures that memory allocati

Re: [PATCH] mm/memblock: Add memblock_alloc_or_panic interface

Andrew Morton wrote on Saturday, 21 December 2024 07:06: > > On Fri, 20 Dec 2024 17:26:38 +0800 Guo Weikang > wrote: > > > Before SLUB initialization, various subsystems used memblock_alloc to > > allocate memory. In most cases, when memory allocation fails, an immediate > > panic is required. T

[PATCH 20/29] crypto: nx - use the new scatterwalk functions

From: Eric Biggers - In nx_walk_and_build(), use scatterwalk_start_at_pos() instead of a more complex way to achieve the same result. - Also in nx_walk_and_build(), use the new functions scatterwalk_next() which consolidates scatterwalk_clamp() and scatterwalk_map(), and use scatterwalk_do

[PATCH 10/29] crypto: powerpc/p10-aes-gcm - simplify handling of linear associated data

From: Eric Biggers p10_aes_gcm_crypt() is abusing the scatter_walk API to get the virtual address for the first source scatterlist element. But this code is only built for PPC64 which is a !HIGHMEM platform, and it can read past a page boundary from the address returned by scatterwalk_map() whic