Re: 2.4.5 troubles

clundberat_private

Yup.  That fixed it right up.  Thanks.

On Thu, 31 May 2001, Chris Wright wrote:

> * Chris Lundberg (clundberat_private) wrote:
> > Just installed the 2.4.5 kernel and the appropriate lsm patch.  I'm having
> > trouble initializing my module now (no trouble in 2.4.4)).  I've chased it
> > down to:
> >
> > int register_security (struct security_operations *ops)
> > {
> >
> >         if (verify(ops)) {
> >                 printk (KERN_INFO __FUNCTION__ " could not verify "
> >                         "security_operations structure.\n");
> >                 return -EINVAL;
> >         }
> > -->     if (security_ops != &dummy_security_ops) {
> > -->              printk (KERN_INFO "There is already a security "
> > -->                     "framework initialized, "
> > -->                     __FUNCTION__ " failed.\n");
> > -->             return -EINVAL;
> > -->     }
> >
> >         security_ops = ops;
> >
> >         return 0 ;
> > }
> >
> > It is indeed returning -EINVAL.  I haven't a clue why.  Is there something
> > that I am not doing that I should be, or something like that?  I wasn't
> > aware that the changes from 2.4.4 to 2.4.5 were that much different...
>
> I am not having this problem with any of the modules I am using with
> 2.4.5.  Is the capabilities module compiled into the kernel?  Make sure
> it is a module and try inserting your module first.
>
> -chris
>
> _______________________________________________
> linux-security-module mailing list
> linux-security-moduleat_private
> http://mail.wirex.com/mailman/listinfo/linux-security-module
>

_______________________________________________
linux-security-module mailing list
linux-security-moduleat_private
http://mail.wirex.com/mailman/listinfo/linux-security-module