[PATCH 2/9] crypto: chacha - centralize the skcipher wrappers for arch code

2025-04-05 Thread Eric Biggers
From: Eric Biggers Following the example of the crc32 and crc32c code, make the crypto subsystem register both generic and architecture-optimized chacha20, xchacha20, and xchacha12 skcipher algorithms, all implemented on top of the appropriate library functions. This eliminates the need for ever

[PATCH 8/9] crypto: x86/chacha - remove the skcipher algorithms

2025-04-05 Thread Eric Biggers
From: Eric Biggers Since crypto/chacha.c now registers chacha20-$(ARCH), xchacha20-$(ARCH), and xchacha12-$(ARCH) skcipher algorithms that use the architecture's ChaCha and HChaCha library functions, individual architectures no longer need to do the same. Therefore, remove the redundant skcipher

[PATCH 9/9] crypto: chacha - remove

2025-04-05 Thread Eric Biggers
From: Eric Biggers is now included only by crypto/chacha.c, so fold it into there. Signed-off-by: Eric Biggers --- crypto/chacha.c | 35 +- include/crypto/internal/chacha.h | 43 2 files changed, 34 insertions(+), 44 de

[PATCH 4/9] crypto: arm64/chacha - remove the skcipher algorithms

2025-04-05 Thread Eric Biggers
From: Eric Biggers Since crypto/chacha.c now registers chacha20-$(ARCH), xchacha20-$(ARCH), and xchacha12-$(ARCH) skcipher algorithms that use the architecture's ChaCha and HChaCha library functions, individual architectures no longer need to do the same. Therefore, remove the redundant skcipher

[PATCH 1/9] crypto: riscv/chacha - implement library instead of skcipher

2025-04-05 Thread Eric Biggers
From: Eric Biggers Currently the RISC-V optimized ChaCha20 is only wired up to the crypto_skcipher API, which makes it unavailable to users of the library API. The crypto_skcipher API for ChaCha20 is going to change to be implemented on top of the library API, so the library API needs to be supp

[PATCH 5/9] crypto: mips/chacha - remove the skcipher algorithms

2025-04-05 Thread Eric Biggers
From: Eric Biggers Since crypto/chacha.c now registers chacha20-$(ARCH), xchacha20-$(ARCH), and xchacha12-$(ARCH) skcipher algorithms that use the architecture's ChaCha and HChaCha library functions, individual architectures no longer need to do the same. Therefore, remove the redundant skcipher

[PATCH 7/9] crypto: s390/chacha - remove the skcipher algorithms

2025-04-05 Thread Eric Biggers
From: Eric Biggers Since crypto/chacha.c now registers chacha20-$(ARCH), xchacha20-$(ARCH), and xchacha12-$(ARCH) skcipher algorithms that use the architecture's ChaCha and HChaCha library functions, individual architectures no longer need to do the same. Therefore, remove the redundant skcipher

[PATCH 6/9] crypto: powerpc/chacha - remove the skcipher algorithms

2025-04-05 Thread Eric Biggers
From: Eric Biggers Since crypto/chacha.c now registers chacha20-$(ARCH), xchacha20-$(ARCH), and xchacha12-$(ARCH) skcipher algorithms that use the architecture's ChaCha and HChaCha library functions, individual architectures no longer need to do the same. Therefore, remove the redundant skcipher

[PATCH 3/9] crypto: arm/chacha - remove the redundant skcipher algorithms

2025-04-05 Thread Eric Biggers
From: Eric Biggers Since crypto/chacha.c now registers chacha20-$(ARCH), xchacha20-$(ARCH), and xchacha12-$(ARCH) skcipher algorithms that use the architecture's ChaCha and HChaCha library functions, individual architectures no longer need to do the same. Therefore, remove the redundant skcipher

[PATCH 0/9] Remove per-architecture ChaCha skcipher glue code

