Re: [PATCH] powerpc: add crtsavres.o to always-y instead of extra-y

On Mon, Feb 5, 2024 at 12:50 PM Michael Ellerman wrote: > > Jan Stancek writes: > > On Tue, Nov 21, 2023 at 10:51:34AM +1000, Nicholas Piggin wrote: > >>On Tue Nov 21, 2023 at 9:23 AM AEST, Masahiro Yamada wrote: > >>> crtsavres.o is linked to modules

Re: [PATCH] powerpc: add crtsavres.o to always-y instead of extra-y

On Tue, Nov 21, 2023 at 10:51:34AM +1000, Nicholas Piggin wrote: On Tue Nov 21, 2023 at 9:23 AM AEST, Masahiro Yamada wrote: crtsavres.o is linked to modules. However, as explained in commit d0e628cd817f ("kbuild: doc: clarify the difference between extra-y and always-y"), 'make modules' does

Re: [PATCH/RFC] powerpc/module_64: allow .init_array constructors to run

On Thu, Jul 7, 2022 at 1:20 PM Christophe Leroy wrote: > > > > Le 17/08/2021 à 15:02, Jan Stancek a écrit : > > gcov and kasan rely on compiler generated constructor code. > > For modules, gcc-8 with gcov enabled generates .init_array section, > > but on p

[PATCH/RFC] powerpc/module_64: allow .init_array constructors to run

renaming .init_array section, so do_mod_ctors() can use it. Cc: Michael Ellerman Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Christophe Leroy Signed-off-by: Jan Stancek --- I wasn't able to trace the comment: "We don't handle .init for the moment: rename to _init" to original pat

[bug] LTP mmap03 stuck in page fault loop after c46241a370a6 ("powerpc/pkeys: Check vma before returning key fault error to the user")

Hi, LTP mmap03 is getting stuck in page fault loop after commit c46241a370a6 ("powerpc/pkeys: Check vma before returning key fault error to the user") System is ppc64le P9 lpar [1] running v5.8-rc2-34-g3e08a95294a4. Here's a minimized reproducer: - 8<

Re: [bug] userspace hitting sporadic SIGBUS on xfs (Power9, ppc64le), v4.19 and later

- Original Message - > > > On 12/6/19 6:09 PM, dftxbs3e wrote: > > Hello! > > > > I am very happy that someone has found this issue. > > > > I have been suffering from rather random SIGBUS errors in similar > > conditions described by the author. > > > > I don't have much

Re: [bug] userspace hitting sporadic SIGBUS on xfs (Power9, ppc64le), v4.19 and later

- Original Message - > Please try the patch below: I ran reproducer for 18 hours on 2 systems were it previously reproduced, there were no crashes / SIGBUS.

Re: [bug] userspace hitting sporadic SIGBUS on xfs (Power9, ppc64le), v4.19 and later

- Original Message - > On Tue, Dec 03, 2019 at 07:50:39AM -0500, Jan Stancek wrote: > > My theory is that there's a race in iomap. There appear to be > > interleaved calls to iomap_set_range_uptodate() for same page > > with varying offset and length. Each call

[bug] userspace hitting sporadic SIGBUS on xfs (Power9, ppc64le), v4.19 and later

Hi, (This bug report is summary from thread [1] with some additions) User-space binaries on Power9 ppc64le (with 64k pages) on xfs filesystem are sporadically hitting SIGBUS: -- 8< -- (gdb) r Starting program: /mnt/testarea/ltp/testcases/bin/genasin Program received signal

Re: ❌ FAIL: Test report for kernel 5.3.13-3b5f971.cki (stable-queue)

- Original Message - > Hi Jan, > > Jan Stancek writes: > > - Original Message - > >> > >> Hello, > >> > >> We ran automated tests on a recent commit from this kernel tree: > >> > >>Kernel repo: &

Re: [bug] KVM: Unrecoverable TM Unavailable Exception f60

- Original Message - > On Thu, 2017-07-13 at 08:07 -0400, Jan Stancek wrote: > > (You may want to CC the patch author... Added Paul). I did CC him using email address from patch. Maybe some list de-duplication dropped it? > > > - Original Message - > >

