From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 38A5EC35240 for ; Wed, 29 Jan 2020 06:10:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1AF4E207FF for ; Wed, 29 Jan 2020 06:10:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726020AbgA2GKo (ORCPT ); Wed, 29 Jan 2020 01:10:44 -0500 Received: from mx2.suse.de ([195.135.220.15]:50612 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725816AbgA2GKo (ORCPT ); Wed, 29 Jan 2020 01:10:44 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 94EDBAF9F; Wed, 29 Jan 2020 06:10:42 +0000 (UTC) From: Qu Wenruo 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 Message-Id: <20200129061036.49327-1-wqu@suse.com> X-Mailer: git-send-email 2.25.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org 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 --- 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