[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878rryxyz5.fsf@email.froward.int.ebiederm.org>
Date: Thu, 21 Apr 2022 10:01:02 -0500
From: "Eric W. Biederman" <ebiederm@...ssion.com>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Peter Zijlstra <peterz@...radead.org>, rjw@...ysocki.net,
mingo@...nel.org, vincent.guittot@...aro.org,
dietmar.eggemann@....com, rostedt@...dmis.org, mgorman@...e.de,
bigeasy@...utronix.de, Will Deacon <will@...nel.org>,
linux-kernel@...r.kernel.org, tj@...nel.org,
linux-pm@...r.kernel.org
Subject: Re: [RFC][PATCH] ptrace: Don't change __state
Oleg Nesterov <oleg@...hat.com> writes:
> On 04/20, Eric W. Biederman wrote:
>> @@ -892,7 +891,6 @@ static int ptrace_resume(struct task_struct *child, long request,
>> * status and clears the code too; this can't race with the tracee, it
>> * takes siglock after resume.
>> */
>> - need_siglock = data && !thread_group_empty(current);
>> if (need_siglock)
>> spin_lock_irq(&child->sighand->siglock);
>
> Hmm?
A half backed out change (I thought ptrace_resume would need to clear
JOBCTL_DELAY_WAKEKILL) in ptrace_resume. I somehow failed to
restore the need_siglock line.
Eric
Powered by blists - more mailing lists