From: Pasha Tatashin <pasha.tatashin@oracle.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
sparclinux@vger.kernel.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-s390@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"x86@kernel.org" <x86@kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
"David S. Miller" <davem@davemloft.net>,
willy@infradead.org, mhocko@kernel.org
Subject: Re: [v5 11/15] arm64/kasan: explicitly zero kasan shadow memory
Date: Fri, 4 Aug 2017 10:01:15 -0400 [thread overview]
Message-ID: <85cce150-74b7-c89b-678c-8fdd0be6c066@oracle.com> (raw)
In-Reply-To: <CAKv+Gu_V_T56qPS=c3kq73TLFwqpP4YHtggCrjGRmgW1itq3pQ@mail.gmail.com>
Hi Ard,
Thank you very much for reviewing this. I will fix the bug you found in
the next iteration.
>> +zero_vemmap_populated_memory(void)
>
> Typo here: vemmap -> vmemmap
Yeap, will rename here, and in Intel variant.
>
>> +{
>> + struct memblock_region *reg;
>> + u64 start, end;
>> +
>> + for_each_memblock(memory, reg) {
>> + start = __phys_to_virt(reg->base);
>> + end = __phys_to_virt(reg->base + reg->size);
>> +
>> + if (start >= end)
> How would this ever be true? And why is it a stop condition?
Yes this is a stop condition. Also look at the way kasan allocates its
shadow memory in this file kasan_init():
187 for_each_memblock(memory, reg) {
188 void *start = (void *)__phys_to_virt(reg->base);
189 void *end = (void *)__phys_to_virt(reg->base + reg->size);
190
191 if (start >= end)
192 break;
...
200 vmemmap_populate(...)
>> +
>
> Are you missing a couple of kasan_mem_to_shadow() calls here? I can't
> believe your intention is to wipe all of DRAM.
True. Thank you for catching this bug. I have not really tested on arm,
only compiled for sanity checking. Need to figure out how to configure
qemu to run most generic arm code. I tested on x86 and sparc both real
and qemu hardware.
>
> KASAN uses vmemmap_populate as a convenience: kasan has nothing to do
> with vmemmap, but the function already existed and happened to do what
> KASAN requires.
>
> Given that that will no longer be the case, it would be far better to
> stop using vmemmap_populate altogether, and clone it into a KASAN
> specific version (with an appropriate name) with the zeroing folded
> into it.
I agree, but this would be outside of the scope of this project.
Pasha
--
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:[~2017-08-04 14:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 21:23 [v5 00/15] complete deferred page initialization Pavel Tatashin
2017-08-03 21:23 ` [v5 01/15] x86/mm: reserve only exiting low pages Pavel Tatashin
2017-08-03 21:23 ` [v5 02/15] x86/mm: setting fields in deferred pages Pavel Tatashin
2017-08-03 21:23 ` [v5 03/15] sparc64/mm: " Pavel Tatashin
2017-08-03 21:23 ` [v5 04/15] mm: discard memblock data later Pavel Tatashin
2017-08-03 21:23 ` [v5 05/15] mm: don't accessed uninitialized struct pages Pavel Tatashin
2017-08-03 21:23 ` [v5 06/15] sparc64: simplify vmemmap_populate Pavel Tatashin
2017-08-03 21:23 ` [v5 07/15] mm: defining memblock_virt_alloc_try_nid_raw Pavel Tatashin
2017-08-03 21:23 ` [v5 08/15] mm: zero struct pages during initialization Pavel Tatashin
2017-08-03 21:23 ` [v5 09/15] sparc64: optimized struct page zeroing Pavel Tatashin
2017-08-04 5:37 ` Sam Ravnborg
2017-08-04 13:50 ` Pasha Tatashin
2017-08-03 21:23 ` [v5 10/15] x86/kasan: explicitly zero kasan shadow memory Pavel Tatashin
2017-08-03 21:23 ` [v5 11/15] arm64/kasan: " Pavel Tatashin
2017-08-04 0:14 ` Ard Biesheuvel
2017-08-04 14:01 ` Pasha Tatashin [this message]
2017-08-03 21:23 ` [v5 12/15] mm: explicitly zero pagetable memory Pavel Tatashin
2017-08-03 21:23 ` [v5 13/15] mm: stop zeroing memory during allocation in vmemmap Pavel Tatashin
2017-08-03 21:23 ` [v5 14/15] mm: optimize early system hash allocations Pavel Tatashin
2017-08-03 21:23 ` [v5 15/15] mm: debug for raw alloctor Pavel Tatashin
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=85cce150-74b7-c89b-678c-8fdd0be6c066@oracle.com \
--to=pasha.tatashin@oracle.com \
--cc=ard.biesheuvel@linaro.org \
--cc=borntraeger@de.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mhocko@kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=will.deacon@arm.com \
--cc=willy@infradead.org \
--cc=x86@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