From: Dan Williams <dan.j.williams@intel.com>
To: "Jan H. Schönherr" <jschoenh@amazon.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] mm: Fix devm_memremap_pages() collision handling
Date: Fri, 19 Jan 2018 16:15:53 -0800 [thread overview]
Message-ID: <CAPcyv4gDpaJZeM0UULLdXU4YPXQUhDfZAzs8xyrXp89AbE-tSg@mail.gmail.com> (raw)
In-Reply-To: <20180118000602.5527-2-jschoenh@amazon.de>
On Wed, Jan 17, 2018 at 4:06 PM, Jan H. Schönherr <jschoenh@amazon.de> wrote:
> If devm_memremap_pages() detects a collision while adding entries
> to the radix-tree, we call pgmap_radix_release(). Unfortunately,
> the function removes *all* entries for the range -- including the
> entries that caused the collision in the first place.
>
> Modify pgmap_radix_release() to take an additional argument to
> indicate where to stop, so that only newly added entries are removed
> from the tree.
>
> Fixes: 9476df7d80df ("mm: introduce find_dev_pagemap()")
> Signed-off-by: Jan H. Schönherr <jschoenh@amazon.de>
Looks good to me, applied for 4.16.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-01-20 0:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 0:06 [PATCH 1/2] mm: Fix memory size alignment in devm_memremap_pages_release() Jan H. Schönherr
2018-01-18 0:06 ` [PATCH 2/2] mm: Fix devm_memremap_pages() collision handling Jan H. Schönherr
2018-01-20 0:15 ` Dan Williams [this message]
2018-01-20 0:15 ` [PATCH 1/2] mm: Fix memory size alignment in devm_memremap_pages_release() Dan Williams
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=CAPcyv4gDpaJZeM0UULLdXU4YPXQUhDfZAzs8xyrXp89AbE-tSg@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=jschoenh@amazon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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