Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] mm: remove zap_page_range and create zap_vma_pages
From:   patchwork-bot+linux-riscv@kernel.org
Message-Id: <167761867732.10135.11248419155612086016.git-patchwork-notify@kernel.org>
Date:   Tue, 28 Feb 2023 21:11:17 +0000
References: <20230104002732.232573-1-mike.kravetz@oracle.com>
In-Reply-To: <20230104002732.232573-1-mike.kravetz@oracle.com>
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
Precedence: bulk

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