Re: [bug] KVM: Unrecoverable TM Unavailable Exception f60

- Original Message - > Hi, > > I'm running into Oops below on IBM PowerNV system (model 8247-22L) > with 4.12 trees and qemu-kvm-2.9. It triggers quickly after I start > KVM guest installation: > > virt-install --name ppc64le_kvm_1cpu --mac 52:56:00:00:00:06 --location > nfs://XXX

[bug] KVM: Unrecoverable TM Unavailable Exception f60

Hi, I'm running into Oops below on IBM PowerNV system (model 8247-22L) with 4.12 trees and qemu-kvm-2.9. It triggers quickly after I start KVM guest installation: virt-install --name ppc64le_kvm_1cpu --mac 52:56:00:00:00:06 --location nfs://XXX --ram=1024 --vcpus=1 --file-size=20 --hvm

[bug] stack protector panics on v4.10-rc1+

Hi, I'm running into panics with stack protector enabled on ppc64le lpar (IBM,8408-E8E), starting with: commit 6533b7c16ee5712041b4e324100550e02a9a5dda Author: Christophe Leroy Date: Tue Nov 22 11:49:30 2016 +0100 powerpc: Initial stack protector

Re: ehea crash on boot

- Original Message - > From: "Michael Ellerman" <m...@ellerman.id.au> > To: "Jan Stancek" <jstan...@redhat.com>, "Denis Kirjanov" > <k...@linux-powerpc.org> > Cc: linuxppc-dev@lists.ozlabs.org > Sent: Tuesday, 11 Octo

Re: ehea crash on boot

Hi Denis / all, Do you know if there is a patch or lead for this problem? I seem to be hitting same Oops with P730 lpar when running 4.8 (see below), but 4.7.7 looks OK. Regards, Jan [8.698424] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [8.713373] IPv6: ADDRCONF(NETDEV_UP):

Re: [bug] crypto/vmx/p8_ghash memory corruption in 4.8-rc7

> Jan, > > Can you check if the problem occurs with this patch? No issues in over-night test with this patch. > --- a/drivers/crypto/vmx/vmx.c > +++ b/drivers/crypto/vmx/vmx.c > @@ -28,6 +28,8 @@ > #include > #include > > +int p8_ghash_fallback_descsize(void); > + > extern struct

Re: [bug] crypto/vmx/p8_ghash memory corruption in 4.8-rc7

- Original Message - > From: "Herbert Xu" <herb...@gondor.apana.org.au> > To: "Marcelo Cerri" <marcelo.ce...@canonical.com> > Cc: "Jan Stancek" <jstan...@redhat.com>, "rui y wang" <rui.y.w...@intel.com&

Re: [bug] crypto/vmx/p8_ghash memory corruption in 4.8-rc7

- Original Message - > From: "Herbert Xu" <herb...@gondor.apana.org.au> > To: "Marcelo Cerri" <marcelo.ce...@canonical.com> > Cc: "Jan Stancek" <jstan...@redhat.com>, "rui y wang" <rui.y.w...@intel.com&

Re: [bug] crypto/vmx/p8_ghash memory corruption in 4.8-rc7

- Original Message - > From: "Marcelo Cerri" <marcelo.ce...@canonical.com> > To: "Jan Stancek" <jstan...@redhat.com> > Cc: "rui y wang" <rui.y.w...@intel.com>, herb...@gondor.apana.org.au, > mhce...@linux.vnet.ibm.com,

[bug] crypto/vmx/p8_ghash memory corruption in 4.8-rc7

Hi, I'm chasing a memory corruption with 4.8-rc7 as I'm observing random Oopses on ppc BE/LE systems (lpars, KVM guests). About 30% of issues is that module list gets corrupted, and "cat /proc/modules" or "lsmod" triggers an Oops, for example: [ 88.486041] Unable to handle kernel paging

Re: [PATCH] Fix: PowerNV crash with 4.4.0-rc8 at sched_init_numa

