From: Andrey Ryabinin <a.ryabinin@samsung.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
linux-mm@kvack.org, Linus Walleij <linus.walleij@linaro.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
David Keitel <dkeitel@codeaurora.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Potapenko <glider@google.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH v3 1/5] mm: kasan: introduce generic kasan_populate_zero_shadow()
Date: Wed, 22 Jul 2015 17:34:25 +0300 [thread overview]
Message-ID: <55AFA9F1.5070703@samsung.com> (raw)
In-Reply-To: <20150722141719.GA16627@e104818-lin.cambridge.arm.com>
On 07/22/2015 05:17 PM, Catalin Marinas wrote:
> On Wed, Jul 22, 2015 at 01:30:33PM +0300, Andrey Ryabinin wrote:
>> diff --git a/arch/x86/mm/kasan_init_64.c b/arch/x86/mm/kasan_init_64.c
>> index e1840f3..2390dba 100644
>> --- a/arch/x86/mm/kasan_init_64.c
>> +++ b/arch/x86/mm/kasan_init_64.c
>> @@ -12,9 +12,9 @@
>> extern pgd_t early_level4_pgt[PTRS_PER_PGD];
>> extern struct range pfn_mapped[E820_X_MAX];
>>
>> -static pud_t kasan_zero_pud[PTRS_PER_PUD] __page_aligned_bss;
>> -static pmd_t kasan_zero_pmd[PTRS_PER_PMD] __page_aligned_bss;
>> -static pte_t kasan_zero_pte[PTRS_PER_PTE] __page_aligned_bss;
>> +pud_t kasan_zero_pud[PTRS_PER_PUD] __page_aligned_bss;
>> +pmd_t kasan_zero_pmd[PTRS_PER_PMD] __page_aligned_bss;
>> +pte_t kasan_zero_pte[PTRS_PER_PTE] __page_aligned_bss;
>>
>> /*
>> * This page used as early shadow. We don't use empty_zero_page
>> @@ -24,7 +24,7 @@ static pte_t kasan_zero_pte[PTRS_PER_PTE] __page_aligned_bss;
>> * that allowed to access, but not instrumented by kasan
>> * (vmalloc/vmemmap ...).
>> */
>> -static unsigned char kasan_zero_page[PAGE_SIZE] __page_aligned_bss;
>> +unsigned char kasan_zero_page[PAGE_SIZE] __page_aligned_bss;
>
> Did you lose part of the patch when rebasing? I can see you copied
> kasan_populate_zero_shadow() to the mm code but it's still present in
> the x86 one and the above changes to remove static seem meaningless.
>
> Or you plan to submit the rest of the x86 code separately?
>
Yes, I was going to send x86 patch later.
Static has to be removed because this conflicts with kasan_zero_p* declarations in include/linux/kasan.h.
> BTW, you could even move kasan_zero_p[tme]d arrays to mm/.
>
Makes sense.
--
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:[~2015-07-22 14:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 10:30 [PATCH v3 0/5] KASAN for arm64 Andrey Ryabinin
2015-07-22 10:30 ` [PATCH v3 1/5] mm: kasan: introduce generic kasan_populate_zero_shadow() Andrey Ryabinin
2015-07-22 14:17 ` Catalin Marinas
2015-07-22 14:34 ` Andrey Ryabinin [this message]
2015-07-22 14:25 ` Alexey Klimov
2015-07-22 14:44 ` Andrey Ryabinin
2015-07-22 10:30 ` [PATCH v3 2/5] arm64: introduce VA_START macro - the first kernel virtual address Andrey Ryabinin
2015-07-22 14:21 ` Catalin Marinas
2015-07-22 10:30 ` [PATCH v3 3/5] arm64: move PGD_SIZE definition to pgalloc.h Andrey Ryabinin
2015-07-22 14:24 ` Catalin Marinas
2015-07-22 10:30 ` [PATCH v3 4/5] arm64: add KASAN support Andrey Ryabinin
2015-07-22 15:49 ` Catalin Marinas
2015-07-22 10:30 ` [PATCH v3 5/5] ARM64: kasan: print memory assignment Andrey Ryabinin
2015-07-22 14:24 ` Catalin Marinas
2015-07-22 14:44 ` [PATCH v3 0/5] KASAN for arm64 Alexey Klimov
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=55AFA9F1.5070703@samsung.com \
--to=a.ryabinin@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dkeitel@codeaurora.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--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