2025-04-05 Thread Eric Biggers
Currently each architecture exposes ChaCha not only through the library API, but also through the crypto_skcipher API. That requires each architecture to implement essentially the same skcipher glue code. Following the example of what's been done for crc32 and crc32c, eliminate this redundancy by

[PATCH 1/3] pci/hotplug/pnv_php: Properly clean up allocated IRQs on unplug

2025-04-05 Thread Shawn Anastasio
In cases where the root of a nested PCIe bridge configuration is unplugged, the pnv_php driver would leak the allocated IRQ resources for the child bridges' hotplug event notifications, resulting in a panic. Fix this by walking all child buses and deallocating all it's IRQ resources before calling

Re: [PATCH v4 10/14] s390: Add support for suppressing warning backtraces

2025-04-05 Thread Heiko Carstens
On Fri, Mar 21, 2025 at 10:05:42PM +0100, Alessandro Carminati wrote: > > > +#ifdef CONFIG_KUNIT_SUPPRESS_BACKTRACE > > > +# define HAVE_BUG_FUNCTION > > > +# define __BUG_FUNC_PTR " .long %0-.\n" > > > +# define __BUG_FUNC __func__ > > > > gcc 7.5.0 on s390 barfs; it doesn't like the

Re: [PATCH 1/2] mm/ptdump: Split note_page() into level specific callbacks

