Sergio Lopez, le Thu 08 Apr 2010 13:15:20 +0200, a écrit : > > So it's really hung in the kernel. And indeed, even if from > > the interface it would seem like it could be asynchronous, > > the memory_object_lock_completed() call is done from the > > memory_object_lock_request function itself... > > > > But even if m_o_lock_completed is called from m_o_lock_request, that > answer should come in another message,
Right, but it still means that m_o_lock_request doesn't return before having completed its job... > If a thread is stalled in mach_msg_trap(), that means the kernel can't > enqueue the message for some reason (and this is very, very bad). Is > possible that ext2fs had a huge number of threads at that moment? No, just a few dozens. Samuel
