On Wed, 16 Apr 2025 15:57:50 -0500 Dave Marquardt wrote:
> Reset the adapter through new function ibmveth_reset, called in
> WARN_ON situations. Removed conflicting and unneeded forward
> declaration.
There's a schedule_work() added but neither cancel nor flush when
interface is shut down or remov
On Tue, Apr 22, 2025 at 08:43:05PM -0500, Jason Gunthorpe wrote:
> On Tue, Apr 22, 2025 at 06:21:32PM -0400, Ben Collins wrote:
> > On Tue, Apr 22, 2025 at 04:09:21PM -0500, Jason Gunthorpe wrote:
> > > On Mon, Apr 21, 2025 at 10:46:19PM -0400, Ben Collins wrote:
> > > > diff --git a/drivers/iommu/
On Tue, Apr 22, 2025 at 06:21:32PM -0400, Ben Collins wrote:
> On Tue, Apr 22, 2025 at 04:09:21PM -0500, Jason Gunthorpe wrote:
> > On Mon, Apr 21, 2025 at 10:46:19PM -0400, Ben Collins wrote:
> > > diff --git a/drivers/iommu/fsl_pamu_domain.c
> > > b/drivers/iommu/fsl_pamu_domain.c
> > > index 30
On Tue, Apr 22, 2025 at 04:09:21PM -0500, Jason Gunthorpe wrote:
> On Mon, Apr 21, 2025 at 10:46:19PM -0400, Ben Collins wrote:
> > diff --git a/drivers/iommu/fsl_pamu_domain.c
> > b/drivers/iommu/fsl_pamu_domain.c
> > index 30be786bff11e..a4bc6482a00f7 100644
> > --- a/drivers/iommu/fsl_pamu_doma
On Tue, Apr 22, 2025 at 11:25:40AM -0500, Arnd Bergmann wrote:
> On Tue, Apr 22, 2025, at 10:56, Ben Collins wrote:
> > On Tue, Apr 22, 2025 at 09:59:42AM -0500, Arnd Bergmann wrote:
> >>
> >> Right, but this could just mean that they end up using SWIOTLB
> >> to bounce the high DMA pages or use a
On Mon, Apr 21, 2025 at 10:46:19PM -0400, Ben Collins wrote:
> diff --git a/drivers/iommu/fsl_pamu_domain.c b/drivers/iommu/fsl_pamu_domain.c
> index 30be786bff11e..a4bc6482a00f7 100644
> --- a/drivers/iommu/fsl_pamu_domain.c
> +++ b/drivers/iommu/fsl_pamu_domain.c
> @@ -214,9 +214,10 @@ static str
From: Eric Biggers
Now that the architecture-optimized ChaCha kconfig symbols are defined
regardless of CRYPTO, there is no need for CRYPTO_LIB_CHACHA to select
CRYPTO. So, remove that. This makes the indirection through the
CRYPTO_LIB_CHACHA_INTERNAL symbol unnecessary, so get rid of that and
From: Eric Biggers
Now that the architecture-optimized Poly1305 kconfig symbols are defined
regardless of CRYPTO, there is no need for CRYPTO_LIB_POLY1305 to select
CRYPTO. So, remove that. This makes the indirection through the
CRYPTO_LIB_POLY1305_INTERNAL symbol unnecessary, so get rid of tha
From: Eric Biggers
Continue disentangling the crypto library functions from the generic
crypto infrastructure by moving the s390 ChaCha library functions into a
new directory arch/s390/lib/crypto/ that does not depend on CRYPTO.
This mirrors the distinction between crypto/ and lib/crypto/.
Acked
From: Eric Biggers
Continue disentangling the crypto library functions from the generic
crypto infrastructure by moving the mips ChaCha and Poly1305 library
functions into a new directory arch/mips/lib/crypto/ that does not
depend on CRYPTO. This mirrors the distinction between crypto/ and
lib/c
From: Eric Biggers
arch/x86/crypto/Kconfig is sourced only when CONFIG_X86=y, so there is
no need for the symbols defined inside it to depend on X86.
In the case of CRYPTO_TWOFISH_586 and CRYPTO_TWOFISH_X86_64, the
dependency was actually on '(X86 || UML_X86)', which suggests that these
two symb
From: Eric Biggers
Continue disentangling the crypto library functions from the generic
crypto infrastructure by moving the arm BLAKE2s, ChaCha, and Poly1305
library functions into a new directory arch/arm/lib/crypto/ that does
not depend on CRYPTO. This mirrors the distinction between crypto/ a
From: Eric Biggers
Continue disentangling the crypto library functions from the generic
crypto infrastructure by moving the riscv ChaCha library functions into
a new directory arch/riscv/lib/crypto/ that does not depend on CRYPTO.
This mirrors the distinction between crypto/ and lib/crypto/.
Sig
From: Eric Biggers
Continue disentangling the crypto library functions from the generic
crypto infrastructure by moving the x86 BLAKE2s, ChaCha, and Poly1305
library functions into a new directory arch/x86/lib/crypto/ that does
not depend on CRYPTO. This mirrors the distinction between crypto/ a
From: Eric Biggers
Continue disentangling the crypto library functions from the generic
crypto infrastructure by moving the powerpc ChaCha and Poly1305 library
functions into a new directory arch/powerpc/lib/crypto/ that does not
depend on CRYPTO. This mirrors the distinction between crypto/ and
This series removes the unnecessary dependency of the ChaCha, Poly1305,
and BLAKE2s library functions on the generic crypto infrastructure, i.e.
CONFIG_CRYPTO. To do this, it moves the architecture-optimized
implementations of these functions into new directories
arch/*/lib/crypto/ which do not de
From: Eric Biggers
Continue disentangling the crypto library functions from the generic
crypto infrastructure by moving the arm64 ChaCha and Poly1305 library
functions into a new directory arch/arm64/lib/crypto/ that does not
depend on CRYPTO. This mirrors the distinction between crypto/ and
lib
From: Eric Biggers
arch/powerpc/crypto/Kconfig is sourced only when CONFIG_PPC=y, so there
is no need for the symbols defined inside it to depend on PPC.
Acked-by: Ard Biesheuvel
Signed-off-by: Eric Biggers
---
arch/powerpc/crypto/Kconfig | 8 +++-
1 file changed, 3 insertions(+), 5 delet
From: Eric Biggers
arch/s390/crypto/Kconfig is sourced only when CONFIG_S390=y, so there is
no need for the symbols defined inside it to depend on S390.
Acked-by: Ard Biesheuvel
Acked-by: Heiko Carstens
Signed-off-by: Eric Biggers
---
arch/s390/crypto/Kconfig | 10 --
1 file changed,
From: Eric Biggers
arch/arm64/crypto/Kconfig is sourced only when CONFIG_ARM64=y, so there
is no need for the symbols defined inside it to depend on ARM64.
Acked-by: Ard Biesheuvel
Signed-off-by: Eric Biggers
---
arch/arm64/crypto/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions
On Tue, Apr 22, 2025 at 04:31:29PM +0200, Christian Brauner wrote:
> On Thu, Mar 27, 2025 at 12:39:28PM +0100, Amir Goldstein wrote:
> > On Thu, Mar 27, 2025 at 10:33 AM Andrey Albershteyn
> > wrote:
> > >
> > > On 2025-03-23 09:56:25, Amir Goldstein wrote:
> > > > On Fri, Mar 21, 2025 at 8:49 PM
On Fri, Mar 21, 2025 at 08:48:42PM +0100, Andrey Albershteyn wrote:
> From: Andrey Albershteyn
>
> Introduce getfsxattrat and setfsxattrat syscalls to manipulate inode
> extended attributes/flags. The syscalls take parent directory fd and
> path to the child together with struct fsxattr.
>
> Thi
On Thu, Mar 27, 2025 at 12:39:28PM +0100, Amir Goldstein wrote:
> On Thu, Mar 27, 2025 at 10:33 AM Andrey Albershteyn
> wrote:
> >
> > On 2025-03-23 09:56:25, Amir Goldstein wrote:
> > > On Fri, Mar 21, 2025 at 8:49 PM Andrey Albershteyn
> > > wrote:
> > > >
> > > > From: Andrey Albershteyn
>
On 4/22/25 6:38 PM, Stephen Rothwell wrote:
> Hi Madhavan,
>
> On Tue, 22 Apr 2025 17:00:23 +0530 Madhavan Srinivasan
> wrote:
>>
>> # suppress some warnings in recent ld versions
>> nowarn="-z noexecstack"
>> -if [ $(${CROSS}ld -v --no-warn-rwx-segments &>/dev/null; echo $?) -eq 0 ];
>> t
Hi Madhavan,
On Tue, 22 Apr 2025 18:40:40 +0530 Madhavan Srinivasan
wrote:
>
> -if [ -f $4/$image_name-$1 ]; then
> - mv $4/$image_name-$1 $4/$image_name-$1.old
> +if [ -f "$4"/"$image_name"-"$1" ]; then
> + mv "$4"/"$image_name"-"$1" "$4"/"$image_name"-"$1".old
"$4/$image_name-$1" is j
Hi Madhavan,
On Tue, 22 Apr 2025 18:40:39 +0530 Madhavan Srinivasan
wrote:
>
> Fix "Double quote to prevent globbing and word splitting."
> warning from shellcheck
Looks good to me.
Reviewed-by: Stephen Rothwell
--
Cheers,
Stephen Rothwell
pgpiFfnobaiO9.pgp
Description: OpenPGP digital si
Fix shellcheck warning such as
"Double quote to prevent globbing and word splitting." and
Use $(...) notation instead of legacy backticks `...`.
Signed-off-by: Madhavan Srinivasan
---
arch/powerpc/boot/install.sh | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/
Fix "Double quote to prevent globbing and word splitting."
warning from shellcheck
Signed-off-by: Madhavan Srinivasan
---
arch/powerpc/kernel/prom_init_check.sh | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/arch/powerpc/kernel/prom_init_check.sh
b/arch/pow
structs are local to the source and does not need to
be in global scope, so make it static.
Signed-off-by: Madhavan Srinivasan
---
arch/powerpc/kernel/btext.c | 2 +-
arch/powerpc/kernel/setup-common.c | 2 +-
arch/powerpc/platforms/powernv/opal.c| 2 +-
arch/powerpc/platf
isa207_pmu_format_group struct is local to the source and does not need to
be in global scope, so make it static
Cleans up sparse warning:
arch/powerpc/perf/isa207-common.c:40:30: warning: symbol
'isa207_pmu_format_group'
was not declared. Should it be static?
Signed-off-by: Madhavan Srinivasan
Fix passing of argument 0 to NULL to avoid sparse warning
Cleans up sparse warning:
arch/powerpc/xmon/ppc-opc.c:797:15: warning: Using plain integer as NULL pointer
arch/powerpc/xmon/ppc-opc.c:797:18: warning: Using plain integer as NULL pointer
arch/powerpc/xmon/ppc-opc.c:801:15: warning: Using p
When compiling for pseries or powernv defconfig with "make C=1",
these warning were reported by sparse tool in powerpc/kernel/kvm.c
arch/powerpc/kernel/kvm.c:635:9: warning: switch with no cases
arch/powerpc/kernel/kvm.c:646:9: warning: switch with no cases
Currently #ifdef were added after the s
Patchset handles fixes for some of the sparse
and shellcheck warnings.
Madhavan Srinivasan (6):
powerpc/kvm: Fix sparse warning
powerpc/xmon: fix sparse warning "Using plain integer as NULL pointer"
powerpc/perf:make isa207_pmu_format_group struct static
powerpc: fix sparse warnings
powe
Hi Madhavan,
On Tue, 22 Apr 2025 17:00:23 +0530 Madhavan Srinivasan
wrote:
>
> # suppress some warnings in recent ld versions
> nowarn="-z noexecstack"
> -if [ $(${CROSS}ld -v --no-warn-rwx-segments &>/dev/null; echo $?) -eq 0 ];
> then
> +if [ "$("${CROSS}"ld -v --no-warn-rwx-segments >/dev/
On Thu, 17 Apr 2025 16:21:14 +0200, J. Neuschäfer wrote:
> This patch rewrites pmc.txt into YAML format. Descriptive texts are
> expanded or shortened in a few places to better fit today's conventions.
>
> The list of compatible strings (and combinations of them) is based on
> existing device tr
On Wed, Apr 16, 2025 at 03:57:51PM -0500, Dave Marquardt wrote:
> Added KUnit tests for ibmveth_remove_buffer_from_pool and
> ibmveth_rxq_get_buffer under new IBMVETH_KUNIT_TEST config option.
>
> Signed-off-by: Dave Marquardt
Reviewed-by: Simon Horman
On Wed, Apr 16, 2025 at 03:57:50PM -0500, Dave Marquardt wrote:
> Reset the adapter through new function ibmveth_reset, called in
> WARN_ON situations. Removed conflicting and unneeded forward
> declaration.
>
> Signed-off-by: Dave Marquardt
Reviewed-by: Simon Horman
On Wed, Apr 16, 2025 at 03:57:49PM -0500, Dave Marquardt wrote:
> Made struct ibmveth_adapter follow indentation rules
>
> Signed-off-by: Dave Marquardt
Reviewed-by: Simon Horman
Commit b2accfe7ca5b '("powerpc/boot: Check for ld-option support")' suppressed
linker warnings, but the expressed used did not go well with POSIX shell (dash)
resulting with this warning
arch/powerpc/boot/wrapper: 237: [: 0: unexpected operator
ld: warning: arch/powerpc/boot/zImage.epapr has a LOA
On Sun, Apr 20, 2025 at 12:26:06PM -0700, Eric Biggers wrote:
> From: Eric Biggers
>
> Continue disentangling the crypto library functions from the generic
> crypto infrastructure by moving the s390 ChaCha library functions into a
> new directory arch/s390/lib/crypto/ that does not depend on CRYP
On Sun, Apr 20, 2025 at 12:25:59PM -0700, Eric Biggers wrote:
> From: Eric Biggers
>
> arch/s390/crypto/Kconfig is sourced only when CONFIG_S390=y, so there is
> no need for the symbols defined inside it to depend on S390.
>
> Acked-by: Ard Biesheuvel
> Signed-off-by: Eric Biggers
> ---
> arc
Hi Hannes,
On Tue, 22 Apr 2025 08:37:32 +0200
Hannes Reinecke wrote:
> On 4/17/25 17:10, Dan Horák wrote:
> > Hi,
> >
> > I am seeing "frozen PHB" on Power9 bare-metal (PowerNV ppc64le) system
> > leading to non-accessible nvme drives (they are behind a switch) in the
> > 6.15-rc2 kernel (origi
On Tue, Apr 22, 2025, at 10:56, Ben Collins wrote:
> On Tue, Apr 22, 2025 at 09:59:42AM -0500, Arnd Bergmann wrote:
>>
>> Right, but this could just mean that they end up using SWIOTLB
>> to bounce the high DMA pages or use an IOMMU rather than actually
>> translating the physical address to a dma
On 21/04/2025 4:41 am, Athira Rajeev wrote:
To pick up the changes in:
commit acea9943271b ("vdso: Address variable shadowing in macros")
Addressing this perf tools build warning:
diff -u tools/include/vdso/unaligned.h include/vdso/unaligned.h
Reported-by: Venkat Rao Bagalko
On Tue, Apr 22, 2025 at 09:59:42AM -0500, Arnd Bergmann wrote:
> On Tue, Apr 22, 2025, at 09:12, Ben Collins wrote:
> > On Tue, Apr 22, 2025 at 08:34:55AM -0500, Arnd Bergmann wrote:
> >>
> >> - SoCs that don't set a dma-ranges property in the parent bus
> >> are normally still capped to 32 bit
On 17/04/25 8:06 pm, Venkat Rao Bagalkote wrote:
On 17/04/25 1:10 am, Hari Bathini wrote:
arch_bpf_trampoline_size() provides JIT size of the BPF trampoline
before the buffer for JIT'ing it is allocated. The total number of
instructions emitted for BPF trampoline JIT code depends on where
th
On 19/04/25 4:31 pm, Naveen N Rao wrote:
On Thu, Apr 17, 2025 at 01:10:37AM +0530, Hari Bathini wrote:
arch_bpf_trampoline_size() provides JIT size of the BPF trampoline
before the buffer for JIT'ing it is allocated. The total number of
instructions emitted for BPF trampoline JIT code depends
arch_bpf_trampoline_size() provides JIT size of the BPF trampoline
before the buffer for JIT'ing it is allocated. The total number of
instructions emitted for BPF trampoline JIT code depends on where
the final image is located. So, the size arrived at with the dummy
pass in arch_bpf_trampoline_size
On Tue, Apr 22, 2025, at 09:12, Ben Collins wrote:
> On Tue, Apr 22, 2025 at 08:34:55AM -0500, Arnd Bergmann wrote:
>>
>> - SoCs that don't set a dma-ranges property in the parent bus
>> are normally still capped to 32 bit DMA. I don't see those
>> properties, so unless there is a special hack
On Tue, Apr 22, 2025 at 08:34:55AM -0500, Arnd Bergmann wrote:
> On Tue, Apr 22, 2025, at 04:49, Ben Collins wrote:
> > On 64-bit QorIQ platforms like T4240, the CPU supports 40-bit addressing
> > and memory configurations > 64GiB. The fsldma driver is limiting itself
> > to only 64GiB in all Elo c
50 matches
Mail list logo
