On Sat, Apr 30, 2016 at 07:58:36PM +0100, Al Viro wrote: > FWIW, I could reproduce that (and I really wonder WTF is going on - looks > like nfs_async_unlink_release() getting lost somehow), but not the memory > corruption with the last commit... What .config are you using? OK, I do understand the deadlock. nfs_unblock_sillyrename() doesn't issue a wakeup. If you have lookup/lookup colliding on nfs_block_sillyrename() *and* no pending delayed unlinks in that directory, you are stuck. Grr... I'll see if the obvious fix helps and push it into the queue if it does. It doesn't explain the memory corruptor, though. Could you post your .config? -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
