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

Akihiro Suda: > aufs do_xino_fwrite:85:java[1077]: err -4 > aufs au_xino_do_write:439:java[1077]: I/O Error, write failed (-4) Thanks for testing. > 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,

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

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

Re: aufs_destroy_inode() deadlock?

Hello Akihiro, Akihiro Suda: > Many people are reporting that AUFS hangs up when a Java process exits. > 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, repro

aufs_destroy_inode() deadlock?

Hello, AUFS users, Many people are reporting that AUFS hangs up when a Java process exits. [1]https://github.com/docker/docker/issues/18180 (Interestingly, the problem seems particular to Java) I suspect this is a deadlock related to i_mutex operations in aufs_destroy_in