Hi Thomas,
I'm attaching a patch for the issue you reported. I've tested myself.
Could you please also try it out?
If it's OK, I'll submit a formal patch later.
Thanks,
Eric
On 06/20/2017 04:38 PM, Eric Ren wrote:
Hi!
Thanks for reporting! I will get to this issue quickly.
Eric
Sent from
Additional stack traces added.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841144
--
Russell Mosemann___
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
Another deadlock path caused by recursive locking is reported.
This kind of issue was introduced since commit 743b5f1434f5 ("ocfs2:
take inode lock in ocfs2_iop_set/get_acl()"). Two deadlock paths
have been fixed by commit b891fa5024a9 ("ocfs2: fix deadlock issue when
taking inode lock at vfs
Define an ->integrity_read file operation method to read data for
integrity hash collection.
Signed-off-by: Mimi Zohar
---
fs/ocfs2/file.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/ocfs2/file.c b/fs/ocfs2/file.c
index bfeb647459d9..2832a7c92acd 100644
---
On 05/22/17 16:17, Gang He wrote:
> This patch is used to get rid of ocfs2_is_o2cb_active() function,
> Why? First, we had the similar functions to identify which cluster
> stack is being used via osb->osb_cluster_stack. Second, the current
> implementation of ocfs2_is_o2cb_active() function is
Another deadlock path caused by recursive locking is reported.
This kind of issue was introduced since commit 743b5f1434f5 ("ocfs2:
take inode lock in ocfs2_iop_set/get_acl()"). Two deadlock paths
have been fixed by commit b891fa5024a9 ("ocfs2: fix deadlock issue when
taking inode lock at vfs