From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F3F1EC433EF for ; Wed, 27 Oct 2021 14:24:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D76D260D42 for ; Wed, 27 Oct 2021 14:24:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238053AbhJ0O1V (ORCPT ); Wed, 27 Oct 2021 10:27:21 -0400 Received: from brightrain.aerifal.cx ([216.12.86.13]:40206 "EHLO brightrain.aerifal.cx" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238214AbhJ0O1U (ORCPT ); Wed, 27 Oct 2021 10:27:20 -0400 Date: Wed, 27 Oct 2021 10:24:51 -0400 From: Rich Felker To: Linus Torvalds Cc: "Eric W. Biederman" , Linux Kernel Mailing List , linux-arch , Oleg Nesterov , Al Viro , Kees Cook , Yoshinori Sato , Linux-sh list Subject: Re: [PATCH 06/20] signal/sh: Use force_sig(SIGKILL) instead of do_group_exit(SIGKILL) Message-ID: <20211027142450.GV7074@brightrain.aerifal.cx> References: <87y26nmwkb.fsf@disp2133> <20211020174406.17889-6-ebiederm@xmission.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Precedence: bulk List-ID: X-Mailing-List: linux-sh@vger.kernel.org On Wed, Oct 20, 2021 at 09:57:58AM -1000, Linus Torvalds wrote: > On Wed, Oct 20, 2021 at 7:44 AM Eric W. Biederman wrote: > > > > + force_sig(SIGKILL); > > I wonder if SIGFPE would be a more intuitive thing. > > Doesn't really matter, this is a "doesn't happen" event anyway, but > that was just my reaction to reading the patch. I think SIGKILL makes more sense unless there's a way the process could handle the resulting SIGFPE and recover. I'd actually like to see the lazy allocation of FPU state just removed (the amount of space saved is tiny relative to the complexity cost and the negative aspects of unrecoverable late failure) but for now let's just go with this. Rich