Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp4546448imm; Fri, 18 May 2018 06:58:08 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpHlykVByNeI2f/oJMMAggVkEmjfTHb3BkMTNFud0YGc/Px6f4eRUQZAwb0vb/T2B86V+XC X-Received: by 2002:a65:4789:: with SMTP id e9-v6mr7699864pgs.235.1526651888197; Fri, 18 May 2018 06:58:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526651888; cv=none; d=google.com; s=arc-20160816; b=u/+IkA+KtNivko8lyfUGeSa1+c1WRlfmOp/XvJj9pkA7iVzDYQrmCWI+xl8omadu05 YFE6sdRMr6vj+iKsHCska3zwh19On5IUQ3QF/T7u/qHc5g57yAQP1o+yk+Vk+OBQEMsx jtZkVZmsGeYJ0cNP9o6X4+Dt2er2jbYxs0TR8s/0vyyvqYa4LN/ziNKr6rvq5YR2rgvE CE0ccYCKGPhxaHX5RY8Ai+e7v8GGD6fEJiDKcT1DTUDC5wp/T083GPW+mtLGZAlC8sj1 mOj3cW1cjRBQSNAoFaJHKN+m0hUTI/bD/Vr5H4syyVygD719H/JLLvt/Z8uUAiXf/knI isow== 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 :organization:references:in-reply-to:message-id:subject:cc:to:from :date:arc-authentication-results; bh=4S0hi5vSZ+NcPkqCItyo+vLPA10D6udX33NvX8cmnC0=; b=js5o5ckxnL2CTr9dD8AizfSvk+LBCgcDCLyAxB7480KeSAEzdXntjjR3sCSMdeRlaM wTxt/t0JcvUQ/b2sjaetOHbAtNvbYC0l0s3sQ8cYMry+UsH1ffeDUIy/RxzOpeauVInj 3G1Bx8sB3+0VKOJdRYxvuPCV6tYouQLL8Lmn4yKQLjMZWQgKBushH6vPtMdhsWn5pu9N KXotx+ihiBTgs2mBxzjUZBmvy03wfyn9PHdxH/LhSUvNU+qLHwCjneNlqFJZw61ILvRV JUwtva1jWlzwGKFKVT6jR5FIslATDWru1PjkZRHG5J0IvVGys0eL+QrmyYcnTBrAU1qv 7q5g== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t1-v6si7724847plb.90.2018.05.18.06.57.52; Fri, 18 May 2018 06:58:08 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752059AbeERN5C (ORCPT + 99 others); Fri, 18 May 2018 09:57:02 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:51348 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752605AbeERN4r (ORCPT ); Fri, 18 May 2018 09:56:47 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 3B34D79D36; Fri, 18 May 2018 13:56:46 +0000 (UTC) Received: from ivy-bridge (ovpn-124-250.rdu2.redhat.com [10.10.124.250]) by smtp.corp.redhat.com (Postfix) with ESMTP id 275D41002972; Fri, 18 May 2018 13:56:34 +0000 (UTC) Date: Fri, 18 May 2018 09:56:36 -0400 From: Steve Grubb To: Richard Guy Briggs Cc: cgroups@vger.kernel.org, containers@lists.linux-foundation.org, linux-api@vger.kernel.org, Linux-Audit Mailing List , linux-fsdevel@vger.kernel.org, LKML , netdev@vger.kernel.org, ebiederm@xmission.com, luto@kernel.org, jlayton@redhat.com, carlos@redhat.com, dhowells@redhat.com, viro@zeniv.linux.org.uk, simo@redhat.com, eparis@parisplace.org, serge@hallyn.com Subject: Re: [RFC PATCH ghak32 V2 01/13] audit: add container id Message-ID: <20180518095636.56ff322d@ivy-bridge> In-Reply-To: <20180517215600.dyswlkvqdtgjwr5y@madcap2.tricolour.ca> References: <20180517170053.7d4afa87@ivy-bridge> <20180517215600.dyswlkvqdtgjwr5y@madcap2.tricolour.ca> Organization: Red Hat MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 10.11.54.3 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Fri, 18 May 2018 13:56:46 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Fri, 18 May 2018 13:56:46 +0000 (UTC) for IP:'10.11.54.3' DOMAIN:'int-mx03.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'sgrubb@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 17 May 2018 17:56:00 -0400 Richard Guy Briggs wrote: > > During syscall events, the path info is returned in a a record > > simply called AUDIT_PATH, cwd info is returned in AUDIT_CWD. So, > > rather than calling the record that gets attached to everything > > AUDIT_CONTAINER_INFO, how about simply AUDIT_CONTAINER. > > Considering the container initiation record is different than the > record to document the container involved in an otherwise normal > syscall, we need two names. I don't have a strong opinion what they > are. > > I'd prefer AUDIT_CONTAIN and AUDIT_CONTAINER_INFO so that the two > are different enough to be visually distinct while leaving > AUDIT_CONTAINERID for the field type in patch 4 ("audit: add > containerid filtering") How about AUDIT_CONTAINER for the auxiliary record? The one that starts the container, I don't have a strong opinion on. Could be AUDIT_CONTAINER_INIT, AUDIT_CONTAINER_START, AUDIT_CONTAINERID, AUDIT_CONTAINER_ID, or something else. The API call that sets the ID for filtering could be AUDIT_CID or AUDIT_CONTID if that helps decide what the initial event might be. Normally, it should match the field being filtered. Best Regards, -Steve