* [PATCH] fstests: btrfs/182: Update the comment for the fix
@ 2020-01-29 6:10 Qu Wenruo
0 siblings, 0 replies; only message in thread
From: Qu Wenruo @ 2020-01-29 6:10 UTC (permalink / raw)
To: fstests, linux-btrfs
The mentioned fix in btrfs-progs is just a dirty fix, and only works for
the test case, not a generic fix.
The proper kernel fix is submitted by Josef, and it's on the good track to be
merged upstream.
So update the comment to make it less confusing.
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
tests/btrfs/182 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/btrfs/182 b/tests/btrfs/182
index 19b4ad8163e4..a9fbbd9b2f0d 100755
--- a/tests/btrfs/182
+++ b/tests/btrfs/182
@@ -9,8 +9,8 @@
# This is a long existing bug, caused by over-estimated metadata
# space_info::bytes_may_use.
#
-# There is one proposed patch for btrfs-progs to fix it, titled:
-# "btrfs-progs: balance: Sync the fs before balancing metadata chunks"
+# The fix is submitted with title:
+# "btrfs: use btrfs_can_overcommit in inc_block_group_ro"
#
seq=`basename $0`
seqres=$RESULT_DIR/$seq
--
2.25.0
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2020-01-29 6:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-29 6:10 [PATCH] fstests: btrfs/182: Update the comment for the fix Qu Wenruo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).