I had a situation yesterday where a processes task_lock (apparently)
wouldn't get released. That, of course, caused every single access to
/proc/PID/any_file to lock up.
There were no debug messages; everything that didn't scan the process
list worked perfectly.
Scanning through the sources, I didn't see any obvious reason why
anything should leave that lock set. Any ideas?
-- Matthias Urlichs | noris network GmbH | smurf@noris.de | ICQ: 20193661 The quote was selected randomly. Really. | http://www.noris.de/~smurf/ -- I was a house that has got over all its troubles; I don't want to spend the rest of my life bringing up a young and inexperienced house. -- Jerome K. Jerome (1859-1927)- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun May 07 2000 - 21:00:16 EST