From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: oleg@redhat.com, mpe@ellerman.id.au, npiggin@gmail.com,
chleroy@kernel.org, david@kernel.org, akpm@linux-foundation.org,
yeoreum.yun@arm.com, sshegde@linux.ibm.com, thuth@redhat.com,
agordeev@linux.ibm.com, mchauras@linux.ibm.com,
segher@kernel.crashing.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
"Mukesh Kumar Chaurasiya (IBM)" <mkchauras@gmail.com>
Cc: "Dmitry V. Levin" <ldv@strace.io>
Subject: Re: [PATCH] powerpc: Fix exit_flags field placement in pt_regs for ptrace
Date: Thu, 30 Jul 2026 11:11:19 +0530 [thread overview]
Message-ID: <178538948391.1278583.4141106305535032892.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260723194809.4046600-1-mkchauras@gmail.com>
On Fri, 24 Jul 2026 01:18:09 +0530, Mukesh Kumar Chaurasiya (IBM) wrote:
> Commit d7a6797e0bc1 ("powerpc: add exit_flags field in pt_regs") added
> the exit_flags field to struct pt_regs to pass internal exit control
> flags (e.g. _TIF_RESTOREALL) from syscall_exit_prepare() to the
> low-level assembly exit path.
>
> However, the field was placed in a way that was visible to userspace
> tools such as strace via PTRACE_GETREGS, or caused a struct layout or
> size regression observable through ptrace. The field is purely
> kernel-internal and must not be exposed beyond the user_pt_regs
> boundary.
>
> [...]
Applied to powerpc/fixes.
[1/1] powerpc: Fix exit_flags field placement in pt_regs for ptrace
https://git.kernel.org/powerpc/c/263e5159e00aa46bf26f3496ff7aae1fc9a6c826
cheers
prev parent reply other threads:[~2026-07-30 5:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 19:48 [PATCH] powerpc: Fix exit_flags field placement in pt_regs for ptrace Mukesh Kumar Chaurasiya (IBM)
2026-07-30 5:41 ` Madhavan Srinivasan [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=178538948391.1278583.4141106305535032892.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=chleroy@kernel.org \
--cc=david@kernel.org \
--cc=ldv@strace.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mchauras@linux.ibm.com \
--cc=mkchauras@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oleg@redhat.com \
--cc=segher@kernel.crashing.org \
--cc=sshegde@linux.ibm.com \
--cc=thuth@redhat.com \
--cc=yeoreum.yun@arm.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