On Tue, 15 Feb 2005 18:50:45 +0100, Arnd Bergmann <[EMAIL PROTECTED]> wrote: > On Dinsdag 15 Februar 2005 02:04, Nishanth Aravamudan wrote: > > Here's at least one example: > > > > drivers/ieee1394/video1394.c:__video1394_ioctl() > > > AFAICS, that one should work just fine using after converting
<snip> > The trick here is that it is known in advance that the state does not actually > have to be protected by the lock after reading it, because the state can not > change from READY to FREE in any other place in the code. > One exception might be two processes calling the ioctl at the same time, but > I think that is racy will any of these variations. Hmm, I think you might be right, actually. So, for now, I guess it is ok to not have these macros globally available (I may end up changing my mind as I go through trying to replace other interruptible_sleep_on() callers, but I'll cross that bridge when I get to it :) Thanks, Nish - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/