+++ /dev/null
-From 5c25699871112853f231e52d51c576d5c759a020 Mon Sep 17 00:00:00 2001
-From: Christoph Hellwig <hch@lst.de>
-Date: Mon, 24 Jul 2023 06:26:54 -0700
-Subject: btrfs: don't wait for writeback on clean pages in extent_write_cache_pages
-
-From: Christoph Hellwig <hch@lst.de>
-
-commit 5c25699871112853f231e52d51c576d5c759a020 upstream.
-
-__extent_writepage could have started on more pages than the one it was
-called for. This happens regularly for zoned file systems, and in theory
-could happen for compressed I/O if the worker thread was executed very
-quickly. For such pages extent_write_cache_pages waits for writeback
-to complete before moving on to the next page, which is highly inefficient
-as it blocks the flusher thread.
-
-Port over the PageDirty check that was added to write_cache_pages in
-commit 515f4a037fb ("mm: write_cache_pages optimise page cleaning") to
-fix this.
-
-CC: stable@vger.kernel.org # 4.14+
-Reviewed-by: Josef Bacik <josef@toxicpanda.com>
-Signed-off-by: Christoph Hellwig <hch@lst.de>
-Reviewed-by: David Sterba <dsterba@suse.com>
-Signed-off-by: David Sterba <dsterba@suse.com>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- fs/btrfs/extent_io.c | 6 ++++++
- 1 file changed, 6 insertions(+)
-
---- a/fs/btrfs/extent_io.c
-+++ b/fs/btrfs/extent_io.c
-@@ -4004,6 +4004,12 @@ retry:
- continue;
- }
-
-+ if (!folio_test_dirty(folio)) {
-+ /* Someone wrote it for us. */
-+ folio_unlock(folio);
-+ continue;
-+ }
-+
- if (wbc->sync_mode != WB_SYNC_NONE) {
- if (PageWriteback(page))
- flush_fn(data);
drivers-net-prevent-tun_build_skb-to-exceed-the-packet-size-limit.patch
ib-hfi1-fix-possible-panic-during-hotplug-remove.patch
btrfs-don-t-stop-integrity-writeback-too-early.patch
-btrfs-don-t-wait-for-writeback-on-clean-pages-in-extent_write_cache_pages.patch
btrfs-set-cache_block_group_error-if-we-find-an-error.patch
+++ /dev/null
-From 5c25699871112853f231e52d51c576d5c759a020 Mon Sep 17 00:00:00 2001
-From: Christoph Hellwig <hch@lst.de>
-Date: Mon, 24 Jul 2023 06:26:54 -0700
-Subject: btrfs: don't wait for writeback on clean pages in extent_write_cache_pages
-
-From: Christoph Hellwig <hch@lst.de>
-
-commit 5c25699871112853f231e52d51c576d5c759a020 upstream.
-
-__extent_writepage could have started on more pages than the one it was
-called for. This happens regularly for zoned file systems, and in theory
-could happen for compressed I/O if the worker thread was executed very
-quickly. For such pages extent_write_cache_pages waits for writeback
-to complete before moving on to the next page, which is highly inefficient
-as it blocks the flusher thread.
-
-Port over the PageDirty check that was added to write_cache_pages in
-commit 515f4a037fb ("mm: write_cache_pages optimise page cleaning") to
-fix this.
-
-CC: stable@vger.kernel.org # 4.14+
-Reviewed-by: Josef Bacik <josef@toxicpanda.com>
-Signed-off-by: Christoph Hellwig <hch@lst.de>
-Reviewed-by: David Sterba <dsterba@suse.com>
-Signed-off-by: David Sterba <dsterba@suse.com>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- fs/btrfs/extent_io.c | 6 ++++++
- 1 file changed, 6 insertions(+)
-
---- a/fs/btrfs/extent_io.c
-+++ b/fs/btrfs/extent_io.c
-@@ -4091,6 +4091,12 @@ retry:
- continue;
- }
-
-+ if (!folio_test_dirty(folio)) {
-+ /* Someone wrote it for us. */
-+ folio_unlock(folio);
-+ continue;
-+ }
-+
- if (wbc->sync_mode != WB_SYNC_NONE) {
- if (PageWriteback(page)) {
- ret = flush_write_bio(epd);
wifi-cfg80211-fix-sband-iftype-data-lookup-for-ap_vlan.patch
ibmvnic-handle-dma-unmapping-of-login-buffs-in-release-functions.patch
btrfs-don-t-stop-integrity-writeback-too-early.patch
-btrfs-don-t-wait-for-writeback-on-clean-pages-in-extent_write_cache_pages.patch
btrfs-set-cache_block_group_error-if-we-find-an-error.patch
+++ /dev/null
-From 5c25699871112853f231e52d51c576d5c759a020 Mon Sep 17 00:00:00 2001
-From: Christoph Hellwig <hch@lst.de>
-Date: Mon, 24 Jul 2023 06:26:54 -0700
-Subject: btrfs: don't wait for writeback on clean pages in extent_write_cache_pages
-
-From: Christoph Hellwig <hch@lst.de>
-
-commit 5c25699871112853f231e52d51c576d5c759a020 upstream.
-
-__extent_writepage could have started on more pages than the one it was
-called for. This happens regularly for zoned file systems, and in theory
-could happen for compressed I/O if the worker thread was executed very
-quickly. For such pages extent_write_cache_pages waits for writeback
-to complete before moving on to the next page, which is highly inefficient
-as it blocks the flusher thread.
-
-Port over the PageDirty check that was added to write_cache_pages in
-commit 515f4a037fb ("mm: write_cache_pages optimise page cleaning") to
-fix this.
-
-CC: stable@vger.kernel.org # 4.14+
-Reviewed-by: Josef Bacik <josef@toxicpanda.com>
-Signed-off-by: Christoph Hellwig <hch@lst.de>
-Reviewed-by: David Sterba <dsterba@suse.com>
-Signed-off-by: David Sterba <dsterba@suse.com>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- fs/btrfs/extent_io.c | 6 ++++++
- 1 file changed, 6 insertions(+)
-
---- a/fs/btrfs/extent_io.c
-+++ b/fs/btrfs/extent_io.c
-@@ -4201,6 +4201,12 @@ retry:
- continue;
- }
-
-+ if (!folio_test_dirty(folio)) {
-+ /* Someone wrote it for us. */
-+ folio_unlock(folio);
-+ continue;
-+ }
-+
- if (wbc->sync_mode != WB_SYNC_NONE) {
- if (PageWriteback(page)) {
- ret = flush_write_bio(epd);
ibmvnic-unmap-dma-login-rsp-buffer-on-send-login-fail.patch
ibmvnic-handle-dma-unmapping-of-login-buffs-in-release-functions.patch
btrfs-don-t-stop-integrity-writeback-too-early.patch
-btrfs-don-t-wait-for-writeback-on-clean-pages-in-extent_write_cache_pages.patch
btrfs-set-cache_block_group_error-if-we-find-an-error.patch
+++ /dev/null
-From 5c25699871112853f231e52d51c576d5c759a020 Mon Sep 17 00:00:00 2001
-From: Christoph Hellwig <hch@lst.de>
-Date: Mon, 24 Jul 2023 06:26:54 -0700
-Subject: btrfs: don't wait for writeback on clean pages in extent_write_cache_pages
-
-From: Christoph Hellwig <hch@lst.de>
-
-commit 5c25699871112853f231e52d51c576d5c759a020 upstream.
-
-__extent_writepage could have started on more pages than the one it was
-called for. This happens regularly for zoned file systems, and in theory
-could happen for compressed I/O if the worker thread was executed very
-quickly. For such pages extent_write_cache_pages waits for writeback
-to complete before moving on to the next page, which is highly inefficient
-as it blocks the flusher thread.
-
-Port over the PageDirty check that was added to write_cache_pages in
-commit 515f4a037fb ("mm: write_cache_pages optimise page cleaning") to
-fix this.
-
-CC: stable@vger.kernel.org # 4.14+
-Reviewed-by: Josef Bacik <josef@toxicpanda.com>
-Signed-off-by: Christoph Hellwig <hch@lst.de>
-Reviewed-by: David Sterba <dsterba@suse.com>
-Signed-off-by: David Sterba <dsterba@suse.com>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- fs/btrfs/extent_io.c | 6 ++++++
- 1 file changed, 6 insertions(+)
-
---- a/fs/btrfs/extent_io.c
-+++ b/fs/btrfs/extent_io.c
-@@ -5013,6 +5013,12 @@ retry:
- continue;
- }
-
-+ if (!folio_test_dirty(folio)) {
-+ /* Someone wrote it for us. */
-+ folio_unlock(folio);
-+ continue;
-+ }
-+
- if (wbc->sync_mode != WB_SYNC_NONE) {
- if (PageWriteback(page)) {
- ret = flush_write_bio(epd);
ibmvnic-unmap-dma-login-rsp-buffer-on-send-login-fail.patch
ibmvnic-handle-dma-unmapping-of-login-buffs-in-release-functions.patch
btrfs-don-t-stop-integrity-writeback-too-early.patch
-btrfs-don-t-wait-for-writeback-on-clean-pages-in-extent_write_cache_pages.patch
btrfs-exit-gracefully-if-reloc-roots-don-t-match.patch
btrfs-reject-invalid-reloc-tree-root-keys-with-stack-dump.patch
btrfs-set-cache_block_group_error-if-we-find-an-error.patch
+++ /dev/null
-From 5c25699871112853f231e52d51c576d5c759a020 Mon Sep 17 00:00:00 2001
-From: Christoph Hellwig <hch@lst.de>
-Date: Mon, 24 Jul 2023 06:26:54 -0700
-Subject: btrfs: don't wait for writeback on clean pages in extent_write_cache_pages
-
-From: Christoph Hellwig <hch@lst.de>
-
-commit 5c25699871112853f231e52d51c576d5c759a020 upstream.
-
-__extent_writepage could have started on more pages than the one it was
-called for. This happens regularly for zoned file systems, and in theory
-could happen for compressed I/O if the worker thread was executed very
-quickly. For such pages extent_write_cache_pages waits for writeback
-to complete before moving on to the next page, which is highly inefficient
-as it blocks the flusher thread.
-
-Port over the PageDirty check that was added to write_cache_pages in
-commit 515f4a037fb ("mm: write_cache_pages optimise page cleaning") to
-fix this.
-
-CC: stable@vger.kernel.org # 4.14+
-Reviewed-by: Josef Bacik <josef@toxicpanda.com>
-Signed-off-by: Christoph Hellwig <hch@lst.de>
-Reviewed-by: David Sterba <dsterba@suse.com>
-Signed-off-by: David Sterba <dsterba@suse.com>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- fs/btrfs/extent_io.c | 6 ++++++
- 1 file changed, 6 insertions(+)
-
---- a/fs/btrfs/extent_io.c
-+++ b/fs/btrfs/extent_io.c
-@@ -4191,6 +4191,12 @@ retry:
- continue;
- }
-
-+ if (!folio_test_dirty(folio)) {
-+ /* Someone wrote it for us. */
-+ folio_unlock(folio);
-+ continue;
-+ }
-+
- if (wbc->sync_mode != WB_SYNC_NONE) {
- if (PageWriteback(page)) {
- ret = flush_write_bio(epd);
net-mlx5-allow-0-for-total-host-vfs.patch
ibmvnic-handle-dma-unmapping-of-login-buffs-in-release-functions.patch
btrfs-don-t-stop-integrity-writeback-too-early.patch
-btrfs-don-t-wait-for-writeback-on-clean-pages-in-extent_write_cache_pages.patch
btrfs-set-cache_block_group_error-if-we-find-an-error.patch
+++ /dev/null
-From 5c25699871112853f231e52d51c576d5c759a020 Mon Sep 17 00:00:00 2001
-From: Christoph Hellwig <hch@lst.de>
-Date: Mon, 24 Jul 2023 06:26:54 -0700
-Subject: btrfs: don't wait for writeback on clean pages in extent_write_cache_pages
-
-From: Christoph Hellwig <hch@lst.de>
-
-commit 5c25699871112853f231e52d51c576d5c759a020 upstream.
-
-__extent_writepage could have started on more pages than the one it was
-called for. This happens regularly for zoned file systems, and in theory
-could happen for compressed I/O if the worker thread was executed very
-quickly. For such pages extent_write_cache_pages waits for writeback
-to complete before moving on to the next page, which is highly inefficient
-as it blocks the flusher thread.
-
-Port over the PageDirty check that was added to write_cache_pages in
-commit 515f4a037fb ("mm: write_cache_pages optimise page cleaning") to
-fix this.
-
-CC: stable@vger.kernel.org # 4.14+
-Reviewed-by: Josef Bacik <josef@toxicpanda.com>
-Signed-off-by: Christoph Hellwig <hch@lst.de>
-Reviewed-by: David Sterba <dsterba@suse.com>
-Signed-off-by: David Sterba <dsterba@suse.com>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----
- fs/btrfs/extent_io.c | 6 ++++++
- 1 file changed, 6 insertions(+)
-
---- a/fs/btrfs/extent_io.c
-+++ b/fs/btrfs/extent_io.c
-@@ -3181,6 +3181,12 @@ retry:
- continue;
- }
-
-+ if (!folio_test_dirty(folio)) {
-+ /* Someone wrote it for us. */
-+ folio_unlock(folio);
-+ continue;
-+ }
-+
- if (wbc->sync_mode != WB_SYNC_NONE) {
- if (PageWriteback(page))
- submit_write_bio(epd, 0);
gpio-sim-mark-the-gpio-chip-as-a-one-that-can-sleep.patch
btrfs-wait-for-actual-caching-progress-during-allocation.patch
btrfs-don-t-stop-integrity-writeback-too-early.patch
-btrfs-don-t-wait-for-writeback-on-clean-pages-in-extent_write_cache_pages.patch
btrfs-properly-clear-end-of-the-unreserved-range-in-cow_file_range.patch
btrfs-exit-gracefully-if-reloc-roots-don-t-match.patch
btrfs-reject-invalid-reloc-tree-root-keys-with-stack-dump.patch