From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
zohar@us.ibm.com, linux-kernel@vger.kernel.org,
eparis@redhat.com, torvalds@linux-foundation.org,
James Morris <jmorris@namei.org>
Subject: Re: [PATCH] allow disabling IMA at runtime
Date: Thu, 27 Aug 2009 19:49:19 +0930 [thread overview]
Message-ID: <200908271949.20185.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090826170225.7574759e.akpm@linux-foundation.org>
On Thu, 27 Aug 2009 09:32:25 am Andrew Morton wrote:
> From my reading of kernel/params.c:parse_args(), every __setup()
> function which returns `1' should result in printk("%s: `%s' invalid
> for parameter `%s'), so I'm all confused and giving up.
Nope, it's an "obsolete_param", so non-zero means success.
> > +__setup("ima=", ima_enabled);
>
> Are we supposed to use core_param() nowadays?
Yeah, if this had backwards compatibility requirements. But for new,
non-core params like this:
1) make sure the module is called "ima" (even if not a module: make the
object ima.o)
2) use module_param(), and make your parameters "disable" and "audit"
(ima_disable and ima_audit if must be nonstatic and use module_param_named).
You don't need to write any parse functions at all!
3) Tell users to use ima.disable and ima.audit.
Thanks,
Rusty.
next prev parent reply other threads:[~2009-08-27 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 2:10 [PATCH] allow disabling IMA at runtime Kyle McMartin
2009-08-26 12:07 ` Mimi Zohar
2009-08-26 12:17 ` Eric Paris
2009-08-27 0:02 ` Andrew Morton
2009-08-27 5:47 ` James Morris
2009-08-27 10:19 ` Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-27 12:30 David Safford
2009-08-27 12:57 ` Eric Paris
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=200908271949.20185.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zohar@us.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