From: toshi.kani@hpe.com (Kani, Toshi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] x86/mm: implement free pmd/pte page interfaces
Date: Wed, 7 Mar 2018 23:22:24 +0000 [thread overview]
Message-ID: <1520467641.2693.52.camel@hpe.com> (raw)
In-Reply-To: <20180307150127.1e09e9826e0f2c80ce42fa4d@linux-foundation.org>
On Wed, 2018-03-07 at 15:01 -0800, Andrew Morton wrote:
> On Wed, 7 Mar 2018 11:32:27 -0700 Toshi Kani <toshi.kani@hpe.com> wrote:
>
> > Implement pud_free_pmd_page() and pmd_free_pte_page() on x86, which
> > clear a given pud/pmd entry and free up lower level page table(s).
> > Address range associated with the pud/pmd entry must have been purged
> > by INVLPG.
>
> OK, now we have implementations which match the naming ;) Again, is a
> cc:stable warranted?
Right. This patch 2/2 fixes the memory leak on x86.
Fixes: e61ce6ade404e ("mm: change ioremap to set up huge I/O mappings")
Patch 1/2 fixes the panic on arm64.
Fixes: 324420bf91f60 ("arm64: add support for ioremap() block mappings")
> Do you have any preferences/suggestions as to which tree these should
> be merged through? You're hitting core, arm and x86.
No, I do not have any preference.
Thanks,
-Toshi
prev parent reply other threads:[~2018-03-07 23:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 18:32 [PATCH 0/2] fix memory leak / panic in ioremap huge pages Toshi Kani
2018-03-07 18:32 ` [PATCH 1/2] mm/vmalloc: Add interfaces to free unused page table Toshi Kani
2018-03-07 22:54 ` Andrew Morton
2018-03-07 23:02 ` Kani, Toshi
2018-03-07 22:55 ` Andrew Morton
2018-03-08 4:00 ` Matthew Wilcox
2018-03-08 15:56 ` Kani, Toshi
2018-03-08 22:07 ` Matthew Wilcox
2018-03-08 23:27 ` Kani, Toshi
2018-03-08 8:08 ` Ingo Molnar
2018-03-08 18:04 ` Will Deacon
2018-03-08 19:30 ` Kani, Toshi
2018-03-07 18:32 ` [PATCH 2/2] x86/mm: implement free pmd/pte page interfaces Toshi Kani
2018-03-07 23:01 ` Andrew Morton
2018-03-07 23:22 ` Kani, Toshi [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=1520467641.2693.52.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).