Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: Madhavan Srinivasan <maddy@linux.ibm.com>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Ritesh Harjani <riteshh@linux.ibm.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	ajd@linux.ibm.com
Cc: LKML <linux-kernel@vger.kernel.org>,
	Christian Brauner <brauner@kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [BUG] powerpc: userspace processes crash in ld64.so.2 when running recent linux-next kernels
Date: Tue, 11 Aug 2026 09:53:03 +0530	[thread overview]
Message-ID: <627c5c2f-a0b3-4fba-811f-7b4ed4c74dbb@linux.ibm.com> (raw)
In-Reply-To: <75419f88-eab9-444b-bf97-28a9765819ad@linux.ibm.com>


On 03/08/26 6:40 pm, Venkat Rao Bagalkote wrote:
> Hi,
>
> We are seeing random userspace crashes while building the kernel on
> ppc64le when running recent upstream/mainline or linux-next kernels.
>
> The failures occur in different userspace programs, but the crash
> signature is consistently inside ld64.so.2.
>
> Environment
> -----------
>
> Architecture:
>   ppc64le
>
> Platform:
>   IBM Power systems (LPAR)
>
> Userspace:
>   RHEL userspace
>
> Workload:
>   Kernel build
>
>     make -j32 -s && make modules_install && make install
>
>
> gcc version 14.3.1 20251022 (Red Hat 14.3.1-4) (GCC)
>
> GNU ld version 2.41-63.el10
> ldd (GNU libc) 2.39
>
>
>
>
> Observation
> -----------
>
> The issue is observed when the system is booted with recent upstream
> kernels.
>
> The same LPAR, userspace, toolchain, and source tree are able to build
> successfully when booted with the base OS kernel.
>
> Typical failures include:
>
>   sh
>   fixdep
>   make
>
> The source file being compiled when the failure occurs varies from run
> to run.
>
> Examples
> --------
>
> Example 1:
>
> [ 1277.872746] fixdepsegfault (11) at 29ac0
> [ 1277.872746] fixdep[122982]: nip 3fffbebd8214 lr 3fffbebd7358
> [ 1277.872746] fixdep[122982]: code 1 in ld64.sofffbeba1000+50000]
>
> [ 1277.872793] fixdepcode:
> f90104a8 7ce903a6 f9410060 f9490008
> f9490010 f9490018 39290020 f9490000
>
> [ 1277.872805] fixdep[122982[37214,3fffbeba1000+50000 f9490018 
> <ea628000> 7e731050 f9410030 fa610020
>
> cripts/Makefile.build:289:
> drivers/gpu/drm/amd/amdgpu/../pm/powerplay/smumgr/vegam_smumgr.o]
> Error 139
>
> Example 2:
>
> [Sun Aug 2 12:36:38 2026] sh[115552]: segfaultbcd0
> nip 3fffbd73d004 lr 3fffbd73c148 code 1 in
> ld64.so.2[35004,3fffbd708000+4d000]
>
> Example 3:
>
> [Sun Aug 2 12:40:08 2026] fixdep[134469]: segfault (11) at 
> 2bcd0c3ca004 lr 3fff8c3c9148 code 1 in
> ld64.so.2[35004,3fff8c395000+4d000]
>
> Example 4:
>
> [Mon Aug 3 05:44:20 2026] make[600291]: segfault (11) ip 3fffaf3b5004 
> lr 3fffaf3b4148 code 1 in
> ld64.so.2[35004,3fffaf380000+4d000]
>
> Notes
> -----
>
> - The crashing executable varies (sh, fixdep, make, etc.).
> - The object file being compiled also varies.
> - The crash always appears to occur in ld64.so.2.
> - The issue has been observed on more than one system.
> - A fresh OS installation with ample free memory reproduces the issue.
>
> Let me know, if any more info is needed.
>
> If you happen to fix this issue, please add below tag.
>
> Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
>
>
>

As part of debugging and suggested by Maddy, I reverted the following 
commit:

   263e5159e00a ("powerpc: Fix exit_flags field placement in pt_regs for 
ptrace")

and rebuilt/booted linux-next with only that change reverted.

After booting the reverted kernel, I rebuilt the latest upstream kernel
using the same userspace and toolchain. The build completed
successfully and I did not observe any of the ld64.so.2 userspace
segfaults that were previously seen during kernel compilation.

Kernel used for testing:

   7.2.0-rc5-next-20260731-00001-g79d9c1ce90a9

Top of tree:

   commit 79d9c1ce90a9873422ca4d6d0124a1d1c10a098c
   Revert "powerpc: Fix exit_flags field placement in pt_regs for ptrace"

The upstream kernel build completed successfully:

   INSTALL /lib/modules/7.2.0-rc7/kernel/net/openvswitch/vport-gre.ko
   DEPMOD  /lib/modules/7.2.0-rc7
   INSTALL /boot

Based on this testing, reverting commit 263e5159e00a appears to
eliminate the random userspace crashes observed during kernel builds,
suggesting that the issue may be related to that change.

>
>
> Thanks,
> Venkat.


  reply	other threads:[~2026-08-11  4:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 13:10 [BUG] powerpc: userspace processes crash in ld64.so.2 when running recent linux-next kernels Venkat Rao Bagalkote
2026-08-11  4:23 ` Venkat Rao Bagalkote [this message]
2026-08-11  4:58   ` Christophe Leroy (CS GROUP)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=627c5c2f-a0b3-4fba-811f-7b4ed4c74dbb@linux.ibm.com \
    --to=venkat88@linux.ibm.com \
    --cc=ajd@linux.ibm.com \
    --cc=brauner@kernel.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=riteshh@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox