From: Chris Wright
Date: Fri May 14 2004 - 14:37:00 EST
* Kevin O'Connor (kevin@xxxxxxxxxxxx) wrote:
> On Thu, May 13, 2004 at 12:38:09PM -0700, Andrew Morton wrote:
> > Chris Wright <chrisw@xxxxxxxx> wrote:
> > >
> > >
> > > +static int capability_mask;
> > > +module_param_named(mask, capability_mask, int, 0);
> > > +MODULE_PARM_DESC(mask, "Mask of capability checks to ignore");
> > Is there a way to make this tunable at runtime, btw?
> I thought that was what the fourth argument to module_param_named was for..
> /* This is the fundamental function for registering boot/module
> parameters. perm sets the visibility in driverfs: 000 means it's
> not there, read bits mean it's readable, write bits mean it's
> writable. */
> #define __module_param_call(prefix, name, set, get, arg, perm) \
> Did I miss something?
No, that's right, but I didn't think it was safe enough, because it
doesn't let you register your own function to manage how the variable is
set. For example, only clearing set bits.
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/