From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Mikhail Zaslonko <zaslonko@linux.ibm.com>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Cc: <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2 1/1] memory_hotplug: fix the panic when memory end is not on the section boundary
Date: Fri, 14 Jun 2019 21:56:36 +0000 [thread overview]
Message-ID: <20190614215637.7E71521473@mail.kernel.org> (raw)
In-Reply-To: <20181105150401.97287-2-zaslonko@linux.ibm.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.1.9, v4.19.50, v4.14.125, v4.9.181, v4.4.181.
v5.1.9: Failed to apply! Possible dependencies:
Unable to calculate
v4.19.50: Failed to apply! Possible dependencies:
Unable to calculate
v4.14.125: Failed to apply! Possible dependencies:
4da2ce250f98 ("mm: distinguish CMA and MOVABLE isolation in has_unmovable_pages()")
da024512a1fa ("mm: pass the vmem_altmap to arch_remove_memory and __remove_pages")
fb52bbaee598 ("mm: move is_pageblock_removable_nolock() to mm/memory_hotplug.c")
v4.9.181: Failed to apply! Possible dependencies:
133ff0eac95b ("mm/hmm: heterogeneous memory management (HMM for short)")
3859a271a003 ("randstruct: Mark various structs for randomization")
4ef589dc9b10 ("mm/hmm/devmem: device memory hotplug using ZONE_DEVICE")
5613fda9a503 ("sched/cputime: Convert task/group cputime to nsecs")
60f3e00d25b4 ("sysv,ipc: cacheline align kern_ipc_perm")
8c8b73c4811f ("sched/cputime, powerpc: Prepare accounting structure for cputime flush on tick")
a19ff1a2cc92 ("sched/cputime, powerpc/vtime: Accumulate cputime and account only on tick/task switch")
b18b6a9cef7f ("timers: Omit POSIX timer stuff from task_struct when disabled")
b584c2544041 ("powerpc/vmemmap: Add altmap support")
baa73d9e478f ("posix-timers: Make them configurable")
c3edc4010e9d ("sched/headers: Move task_struct::signal and task_struct::sighand types and accessors into <linux/sched/signal.h>")
d3df0a423397 ("mm/hmm: add new helper to hotplug CDM memory region")
d69dece5f5b6 ("LSM: Add /sys/kernel/security/lsm")
d7d9b612f1b0 ("powerpc/vmemmap: Reshuffle vmemmap_free()")
da024512a1fa ("mm: pass the vmem_altmap to arch_remove_memory and __remove_pages")
fb52bbaee598 ("mm: move is_pageblock_removable_nolock() to mm/memory_hotplug.c")
v4.4.181: Failed to apply! Possible dependencies:
11a6f6abd74a ("powerpc/mm: Move radix/hash common data structures to book3s64 headers")
15b1624b7807 ("powerpc: Use defines for __init_tlb_power[78]")
18569c1f134e ("powerpc/64: Don't try to use radix MMU under a hypervisor")
1a01dc87e09b ("powerpc/mm: Add mmu_early_init_devtree()")
26b6a3d9bb48 ("powerpc/mm: move pte headers to book3s directory")
2bfd65e45e87 ("powerpc/mm/radix: Add radix callbacks for early init routines")
3dfcb315d81e ("powerpc/mm: make a separate copy for book3s")
5c3c7ede2bdc ("powerpc/mm: Split hash page table sizing heuristic into a helper")
756d08d1ba16 ("powerpc/mm: Abstract early MMU init in preparation for radix")
b275bfb26963 ("powerpc/mm/radix: Add a kernel command line to disable radix")
b584c2544041 ("powerpc/vmemmap: Add altmap support")
c3ab300ea555 ("powerpc: Add POWER9 cputable entry")
c610ec60ed63 ("powerpc/mm: Move disable_radix handling into mmu_early_init_devtree()")
da024512a1fa ("mm: pass the vmem_altmap to arch_remove_memory and __remove_pages")
f64e8084c94b ("powerpc/mm: Move hash related mmu-*.h headers to book3s/")
fb52bbaee598 ("mm: move is_pageblock_removable_nolock() to mm/memory_hotplug.c")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-06-14 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 15:04 [PATCH v2 0/1] memory_hotplug: fix the panic when memory end is not Mikhail Zaslonko
2018-11-05 15:04 ` [PATCH v2 1/1] memory_hotplug: fix the panic when memory end is not on the section boundary Mikhail Zaslonko
2019-06-14 21:56 ` Sasha Levin [this message]
2018-11-05 18:35 ` [PATCH v2 0/1] memory_hotplug: fix the panic when memory end is not Michal Hocko
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=20190614215637.7E71521473@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-kernel@vger.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.