From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: "Longpeng(Mike)" <longpeng2@huawei.com>
To: Longpeng <longpeng2@huawei.com>
To: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Cc: <kvm@vger.kernel.org>, <arei.gonglei@huawei.com>
Cc: Mike Kravetz <mike.kravetz@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v3] mm/hugetlb: fix a addressing exception caused by huge_pte_offset
Date: Fri, 27 Mar 2020 15:03:44 +0000 [thread overview]
Message-ID: <20200327150345.736D520748@mail.kernel.org> (raw)
In-Reply-To: <20200327014007.1915-1-longpeng2@huawei.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.5.11, v5.4.27, v4.19.112, v4.14.174, v4.9.217, v4.4.217.
v5.5.11: Build OK!
v5.4.27: Build OK!
v4.19.112: Build OK!
v4.14.174: Build OK!
v4.9.217: Failed to apply! Possible dependencies:
166f61b9435a ("mm: codgin-style fixes")
505a60e22560 ("asm-generic: introduce 5level-fixup.h")
82b0f8c39a38 ("mm: join struct fault_env and vm_fault")
953c66c2b22a ("mm: THP page cache support for ppc64")
c2febafc6773 ("mm: convert generic code to 5-level paging")
fd60775aea80 ("mm, thp: avoid unlikely branches for split_huge_pmd")
v4.4.217: Failed to apply! Possible dependencies:
01c8f1c44b83 ("mm, dax, gpu: convert vm_insert_mixed to pfn_t")
0e749e54244e ("dax: increase granularity of dax_clear_blocks() operations")
166f61b9435a ("mm: codgin-style fixes")
34c0fd540e79 ("mm, dax, pmem: introduce pfn_t")
505a60e22560 ("asm-generic: introduce 5level-fixup.h")
52db400fcd50 ("pmem, dax: clean up clear_pmem()")
5c6a84a3f455 ("mm/kasan: Switch to using __pa_symbol and lm_alias")
82b0f8c39a38 ("mm: join struct fault_env and vm_fault")
9973c98ecfda ("dax: add support for fsync/sync")
aac453635549 ("mm, oom: introduce oom reaper")
ac401cc78242 ("dax: New fault locking")
b2e0d1625e19 ("dax: fix lifetime of in-kernel dax mappings with dax_map_atomic()")
bae473a423f6 ("mm: introduce fault_env")
bc2466e42573 ("dax: Use radix tree entry lock to protect cow faults")
c2febafc6773 ("mm: convert generic code to 5-level paging")
e4b274915863 ("DAX: move RADIX_DAX_ definitions to dax.c")
f9fe48bece3a ("dax: support dirty DAX entries in radix tree")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
prev parent reply other threads:[~2020-03-27 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 1:40 [PATCH v3] mm/hugetlb: fix a addressing exception caused by huge_pte_offset Longpeng(Mike)
2020-03-27 12:11 ` Jason Gunthorpe
2020-03-27 23:32 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2020-03-27 15:03 ` Sasha Levin [this message]
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=20200327150345.736D520748@mail.kernel.org \
--to=sashal@kernel.org \
--cc=arei.gonglei@huawei.com \
--cc=kvm@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 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.