On Fri, Oct 26, 2007 at 01:07:50PM -0400, J. Bruce Fields wrote:
quoted text
> 
> It may take multiple steps to identify a deadlock.  With the above
> you'll miss deadlocks like
> 
> 	process 1 is requesting a lock held by process 2
> 	process 2 is blocking on a lock held by process 3
> 	process 3 is blocking on a lock held by process 1.
> 
> Could you give more details about how you're causing
> posix_locks_deadlock to hang?  Is there a simple test-case you can post?


Sorry I missed your message due to procmail filters and failure to
read linux-kernel for a week.  : )

A bit late now since you've appliead a workaround but FWIW the test
case was posted as a followup to my initial post.

--
Regards,
George
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/