proc_lock is no longer an irqsave
authorBarret Rhoden <brho@cs.berkeley.edu>
Sun, 25 Apr 2010 02:09:51 +0000 (19:09 -0700)
committerKevin Klues <klueska@cs.berkeley.edu>
Thu, 3 Nov 2011 00:35:44 +0000 (17:35 -0700)
commit204d70997f92ece435e70832c5f744147ead320a
tree5bad87eb4ef848edba75185d567f5080099ea7d3
parentac1835cf94f08c782211d4ee962cabb63e52ed3e
proc_lock is no longer an irqsave

Do not grab it from interrupt context.  Technically, this includes the
monitor, if you have the CONFIG_MONITOR_ON_INT flag set.  I'll address
those issues in a later patch.  Calling schedule() from a timer
interrupt also does this.  That'll get fixed later, and probably won't
cause a problem for now.
Documentation/kernel_messages.txt
Documentation/process-internals.txt
kern/src/manager.c
kern/src/mm.c
kern/src/monitor.c
kern/src/process.c
kern/src/resource.c
kern/src/syscall.c