From: Oleg Nesterov <oleg@redhat.com>
To: Zhao Gongyi <zhaogongyi@bytedance.com>
Cc: catalin.marinas@arm.com, will@kernel.org, mark.rutland@arm.com,
ruanjinjie@huawei.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] arm64: ptrace: don't warn on missing siginfo in a group-stop
Date: Sun, 8 Nov 2026 19:59:25 +0100 [thread overview]
Message-ID: <avDGjYYR6Tj1sVgP@redhat.com> (raw)
In-Reply-To: <20261105113051.97810-1-zhaogongyi@bytedance.com>
On 11/05, Zhao Gongyi wrote:
>
> --- a/arch/arm64/kernel/ptrace.c
> +++ b/arch/arm64/kernel/ptrace.c
> @@ -573,8 +573,8 @@ static void update_syscall_orig_x0_after_ptrace(struct task_struct *target)
> if (regs->syscallno == NO_SYSCALL)
> return;
>
> - /* We should only be called when target is in a ptrace stop */
> - if (WARN_ON_ONCE(!info))
> + /* Non-seized group-stops do not provide siginfo (see do_jobctl_trap()). */
> + if (!info)
> return;
First of all, FWIW
Acked-by: Oleg Nesterov <oleg@redhat.com>
This change is "obviously good" and doesn't change the current behaviour.
----------------------------------------------------------------------------
But can't resist... The old comment was obviously wrong, the new one doesn't
look clear to me. It correctly explains why info can be NULL, but not why we
should not update orig_x0 in this case. May be it should just say that exit-stop
always comes with info != NULL?
Nevermind, I leave this to you, Catalin, and Will.
And I see another email from Will, I'll try to reply tomorrow.
In any case, let me repeat, the patch looks fine to me.
Oleg.
prev parent reply other threads:[~2026-11-08 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 11:30 Zhao Gongyi
2026-11-08 18:59 ` Oleg Nesterov [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=avDGjYYR6Tj1sVgP@redhat.com \
--to=oleg@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ruanjinjie@huawei.com \
--cc=will@kernel.org \
--cc=zhaogongyi@bytedance.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
all inboxes | Powered by JetHome®