[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220506141403.GA16084@redhat.com>
Date: Fri, 6 May 2022 16:14:30 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: linux-kernel@...r.kernel.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>, tj@...nel.org,
linux-pm@...r.kernel.org, Peter Zijlstra <peterz@...radead.org>,
Richard Weinberger <richard@....at>,
Anton Ivanov <anton.ivanov@...bridgegreys.com>,
Johannes Berg <johannes@...solutions.net>,
linux-um@...ts.infradead.org, Chris Zankel <chris@...kel.net>,
Max Filippov <jcmvbkbc@...il.com>,
linux-xtensa@...ux-xtensa.org, Jann Horn <jannh@...gle.com>,
Kees Cook <keescook@...omium.org>, linux-ia64@...r.kernel.org
Subject: Re: [PATCH v4 0/12] ptrace: cleaning up ptrace_stop
On 05/05, Eric W. Biederman wrote:
>
> Eric W. Biederman (11):
> signal: Rename send_signal send_signal_locked
> signal: Replace __group_send_sig_info with send_signal_locked
> ptrace/um: Replace PT_DTRACE with TIF_SINGLESTEP
> ptrace/xtensa: Replace PT_SINGLESTEP with TIF_SINGLESTEP
> ptrace: Remove arch_ptrace_attach
> signal: Use lockdep_assert_held instead of assert_spin_locked
> ptrace: Reimplement PTRACE_KILL by always sending SIGKILL
> ptrace: Document that wait_task_inactive can't fail
> ptrace: Admit ptrace_stop can generate spuriuos SIGTRAPs
> ptrace: Don't change __state
> ptrace: Always take siglock in ptrace_resume
>
> Peter Zijlstra (1):
> sched,signal,ptrace: Rework TASK_TRACED, TASK_STOPPED state
I can't comment 5/12. to be honest I didn't even try to look into
arch/ia64/.
But other than that I see no problems in this version. However, I'd
like to actually apply the whole series and read the changed code
carefully, but sorry, I don't think I can do this before Monday.
Oleg.
Powered by blists - more mailing lists