From: Qu Wenruo <wqu@suse.com>
To: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: [PATCH] fstests: btrfs/182: Update the comment for the fix
Date: Wed, 29 Jan 2020 14:10:36 +0800 [thread overview]
Message-ID: <20200129061036.49327-1-wqu@suse.com> (raw)
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
reply other threads:[~2020-01-29 6:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200129061036.49327-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox