Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp10653099imu; Thu, 6 Dec 2018 04:47:08 -0800 (PST) X-Google-Smtp-Source: AFSGD/X5qu0oQ4DGFrCjbEE8IhytdbxDE9zY3GPC8++L04K3+plEo9XpXE2+SzwWZGvNzaUWtWVh X-Received: by 2002:a65:6094:: with SMTP id t20mr23699448pgu.285.1544100428512; Thu, 06 Dec 2018 04:47:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544100428; cv=none; d=google.com; s=arc-20160816; b=VZxDakC/lZA6zkRIoQT6Vvc1SgfIB3SbDXjT/bOIW5fuwWZhwXmeSFNoqI+TKBZj0p VEibhB73ewwiEl1nwArWZ4lRVsbYRXvKtt1/NafSMuc5iGOHgqeNLwa8FSGpnqZmpCC0 5txAkG2y01vfsZN8+6V5sfczqxQx+vtgDR3VERTwNEjCMGA2FD44T5t/Ykl7NmEV7m61 ZVdQqd8U68QGO3UIuAgQyt+6M0A+5kx9r1Z5OenN7ZFewKXno1X73czS97kO50gaOoWF KgLHcQe29Ab0esUWvbiXM0gE53WssDoTPn6bRRxvfA17eRZhY8YgzmYhlmH8mWBshrV3 7aeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=KL3aGf/R/skOaIjja6vssnZKj+DriZN1ZQFnFb/7Xx0=; b=VjX28q9c3osTJgb99Zs9GgNcCNYLrgt1ISbd32PpRDb5D50yoDhRD80Gx2ROw/3peT JoM9P1RqlDtKmiBdmPfwnRzdcJiWlE4hvEM7ok6AT0rh5FIGJFn3cEAN1ZajmZqRbr8d Ped5/0AecQ5eaoQGUQtaU/HH96M5IQ9/rJte6IoZ8nsO1YkwjOLGdNAG9P1Zik34A3U4 pKDRplSa1qz/+B2q9UoiqToVw9jDVbeTZxmOGe3pUDtiGYwfi/YAn5vpQ7opS2y+nokK i6n6fJCUu+05DosmZwmoHr06WtycOMhjD2wBUQzDSlr5g/zCS+Yb61ozHe61jpSPv2bx AWzw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y17si236505pll.10.2018.12.06.04.46.50; Thu, 06 Dec 2018 04:47:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729580AbeLFMp6 (ORCPT + 99 others); Thu, 6 Dec 2018 07:45:58 -0500 Received: from nov-007-i657.relay.mailchannels.net ([46.232.183.211]:37472 "EHLO nov-007-i657.relay.mailchannels.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729069AbeLFMp6 (ORCPT ); Thu, 6 Dec 2018 07:45:58 -0500 X-Sender-Id: novatrend|x-authuser|juerg@bitron.ch Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 9897BBE02DD; Thu, 6 Dec 2018 12:45:51 +0000 (UTC) Received: from srv17.tophost.ch (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTPA id C7472BE0216; Thu, 6 Dec 2018 12:45:42 +0000 (UTC) X-Sender-Id: novatrend|x-authuser|juerg@bitron.ch Received: from srv17.tophost.ch (srv17.tophost.ch [193.33.128.141]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.15.2); Thu, 06 Dec 2018 12:45:51 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: novatrend|x-authuser|juerg@bitron.ch X-MailChannels-Auth-Id: novatrend X-Imminent-Fearful: 4550cf1558334c97_1544100350449_1137243920 X-MC-Loop-Signature: 1544100350449:922322940 X-MC-Ingress-Time: 1544100350448 Received: from [80.219.231.201] (port=47390 helo=jzen.bitron.ch) by srv17.tophost.ch with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gUt2C-00F9ZN-Et; Thu, 06 Dec 2018 13:45:40 +0100 Message-ID: Subject: Re: [PATCH v4] signal: add taskfd_send_signal() syscall From: =?ISO-8859-1?Q?J=FCrg?= Billeter To: Florian Weimer , Christian Brauner Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, luto@kernel.org, arnd@arndb.de, ebiederm@xmission.com, serge@hallyn.com, jannh@google.com, akpm@linux-foundation.org, oleg@redhat.com, cyphar@cyphar.com, viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org, dancol@google.com, timmurray@google.com, linux-man@vger.kernel.org, keescook@chromium.org, tglx@linutronix.de, x86@kernel.org Date: Thu, 06 Dec 2018 13:45:39 +0100 In-Reply-To: <87h8fq7s84.fsf@oldenburg2.str.redhat.com> References: <20181206121858.12215-1-christian@brauner.io> <87h8fq7s84.fsf@oldenburg2.str.redhat.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.2 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-AuthUser: juerg@bitron.ch Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2018-12-06 at 13:30 +0100, Florian Weimer wrote: > * Christian Brauner: > > > /* zombies */ > > Zombies can be signaled just as any other process. No special error will be > > reported since a zombie state is an unreliable state (cf. [3]). > > I still disagree with this analysis. If I know that the target process > is still alive, and it is not, this is a persistent error condition > which can be reliably reported. Given that someone might send SIGKILL > to the process behind my back, detecting this error condition could be > useful. As I understand it, kill() behaves the same way. I think it's good that this new syscall keeps the behavior as close as possible to kill(). E.g., this would allow emulating kill() (or a higher level API equivalent) on top of taskfds without subtle differences in behavior. As the new syscall supports flags, we could consider introducing a flag that changes the behavior in the zombie case. However, I think that should be a separate discussion (after merge of the syscall) and the default behavior makes sense as is. Jürg