Re: [PATCH] Yama: allow access for the current ptrace parent

On Mon, Dec 5, 2016 at 11:13 AM, Josh Stone wrote: > On 12/02/2016 03:27 PM, Kees Cook wrote: >>> + /* If there's already an active tracing relationship, then make an >> >> I'll adjust the comment style here and add it to my tree for -next. > > Thanks! > > I guess the

Re: [PATCH] Yama: allow access for the current ptrace parent

On Mon, Dec 5, 2016 at 11:13 AM, Josh Stone wrote: > On 12/02/2016 03:27 PM, Kees Cook wrote: >>> + /* If there's already an active tracing relationship, then make an >> >> I'll adjust the comment style here and add it to my tree for -next. > > Thanks! > > I guess the tweak is that it

Re: [PATCH] Yama: allow access for the current ptrace parent

On 12/02/2016 03:27 PM, Kees Cook wrote: >> + /* If there's already an active tracing relationship, then make an > > I'll adjust the comment style here and add it to my tree for -next. Thanks! I guess the tweak is that it should have an empty "/*" line? FWIW, checkpatch.pl doesn't warn

Re: [PATCH] Yama: allow access for the current ptrace parent

On 12/02/2016 03:27 PM, Kees Cook wrote: >> + /* If there's already an active tracing relationship, then make an > > I'll adjust the comment style here and add it to my tree for -next. Thanks! I guess the tweak is that it should have an empty "/*" line? FWIW, checkpatch.pl doesn't warn

Re: [PATCH] Yama: allow access for the current ptrace parent

On Fri, 2 Dec 2016, Kees Cook wrote: > James, can you pull this into your -next tree? I made a tiny fix to the > comment style, but it is otherwise identical to what Josh sent originally. Applied, thanks! -- James Morris

Re: [PATCH] Yama: allow access for the current ptrace parent

On Fri, 2 Dec 2016, Kees Cook wrote: > James, can you pull this into your -next tree? I made a tiny fix to the > comment style, but it is otherwise identical to what Josh sent originally. Applied, thanks! -- James Morris

[PATCH] Yama: allow access for the current ptrace parent

From: Josh Stone Under ptrace_scope=1, it's possible to have a tracee that is already ptrace-attached, but is no longer a direct descendant. For instance, a forking daemon will be re-parented to init, losing its ancestry to the tracer that launched it. The tracer can

[PATCH] Yama: allow access for the current ptrace parent

From: Josh Stone Under ptrace_scope=1, it's possible to have a tracee that is already ptrace-attached, but is no longer a direct descendant. For instance, a forking daemon will be re-parented to init, losing its ancestry to the tracer that launched it. The tracer can continue using ptrace in

Re: [PATCH] Yama: allow access for the current ptrace parent

On Wed, Nov 30, 2016 at 5:24 PM, Josh Stone wrote: > Under ptrace_scope=1, it's possible to have a tracee that is already > ptrace-attached, but is no longer a direct descendant. For instance, a > forking daemon will be re-parented to init, losing its ancestry to the > tracer

Re: [PATCH] Yama: allow access for the current ptrace parent

On Wed, Nov 30, 2016 at 5:24 PM, Josh Stone wrote: > Under ptrace_scope=1, it's possible to have a tracee that is already > ptrace-attached, but is no longer a direct descendant. For instance, a > forking daemon will be re-parented to init, losing its ancestry to the > tracer that launched it. >

[PATCH] Yama: allow access for the current ptrace parent

Under ptrace_scope=1, it's possible to have a tracee that is already ptrace-attached, but is no longer a direct descendant. For instance, a forking daemon will be re-parented to init, losing its ancestry to the tracer that launched it. The tracer can continue using ptrace in that state, but it

[PATCH] Yama: allow access for the current ptrace parent

Under ptrace_scope=1, it's possible to have a tracee that is already ptrace-attached, but is no longer a direct descendant. For instance, a forking daemon will be re-parented to init, losing its ancestry to the tracer that launched it. The tracer can continue using ptrace in that state, but it