[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20201109125020.634217572@linuxfoundation.org>
Date: Mon, 9 Nov 2020 13:55:09 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-kernel@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
stable@...r.kernel.org,
Ben Hutchings <ben.hutchings@...ethink.co.uk>
Subject: [PATCH 4.19 15/71] Revert "btrfs: flush write bio if we loop in extent_write_cache_pages"
From: Ben Hutchings <ben.hutchings@...ethink.co.uk>
This reverts commit 860473714cbe7fbedcf92bfe3eb6d69fae8c74ff. That
has an incorrect upstream commit reference, and was modified in a way
that conflicts with some older fixes. We can cleanly cherry-pick the
upstream commit *after* those fixes.
Signed-off-by: Ben Hutchings <ben.hutchings@...ethink.co.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
---
fs/btrfs/extent_io.c | 8 --------
1 file changed, 8 deletions(-)
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -4045,14 +4045,6 @@ retry:
*/
scanned = 1;
index = 0;
-
- /*
- * If we're looping we could run into a page that is locked by a
- * writer and that writer could be waiting on writeback for a
- * page in our current bio, and thus deadlock, so flush the
- * write bio here.
- */
- flush_write_bio(epd);
goto retry;
}
Powered by blists - more mailing lists