[rsbac] Random "file not found" errors

[Amon Ott]

On Freitag 03 Juni 2005 14:40, Oliver Breuer wrote:
> here the problem occurs quite often. It occurs not only with 
virtual-fs. I even cannot compile a kernel because it stops compiling 
already after a short time complaining about some random file not 
found. When running under a non rsbac-kernel, the same compilation 
completes without errors.

This is symlinks only, or files, too?

> RSBAC Discussion and Announcements <rsbac at rsbac.org> schrieb am 
03.06.05 14:33:24:
> 
> > I have already mentioned this on this list on January 21, 2005. 
> > The problem continues on my boxes at random times and very seldom 
(a 
> > couple of times a week). The only thing that I noticed it is that 
it has 
> > to do always with some SYM-LINKS, independently if the file is 
protected
> > with RC, FF or other modules. No clue of the reason, but something 
with 
> > virtual-fs and RSBAC perhaps.
> > 
> > Andrea
> > 
> > 
> > On Thu, May 12, 2005 at 02:56:07PM +0200, Oliver Breuer wrote:
> > *  Hi all,
> > * 
> > * when using the 2.6.11-Kernel with RSBAC 1.2.4, at random times 
random
> > * files are not found when trying to access them. But this occures 
only
> > * at random times. The next try (just one second later), the file 
can be
> > * accessed. There are no log messages generated from RSBAC.
> > * 
> > * After a lot of trying I found one reproducible case:
> > * 
> > * - tmpfs mounted on /sysmnt/shmtmp/shm
> > *   -> unix-mode: rwxrwxrwt
> > * - symlink /shm -> /sysmnt/shmtmp/shm
> > * - normal user "testuser"
> > *   -> no RC-writing rights to / (only CHDIR, CLOSE, 
GET_PERMISSIONS_DATA, GET_STATUS_DATA, READ, READ_OPEN, SEARCH)
> > *   -> RC-writing rights to /sysmnt/shmtmp (APPEND, CHDIR, CLOSE, 
CREATE, DELETE, GET_PERMISSIONS_DATA, GET_STATUS_DATA, LINK_HARD, 
MODIFY_ACCESS_DATA, MODIFY_PERMISSIONS_DATA, READ, READ_WRITE_OPEN, 
READ_OPEN, RENAME, SEARCH, TRUNCATE, WRITE, WRITE_OPEN)
> > * - as user "testuser":
> > *   -> mkdir /shm/test1
> > *   -> mkdir /shm/test1/test2
> > *   -> mkdir /home/testuser/test3
> > *   -> cd /home/testuser/test3
> > *   -> ln -s /shm/test1/test2 test4
> > *   -> ls test4/
> > *     => no such file or directory!
> > *   -> ls /shm/test1/test2/
> > *     => no problems
> > * 
> > * The access through the symlink "/shm -> /sysmnt/shmtmp/shm" 
somehow doesn't work. When I boot a kernel compiled the 
same .config-file but without the rsbac-patch, there are no problems.

I will look into it on Monday.

Amon.
-- 
http://www.rsbac.org - GnuPG: 2048g/5DEAAA30 2002-10-22