Received: by 10.213.65.68 with SMTP id h4csp523035imn; Fri, 30 Mar 2018 10:00:48 -0700 (PDT) X-Google-Smtp-Source: AIpwx48ZSKYCbOflkCyJT/++xvORZR+WzowOeGj6EgA/42xvtexcRSzQ0e8rVnJ1CDwmgRlBBvnu X-Received: by 10.99.119.74 with SMTP id s71mr8900626pgc.321.1522429248168; Fri, 30 Mar 2018 10:00:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522429248; cv=none; d=google.com; s=arc-20160816; b=ygFptpL8buOQgEF5QH5tbumJ3vMXuh5ZvTWxe2G8icpAcCHl4ngOwgGhJkzYu4YyGJ gvNnTpNnGuxJNl/fljFVEvt0aVOs7bRmnQWJ0kMFIKm4hBXonIhpYHPb3eI+xfekfsiH fBW8q0KizZ2+capJC77Jmdum2K3lfKWFWeooZROpugQeRK8MCir2dTpTNpyF70Hv9RL8 0qeyjCcWTHooTXbXiXgm1OXwP9u3UcT/FCJ/ECy6vaLRb0ZgZbm4bn5B2ztwq7OAbFy8 DYSPknVMAMyLbZ4d8KKujv1zCOUcEuJCGo1rpP5+44WlOmIIR5FXDQFBMk0kdCbeCFjX WFJA== 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 :references:in-reply-to:from:subject:cc:to:message-id:date :arc-authentication-results; bh=p9qfDIaD7oAWYCRWnmS41LEv1wbBR4SE9YoubR9RWFA=; b=q8sK1x6uOZ6LnvriIju1+3oUZXviH8KkR0jqmMnuXktrI/InmsE+ZiRBGDDaFvXyP2 36N1+v6eN4xR63CHSu/8G6P/04wQe9Hv7NzjGFPAHCxmT4bdQTTpU96jjEX1sGwrMwsu GkdhwSDp3ENBf/DNpFCqmolzv+LCb0XTt8P2sxhk69A4NSSNEPW4gRcjiQKYffG8+etf oIGmjB5kZHpMUq4gHxQS/9CZ8jQ9OUBDu5IkbrfimbZRGEQsMj5Q8C2oe1HxBCWVfq8o 65d5ZVyizKXdOV3RgN6ugH1W5af8eBZo5KYMYJqVkp//5SNtd77quDOyH4X7Z5oi8obu XT6w== 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 f5si5660543pgv.668.2018.03.30.10.00.34; Fri, 30 Mar 2018 10:00:48 -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; 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 S1752197AbeC3Q7Y (ORCPT + 99 others); Fri, 30 Mar 2018 12:59:24 -0400 Received: from shards.monkeyblade.net ([184.105.139.130]:33198 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750794AbeC3Q7W (ORCPT ); Fri, 30 Mar 2018 12:59:22 -0400 Received: from localhost (67.110.78.66.ptr.us.xo.net [67.110.78.66]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id B83EC123C4B96; Fri, 30 Mar 2018 09:59:21 -0700 (PDT) Date: Fri, 30 Mar 2018 12:59:21 -0400 (EDT) Message-Id: <20180330.125921.653839794312978457.davem@davemloft.net> To: sstrogin@cisco.com Cc: zbr@ioremap.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, xe-linux-external@cisco.com, jderehag@hotmail.com, matt.helsley@gmail.com, minipli@googlemail.com Subject: Re: [PATCH] connector: add parent pid and tgid to coredump and exit events From: David Miller In-Reply-To: <20180329141247.20943-1-sstrogin@cisco.com> References: <20180329141247.20943-1-sstrogin@cisco.com> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Fri, 30 Mar 2018 09:59:22 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.