Received: by 2002:a05:7412:3b8b:b0:fc:a2b0:25d7 with SMTP id nd11csp1044893rdb; Fri, 9 Feb 2024 08:40:48 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCVqmObuZWOfL7viSUSSybMgUyEZD8mrT3uezwAtxukZsd1GJfskTiHmHEhoFciDomvn3RyfS3Tj5s1b5sXjfkapkADBVamQrMr8EVTuqA== X-Google-Smtp-Source: AGHT+IG35dPY6xnDy8Eyr2oBisDz2T4/zo3VhJl6AA8iqfaB2lKGNg7noCn7g69wup4RaZdJfBOe X-Received: by 2002:a17:906:e213:b0:a3c:d6f:4788 with SMTP id gf19-20020a170906e21300b00a3c0d6f4788mr501468ejb.48.1707496848547; Fri, 09 Feb 2024 08:40:48 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCXXNbo53zbj/IBB//S3KTc6ejeMIPKf1yxpP182H/EYnfjceHNSyB2d4JRbSNyUkkcNqP5Y1E0Eu/m2iZyWm54Iue7mIYN/lc+iTfAwPg== Return-Path: Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [147.75.80.249]) by mx.google.com with ESMTPS id v16-20020a1709060b5000b00a387f424647si1012919ejg.800.2024.02.09.08.40.48 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 09 Feb 2024 08:40:48 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-59619-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@redhat.com header.s=mimecast20190719 header.b=POmLrgOx; arc=fail (body hash mismatch); spf=pass (google.com: domain of linux-kernel+bounces-59619-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) smtp.mailfrom="linux-kernel+bounces-59619-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by am.mirrors.kernel.org (Postfix) with ESMTPS id 203B21F22592 for ; Fri, 9 Feb 2024 16:40:48 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 4DCE67B3FF; Fri, 9 Feb 2024 16:40:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="POmLrgOx" Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 129347691B for ; Fri, 9 Feb 2024 16:40:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707496840; cv=none; b=fjFQ/jiBPwiglZidrzcVmt/Sc+vAUjD9/DFmfIPModO59td5sxwnmAvIupUKbRlx7+nr/6DeEamqR4Nnq1zBTHBQF8TmEBMDGtygzZ3j2JLNvGaQw6ODWU9VO/n3dadg1qUywmJtxbBqth34UmEfwn2rdVctokDIImO2o29tIjE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707496840; c=relaxed/simple; bh=QWA/960C0OvEZHcS8yLgjPfOLmmCZE7fkhbKn7qioA0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=D/jHP23L/XnHraAxqKl4D8rDZuRUGap8LOPD3AQFifxKVCPa1K4co6MbiGEwMYXExP4v9LzBuFc+wzXECqJG/F68gvP/0BK3nBSr7mJAjEKOmLS/ND+YbLY8VlgWds4gP9shmW9bDtQNpaWgQdS4M4hS/fRsx4cBRZtN2+mpr5c= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=POmLrgOx; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1707496838; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=3ZYBw4xEyhcf/nGZTwXmlIzT8+wX9rv4YZJK1yqjVjI=; b=POmLrgOxvBP2uycgzyzrXWtnTmLMegF7eZ+0saEXd8AADebk6OFxHMpBMwnIZeDphvrYT3 pSwaKrNkJhg1D0NYWG1er3AZU+KiSBYRK0VyTWItWsvAwLuGD++LzoR3g9oEycm5FRfp1o G5hzm7zvqQBKIRl0CO0fbCwcqkVJfdc= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-670-8PQEj3GYMC-K35ffYqZ28g-1; Fri, 09 Feb 2024 11:40:33 -0500 X-MC-Unique: 8PQEj3GYMC-K35ffYqZ28g-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 2ADEC83B8ED; Fri, 9 Feb 2024 16:40:33 +0000 (UTC) Received: from dhcp-27-174.brq.redhat.com (unknown [10.45.226.84]) by smtp.corp.redhat.com (Postfix) with SMTP id 7E6E91103A; Fri, 9 Feb 2024 16:40:31 +0000 (UTC) Received: by dhcp-27-174.brq.redhat.com (nbSMTP-1.00) for uid 1000 oleg@redhat.com; Fri, 9 Feb 2024 17:39:16 +0100 (CET) Date: Fri, 9 Feb 2024 17:39:14 +0100 From: Oleg Nesterov To: "Eric W. Biederman" Cc: Christian Brauner , Andy Lutomirski , Tycho Andersen , linux-api@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/2] signal: add the "int si_code" arg to prepare_kill_siginfo() Message-ID: <20240209163914.GE3282@redhat.com> References: <20240209130620.GA8039@redhat.com> <87sf21zjy8.fsf@email.froward.int.ebiederm.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87sf21zjy8.fsf@email.froward.int.ebiederm.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.5 On 02/09, Eric W. Biederman wrote: > > Could you can pass in the destination type instead of the si_code? > Something like I have shown below? .. > info->si_code = (type == PIDTYPE_PID) ? SI_TKILL : SI_USER; Yes, I considered this option too. OK, will send V3 tomorrow. Oleg.