[rsbac] Weird vfs log error (rsbac 1.2.3 - 2.6.9)

[kang]

I just have
Nov  9 19:31:13 localhost do_fork() [sys_fork(), sys_clone()]: 
rsbac_adf_set_attr() returned error!
Nov  9 19:31:13 localhost do_execve() [sys_execve]: rsbac_adf_set_attr() 
returned error

in kernel facility logging
rest is what i pasted already in my catch (almost) all log
this machine was running in softmode since a while, the errors happens

Which kind of error should normally be there ?

On Wed, 10 Nov 2004, Amon Ott wrote:

> On Mittwoch, 10. November 2004 01:04, kang wrote:
>> Hello list,
>> since 2.6.9, i'm getting once in a while a weird error in my log
> (not
>> rsbac log, that's system log)
>>
>> here it is:
>>
>> Nov 10 00:57:05 localhost en() [sys_open()]]]]: rsbac_adf_set_attr()
>> returned error<4>vfs_create() [open_namei() [filp_open() [do_open()
>> [sys_open()]]]]: rsbac_adf_set_attr() returned error<4>vfs_create()
>> [open_namei() [filp_open() [do_open() [sys_open()]]]]:
>> rsbac_adf_set_attr() returned error<4>vfs_create() [open_namei()
>> [filp_open() [do_open() [sys_open()]]]]: rsbac_adf_set_attr()
> returned
>> error<4>vfs_create() [open_namei() [filp_open() [do_open()
>> [sys_open()]]]]: rsbac_adf_set_attr() returned error<4>vfs_create()
>> [open_namei() [filp_open() [do_open() [sys_open()]]]]:
>> rsbac_adf_set_attr() returned error<4>vfs_create() [open_namei()
>> [filp_open() [do_open() [sys_open()]]]]: rsbac_adf_set_attr()
> returned
>> error<4>do_fork() [sys_fork(), sys_clone()]: rsbac_adf_set_attr()
>> returned error!
>
> These are warning messages that some module could not set attributes
> correctly after creating a new filesystem object or forking. It means
> that the new object or process might now have wrong attributes and
> thus wrong access rights. The missing newline in the messages has
> just been fixed in my tree.
>
> What puzzles me is that there are no other messages - in every such
> caes, there should be additional log messages. Do you have more info
> in another log file, which logs other log levels, too?
> E.g. /var/log/syslog.
>
>> pretty hard to read, I know. It sounds a bit like a filesystem error
> but
>> i'm not so sure, disk I/O seems to be ok and I've no major problems.
>
> No, these are RSBAC related.
>
> Amon.
> -- 
> http://www.rsbac.org - GnuPG: 2048g/5DEAAA30 2002-10-22
>