memory allocation for > non existent nodes. > > When DEBUG_PER_CPU_MAPS enabled, powerNV system failed to boot because > in sched_init_numa, cpumask_or operation was done on unallocated nodes. > Fix that by making cpumask_or operation only on existing nodes. > > [ Tested with and w/

Re: [BUG] PowerNV crash with 4.4.0-rc8 at sched_init_numa (related to commit c118baf80256)

- Original Message - > From: "Raghavendra K T" <raghavendra...@linux.vnet.ibm.com> > To: "Jan Stancek" <jstan...@redhat.com> > Cc: linuxppc-dev@lists.ozlabs.org, "raghavendra kt" > <raghavendra...@linux.vnet.ibm.com>, vdavy...

Re: [BUG] PowerNV crash with 4.4.0-rc8 at sched_init_numa (related to commit c118baf80256)

- Original Message - > From: "Raghavendra K T" <raghavendra...@linux.vnet.ibm.com> > To: "Jan Stancek" <jstan...@redhat.com> > Cc: linuxppc-dev@lists.ozlabs.org, vdavy...@parallels.com, > b...@kernel.crashing.org, pau...@samba.or

[BUG] PowerNV crash with 4.4.0-rc8 at sched_init_numa (related to commit c118baf80256)

Hi, I'm seeing bare metal ppc64le system crashing early during boot with latest upstream kernel (4.4.0-rc8): # git describe v4.4-rc8-96-g751e5f5 [0.625451] Unable to handle kernel paging request for data at address 0x [0.625586] Faulting instruction address: 0xc04ae000

Re: [PATCH] PPC: fix LOGMPP instruction opcode and inline asm

rashing.org> > Suggested-by: Benjamin Herrenschmidt <b...@kernel.crashing.org> > Suggested-by: Paul Mackerras <pau...@samba.org> > Signed-off-by: Stewart Smith <stew...@linux.vnet.ibm.com> Tested-by: Jan Stancek <jstan...@redhat.com> After running a kernel with this patch f

Re: powerpc/powernv/pci-ioda: fix kdump with non-power-of-2 crashkernel=

On Fri, Sep 04, 2015 at 09:59:38AM -0700, Nishanth Aravamudan wrote: > The 32-bit TCE table initialization relies on the DMA window having a > size equal to a power of 2 (and checks for it explicitly). But > crashkernel= has no constraint that requires a power-of-2 be specified. > This causes the

Re: [PATCH v2] powerpc/powernv/pci-ioda: fix kdump with non-power-of-2 crashkernel=

m.com>, "Alexey Kardashevskiy" > <a...@ozlabs.ru>, "Ben Herrenschmidt" <b...@kernel.crashing.org>, "Paul > Mackerras" <pau...@samba.org>, "David Gibson" > <da...@gibson.dropbear.id.au>, "Wei Yang" <weiy...@linux

[PATCH] powerpc: fix memory corruption by pnv_alloc_idle_core_states

: 7cba160ad789 (powernv/cpuidle: Redesign idle states management) Signed-off-by: Jan Stancek jstan...@redhat.com --- arch/powerpc/include/asm/cputhreads.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/include/asm/cputhreads.h b/arch/powerpc/include/asm

Re: powerpc/perf: add missing put_cpu_var in power_pmu_event_init

- Original Message - From: Michael Ellerman m...@ellerman.id.au To: Jan Stancek jstan...@redhat.com, linuxppc-dev@lists.ozlabs.org Cc: linux-ker...@vger.kernel.org, pau...@samba.org, an...@samba.org, t...@kernel.org, c...@linux.com, jo...@redhat.com, jstan...@redhat.com, j

[PATCH] powerpc/perf: add missing put_cpu_var in power_pmu_event_init

, .branch_sample_type = PERF_SAMPLE_BRANCH_ANY_RETURN, }; int main() { syscall(__NR_perf_event_open, event, 0, -1, -1, 0); } Signed-off-by: Jan Stancek jstan...@redhat.com --- arch/powerpc/perf/core-book3s.c |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff