From: patchwork-bot+linux-riscv@kernel.org
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-riscv@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
hch@infradead.org, david@redhat.com, mhocko@suse.com,
peterx@redhat.com, nadav.amit@gmail.com, willy@infradead.org,
vbabka@suse.cz, riel@surriel.com, will@kernel.org,
mpe@ellerman.id.au, palmer@dabbelt.com,
borntraeger@linux.ibm.com, dave.hansen@linux.intel.com,
brauner@kernel.org, edumazet@google.com,
akpm@linux-foundation.org
Subject: Re: [PATCH] mm: remove zap_page_range and create zap_vma_pages
Date: Tue, 28 Feb 2023 21:11:17 +0000 [thread overview]
Message-ID: <167761867732.10135.11248419155612086016.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230104002732.232573-1-mike.kravetz@oracle.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Andrew Morton <akpm@linux-foundation.org>:
On Tue, 3 Jan 2023 16:27:32 -0800 you wrote:
> zap_page_range was originally designed to unmap pages within an address
> range that could span multiple vmas. While working on [1], it was
> discovered that all callers of zap_page_range pass a range entirely within
> a single vma. In addition, the mmu notification call within zap_page
> range does not correctly handle ranges that span multiple vmas. When
> crossing a vma boundary, a new mmu_notifier_range_init/end call pair
> with the new vma should be made.
>
> [...]
Here is the summary with links:
- mm: remove zap_page_range and create zap_vma_pages
https://git.kernel.org/riscv/c/e9adcfecf572
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-28 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 0:27 [PATCH] mm: remove zap_page_range and create zap_vma_pages Mike Kravetz
2023-01-04 7:46 ` Michal Hocko
2023-01-04 16:44 ` Peter Xu
2023-01-04 18:09 ` Heiko Carstens
2023-01-08 17:24 ` Christoph Hellwig
2023-02-15 3:19 ` Palmer Dabbelt
2023-02-28 21:11 ` patchwork-bot+linux-riscv [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=167761867732.10135.11248419155612086016.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=brauner@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=edumazet@google.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=nadav.amit@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=peterx@redhat.com \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).