[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3a8857fd-d4f2-7743-d2e8-8580145d32e7@huawei.com>
Date: Tue, 14 Sep 2021 17:27:32 +0800
From: Miaohe Lin <linmiaohe@...wei.com>
To: Michal Hocko <mhocko@...e.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>, <vbabka@...e.cz>,
<linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] mm/page_isolation: fix potential missing call to
unset_migratetype_isolate()
On 2021/9/14 15:06, Michal Hocko wrote:
> On Tue 14-09-21 11:09:47, Miaohe Lin wrote:
> [...]
>> So even the Fixes tag should be removed ?
>
> I would keep that one there. Fixes tag is useful to frame the scope of
> the fix. For example when somebody is backporting the commit mentioned
> in the Fixes tag then a) a lot of follow up patches with Fixes can tell
> you this won't be an easy ride and you might want to reconsider risks
> vs. benefit b) it helps to collect follow up fixes more easily.
>
> That is a different story from cc: stable which just collects patches
> and push them to all consumers of the stable branch if they apply.
>
> To conclude, the Fixes tag is a generaly useful tag to bind patches
> together and let people evaluate how important that is while Cc stable
> is an indication that a fix is serious enough to push to all stable
> users.
>
I see. Many thanks for your detailed explanation! :)
Powered by blists - more mailing lists