[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f263571b-8852-02c9-f606-9dc013b8124f@redhat.com>
Date: Mon, 6 Jul 2020 10:11:50 +0200
From: David Hildenbrand <david@...hat.com>
To: Sasha Levin <sashal@...nel.org>, linux-kernel@...r.kernel.org
Cc: linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...e.com>,
Minchan Kim <minchan@...nel.org>,
Huang Ying <ying.huang@...el.com>,
Wei Yang <richard.weiyang@...il.com>,
Mel Gorman <mgorman@...hsingularity.net>,
stable@...r.kernel.org
Subject: Re: [PATCH v3 1/3] mm/shuffle: don't move pages between zones and
don't read garbage memmaps
On 01.07.20 21:33, Sasha Levin wrote:
> Hi
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag
> fixing commit: e900a918b098 ("mm: shuffle initial free memory to improve memory-side-cache utilization").
>
> The bot has tested the following trees: v5.7.6, v5.4.49.
>
> v5.7.6: Build OK!
> v5.4.49: Failed to apply! Possible dependencies:
> e03d1f78341e8 ("mm/sparse: rename pfn_present() to pfn_in_present_section()")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
>
It contains
Cc: <stable@...r.kernel.org> [5.2+]
so a stable backport is desired once upstream. The v5.4.49 backport
should be fairly easy.
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists