Skip to contentSkip to conversation

FAILED: patch "[PATCH] ocfs2: direct write will call ocfs2_rw_unlock() twice when" failed to apply to 4.1-stable tree

PATCH [email protected] 1 participant 1 message Sep 19, 2015

Subsystems (2)
Stable branch OCFS2
lore
Share & tools
lore

[email protected]

author maintainer
#0 lore raw

The patch below does not apply to the 4.1-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.

thanks,

greg k-h

------------------ original commit in Linus's tree ------------------

Quoted 1 line

From aa1057b3dec478b20c77bad07442318ae36d893c Mon Sep 17 00:00:00 2001

From: Ryan Ding <[email protected]>
Date: Fri, 4 Sep 2015 15:42:36 -0700
Subject: [PATCH] ocfs2: direct write will call ocfs2_rw_unlock() twice when
doing aio+dio

ocfs2_file_write_iter() is usng the wrong return value ('written'). This will cause ocfs2_rw_unlock() be called both in write_iter & end_io, triggering a BUG_ON.

This issue was introduced by commit 7da839c47589 ("ocfs2: use __generic_file_write_iter()").

Orabug: 21612107

Fixes 7da839c47589 ("ocfs2: use __generic_file_write_iter()")
Signed-off-by Ryan Ding <[email protected]>
Reviewed-by Junxiao Bi <[email protected]>
Cc Al Viro <[email protected]>
Cc Mark Fasheh <[email protected]>
Cc Joel Becker <[email protected]>
Cc <[email protected]>
Signed-off-by Andrew Morton <[email protected]>
Signed-off-by Linus Torvalds <[email protected]>
fs/ocfs2/file.c +14 -14
index 7210583b472f..2eb11363b1f7 100644
@@ -2378,6 +2378,20 @@ relock:
 	/* buffered aio wouldn't have proper lock coverage today */
 	BUG_ON(written == -EIOCBQUEUED && !(iocb->ki_flags & IOCB_DIRECT));
 
+	/*
+	 * deep in g_f_a_w_n()->ocfs2_direct_IO we pass in a ocfs2_dio_end_io
+	 * function pointer which is called when o_direct io completes so that
+	 * it can unlock our rw lock.
+	 * Unfortunately there are error cases which call end_io and others
+	 * that don't.  so we don't have to unlock the rw_lock if either an
+	 * async dio is going to do it in the future or an end_io after an
+	 * error has already done it.
+	 */
+	if ((written == -EIOCBQUEUED) || (!ocfs2_iocb_is_rw_locked(iocb))) {
+		rw_level = -1;
+		unaligned_dio = 0;
+	}
+
 	if (unlikely(written <= 0))
 		goto no_sync;
 

@@ -2402,20 +2416,6 @@ relock:
 	}
 
 no_sync:
-	/*
-	 * deep in g_f_a_w_n()->ocfs2_direct_IO we pass in a ocfs2_dio_end_io
-	 * function pointer which is called when o_direct io completes so that
-	 * it can unlock our rw lock.
-	 * Unfortunately there are error cases which call end_io and others
-	 * that don't.  so we don't have to unlock the rw_lock if either an
-	 * async dio is going to do it in the future or an end_io after an
-	 * error has already done it.
-	 */
-	if ((ret == -EIOCBQUEUED) || (!ocfs2_iocb_is_rw_locked(iocb))) {
-		rw_level = -1;
-		unaligned_dio = 0;
-	}
-
 	if (unaligned_dio) {
 		ocfs2_iocb_clear_unaligned_aio(iocb);
 		mutex_unlock(&OCFS2_I(inode)->ip_unaligned_aio);