From: Dan Williams <dan.j.williams@intel.com>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
david <david@fromorbit.com>,
kasan-dev@googlegroups.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>, Dmitry Vyukov <dvyukov@google.com>,
Alexander Potapenko <glider@google.com>
Subject: Re: [PATCH v2] kernel/memremap, kasan: Make ZONE_DEVICE with work with KASAN
Date: Mon, 2 Jul 2018 10:28:23 -0700 [thread overview]
Message-ID: <CAPcyv4gN_f0q2a+e2-cXZoDGwKe2DfcMcHMZnf3UmyWp+dekSA@mail.gmail.com> (raw)
In-Reply-To: <788aa605-94c7-f730-6ec6-0eac53cb10cf@virtuozzo.com>
On Mon, Jul 2, 2018 at 10:22 AM, Andrey Ryabinin
<aryabinin@virtuozzo.com> wrote:
[..]
> It could be possible to not unmap kasan_zero_page, just leave it there after devm_memremap_pages_release().
> But we must have some guarantee that after devm_memremap_pages()/devm_memremap_pages_release() the same
> addresses can't be reused for ordinary hotpluggable memory.
While this does not happen today we are looking to support it the
future. I.e. have userspace policy pick whether to access an address
range through a device-file mmap, or treat it as typical memory.
prev parent reply other threads:[~2018-07-02 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 17:02 [PATCH] " Andrey Ryabinin
2018-06-25 19:51 ` kbuild test robot
2018-06-25 20:15 ` kbuild test robot
2018-06-29 16:49 ` [PATCH v2] " Andrey Ryabinin
2018-06-29 17:13 ` Dan Williams
2018-06-30 2:33 ` Andrew Morton
2018-06-30 3:19 ` Dan Williams
2018-07-02 17:22 ` Andrey Ryabinin
2018-07-02 17:28 ` Dan Williams [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=CAPcyv4gN_f0q2a+e2-cXZoDGwKe2DfcMcHMZnf3UmyWp+dekSA@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=david@fromorbit.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--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