Re: cdrecord deadlocks linux 2.6.8.1 (problem in setscheduler)

From: Chris Wright (chrisw@private)
Date: Wed Oct 20 2004 - 12:09:41 PDT


* John Johansen (johansen@private) wrote:
> ya sorry, I ran out of time this morning and had to run to the accountant.

No problem.

> I think you are right that it likely won't fly, and that looping in the
> unlikely case of policy change is probabley better.

Yeah, let's not add an extra lock.  It's extra complexity that I think
we can avoid.  The patch I posted, (which actually doesn't loop, it just
errors out) works for me.  Wanna give it a spin?

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



This archive was generated by hypermail 2.1.3 : Wed Oct 20 2004 - 12:09:59 PDT