[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190523161509.GE31896@fuggles.cambridge.arm.com>
Date: Thu, 23 May 2019 17:15:09 +0100
From: Will Deacon <will.deacon@....com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: linux-kernel@...r.kernel.org,
Linux Containers <containers@...ts.linux-foundation.org>,
Oleg Nesterov <oleg@...hat.com>, linux-arch@...r.kernel.org,
Dave Martin <Dave.Martin@....com>,
James Morse <james.morse@....com>
Subject: Re: [REVIEW][PATCHv2 03/26] signal/arm64: Use force_sig not
force_sig_fault for SIGKILL
On Thu, May 23, 2019 at 11:11:19AM -0500, Eric W. Biederman wrote:
> diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c
> index ade32046f3fe..e45d5b440fb1 100644
> --- a/arch/arm64/kernel/traps.c
> +++ b/arch/arm64/kernel/traps.c
> @@ -256,7 +256,10 @@ void arm64_force_sig_fault(int signo, int code, void __user *addr,
> const char *str)
> {
> arm64_show_signal(signo, str);
> - force_sig_fault(signo, code, addr, current);
> + if (signo == SIGKILL)
> + force_sig(SIGKILL, current);
> + else
> + force_sig_fault(signo, code, addr, current);
> }
Acked-by: Will Deacon <will.deacon@....com>
Are you planning to send this series on, or would you like me to pick this
into the arm64 tree?
Will
Powered by blists - more mailing lists