Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	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 06:58:57 +0200	[thread overview]
Message-ID: <eff5c192-ed33-44e8-8834-fa5b4803f39b@kernel.org> (raw)
In-Reply-To: <627c5c2f-a0b3-4fba-811f-7b4ed4c74dbb@linux.ibm.com>



Le 11/08/2026 à 06:23, Venkat Rao Bagalkote a écrit :
> 
> 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.

But commit 263e5159e00a fixes commit d7a6797e0bc1 ("powerpc: add 
exit_flags field in pt_regs"), by reverting commit 263e5159e00a you 
re-introduce other bugs.

It's a bit difficult to see what commit 263e5159e00a is doing exactly, 
most of it is a revert of commit d7a6797e0bc1 but it does something 
instead. Need to see what remains with both commits applied.

Christophe


      reply	other threads:[~2026-08-11  4:59 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
2026-08-11  4:58   ` Christophe Leroy (CS GROUP) [this message]

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=eff5c192-ed33-44e8-8834-fa5b4803f39b@kernel.org \
    --to=chleroy@kernel.org \
    --cc=ajd@linux.ibm.com \
    --cc=brauner@kernel.org \
    --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 \
    --cc=venkat88@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