From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Google-Smtp-Source: AG47ELtiD9ltDT+13QsUFPCUVctxglcz5NQeP1Ev9xh3YvcSlU0aH04RkPyMyg1IR6CWgJdbs1S9 ARC-Seal: i=1; a=rsa-sha256; t=1521484112; cv=none; d=google.com; s=arc-20160816; b=J/1vE2TUInJ3uu/mnnAMYT1uZZzT1WP4dNp5DLNLJMLhmkcFTwUucgen230uSe9fR4 58VWFpzGT+tqnODTpaF6OkxNRU5zLJqnYODRC4QCnAX9sw9uwuPPRuVR5rRH7p+2HN1d A7JF2UFejVWWWv/iv5gM5sBoKpLHzMQReWvvxaN85bCtedRqQyA8hhwE54ExjLRfhaHp FR8DMRd0cxa+05gGWvgKP2sNPz6QrvX3KabozjiH4Gq5T1URlLwCuN8LtcXVavrvB0rs llXHO0ea7roWjA4HdpV4IxzEGN3Sahyyerxtz4Tkifj+sXnlRgje4DRrQivfAtpaVyHk qmCw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:user-agent:references:in-reply-to:message-id:date :subject:cc:to:from:arc-authentication-results; bh=UVe1TGMdrr286F0JseZqAWKp3QaQ/gr4JL+ijC+M1YY=; b=KxvcyJ8PMVc3OXUjdHzRCjcQdDeMdo6Iz27/5d5cDBCP8HHESqfP5Xd0UBMt3hYFdK SvQyYxQa42DoBoxpmRgSkP0ekNuwrbcEF5OCvzTbZjZtKiT8QYPj9k0XUjKrl+NLc39l SxnqfLFbDbRtxTbcKX1DM45viP2QmelEQkCK67nIF9WE1a0wH52pipg3SmTlSUDqedHD +PNx5GeRThDSUByflIYlyn/fsdZmoZMmW1u6k7ZcOLmlQw7Ns2fTrfXtMLDyRGEh6/fb WQI6PEcgOxk8D3hkeNMdgWhIY70XRusu32vMzX7kEmz+F8XZ+GHoEPxrCcAOlxXwayC+ YHVw== ARC-Authentication-Results: i=1; mx.google.com; spf=softfail (google.com: domain of transitioning gregkh@linuxfoundation.org does not designate 90.92.61.202 as permitted sender) smtp.mailfrom=gregkh@linuxfoundation.org Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning gregkh@linuxfoundation.org does not designate 90.92.61.202 as permitted sender) smtp.mailfrom=gregkh@linuxfoundation.org From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Naohiro Aota , Hans van Kranenburg , David Sterba Subject: [PATCH 4.9 236/241] btrfs: alloc_chunk: fix DUP stripe size handling Date: Mon, 19 Mar 2018 19:08:21 +0100 Message-Id: <20180319180800.945063410@linuxfoundation.org> X-Mailer: git-send-email 2.16.2 In-Reply-To: <20180319180751.172155436@linuxfoundation.org> References: <20180319180751.172155436@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-LABELS: =?utf-8?b?IlxcU2VudCI=?= X-GMAIL-THRID: =?utf-8?q?1595391036259141384?= X-GMAIL-MSGID: =?utf-8?q?1595391724885321392?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: 4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Hans van Kranenburg commit 92e222df7b8f05c565009c7383321b593eca488b upstream. In case of using DUP, we search for enough unallocated disk space on a device to hold two stripes. The devices_info[ndevs-1].max_avail that holds the amount of unallocated space found is directly assigned to stripe_size, while it's actually twice the stripe size. Later on in the code, an unconditional division of stripe_size by dev_stripes corrects the value, but in the meantime there's a check to see if the stripe_size does not exceed max_chunk_size. Since during this check stripe_size is twice the amount as intended, the check will reduce the stripe_size to max_chunk_size if the actual correct to be used stripe_size is more than half the amount of max_chunk_size. The unconditional division later tries to correct stripe_size, but will actually make sure we can't allocate more than half the max_chunk_size. Fix this by moving the division by dev_stripes before the max chunk size check, so it always contains the right value, instead of putting a duct tape division in further on to get it fixed again. Since in all other cases than DUP, dev_stripes is 1, this change only affects DUP. Other attempts in the past were made to fix this: * 37db63a400 "Btrfs: fix max chunk size check in chunk allocator" tried to fix the same problem, but still resulted in part of the code acting on a wrongly doubled stripe_size value. * 86db25785a "Btrfs: fix max chunk size on raid5/6" unintentionally broke this fix again. The real problem was already introduced with the rest of the code in 73c5de0051. The user visible result however will be that the max chunk size for DUP will suddenly double, while it's actually acting according to the limits in the code again like it was 5 years ago. Reported-by: Naohiro Aota Link: https://www.spinics.net/lists/linux-btrfs/msg69752.html Fixes: 73c5de0051 ("btrfs: quasi-round-robin for chunk allocation") Fixes: 86db25785a ("Btrfs: fix max chunk size on raid5/6") Signed-off-by: Hans van Kranenburg Reviewed-by: David Sterba [ update comment ] Signed-off-by: David Sterba Signed-off-by: Greg Kroah-Hartman --- fs/btrfs/volumes.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) --- a/fs/btrfs/volumes.c +++ b/fs/btrfs/volumes.c @@ -4748,10 +4748,13 @@ static int __btrfs_alloc_chunk(struct bt if (devs_max && ndevs > devs_max) ndevs = devs_max; /* - * the primary goal is to maximize the number of stripes, so use as many - * devices as possible, even if the stripes are not maximum sized. + * The primary goal is to maximize the number of stripes, so use as + * many devices as possible, even if the stripes are not maximum sized. + * + * The DUP profile stores more than one stripe per device, the + * max_avail is the total size so we have to adjust. */ - stripe_size = devices_info[ndevs-1].max_avail; + stripe_size = div_u64(devices_info[ndevs - 1].max_avail, dev_stripes); num_stripes = ndevs * dev_stripes; /* @@ -4791,8 +4794,6 @@ static int __btrfs_alloc_chunk(struct bt stripe_size = devices_info[ndevs-1].max_avail; } - stripe_size = div_u64(stripe_size, dev_stripes); - /* align to BTRFS_STRIPE_LEN */ stripe_size = div_u64(stripe_size, raid_stripe_len); stripe_size *= raid_stripe_len;