From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Dan Williams <dan.j.williams@intel.com>
To: akpm@linux-foundation.org
Cc: stable@vger.kernel.org, linux-mm@kvack.org,
Cc: <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v5 09/10] libnvdimm/pfn: Fix fsdax-mode namespace info-block zero-fields
Date: Wed, 27 Mar 2019 14:00:50 +0000 [thread overview]
Message-ID: <20190327140051.7092C2087C@mail.kernel.org> (raw)
In-Reply-To: <155327392164.225273.1248065676074470935.stgit@dwillia2-desk3.amr.corp.intel.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 32ab0a3f5170 libnvdimm, pmem: 'struct page' for pmem.
The bot has tested the following trees: v5.0.4, v4.19.31, v4.14.108, v4.9.165, v4.4.177.
v5.0.4: Build OK!
v4.19.31: Failed to apply! Possible dependencies:
48af2f7e52f4 ("libnvdimm, pfn: during init, clear errors in the metadata area")
v4.14.108: Failed to apply! Possible dependencies:
48af2f7e52f4 ("libnvdimm, pfn: during init, clear errors in the metadata area")
v4.9.165: Failed to apply! Possible dependencies:
48af2f7e52f4 ("libnvdimm, pfn: during init, clear errors in the metadata area")
v4.4.177: Failed to apply! Possible dependencies:
0731de0dd95b ("libnvdimm, pfn: move 'memory mode' indication to sysfs")
0bfb8dd3edd6 ("libnvdimm: cleanup nvdimm_namespace_common_probe(), kill 'host'")
0caeef63e6d2 ("libnvdimm: Add a poison list and export badblocks")
0e749e54244e ("dax: increase granularity of dax_clear_blocks() operations")
2dc43331e34f ("libnvdimm, pfn: fix pfn seed creation")
315c562536c4 ("libnvdimm, pfn: add 'align' attribute, default to HPAGE_SIZE")
34c0fd540e79 ("mm, dax, pmem: introduce pfn_t")
4b94ffdc4163 ("x86, mm: introduce vmem_altmap to augment vmemmap_populate()")
52db400fcd50 ("pmem, dax: clean up clear_pmem()")
87ba05dff351 ("libnvdimm: don't fail init for full badblocks list")
9476df7d80df ("mm: introduce find_dev_pagemap()")
9c41242817f4 ("libnvdimm: fix mode determination for e820 devices")
ad9a8bde2cb1 ("libnvdimm, pmem: move definition of nvdimm_namespace_add_poison to nd.h")
b2e0d1625e19 ("dax: fix lifetime of in-kernel dax mappings with dax_map_atomic()")
b95f5f4391fa ("libnvdimm: convert to statically allocated badblocks")
bd032943b5b2 ("libnvdimm, pfn, convert nd_pfn_probe() to devm")
c5ed9268643c ("libnvdimm, dax: autodetect support")
cd03412a51ac ("libnvdimm, dax: introduce device-dax infrastructure")
cfe30b872058 ("libnvdimm, pmem: adjust for section collisions with 'System RAM'")
d2c0f041e1bb ("libnvdimm, pfn, pmem: allocate memmap array in persistent memory")
d9cbe09d39aa ("libnvdimm, pmem: fix 'pfn' support for section-misaligned namespaces")
f6ed58c70d14 ("libnvdimm, pfn: 'resource'-address and 'size' attributes for pfn devices")
f7c6ab80fa5f ("libnvdimm, pfn: clean up pfn create parameters")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-03-27 14:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 16:57 [PATCH v5 00/10] mm: Sub-section memory hotplug support Dan Williams
2019-03-22 16:57 ` [PATCH v5 01/10] mm/sparsemem: Introduce struct mem_section_usage Dan Williams
2019-03-22 16:58 ` [PATCH v5 02/10] mm/sparsemem: Introduce common definitions for the size and mask of a section Dan Williams
2019-03-22 16:58 ` [PATCH v5 03/10] mm/sparsemem: Add helpers track active portions of a section at boot Dan Williams
2019-03-22 16:58 ` [PATCH v5 04/10] mm/hotplug: Prepare shrink_{zone, pgdat}_span for sub-section removal Dan Williams
2019-03-22 16:58 ` [PATCH v5 05/10] mm/sparsemem: Convert kmalloc_section_memmap() to populate_section_memmap() Dan Williams
2019-03-22 16:58 ` [PATCH v5 06/10] mm/sparsemem: Prepare for sub-section ranges Dan Williams
2019-03-22 16:58 ` [PATCH v5 07/10] mm/sparsemem: Support sub-section hotplug Dan Williams
2019-03-22 16:58 ` [PATCH v5 08/10] mm/devm_memremap_pages: Enable sub-section remap Dan Williams
2019-03-22 16:58 ` [PATCH v5 09/10] libnvdimm/pfn: Fix fsdax-mode namespace info-block zero-fields Dan Williams
2019-03-27 14:00 ` Sasha Levin [this message]
2019-03-22 16:58 ` [PATCH v5 10/10] libnvdimm/pfn: Stop padding pmem namespaces to section alignment Dan Williams
2019-03-22 18:05 ` [PATCH v5 00/10] mm: Sub-section memory hotplug support Michal Hocko
2019-03-22 18:32 ` Dan Williams
2019-03-25 10:19 ` Michal Hocko
2019-03-25 14:28 ` Jeff Moyer
2019-03-25 14:50 ` Michal Hocko
2019-03-25 20:03 ` Dan Williams
2019-03-26 8:04 ` Michal Hocko
2019-03-27 0:20 ` Dan Williams
2019-03-27 16:13 ` Michal Hocko
2019-03-27 16:17 ` Dan Williams
2019-03-28 13:38 ` David Hildenbrand
2019-03-28 14:16 ` Michal Hocko
2019-04-01 9:18 ` David Hildenbrand
2019-03-28 20:10 ` David Hildenbrand
2019-03-28 20:43 ` Dan Williams
2019-03-28 21:17 ` David Hildenbrand
2019-03-28 21:32 ` Dan Williams
2019-03-28 21:54 ` David Hildenbrand
2019-04-10 9:51 ` David Hildenbrand
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=20190327140051.7092C2087C@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.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 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).