From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D37E2C433DF for ; Mon, 12 Oct 2020 22:59:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7208920757 for ; Mon, 12 Oct 2020 22:59:26 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="JJQ4S6hW" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390912AbgJLW5l (ORCPT ); Mon, 12 Oct 2020 18:57:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33210 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388573AbgJLW5k (ORCPT ); Mon, 12 Oct 2020 18:57:40 -0400 Received: from mail-pf1-x441.google.com (mail-pf1-x441.google.com [IPv6:2607:f8b0:4864:20::441]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 25B47C0613D1 for ; Mon, 12 Oct 2020 15:57:39 -0700 (PDT) Received: by mail-pf1-x441.google.com with SMTP id f19so15108724pfj.11 for ; Mon, 12 Oct 2020 15:57:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=ho1l607OAVVmLnoWlMqhfwRhJkqSim+LddBz61r0Qos=; b=JJQ4S6hWNOQEK+Sy3Y+6MHvE6gOOcxmTo+VnXkRAr4YZg1jAzA2NjbHn3GiUPeK8gf 0ipw1LXDfr3tEdWE6dRrL6M12460zyb+sjoMJRNxEoEbW1Tj6e5VYs12zu49n5jFE+ag LA//Dq0oC90jGuPSuhQwam8VrIDDiTx3NpK3M= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=ho1l607OAVVmLnoWlMqhfwRhJkqSim+LddBz61r0Qos=; b=nkufcJg9JSMIz2XXwPTr8fomN09sMaEctc/1c3p7VUaOvt3g33CZQhgXNLzk66muRg ey5RU1Y0tFzk4SyvguVmMnMqhHwGCMsJSwmfMZd2uRYXUNvsd3epG6XEf5btoGn6xlFI //7cCCLFarpCWk/ZMvMsZUMwtw37ev4n8jk9aS9WEbvJ0Oq6b6s1JRv6G3ZU6xSJxOj1 DhTX/xGz1TXJIQjYQ+M9hl3jfq2OYLlgn9SBPAhWmgE3Q1pfK2SPuNZo0dyspDZKCl+G yk7PFd958wWARynmlv0GxG5U/7lWIDpLXalWe5QGr+y/AJXgkQm+xKcRNRec5ir06oPp gnCQ== X-Gm-Message-State: AOAM5322QL9Y1Voupz0i/WvhmWeTnNS5siXrreUYjUrE2SMxth5AQ9xX hoCMgpgmHg1Nxk7iblyRo84elQ== X-Google-Smtp-Source: ABdhPJxRLYOMHo59Ns0oO1+b1TTIgg1tJPZTI/F+6kwXefZKFzuOW2ptOTYCFNOKi97y0iBzVBYADg== X-Received: by 2002:a17:90a:a782:: with SMTP id f2mr2869911pjq.50.1602543458516; Mon, 12 Oct 2020 15:57:38 -0700 (PDT) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id j6sm20479216pfi.129.2020.10.12.15.57.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 12 Oct 2020 15:57:37 -0700 (PDT) Date: Mon, 12 Oct 2020 15:57:36 -0700 From: Kees Cook To: YiFei Zhu Cc: Linux Containers , YiFei Zhu , bpf , kernel list , Aleksa Sarai , Andrea Arcangeli , Andy Lutomirski , David Laight , Dimitrios Skarlatos , Giuseppe Scrivano , Hubertus Franke , Jack Chen , Jann Horn , Josep Torrellas , Tianyin Xu , Tobin Feldman-Fitzthum , Tycho Andersen , Valentin Rothberg , Will Drewry Subject: Re: [PATCH v4 seccomp 5/5] seccomp/cache: Report cache data through /proc/pid/seccomp_cache Message-ID: <202010121556.1110776B83@keescook> References: <202010091613.B671C86@keescook> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Oct 10, 2020 at 08:26:16AM -0500, YiFei Zhu wrote: > On Fri, Oct 9, 2020 at 6:14 PM Kees Cook wrote: > > HAVE_ARCH_SECCOMP_CACHE isn't used any more. I think this was left over > > from before. > > Oh, I was meant to add this to the dependencies of > SECCOMP_CACHE_DEBUG. Is this something that would make sense? I think it's fine to just have this "dangle" with a help text update of "if seccomp action caching is supported by the architecture, provide the /proc/$pid ..." -- Kees Cook