public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH 6.12 1/2] Revert "btrfs: avoid monopolizing a core when activating a swap file"
@ 2025-02-06 16:22 Koichiro Den
  2025-02-06 16:22 ` [PATCH 6.12 2/2] btrfs: avoid monopolizing a core when activating a swap file Koichiro Den
  2025-02-07 22:51 ` [PATCH 6.12 1/2] Revert "btrfs: avoid monopolizing a core when activating a swap file" Sasha Levin
  0 siblings, 2 replies; 3+ messages in thread
From: Koichiro Den @ 2025-02-06 16:22 UTC (permalink / raw)
  To: gregkh, stable; +Cc: wqu, fdmanana, dsterba

This reverts commit 9f372e86b9bd1914df58c8f6e30939b7a224c6b0.

The backport for linux-6.12.y, commit 9f372e86b9bd ("btrfs: avoid
monopolizing a core when activating a swap file"), inserted
cond_resched() in the wrong location.

Revert it now; a subsequent commit will re-backport the original patch.

Fixes: 9f372e86b9bd ("btrfs: avoid monopolizing a core when activating a swap file") # linux-6.12.y
Signed-off-by: Koichiro Den <koichiro.den@canonical.com>
---
 fs/btrfs/inode.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index a3c861b2a6d2..a74a09cf622d 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -7117,8 +7117,6 @@ noinline int can_nocow_extent(struct inode *inode, u64 offset, u64 *len,
 			ret = -EAGAIN;
 			goto out;
 		}
-
-		cond_resched();
 	}
 
 	if (file_extent)
-- 
2.45.2


^ permalink raw reply related	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-02-07 22:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-02-06 16:22 [PATCH 6.12 1/2] Revert "btrfs: avoid monopolizing a core when activating a swap file" Koichiro Den
2025-02-06 16:22 ` [PATCH 6.12 2/2] btrfs: avoid monopolizing a core when activating a swap file Koichiro Den
2025-02-07 22:51 ` [PATCH 6.12 1/2] Revert "btrfs: avoid monopolizing a core when activating a swap file" Sasha Levin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox