From: David Hildenbrand <david@redhat.com>
To: Sasha Levin <sashal@kernel.org>, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Pavel Tatashin <pasha.tatashin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Sistare <steven.sistare@oracle.com>,
Michal Hocko <mhocko@suse.com>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
Bob Picco <bob.picco@oracle.com>,
Oscar Salvador <osalvador@suse.de>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/3] mm: fix uninitialized memmaps on a partially populated last section
Date: Wed, 18 Dec 2019 10:25:22 +0100 [thread overview]
Message-ID: <0597c667-bec7-6f89-d751-fc5abb976c6f@redhat.com> (raw)
In-Reply-To: <20191216150640.784E820733@mail.kernel.org>
On 16.12.19 16:06, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: f7f99100d8d9 ("mm: stop zeroing memory during allocation in vmemmap").
>
> The bot has tested the following trees: v5.4.2, v5.3.15, v4.19.88.
>
> v5.4.2: Build OK!
> v5.3.15: Build OK!
> v4.19.88: Failed to apply! Possible dependencies:
> 907ec5fca3dc ("mm: zero remaining unavailable struct pages")
> ec393a0f014e ("mm: return zero_resv_unavail optimization")
Yes, these two look like the right dependencies and should be picked as
well.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-12-18 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 16:31 [PATCH v2 0/3] mm: fix max_pfn not falling on section boundary David Hildenbrand
2019-12-11 16:31 ` [PATCH v2 1/3] mm: fix uninitialized memmaps on a partially populated last section David Hildenbrand
[not found] ` <20191216150640.784E820733@mail.kernel.org>
2019-12-18 9:25 ` David Hildenbrand [this message]
2019-12-11 16:32 ` [PATCH v2 2/3] fs/proc/page.c: allow inspection of last section and fix end detection David Hildenbrand
2019-12-11 16:32 ` [PATCH v2 3/3] mm: initialize memmap of unavailable memory directly David Hildenbrand
2020-01-31 3:52 ` [PATCH v2 0/3] mm: fix max_pfn not falling on section boundary Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0597c667-bec7-6f89-d751-fc5abb976c6f@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bob.picco@oracle.com \
--cc=daniel.m.jordan@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@oracle.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=steven.sistare@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).