Received: by 10.192.165.148 with SMTP id m20csp3891872imm; Mon, 30 Apr 2018 08:07:12 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpEVEnwsy0OgGcnp5EIobP3UJ6GQIfMKoX+7CWJjpllc6AJnAP0kIDnu9eOMcH5Ajrr45S1 X-Received: by 2002:a63:7e08:: with SMTP id z8-v6mr2857144pgc.383.1525100831996; Mon, 30 Apr 2018 08:07:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525100831; cv=none; d=google.com; s=arc-20160816; b=X7quXxGZYIPWq9oDykGDRgWIqrH8MwN+JjIGe2gXxBOTM/KfTqMhlwY5FQPo2TOsUb Rf4XcAgoVXxeYwnqTJH0QeojEms+lvLgL1/6cHGKrw8hmISozGH3tIKMGBBFMb7o/R71 qeyfXbU3bpf8+2MVtH2n96FPJWgReiE7+gxulocN17UxL8DdypQEnC2q+few4rhx76QM yMyIt8dXq/V3/LXUjprYfLLLG52lmsTRZ1Gmhf4TAQ3LA9TMMCvaSVcsQbgttpAaWiiH HtD6fJkBQZv0wYpscUHc605Q4PFDlEDr+LuvBQHf6nKiVpvTZiaS4xPX+g8r0ozLxZuH TEJQ== 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:date:message-id :mime-version:subject:references:cc:to:envelope-from:from :dkim-signature:arc-authentication-results; bh=BmP5ewGpuSJPpQkrTDkQdoTg2DievcGSvpu9k/pRVvY=; b=mFu4VgBHHe1pbf+v3F1yzKOLyWej9tYNmNARoHwtBuYNt+BJymgL3kov1wdiOwcitb DYEvGrVxbBn+CMMmp4FsRXwY3hm+DeF+q30mcfd/DgNHocSpYQ1+YgLGfkBifro84wBY tlLa86ptkafvzw5En68Vk3i3Y4WdyhBs6tyCWbr6InYZtyHmeE9qpwXv/dmF7xNj4wV2 GB2NmtO4sJdh+Di8fEPyebpG0er8tKB/gsMCIEwnbY5T8oB+ULQHlcvR4gMoe6pAQPmV UE5N4lE3KT3IoJrvPcwYGZ5LUN9xFEF7Dw9sikTH5vKPnRrNiLJNOXDuRTHdgd/92ZK8 13ig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@yandex.ru header.s=mail header.b=rpfT2GPd; 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 e7-v6si7556186plk.397.2018.04.30.08.06.50; Mon, 30 Apr 2018 08:07:11 -0700 (PDT) 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; dkim=pass header.i=@yandex.ru header.s=mail header.b=rpfT2GPd; 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 S1754333AbeD3PGi (ORCPT + 99 others); Mon, 30 Apr 2018 11:06:38 -0400 Received: from forward1p.cmail.yandex.net ([77.88.31.16]:58536 "EHLO forward1p.cmail.yandex.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753691AbeD3PGh (ORCPT ); Mon, 30 Apr 2018 11:06:37 -0400 X-Greylist: delayed 303 seconds by postgrey-1.27 at vger.kernel.org; Mon, 30 Apr 2018 11:06:37 EDT Received: from mxback12g.mail.yandex.net (mxback12g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:91]) by forward1p.cmail.yandex.net (Yandex) with ESMTP id E674C20B5B; Mon, 30 Apr 2018 18:01:31 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback12g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id C0cfBUPGIN-1U001782; Mon, 30 Apr 2018 18:01:31 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1525100491; bh=BmP5ewGpuSJPpQkrTDkQdoTg2DievcGSvpu9k/pRVvY=; h=From:To:Cc:References:Subject:Message-Id:Date; b=rpfT2GPdSPYmtS0lkPGxwcVf1UZ5zBaxguIzXU7sThaRfo+BpfK2sqe8e9jCzo2/I 783m8Pi1we0SNkM/6GIyS1kyafn6qFeQ0FMbslaNMPJNmh7s3f5stGafVeGz8YkGzv ml5+6H329nM5uEfayJb0tBNawrrSrT77kkXdQd9Y= Authentication-Results: mxback12g.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: by web38o.yandex.ru with HTTP; Mon, 30 Apr 2018 18:01:30 +0300 From: Evgeniy Polyakov Envelope-From: drustafa@yandex.ru To: Stefan Strogin , Jesper Derehag , David Miller Cc: "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "xe-linux-external@cisco.com" , "matt.helsley@gmail.com" References: <20180329141247.20943-1-sstrogin@cisco.com> <20180330.125921.653839794312978457.davem@davemloft.net> <7d976488-6375-b3a8-e9d7-dc86b4c51b86@cisco.com> <32f14672-5715-3e21-ba85-b27dc8d2c6b0@gmail.com> Subject: Re: [PATCH] connector: add parent pid and tgid to coredump and exit events MIME-Version: 1.0 Message-Id: <4667631525100490@web38o.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Mon, 30 Apr 2018 18:01:30 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Stefan, hi Sorry for delay. 26.04.2018, 15:04, "Stefan Strogin" : > Hi David, Evgeniy, > > Sorry to bother you, but could you please comment about the UAPI change and the patch? With 4-bytes pid_t everything looks fine, and I do not know arch where pid is larger currently, so it looks safe. David, please pull it into your tree, or should it go via different path? Acked-by: Evgeniy Polyakov >>  I don't see how it breaks UAPI. The point is that structures >>  coredump_proc_event and exit_proc_event are members of *union* >>  event_data, thus position of the existing data in the structure is >>  unchanged. Furthermore, this change won't increase size of struct >>  proc_event, because comm_proc_event (also a member of event_data) is >>  of bigger size than the changed structures. >> >>  If I'm wrong, could you please explain what exactly will the change >>  break in UAPI? >> >>  On 30/03/18 19:59, David Miller wrote: >>>  From: Stefan Strogin >>>  Date: Thu, 29 Mar 2018 17:12:47 +0300 >>> >>>>  diff --git a/include/uapi/linux/cn_proc.h b/include/uapi/linux/cn_proc.h >>>>  index 68ff25414700..db210625cee8 100644 >>>>  --- a/include/uapi/linux/cn_proc.h >>>>  +++ b/include/uapi/linux/cn_proc.h >>>>  @@ -116,12 +116,16 @@ struct proc_event { >>>>               struct coredump_proc_event { >>>>                       __kernel_pid_t process_pid; >>>>                       __kernel_pid_t process_tgid; >>>>  + __kernel_pid_t parent_pid; >>>>  + __kernel_pid_t parent_tgid; >>>>               } coredump; >>>> >>>>               struct exit_proc_event { >>>>                       __kernel_pid_t process_pid; >>>>                       __kernel_pid_t process_tgid; >>>>                       __u32 exit_code, exit_signal; >>>>  + __kernel_pid_t parent_pid; >>>>  + __kernel_pid_t parent_tgid; >>>>               } exit; >>>> >>>>       } event_data; >>> >>>  I don't think you can add these members without breaking UAPI.