From: Dave Hansen Subject: Re: [PATCH v2 1/3] ima: use ahash API for file hash calculation Date: Wed, 02 Jul 2014 11:52:53 -0700 Message-ID: <53B45505.5070507@intel.com> References: <72d68808fd8db2b896a459b120f3e550e5f976c1.1404245510.git.d.kasatkin@samsung.com> <53B45095.80102@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Mimi Zohar , linux-ima-devel@lists.sourceforge.net, linux-security-module , "linux-kernel@vger.kernel.org" , linux-crypto , Dmitry Kasatkin To: Dmitry Kasatkin Return-path: Received: from mga09.intel.com ([134.134.136.24]:58513 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754536AbaGBSxI (ORCPT ); Wed, 2 Jul 2014 14:53:08 -0400 In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-ID: On 07/02/2014 11:40 AM, Dmitry Kasatkin wrote: >> > We should reserve command-line parameters for things that really need >> > tweaking in early boot or are _needed_ to boot. ... > Is module param good enough or it should be sysctl? Doesn't matter to me much. sysctls seem to be the easiest things to configure and make persistent. I'm not sure if the normal /etc/modprobe.d things work for built-in features, but if they do I'd say a modparam is fine.