In security_load_policy() and security_set_bools() we take write_lock_irq(&policy_rwlock); I want to make sure I understand why we need the _irq. Is it just because it's possible that in irq context we might come down a path that leads to a read_lock() which would deadlock against the write_lock? There is no concern for irqs to ever get to a write_lock that I can see, is that correct as well? /me playing with locking a bit.... -Eric -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.