From: Dave Hansen <dave.hansen@intel.com>
To: Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-ima-devel@lists.sourceforge.net,
linux-security-module <linux-security-module@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-crypto <linux-crypto@vger.kernel.org>,
Dmitry Kasatkin <d.kasatkin@samsung.com>
Subject: Re: [PATCH v2 1/3] ima: use ahash API for file hash calculation
Date: Wed, 02 Jul 2014 11:52:53 -0700 [thread overview]
Message-ID: <53B45505.5070507@intel.com> (raw)
In-Reply-To: <CACE9dm_S-a-ifJN4J+uU4GNy=-oP5h1PrU9x14CY1f0mnPZ-XA@mail.gmail.com>
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.
next prev parent reply other threads:[~2014-07-02 18:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 20:12 [PATCH v2 0/3] ima: use asynchronous hash API for hash calculation Dmitry Kasatkin
2014-07-01 20:12 ` [PATCH v2 1/3] ima: use ahash API for file " Dmitry Kasatkin
2014-07-02 16:40 ` Mimi Zohar
2014-07-02 18:20 ` Dmitry Kasatkin
2014-07-02 19:35 ` Mimi Zohar
2014-07-02 17:44 ` Mimi Zohar
2014-07-02 18:21 ` Dmitry Kasatkin
2014-07-02 19:38 ` Mimi Zohar
2014-07-02 18:33 ` Dave Hansen
2014-07-02 18:40 ` Dmitry Kasatkin
2014-07-02 18:52 ` Dave Hansen [this message]
2014-07-01 20:12 ` [PATCH v2 2/3] ima: introduce multi-page collect buffers Dmitry Kasatkin
2014-07-02 20:21 ` Mimi Zohar
2014-07-02 20:26 ` Dmitry Kasatkin
2014-07-01 20:12 ` [PATCH v2 3/3] ima: provide double buffering for hash calculation Dmitry Kasatkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53B45505.5070507@intel.com \
--to=dave.hansen@intel.com \
--cc=d.kasatkin@samsung.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).