[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180601155612.GB1058@redhat.com>
Date: Fri, 1 Jun 2018 17:56:12 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Christian Brauner <christian@...uner.io>
Cc: linux-kernel@...r.kernel.org, ebiederm@...ssion.com,
gregkh@...uxfoundation.org, mingo@...nel.org,
james.morris@...rosoft.com, keescook@...omium.org,
peterz@...radead.org, sds@...ho.nsa.gov, viro@...iv.linux.org.uk,
akpm@...ux-foundation.org
Subject: Re: [PATCH v2 03/17] signal: make may_ptrace_stop() return bool
On 06/01, Christian Brauner wrote:
>
> may_ptrace_stop() already behaves like a boolean function. Let's actually
> declare it as such too.
OK. Then probably this patch should only make it return bool and do nothing else?
> - if (unlikely(current->mm->core_state) &&
> - unlikely(current->mm == current->parent->mm))
> - return 0;
> + if (likely(!current->mm->core_state ||
> + current->mm != current->parent->mm))
> + return false;
this is wrong.
Oleg.
Powered by blists - more mailing lists