Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1036111imu; Wed, 23 Jan 2019 09:44:02 -0800 (PST) X-Google-Smtp-Source: ALg8bN4Q70XIUuBtiyAsHuwRIOPqaBv8ccnj5v1uYlSx2/0TST0km7OnwqgfgIO0RNeoi7D1sd0P X-Received: by 2002:a65:500c:: with SMTP id f12mr2775722pgo.226.1548265442412; Wed, 23 Jan 2019 09:44:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548265442; cv=none; d=google.com; s=arc-20160816; b=VFV8iAlhda6VMgqvqueY5DeuVvAnRyJOXF/I10f+88Mfn3RB9oxeXkSUVq//7KNFht 8wkHhyBHEVakXN5xVQs5qfl5DXUDbNBV3uSupmnRiSthGT2KgHl6qrRbF8YkTtAiiTkt cA7YirsbP5ZlGB/cWQintBd7ZSoOOwVNRbRDWBYbxVGxxkhwikpjGtu4yBluyLXiuE3i nzDryNyxQ/sfGhRgMtuZbCgO+aqYqrPa2lAjkzsigcu/G1rrDIFGU9y2Xl7nEvID02hm vmYL8+BuT7+j+vK5E9TsNf05NfmdOI/VARhz9Vb2D5IOvgMSAdHpoMwxv4RObm4fetSL /cxA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :reply-to:message-id:subject:cc:to:from:date; bh=BaBtlZGVZmL1zQqGB4ysxC39BMuCzFnwHCZtsIeQybI=; b=DOPUCRVE+K/fPE5uu9qZweBwGDxVG4ZEOjHWGsLSOnx8hf0zgA3+XH7awnnQSA0iLm I8LJl7dJThh6LYgkkXtgsz3i2lkg5RkdlUL1y5T84KkWBxvIRc3m4nr+XYXnrl/58GUg 6gewcgDC59rFNEjW+QKNYhAHxxPgDdu2gCsZF0DEr44u/TQ17Xcilj/4d1nGqzUzBnHu 4fW11VN7w0ZYBM3ixwmF5qVd+ihgy5poZ97lI6PJ2mcFT468ec3t/kReP4PFUS/SJ6jT hmZtLEs95hqu7MBfmjlBGQ3LrOGCE2X/q6/stBnGfKv0sd0p5u5TNHWxKMJaJooBiprB MKIw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p9si20171204pll.63.2019.01.23.09.43.46; Wed, 23 Jan 2019 09:44:02 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726647AbfAWRmX (ORCPT + 99 others); Wed, 23 Jan 2019 12:42:23 -0500 Received: from mx2.suse.de ([195.135.220.15]:38464 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726038AbfAWRmX (ORCPT ); Wed, 23 Jan 2019 12:42:23 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 97433B080; Wed, 23 Jan 2019 17:42:21 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id E3A26DA6F5; Wed, 23 Jan 2019 18:41:48 +0100 (CET) Date: Wed, 23 Jan 2019 18:41:47 +0100 From: David Sterba To: Hans van Kranenburg Cc: Sasha Levin , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , David Sterba , "linux-btrfs@vger.kernel.org" Subject: Re: [PATCH AUTOSEL 4.20 072/117] btrfs: alloc_chunk: fix more DUP stripe size handling Message-ID: <20190123174146.GV2900@twin.jikos.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Hans van Kranenburg , Sasha Levin , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , David Sterba , "linux-btrfs@vger.kernel.org" References: <20190108192628.121270-1-sashal@kernel.org> <20190108192628.121270-72-sashal@kernel.org> <783ccf1f-65df-d388-079c-9449d4319c27@mendix.com> <20190123143732.GL202535@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 23, 2019 at 03:54:00PM +0000, Hans van Kranenburg wrote: > On 1/23/19 3:37 PM, Sasha Levin wrote: > > On Tue, Jan 08, 2019 at 11:52:02PM +0000, Hans van Kranenburg wrote: > >> Hi Sasha, > >> > >> On 1/8/19 8:25 PM, Sasha Levin wrote: > >>> From: Hans van Kranenburg > >>> > >>> [ Upstream commit baf92114c7e6dd6124aa3d506e4bc4b694da3bc3 ] > >>> > >>> Commit 92e222df7b "btrfs: alloc_chunk: fix DUP stripe size handling" > >>> fixed calculating the stripe_size for a new DUP chunk. > >> > >> That one also ended up as: > >> > >> 4.14-stable > >> 0136bd7238b2cb8238426af4183ed0b02165c3f9 > >> > >> 4.9-stable > >> 8890bae03f4dba1c2292e5445682b556af4e8f1b > >> > >> 4.4-stable > >> 97c3e46ef53748278286fc09dcc30b138d6677c4 > >> > >> 3.16.57-rc1 > >> f68f46284a199f6837c1d5b94a6ae979a2cc463c > >> > >> While hitting the failure condition without adding "crafting" steps to > >> make it exactly match the scenario is unlikely, it might be good if we > >> just go all the way back with this regression fix? > > > > What do you mean with "all the way back"? > > Oh, apologies for not using unambigious phrasing. > > I mean, it seems the autoselection only found 92e222df7b in places where > it's actually called 92e222df7b, and not where it was cherry-picked. > > So, for my own understanding: If I have to do something like this ever > again, then should I have added it like this inside baf92114c? > > Fixes: 92e222df7b ("btrfs: alloc_chunk: fix DUP stripe size handling") > Fixes: 0136bd7238 ("btrfs: alloc_chunk: fix DUP stripe size handling") > Fixes: 8890bae03f ("btrfs: alloc_chunk: fix DUP stripe size handling") > Fixes: 97c3e46ef5 ("btrfs: alloc_chunk: fix DUP stripe size handling") > Fixes: f68f46284a ("btrfs: alloc_chunk: fix DUP stripe size handling") The Fixes: tag should always refer to a commit id in Linus' tree, the stable tree backports use that for common reference so the individual commit ids of stable trees are not relevant.