2025-04-05 Thread Alexander Gordeev
On Mon, Mar 17, 2025 at 11:48:17AM +0530, Anshuman Khandual wrote: Hi Anshuman, ... > --- a/include/linux/ptdump.h > +++ b/include/linux/ptdump.h > @@ -11,9 +11,12 @@ struct ptdump_range { > }; > > struct ptdump_state { > - /* level is 0:PGD to 4:PTE, or -1 if unknown */ > - void (*no

[PATCH V2 5/9] powerpc/pseries/htmdump: Add htm info support to htmdump module

2025-04-05 Thread Athira Rajeev
Support dumping system processor configuration from Hardware Trace Macro (HTM) function via debugfs interface. Under debugfs folder "/sys/kernel/debug/powerpc/htmdump", add file "htminfo”. The interface allows only read of this file which will present the content of HTM buffer from the hcall. The

Re: [PATCH v9 0/7] Add character devices for indices, platform-dump

2025-04-05 Thread Sathvika Vasireddy
On 3/15/25 2:57 PM, Haren Myneni wrote: Several APIs such as rtas_get_indices(), rtas_get_dynamic_sensor(), rtas_set_dynamic_indicator(), rtas_platform_dump() and rtas_physical_attestation() provided by librtas library are implemented in user space using rtas syscall in combination with writabl

Re: Using Restricted DMA for virtio-pci

2025-04-05 Thread David Woodhouse
On Sun, 2025-03-30 at 09:42 -0400, Michael S. Tsirkin wrote: > On Fri, Mar 28, 2025 at 05:40:41PM +, David Woodhouse wrote: > > On Fri, 2025-03-21 at 18:42 +, David Woodhouse wrote: > > > > > > > > I don't mind as such (though I don't understand completely), but since > > > > this is chang

Re: Please add powerpc topic/cxl branch to linux-next

2025-04-05 Thread Stephen Rothwell
Hi Michael, On Thu, 03 Apr 2025 13:32:43 +1100 Michael Ellerman wrote: > > This branch has been merged intoo mainline, you can drop it from > linux-next. Thanks. Done. -- Cheers, Stephen Rothwell pgpYE1UKqL5ho.pgp Description: OpenPGP digital signature

[PATCH 3/4] PCI: Add link down handling for host bridges

2025-04-05 Thread Manivannan Sadhasivam via B4 Relay
From: Manivannan Sadhasivam The PCI link, when down, needs to be recovered to bring it back. But that cannot be done in a generic way as link recovery procedure is specific to host bridges. So add a new API pci_host_handle_link_down() that could be called by the host bridge drivers when the link

[PATCH v2 0/3] MAINTAINERS: updates for the fsl-mc bus entry

2025-04-05 Thread Ioana Ciornei
This patch set updates the fsl-mc bus driver MAINTAINERS entry. Since there are small separate changes, I put each of them into a separate patch. Changes in v2: - 1/3: also removed Stuart from the MAINTAINERS file https://lore.kernel.org/linuxppc-dev/caeac7tyqe76z4pyminhvmjr6gz66rprv4pxm-u9vpgjjvn

Re: [PATCH v13 2/5] arm64: add support for ARCH_HAS_COPY_MC

2025-04-05 Thread Tong Tiangen
在 2025/3/29 1:06, Yeoreum Yun 写道: Hi, 在 2025/2/13 0:21, Catalin Marinas 写道: (catching up with old threads) On Mon, Dec 09, 2024 at 10:42:54AM +0800, Tong Tiangen wrote: For the arm64 kernel, when it processes hardware memory errors for synchronize notifications(do_sea()), if the errors

Re: [PATCH] bus: fsl-mc: Remove deadcode

2025-04-05 Thread Christophe Leroy
Ioana, Le 15/11/2024 à 16:20, li...@treblig.org a écrit : [Vous ne recevez pas souvent de courriers de li...@treblig.org. Découvrez pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ] From: "Dr. David Alan Gilbert" fsl_mc_allocator_driver_exit() was added explicitly

Re: [PATCH v4 00/14] Add support for suppressing warning backtraces

2025-04-05 Thread Shuah Khan
On 3/13/25 16:05, Andrew Morton wrote: On Thu, 13 Mar 2025 11:31:12 -0700 Guenter Roeck wrote: On Thu, Mar 13, 2025 at 06:24:25PM +0100, Maxime Ripard wrote: Yeah, as with my prior review, I'm a fan of this. It makes a bunch of my very noisy tests much easier to deal with. And for the reco

Re: [PATCH v5 6/6] powerpc/kvm-hv-pmu: Add perf-events for Hostwide counters

2025-04-05 Thread Athira Rajeev
> On 17 Mar 2025, at 3:38 PM, Vaibhav Jain wrote: > > Update 'kvm-hv-pmu.c' to add five new perf-events mapped to the five > Hostwide counters. Since these newly introduced perf events are at system > wide scope and can be read from any L1-Lpar CPU, 'kvmppc_pmu' scope and > capabilities are up

Re: [PATCH v4 07/14] arm64: Add support for suppressing warning backtraces

2025-04-05 Thread Guenter Roeck
On 3/18/25 08:59, Will Deacon wrote: On Thu, Mar 13, 2025 at 05:40:59PM +0100, Alessandro Carminati wrote: On Thu, Mar 13, 2025 at 1:25 PM Will Deacon wrote: On Thu, Mar 13, 2025 at 11:43:22AM +, Alessandro Carminati wrote: diff --git a/arch/arm64/include/asm/bug.h b/arch/arm64/include/a

Re: Using Restricted DMA for virtio-pci

2025-04-05 Thread Michael S. Tsirkin
On Fri, Mar 21, 2025 at 06:42:20PM +, David Woodhouse wrote: > On Fri, 2025-03-21 at 14:32 -0400, Michael S. Tsirkin wrote: > > On Fri, Mar 21, 2025 at 03:38:10PM +, David Woodhouse wrote: > > > On Tue, 2021-02-09 at 14:21 +0800, Claire Chang wrote: > > > > This series implements mitigation

[PATCH v2 39/57] irqdomain: ppc: Switch irq_domain_add_nomap() to use fwnode

2025-04-05 Thread Jiri Slaby (SUSE)
All irq_domain_add_*() functions are going away. PowerPC is the only user of irq_domain_add_nomap() and there is no irq_domain_create_nomap() complement. Therefore, to align with the rest of kernel, rename irq_domain_add_nomap() to irq_domain_create_nomap() and accept fwnode_handle instead of devi

Re: [PATCH v4 06/14] x86: Add support for suppressing warning backtraces

2025-04-05 Thread Peter Zijlstra
On Tue, Apr 01, 2025 at 10:53:46AM -0700, Guenter Roeck wrote: > > > #define _BUG_FLAGS(ins, flags, extra) > > > \ > > > do { > > > \ > > > asm_inline volatile("1:\t" ins "\n"

Re: [PATCH v4 1/3] lsm: introduce new hooks for setting/getting inode fsxattr

2025-04-05 Thread Paul Moore
On Mar 21, 2025 Andrey Albershteyn wrote: > > Introduce new hooks for setting and getting filesystem extended > attributes on inode (FS_IOC_FSGETXATTR). > > Cc: seli...@vger.kernel.org > Cc: Paul Moore > > Signed-off-by: Andrey Albershteyn > --- > fs/ioctl.c| 7 ++- >

Re: [PATCH 00/11] Always call constructor for kernel page tables

2025-04-05 Thread Kevin Brodsky
On 17/03/2025 16:30, Ryan Roberts wrote: > On 17/03/2025 14:16, Kevin Brodsky wrote: >> The complications in those special pgtable allocators beg the question: >> does it really make sense to treat efi_mm and init_mm differently in >> e.g. apply_to_pte_range()? Maybe what we really need is a way to

Re: [PATCH 0/9] Add support for configure and control of Hardware Trace Macro(HTM)

2025-04-05 Thread Athira Rajeev
> On 20 Mar 2025, at 6:43 PM, Venkat Rao Bagalkote > wrote: > > On 14/03/25 7:25 pm, Athira Rajeev wrote: >> H_HTM (Hardware Trace Macro) hypervisor call is an HCALL to export >> data from Hardware Trace Macro (HTM) function. The debugfs interface >> to export the HTM function data in a parti

Re: [PATCH v1] ASoC: imx-card: Add NULL check in imx_card_probe()

2025-04-05 Thread Mark Brown
On Tue, 01 Apr 2025 22:25:10 +0800, Henry Martin wrote: > devm_kasprintf() returns NULL when memory allocation fails. Currently, > imx_card_probe() does not check for this case, which results in a NULL > pointer dereference. > > Add NULL check after devm_kasprintf() to prevent this issue. > > >

Re: [RFC 2/3] mm: introduce GCMA

2025-04-05 Thread Christoph Hellwig
On Thu, Mar 20, 2025 at 10:39:30AM -0700, Suren Baghdasaryan wrote: > From: Minchan Kim > > This patch introduces GCMA (Guaranteed Contiguous Memory Allocator) > cleacache backend which reserves some amount of memory at the boot > and then donates it to store clean file-backed pages in the cleanc

Re: [PATCH v2 1/1] mm: pgtable: fix pte_swp_exclusive

2025-04-05 Thread John Paul Adrian Glaubitz
Hi Magnus, On Tue, 2025-02-18 at 18:55 +0100, Magnus Lindholm wrote: > Make pte_swp_exclusive return bool instead of int. This will better reflect > how pte_swp_exclusive is actually used in the code. This fixes swap/swapoff > problems on Alpha due pte_swp_exclusive not returning correct values wh

Re: [PATCH 2/3] MAINTAINERS: fix nonexistent dtbinding file name

2025-04-05 Thread Christophe Leroy
Le 19/03/2025 à 10:43, Ioana Ciornei a écrit : [Vous ne recevez pas souvent de courriers de ioana.cior...@nxp.com. Découvrez pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ] The blamed commit converted the fsl,qoriq-mc.txt into fsl,qoriq-mc.yaml but forgot to als

Re: [PATCH v13 00/11] Support page table check on PowerPC

2025-04-05 Thread Madhavan Srinivasan
On 2/11/25 9:43 PM, Andrew Donnellan wrote: > Support page table check on all PowerPC platforms. This works by > serialising assignments, reassignments and clears of page table > entries at each level in order to ensure that anonymous mappings > have at most one writable consumer, and likewise t

Using Restricted DMA for virtio-pci

2025-04-05 Thread David Woodhouse
On Tue, 2021-02-09 at 14:21 +0800, Claire Chang wrote: > This series implements mitigations for lack of DMA access control on > systems without an IOMMU, which could result in the DMA accessing the > system memory at unexpected times and/or unexpected addresses, possibly > leading to data leakage o

[PATCH v3] powerpc/boot: Fix build with gcc 15

2025-04-05 Thread Michal Suchanek
Similar to x86 the ppc boot code does not build with GCC 15. Copy the fix from commit ee2ab467bddf ("x86/boot: Use '-std=gnu11' to fix build with GCC 15") Signed-off-by: Michal Suchanek --- v2: Move the fix outside of ifdef to apply to all subarchitectures v3: Change BOOTCFLAGS rather than BOOTT

Re: [BUG?] ppc64le: fentry BPF not triggered after live patch (v6.14)

2025-04-05 Thread Steven Rostedt
On Mon, 31 Mar 2025 21:19:36 +0800 Shung-Hsi Yu wrote: > Hi all, > > On ppc64le (v6.14, kernel config attached), I've observed that fentry > BPF programs stop being invoked after the target kernel function is live > patched. This occurs regardless of whether the BPF program was attached > before

Re: [PATCH v2 1/1] mm: pgtable: fix pte_swp_exclusive

2025-04-05 Thread Sam James
Sam James writes: > Lovely cleanup and a great suggestion from Al. > > Reviewed-by: Sam James > > I'd suggest adding a: > Suggested-by: Al Viro Al, were you planning on taking this through your tree? > > thanks, > sam

Re: [BUG?] ppc64le: fentry BPF not triggered after live patch (v6.14)

2025-04-05 Thread Jiri Olsa
On Mon, Mar 31, 2025 at 10:09:40AM -0400, Steven Rostedt wrote: > On Mon, 31 Mar 2025 21:19:36 +0800 > Shung-Hsi Yu wrote: > > > Hi all, > > > > On ppc64le (v6.14, kernel config attached), I've observed that fentry > > BPF programs stop being invoked after the target kernel function is live > >

Re: [PATCH v4 1/3] lsm: introduce new hooks for setting/getting inode fsxattr

2025-04-05 Thread Mickaël Salaün
On Fri, Mar 21, 2025 at 05:32:25PM -0400, Paul Moore wrote: > On Mar 21, 2025 Andrey Albershteyn wrote: > > > > Introduce new hooks for setting and getting filesystem extended > > attributes on inode (FS_IOC_FSGETXATTR). > > > > Cc: seli...@vger.kernel.org > > Cc: Paul Moore > > > > Signed-off

[PATCH] tools/perf/arch/powerpc/util: Fix is_compat_mode build break in ppc64

2025-04-05 Thread Likhitha Korrapati
Commit 54f9aa1092457 ("tools/perf/powerpc/util: Add support to handle compatible mode PVR for perf json events") introduced to select proper JSON events in case of compat mode using auxiliary vector. But this caused a compilation error in ppc64 Big Endian. arch/powerpc/util/header.c: In function '

Re: [PATCH v4 00/14] Add support for suppressing warning backtraces

2025-04-05 Thread David Gow
On Thu, 13 Mar 2025 at 19:44, Alessandro Carminati wrote: > > Some unit tests intentionally trigger warning backtraces by passing bad > parameters to kernel API functions. Such unit tests typically check the > return value from such calls, not the existence of the warning backtrace. > > Such inten

[PATCH v2 1/3] MAINTAINERS: add myself as maintainer for the fsl-mc bus

2025-04-05 Thread Ioana Ciornei
Both Laurentiu and Stuart left the company and are no longer involved with the fsl-mc bus. Remove them and add myself as maintainer. Signed-off-by: Ioana Ciornei --- Changes in v2: - also removed Stuart from the MAINTAINERS file https://lore.kernel.org/linuxppc-dev/caeac7tyqe76z4pyminhvmjr6gz66rp