From: carver4lio@163.com
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Russell King <linux@armlinux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
Hailong Liu <liu.hailong6@zte.com.cn>
Subject: Re: [RESEND PATCH v2] arm/mm/ptdump:Add address markers for KASAN regions
Date: Tue, 26 Jan 2021 22:38:30 +0800 [thread overview]
Message-ID: <bf5040d0-a131-02a5-8eed-005e2604b355@163.com> (raw)
In-Reply-To: <CACRpkda5VXyg5F7r4RaHrSh303KZ3FjxnLEsQ1tFNXjMhxDqLw@mail.gmail.com>
On 1/21/21 4:36 PM, Linus Walleij wrote:
> On Wed, Jan 20, 2021 at 1:54 PM Hailong liu <carver4lio@163.com> wrote:
>
>> From: Hailong Liu <liu.hailong6@zte.com.cn>
>>
>> ARM has recently supported KASAN, so I think that it's time to add KASAN
>> regions for PTDUMP on ARM.
>>
>> I have tested this patch with QEMU + vexpress-a15. Both CONFIG_ARM_LPAE
>> and no CONFIG_ARM_LPAE.
>>
>> The result after patching looks like this:
>> ---[ Kasan shadow start ]---
>> 0x6ee00000-0x7af00000 193M RW NX SHD MEM/CACHED/WBWA
>> 0x7b000000-0x7f000000 64M ro NX SHD MEM/CACHED/WBWA
>> ---[ Kasan shadow end ]---
>> ---[ Modules ]---
>> ---[ Kernel Mapping ]---
>> ......
>> ---[ vmalloc() Area ]---
>> ......
>> ---[ vmalloc() End ]---
>> ---[ Fixmap Area ]---
>> ---[ Vectors ]---
>> ......
>> ---[ Vectors End ]---
>>
>> v2:
>> - fix the puzzling subject and the description due to my
>> carelessness.
>>
>> Signed-off-by: Hailong Liu <liu.hailong6@zte.com.cn>
>
> Looks correct!
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Please put this into Russell's patch tracker.
I have put this patch into Russell's patch tracker, and its status now is
incoming.
prev parent reply other threads:[~2021-01-26 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 12:50 Hailong liu
2021-01-21 8:36 ` Linus Walleij
2021-01-26 14:38 ` carver4lio [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=bf5040d0-a131-02a5-8eed-005e2604b355@163.com \
--to=carver4lio@163.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liu.hailong6@zte.com.cn \
--cc=rppt@kernel.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
all inboxes | Powered by JetHome®