>>> On 05.04.16 at 16:19, <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > Which /proc file is it that causes the read/write/lseek path to then > presumably recurse into another read/write/lseek and cause a deadlock? > Are there perhaps other cases we'd need to worry about? It was /proc/xen/xenbus, which doesn't exist in the upstream kernel (it's replacement is a miscdev at /dev/xen/xenbus there), hence I didn't really consider it feasible to include that additional information in the commit message. If you're nevertheless interested in the details, I can try to reconstruct that from the report (I didn't observe the problem myself, it was just reasonably straightforward to find the cause of it), or I could point you at the (openSUSE) bug report. Jan -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
