LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Harsh Prateek Bora <harsh.prateek.bora@gmail.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Shrikanth Hegde <sshegde@linux.ibm.com>,
	Mukesh Kumar Chaurasiya <mkchauras@gmail.com>,
	Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Subject: Re: [PATCH] powerpc: Don't drop _TIF_RESTOREALL on syscall restart
Date: Thu, 03 Sep 2026 23:55:50 +0530	[thread overview]
Message-ID: <fqzqtcnl.ritesh.list@gmail.com> (raw)
In-Reply-To: <CAEuJdmqPPYET2tjQmKCzamRr6aBhb4JNjBPN0R6G72w0KdLjKg@mail.gmail.com>

Harsh Prateek Bora <harsh.prateek.bora@gmail.com> writes:

>
> Thanks for the fix, Ritesh!
> Are we leaving ret unused as well?
>

No, it's not unused. It is getting used to sample whether exit_flags has
_TIF_RESTOREALL set or not.

Though maybe it can be optimized away if needed in a separate patch
later. But for now we are good and this fix is needed as many of us have
reported ld64 crash on v7.2.

> Otherwise,
> Reviewed-by: Harsh Prateek Bora <harsh.prateek.bora@gmail.com>
>
Thanks!

-ritesh


  reply	other threads:[~2026-09-03 18:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-29  4:19 [PATCH] powerpc: Don't drop _TIF_RESTOREALL on syscall restart Ritesh Harjani (IBM)
2026-08-29  5:54 ` Venkat Rao Bagalkote
2026-08-31  4:40 ` Mukesh Kumar Chaurasiya
2026-09-02 14:28 ` Shrikanth Hegde
2026-09-02 15:00 ` Amit Machhiwal
2026-09-03 18:09 ` Harsh Prateek Bora
2026-09-03 18:25   ` Ritesh Harjani [this message]
2026-09-04  2:22 ` Aboorva Devarajan
2026-09-09  6:18 ` Madhavan Srinivasan

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=fqzqtcnl.ritesh.list@gmail.com \
    --to=ritesh.list@gmail.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=harsh.prateek.bora@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mkchauras@gmail.com \
    --cc=sshegde@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