From: "Longpeng (Mike, Cloud Infrastructure Service Product Dept.)" <longpeng2@huawei.com>
To: Sasha Levin <sashal@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>
Cc: Mike Kravetz <mike.kravetz@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Matthew Wilcox <willy@infradead.org>,
Sean Christopherson <sean.j.christopherson@intel.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH v5] mm/hugetlb: fix a addressing exception caused by huge_pte_offset
Date: Wed, 22 Apr 2020 09:01:39 +0800 [thread overview]
Message-ID: <f88c98ce-f969-99bf-4d24-62bb804c32ac@huawei.com> (raw)
In-Reply-To: <20200421195617.6104D20747@mail.kernel.org>
This bug was introduced by commit 9b19df292c666b57c407fed2496827c6aba05be2
("mm/hugetlb.c: make huge_pte_offset() consistent and document behaviour"), but
v4.4.219 and v4.9.219 haven't included it, so we needn't to apply my patch to
these two stable trees.
On 2020/4/22 3:56, Sasha Levin wrote:
> 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.6.5, v5.5.18, v5.4.33, v4.19.116, v4.14.176, v4.9.219, v4.4.219.
>
> v5.6.5: Build OK!
> v5.5.18: Build OK!
> v5.4.33: Build OK!
> v4.19.116: Build OK!
> v4.14.176: Build OK!
> v4.9.219: 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.219: 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?
>
--
---
Regards,
Longpeng(Mike)
prev parent reply other threads:[~2020-04-22 1:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 1:03 Longpeng(Mike)
2020-04-13 21:47 ` Mike Kravetz
2020-04-14 19:13 ` Jason Gunthorpe
2020-04-21 19:56 ` Sasha Levin
2020-04-22 1:01 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.) [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=f88c98ce-f969-99bf-4d24-62bb804c32ac@huawei.com \
--to=longpeng2@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=sashal@kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.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