Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp975445imm; Wed, 26 Sep 2018 09:36:30 -0700 (PDT) X-Google-Smtp-Source: ACcGV61R8LtZsj4ayP+JWSGT1K7ccFfc1XGrtHt8TZO0m6ax5twSDDdzXwF7tJnzlSinxn6S8ViF X-Received: by 2002:a62:b40c:: with SMTP id h12-v6mr7153864pfn.18.1537979790411; Wed, 26 Sep 2018 09:36:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537979790; cv=none; d=google.com; s=arc-20160816; b=oWa9la2NrJoEgRM4LTako8pHrXgsoO1lgd8vRhmolzsp+FA/n4b2h/UEn9Ug0obzhf PZhg/FPFW94cuJ+u0Uc0NaFRngiIwlksOgbcIg/MQMAK2wnIR/80bXqFRSzhrNPsa3V5 qw1FWGBmQ0UM0mtiNEit9DhSy/K3ja33qgS96rn+jtNF4W9LsZxBYVMMjh1FhSi9fOLN M67vznc1E8l7aOQQTZodZ9isRk/tStyCGeX8eJ4Y+YhVVRsaOGCmtUBU5TetNHdeFBog s8nHTqNa9Kgrdr0fBF0iH1pQ0qHR1tIFZ/laX9wWUBLDDS0kak3laAAyLGxrtsTcxU9+ aFeQ== 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:message-id:subject:cc:to:from:date; bh=H6ZXXOH0TpPKGtNseiSnoF5eZtj3DCGLQ8uDdyZrWpE=; b=sICFRYwhJumHc7qapezhLEFi+vM3MAT6th3qmu2BIprFhtgE2CQvESXFqi3jgfzKed aMNwqwT6jrer6CMyqQQUCeV39uK7H+g5hZfyC0e2drqgKmU2S6dTAmiCjSyc5yRkTnoW Ov8m7X4HA243bRmOA1wFRb44xDyoQIo03BOiakJ/H8zKWh5VU3v3jBONSKuqMvlq7BDQ SR/ZUuJaI9BhSqfD0ygIPw3g367MuYXWpRDWZOZBvrWv8gjxKZlzBrLmYx5KLBuWsGLl jyTzY0ew/Elt2E55zLSuRX4GoyfPc+XmXwKfw5sa6fY+6HnoHVSoMtGu2+7T2ockUiRa z4Kw== 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 u10-v6si5858431pls.89.2018.09.26.09.36.15; Wed, 26 Sep 2018 09:36:30 -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 S1728560AbeIZWtS (ORCPT + 99 others); Wed, 26 Sep 2018 18:49:18 -0400 Received: from mail.kernel.org ([198.145.29.99]:34506 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728241AbeIZWtR (ORCPT ); Wed, 26 Sep 2018 18:49:17 -0400 Received: from vmware.local.home (cpe-66-24-56-78.stny.res.rr.com [66.24.56.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 438562147D; Wed, 26 Sep 2018 16:35:28 +0000 (UTC) Date: Wed, 26 Sep 2018 12:35:22 -0400 From: Steven Rostedt To: Kees Cook Cc: James Morris , "Serge E. Hallyn" , Abderrahmane Benbachir , linux-security-module@vger.kernel.org, Casey Schaufler , John Johansen , Tetsuo Handa , Paul Moore , Stephen Smalley , "Schaufler, Casey" , Jonathan Corbet , linux-doc@vger.kernel.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH security-next v3 04/29] LSM: Remove initcall tracing Message-ID: <20180926123522.4080d9eb@vmware.local.home> In-Reply-To: <20180925001832.18322-5-keescook@chromium.org> References: <20180925001832.18322-1-keescook@chromium.org> <20180925001832.18322-5-keescook@chromium.org> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 24 Sep 2018 17:18:07 -0700 Kees Cook wrote: > This partially reverts commit 58eacfffc417 ("init, tracing: instrument > security and console initcall trace events") since security init calls > are about to no longer resemble regular init calls. I'm not against the change, but how much are they going to "no longer resemble regular init calls"? -- Steve > > Cc: James Morris > Cc: "Serge E. Hallyn" > Cc: Abderrahmane Benbachir > Cc: Steven Rostedt (VMware) > Cc: linux-security-module@vger.kernel.org > Signed-off-by: Kees Cook > --- > security/security.c | 8 +------- > 1 file changed, 1 insertion(+), 7 deletions(-) > > diff --git a/security/security.c b/security/security.c > index 892fe6b691cf..41a5da2c7faf 100644 > --- a/security/security.c > +++ b/security/security.c > @@ -30,8 +30,6 @@ > #include > #include > > -#include > - > #define MAX_LSM_EVM_XATTR 2 > > /* Maximum number of letters for an LSM name string */ > @@ -47,17 +45,13 @@ static __initdata char chosen_lsm[SECURITY_NAME_MAX + 1] = > > static void __init do_security_initcalls(void) > { > - int ret; > initcall_t call; > initcall_entry_t *ce; > > ce = __start_lsm_info; > - trace_initcall_level("security"); > while (ce < __end_lsm_info) { > call = initcall_from_entry(ce); > - trace_initcall_start(call); > - ret = call(); > - trace_initcall_finish(call, ret); > + call(); > ce++; > } > }