From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org,
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Steven Sistare <steven.sistare@oracle.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Daniel Jordan <daniel.m.jordan@oracle.com>
Cc: Bob Picco <bob.picco@oracle.com>
Cc: Oscar Salvador <osalvador@suse.de>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2 1/3] mm: fix uninitialized memmaps on a partially populated last section
Date: Mon, 16 Dec 2019 15:06:39 +0000 [thread overview]
Message-ID: <20191216150640.784E820733@mail.kernel.org> (raw)
In-Reply-To: <20191211163201.17179-2-david@redhat.com>
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")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-12-16 15:06 UTC|newest]
Thread overview: 7+ 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
2019-12-16 15:06 ` Sasha Levin [this message]
2019-12-18 9:25 ` David Hildenbrand
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=20191216150640.784E820733@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-mm@kvack.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.