[rsbac] Boot problem with RSBAC

Patrique Wolfrum Patrique.Wolfrum at vwl.uni-freiburg.de
Tue Oct 28 11:58:03 MET 2003


Hello,

Bencsath Boldizsar wrote:

>I have no time tonight to find exactly, but there is an option of what
>should be the rsbac aware of at delay_init. As for standard if anything
>with major>0 is mounted it starts rsbac init. You can set a kernel option
>(... rsbac_delay_something,... this is what i ought to search) and this
>way you can set what is the 'major' of the disk after rsbac should be
>init'ed.
>If you set this to 99 , rsbac won't load at all at boot time, only if you
>run rsbac_init manually (or by a script).
>I think if you try to boot this way without rsbac and try the rsbac_init ,
>then we 'll be smarter about what happened...
>  
>
I tried it now with the suggested kernel parameter 
(rsbac_delayed_root=99:99), and one time it went well, and the next time 
the following occured during the rsbac_init (manually started after the 
system finished booting up):

Oct 28 12:57:31 kernel: rsbac_init(): Setting init timeout to 99 seconds 
(9900 jiffies).
Oct 28 12:57:31 kernel: rsbac_init(): Started rsbac_initd thread with 
pid 1191
Oct 28 12:57:31 kernel: rsbac_initd(): Initializing.
Oct 28 12:57:31 kernel: rsbac_do_init(): Initializing RSBAC v1.2.2
Oct 28 12:57:31 kernel: rsbac_do_init(): compiled modules: REG FF RC 
AUTH ACL CAP JAIL
Oct 28 12:57:31 kernel: rsbac_do_init(): Initializing memory slabs
Oct 28 12:57:31 kernel: rsbac_do_init(): Registering RSBAC proc dir
Oct 28 12:57:31 kernel: rsbac_do_init(): Initializing generic lists
Oct 28 12:57:31 kernel: rsbac_init_rc(): Initializing RSBAC: RC subsystem
Oct 28 12:57:31 kernel: rsbac_init_auth(): Initializing RSBAC: AUTH 
subsystem
Oct 28 12:57:31 kernel: rsbac_init_auth(): Registering FD lists
Oct 28 12:57:31 kernel: rsbac_init_acl(): Initializing RSBAC: ACL subsystem
Oct 28 12:57:31 kernel: rsbac_init_acl(): Group list empty on dev 08:12!
Oct 28 12:57:31 kernel: rsbac_init_acl(): Group membership list empty on 
dev 08:12!
Oct 28 12:57:31 kernel: rsbac_delay_init is set
Oct 28 12:57:31 kernel: rsbac_delayed_root is 99:99
Oct 28 12:57:31 kernel: rsbac_reg_init(): Initializing RSBAC: REG module 
and syscall registration
Oct 28 12:57:31 kernel: rsbac_do_init(): Ready.
Oct 28 12:57:31 kernel: rsbac_initd(): Exiting.
Oct 28 12:57:31 kernel: rsbacd(): Initializing.
Oct 28 12:57:31 kernel: rsbac_init(): Started rsbacd thread with pid 1192
Oct 28 12:57:31 kernel: rsbac_init(): Ready.
Oct 28 12:57:35 kernel: rsbac_get_attr(): auto-mounting device 08:10
Oct 28 12:57:35 kernel: rsbac_get_attr(): auto-mounting device 00:02
Oct 28 12:57:36 kernel: rsbac_get_attr(): auto-mounting device 08:06
Oct 28 12:57:38 kernel: rsbac_get_attr(): auto-mounting device 00:05
Oct 28 12:57:38 kernel: rsbac_acl_get_single_right(): Could not lookup 
device!
Oct 28 12:57:38 kernel: rsbac_acl_check_right(): 
rsbac_acl_get_single_right() returned error RSBAC_EINVALIDDEV! Path 
pipe:/[9417], attr , value 0, result NOT_GRANTED by ACL
Oct 28 12:57:38 kernel: filp_close() [sys_close]: ADF-call returned 
NOT_GRANTED
Oct 28 12:57:38 kernel: rsbac_acl_get_single_right(): Could not lookup 
device!
Oct 28 12:57:38 kernel: rsbac_acl_check_right(): 
rsbac_acl_get_single_right() returned error RSBAC_EINVALIDDEV!
 Path pipe:/[9417], attr , value 0, result NOT_GRANTED by ACL
Oct 28 12:57:38 kernel: filp_close() [sys_close]: ADF-call returned 
NOT_GRANTED
Oct 28 12:57:56 kernel: rsbac_get_attr(): auto-mounting device 08:08
Oct 28 12:57:58 kernel: rsbac_get_attr(): auto-mounting device 08:07

I hope this helps in finding the bug.

With best regards.
    Patrique Wolfrum



More information about the rsbac mailing list