Received: by 10.213.65.68 with SMTP id h4csp1508084imn; Thu, 29 Mar 2018 06:05:47 -0700 (PDT) X-Google-Smtp-Source: AIpwx48iCW11tKNxVYkkaNuojnElBdt805z8MoZ0gYvdPjeyGFGQvxXjQMCN/jhvyeIVlN1cXnPl X-Received: by 10.98.110.71 with SMTP id j68mr6250471pfc.93.1522328746951; Thu, 29 Mar 2018 06:05:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522328746; cv=none; d=google.com; s=arc-20160816; b=jtLOfqIT0S4CKLxstsgLQywWPmMRednDdq7vWz4QBQYiVaw4/KWbKuBGWkCMxN/Lqj oyMrrNgfXGPQS27wWJC1ralju4TxjlzzunyFz1XJ5iy49Jt0WPJsadP16jiemkXgmr4Y n2Ky6O7mkXjw61oVtsUItFhr44nIcV8J+osqO9BAroM06tvH7H1P5w1aKsnDpA1DrOV+ uLzdGRfwvy4/JcLjeeU9JpwGoDuwLdgAIAqcM3mb2ddwK4tZQ2vJIlGNaC48QIeRChUN G113TuXyCtuJYu3OOC81z6rjkcFdFjAQCOoYh0tPx1w4qARFpFOLQlIjiHbYdYtQctZS gygw== 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=p6yucpxm53jj0sBPEPthUGySMo/Cpuon+0u6e1cTQa4=; b=qagQePA2JHd6vZvqEyaGglHoV1oLM7zWIHApr4eVzmxdN4niUrQ4Typ2f8wybj+dg0 2q6mhmkZKXFul+JqjEU15GWhOfn/6F2Vs3UeSh2NHy0o0yvlGZjHI1iu317XQKnzWyO4 xYKfb9KM0eOAMy4ObzrApMcyPVobzl9QkxI5Nn/QJdSEKCrl3PloyN54NrM3OQTSs0yT sA46xQkHWssBrQ0dkfxnwahGI3BfKVlSc4Up83unkTiguoY2nUs9ZKtYzvl+Kpimw37y 5rT/2Lq915ChrkfVyLPIAnredUL4JsLparzlUckByiW5D/GQ+JKPtbF9ibzS3DCXuIGG a86A== 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 y11si2516261pfk.380.2018.03.29.06.05.25; Thu, 29 Mar 2018 06:05:46 -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 S1752701AbeC2NDb (ORCPT + 99 others); Thu, 29 Mar 2018 09:03:31 -0400 Received: from ms.lwn.net ([45.79.88.28]:50814 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752487AbeC2ND3 (ORCPT ); Thu, 29 Mar 2018 09:03:29 -0400 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 1C20D2C7; Thu, 29 Mar 2018 13:03:28 +0000 (UTC) Date: Thu, 29 Mar 2018 07:03:27 -0600 From: Jonathan Corbet 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, luto@kernel.org, jlayton@redhat.com, carlos@redhat.com, viro@zeniv.linux.org.uk, dhowells@redhat.com, simo@redhat.com, eparis@parisplace.org, serge@hallyn.com, ebiederm@xmission.com, madzcar@gmail.com Subject: Re: [RFC PATCH ghak32 V2 01/13] audit: add container id Message-ID: <20180329070327.7f4c92c8@lwn.net> In-Reply-To: <20180329090132.r3qfomigkw3hbwbw@madcap2.tricolour.ca> References: <20180328123912.49b11c98@lwn.net> <20180329090132.r3qfomigkw3hbwbw@madcap2.tricolour.ca> Organization: LWN.net X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 29 Mar 2018 05:01:32 -0400 Richard Guy Briggs wrote: > > A little detail, but still... > > I am understanding that you would prefer more context (as opposed to > operational detail) in the description, laying out the use case for this > patch(set)? No, sorry, "a little detail" was referring to my comment. The use case, I believe, has been well described. Thanks, jon