Re: cdrecord deadlocks linux 2.6.8.1 (problem in setscheduler)

• Stephen Smalley (sds@epoch.ncsc.mil) wrote:
  > Works for me. However, the test may be overly strong, e.g. if policy >=
  > 0 on entry, then oldpolicy isn't used, and we don't care whether it
  > stayed the same, right?
  

Heh, I figured you'd mention that ;-) It's basically what the old behaviour is, when rq_lock serialized it.

thanks,
-chris

-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.