[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070625013818.GC3723@sequoia.sous-sol.org>
Date: Sun, 24 Jun 2007 18:38:18 -0700
From: Chris Wright <chrisw@...s-sol.org>
To: James Morris <jmorris@...ei.org>
Cc: Chris Wright <chrisw@...s-sol.org>,
linux-security-module@...r.kernel.org,
"Serge E. Hallyn" <serue@...ibm.com>,
Andrew Morgan <agm@...gle.com>,
Andrew Morton <akpm@...gle.com>,
Stephen Smalley <sds@...ho.nsa.gov>,
lkml <linux-kernel@...r.kernel.org>,
Arjan van de Ven <arjan@...radead.org>,
Greg KH <greg@...ah.com>, Eric Paris <eparis@...hat.com>
Subject: Re: [PATCH][RFC] security: Convert LSM into a static interface
* James Morris (jmorris@...ei.org) wrote:
> On Sun, 24 Jun 2007, Chris Wright wrote:
>
> > * James Morris (jmorris@...ei.org) wrote:
> > > -module_param_named(disable, capability_disable, int, 0);
> > > -MODULE_PARM_DESC(disable, "To disable capabilities module set disable = 1");
> > > +
> > > +static int __init capability_disable_setup(char *str)
> > > +{
> > > + capability_disable = simple_strtol(str, NULL, 0);
> > > + return 1;
> > > +}
> > > +__setup("capability_disable=", capability_disable_setup);
> >
> > This changes the command line argument. Other than that and a some
> > sanity testing I'll take this.
>
> Do you mean the name change, or the logic?
>
> The name needs to change because kernel parameters are in a global
> namespace.
Sorry, I mean it's currently capability.disable (and the only reason it
matters is that at one point I know there were users of it).
thanks,
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists