aufs_do_xino_fwrite() EINTR loop (WAS: aufs_destroy_inode() deadlock?)

[Akihiro Suda]

   Hi, Okajima-san,
   Thanks a lot for looking into this.
   After applying your patch, I got EINTR like this:
   Â aufs do_xino_fwrite:85:java[1077]: err -4
   Â aufs au_xino_do_write:439:java[1077]: I/O Error, write failed (-4)
   The patch actually worked as an ad-hoc solution for the bug, as it breaks
   the loop in do_xino_fwrite(). (it is not a mutex deadlock! sorry for the
   misunderstanding.)
   [1]https://github.com/sfjro/aufs4-linux/blob/aufs4.1/fs/aufs/xino.c#L56-L59
   I'll continue to find the source of this EINTR loop.
   Maybe this is a bug of Linux kernel itself (kernel/pid_namespace.c?) rather
   than AUFS, but I'm still not sure.
   2015-12-23 21:25 GMT+09:00 <[2]sf...@users.sourceforge.net>:

     Hello Akihiro,
     Akihiro Suda:
     > Many people are reporting that AUFS hangs up when a Java process exits.
     > [3]https://github.com/docker/docker/issues/18180
     > (Interestingly, the problem seems particular to Java)
     Thanks for reporting. This is new to me and ML.
     Here is a debug patch. Please apply, reproduce and post the [4]kern.info
     log.
     Note that the patch never solves the problem. This is just to
     investigate the problem.
     J. R. Okajima

References

   1. https://github.com/sfjro/aufs4-linux/blob/aufs4.1/fs/aufs/xino.c#L56-L59
   2. mailto:sf...@users.sourceforge.net
   3. https://github.com/docker/docker/issues/18180
   4. http://kern.info/

------------------------------------------------------------------------------