[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180528215355.16119-20-christian@brauner.io>
Date: Mon, 28 May 2018 23:53:54 +0200
From: Christian Brauner <christian@...uner.io>
To: linux-kernel@...r.kernel.org
Cc: 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,
oleg@...hat.com, Christian Brauner <christian@...uner.io>
Subject: [PATCH v1 19/20] signal: make security_task_kill() return bool
security_task_kill() already behaves like a boolean function. Let's
actually declare it as such too.
Signed-off-by: Christian Brauner <christian@...uner.io>
---
v0->v1:
* patch introduced
---
kernel/signal.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index 7e217e83a6de..a4787c90faab 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -1928,10 +1928,10 @@ static inline bool may_ptrace_stop(void)
* Return non-zero if there is a SIGKILL that should be waking us up.
* Called with the siglock held.
*/
-static int sigkill_pending(struct task_struct *tsk)
+static bool sigkill_pending(struct task_struct *tsk)
{
- return sigismember(&tsk->pending.signal, SIGKILL) ||
- sigismember(&tsk->signal->shared_pending.signal, SIGKILL);
+ return sigismember(&tsk->pending.signal, SIGKILL) ||
+ sigismember(&tsk->signal->shared_pending.signal, SIGKILL);
}
/*
--
2.17.0
Powered by blists - more mailing lists