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=-7.5 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 AD970C433E6 for ; Tue, 1 Sep 2020 16:36:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7CEA52087D for ; Tue, 1 Sep 2020 16:36:57 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="ICh1zf3z" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730680AbgIAQgx (ORCPT ); Tue, 1 Sep 2020 12:36:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36256 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729301AbgIAQgk (ORCPT ); Tue, 1 Sep 2020 12:36:40 -0400 Received: from mail-pl1-x641.google.com (mail-pl1-x641.google.com [IPv6:2607:f8b0:4864:20::641]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 15FA5C061244; Tue, 1 Sep 2020 09:36:39 -0700 (PDT) Received: by mail-pl1-x641.google.com with SMTP id y6so794645plk.10; Tue, 01 Sep 2020 09:36:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=6LJNp3SfPZQzgGoLbBE6N8TqVacFA/OYrfyGljmiagI=; b=ICh1zf3zGn7XnEwLtLXWBXdrXz03RkOwx69AHgL9W4kNO36ZTyq4x0oYmzBehu8awg H4s2r0Y5X6xbC/FNLDnAb4GVLCb9yQdELSo/Q8tZoz5VxuM8t5v027lrHZfB1+jP7Fo7 dRkz81Zj6At5l+CA1aYdgCtRFFvWKsv0tjeGrrTSsJtP0EvC3uuvIl7/xaUtH4rcE9zV HfK+Ue8YUa95CemaV+ILl9zRx3EnJ9mykPNSuoC6YwuXh0rEGidwyZdP2l8rfr8kytTk nc3KvUvz21A03NC6SBXoZEdnC74IcgDh8hpd3eC1/ESEi3+YI5lYKq4kbyrz28E0LEIB kLLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=6LJNp3SfPZQzgGoLbBE6N8TqVacFA/OYrfyGljmiagI=; b=Kt080CfEFZ4mbSheKf2P4tNa5zRn/janx73a4edNJzeGKzDPe1fcVTaAOxS7ST9cCV TLEsAqNZ7+Td0FsWbhC9uiz5lSPd91o2JDVdRlgfg1eCW7zHQ9uFPSOfcINYiE2y172C kSGpPQlGatHB3QMJ0TA5Wm2GyUYW9fKoW/gKB7K+qDCmpEO2GBrCkrsr9DiFF7DR8hH1 mboxqTJ4qALm7iHgOJXhwe6XxsmtChrRh0o7R44INS7qTDTIB8ljO5vYxzvs76656WjV mWOEWHts7OqP5ZmmKnvNk0ZFnEM4aTiHlf3YtkpPvnXyzl9AMx12RPdM02l/v0UXIPex twsg== X-Gm-Message-State: AOAM533OmNqv7bue68WcYgBmZEzae0InmlTWVL+HOwNv1a/RAbdpWwmG 4MP8hp2aOdVu4kz3xqYYIYs= X-Google-Smtp-Source: ABdhPJwjKrOK7WaCiEzd+HbASOS0a4uBs7I11ulx5TrI35FSx0o5kfHkjravTXJH/V/xrrCIgPhiAg== X-Received: by 2002:a17:90b:110:: with SMTP id p16mr2361655pjz.98.1598978198498; Tue, 01 Sep 2020 09:36:38 -0700 (PDT) Received: from [192.168.1.3] (ip68-111-84-250.oc.oc.cox.net. [68.111.84.250]) by smtp.gmail.com with ESMTPSA id y7sm2452654pfm.68.2020.09.01.09.36.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 01 Sep 2020 09:36:37 -0700 (PDT) Subject: Re: RFC: backport of commit a32c1c61212d To: Doug Berger , Greg Kroah-Hartman Cc: stable@vger.kernel.org, Andrew Morton , Mike Rapoport , Pavel Tatashin , Russell King , Michal Hocko , Olof Johansson , Zhaoyang Huang , zhaoyang , Ingo Molnar , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, David Hildenbrand , Baoquan He References: <20200901140018.GD397411@kroah.com> <4eb51ae0-427d-5359-2439-b38dc0d3b2e5@gmail.com> From: Florian Fainelli Message-ID: <98f2309c-e674-c3fc-0c13-0bf85f123f8c@gmail.com> Date: Tue, 1 Sep 2020 09:36:36 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.1.1 MIME-Version: 1.0 In-Reply-To: <4eb51ae0-427d-5359-2439-b38dc0d3b2e5@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/1/2020 9:06 AM, Doug Berger wrote: > On 9/1/2020 7:00 AM, Greg Kroah-Hartman wrote: [snip] > Sorry for the confusion, but thanks for the reply. > > There is functionality that exists in Linus' tree, but it is not the > result of a single commit that can be easily backported. I have been > unable to find anything in the documentation for submitting a patch to a > stable branch that covers this type of submission so I have sent this as > an RFC about process rather than a patch. > > The upstream commit that ultimately results in the functional change is: > commit a32c1c61212d ("arm: simplify detection of memory zone boundaries") > > That commit is dependent on other commits that aren't necessary for the > stable branches. > > In my downstream kernel I would apply the single line patch included in > my original email, but it is not appropriate to apply that patch to > Linus' tree since the problem does not exist there. > > This creates the situation where a simple patch could be applied to a > stable branch to improve its stability, but there is not a clear > upstream commit to reference. > > My best guess at this point is to submit patches to the affected stable > branches like the one in my RFC and reference a32c1c61212d as the > upstream commit. This would be confusing to anyone that tried to compare > the submitted patch with the upstream patch since they > wouldn't look at all alike, but the fixes and upstream tags would define > the affected range in Linus' tree. > > I would appreciate any guidance on how best to handle this kind of > situation. You could submit various patches with [PATCH stable x.y] in the subject to indicate they are targeting a specific stable branch, copy stable@vger.kernel.org as well as all recipients in this email and see if that works. Not sure if there is a more documented process than that. -- Florian