Re: 1.0.9b-pre2 uploaded

From: ao@morpork.shnet.org (A. Ott)
Subject: Re: 1.0.9b-pre2 uploaded
Date: 25 Feb 2000 13:17:00 +0100

Next Article (by Subject): Re: 1.0.9b-pre2 uploaded Jesse Pollard
Previous Article (by Subject): Re: 1.0.9b-pre2 uploaded ao@morpork.shnet.org (A. Ott)
Top of Thread: 1.0.9b-pre2 uploaded ao@morpork.shnet.org (A. Ott)
Next in Thread: Re: 1.0.9b-pre2 uploaded Jesse Pollard
Articles sorted by: [Date] [Author] [Subject]

********* ***************** ********** ****  *****   ***** ************
  To subject Re: 1.0.9b-pre2 uploaded
  ao@morpork.shnet.org (A. Ott)  wrote:
********** ******************** ******  ********  ******* *************

> ********* ***************** ********** ****  *****   ***** ************
>   To subject Re: 1.0.9b-pre2 uploaded
>   pollard@dns1.navo.hpc.mil (Jesse Pollard)  wrote:
> ********** ******************** ******  ********  ******* *************
> > I have installed the RSBAC patches (for 2.2.13 - not all documents have
> > been updated yet), created a maintenance and secure kernel.
> >
> > And unfortunately, I don't have a free partition to stick it on. I do have
> > a backup system partition however (I don't fully count that as a free
> > partition).
> >
> > I booted both maintenance and secured kernels just to see what would
> > happen; they both hung after reporting the "can't compeletely read..."
> > messages.
>
> This is sure a locking issue. What exactly was the last message that
> appeared, so we can nail the part down? What, if using kernel param
> rsbac_debug_all (Warning: loads of messages!)?
>
> > I was wondering if the problem may be related to accepting the default
> > RSBAC options.
>
> No, definately not. You would get RSBAC logging messages with lots of
> NOT_GRANTED, if the settings were wrong.
> >
> > The hang appeared to occur at the end of the RSBAC initialization. The
> > sections after that in my boot sequence are to complete the single user
> > list - loading modules for filesystems, controller, network, sound card
> > ... Then the multi-user startup.
>
> S.a.: This must be a locking problem. I will recheck the spinlocks used
> during init. I would like to get those hangs fixed before releasing
> 1.0.9b-final. This is why I asked for SMP help.

I did some locking changes and found some read locks where there should  
have been write locks. I will wait for your answer to my previous post, do  
some more checks and build a pre3 for SMP testing.

Amon.

--
Please remove second ao for E-Mail reply - no spam please!
## CrossPoint v3.11 ##
-
To unsubscribe from the rsbac list, send a mail to
majordomo@morpork.shnet.org with
unsubscribe rsbac
as single line in the body.

Go to Compuniverse LWGate Home Page.