From: Daniel Axtens <dja@axtens•net>
To: Christophe Leroy <christophe.leroy@c-s•fr>,
aneesh.kumar@linux•ibm.com, bsingharora@gmail•com
Cc: linuxppc-dev@lists•ozlabs.org,
"Aneesh Kumar K . V" <aneesh.kumar@linux•vnet.ibm.com>,
kasan-dev@googlegroups•com
Subject: Re: [RFC PATCH 5/5] powerpc: KASAN for 64bit Book3E
Date: Tue, 19 Feb 2019 11:14:18 +1100 [thread overview]
Message-ID: <87wolw3a91.fsf@dja-thinkpad.axtens.net> (raw)
In-Reply-To: <e0373aa9-5035-3d32-2422-a08e52d2a4fb@c-s.fr>
>> diff --git a/arch/powerpc/mm/kasan/kasan_init_book3e_64.c b/arch/powerpc/mm/kasan/kasan_init_book3e_64.c
>> new file mode 100644
>> index 000000000000..93b9afcf1020
>> --- /dev/null
>> +++ b/arch/powerpc/mm/kasan/kasan_init_book3e_64.c
>> @@ -0,0 +1,53 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +
>> +#define DISABLE_BRANCH_PROFILING
>> +
>> +#include <linux/kasan.h>
>> +#include <linux/printk.h>
>> +#include <linux/memblock.h>
>> +#include <linux/sched/task.h>
>> +#include <asm/pgalloc.h>
>> +
>> +DEFINE_STATIC_KEY_FALSE(powerpc_kasan_enabled_key);
>> +EXPORT_SYMBOL(powerpc_kasan_enabled_key);
>
> Why does this symbol need to be exported ?
I suppose it probably doesn't! I copied Balbir's code without much
thought as it seemed a lot smarter than my random global variable code.
Regards,
Daniel
>
> Christophe
next prev parent reply other threads:[~2019-02-19 0:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 0:04 [RFC PATCH 0/5] powerpc: KASAN for 64-bit Book3E Daniel Axtens
2019-02-15 0:04 ` [RFC PATCH 1/5] kasan: do not open-code addr_has_shadow Daniel Axtens
2019-02-15 0:12 ` Andrew Donnellan
2019-02-15 8:21 ` Dmitry Vyukov
2019-02-15 0:04 ` [RFC PATCH 2/5] kasan: allow architectures to manage the memory-to-shadow mapping Daniel Axtens
2019-02-15 6:35 ` Dmitry Vyukov
2019-02-15 0:04 ` [RFC PATCH 3/5] kasan: allow architectures to provide an outline readiness check Daniel Axtens
2019-02-15 8:25 ` Dmitry Vyukov
2019-02-17 12:05 ` christophe leroy
2019-02-18 6:13 ` Daniel Axtens
2019-02-25 14:01 ` Christophe Leroy
2019-02-26 0:14 ` Daniel Axtens
2019-02-15 0:04 ` [RFC PATCH 4/5] powerpc: move KASAN into its own subdirectory Daniel Axtens
2019-02-15 0:24 ` Andrew Donnellan
2019-02-17 16:29 ` christophe leroy
2019-02-18 9:14 ` Michael Ellerman
2019-02-18 12:27 ` Christophe Leroy
2019-02-19 0:44 ` Michael Ellerman
2019-02-15 0:04 ` [RFC PATCH 5/5] powerpc: KASAN for 64bit Book3E Daniel Axtens
2019-02-15 8:28 ` Dmitry Vyukov
2019-02-19 6:37 ` Daniel Axtens
2019-02-17 14:06 ` christophe leroy
2019-02-18 19:26 ` Christophe Leroy
2019-02-19 0:14 ` Daniel Axtens [this message]
2019-02-15 16:39 ` [RFC PATCH 0/5] powerpc: KASAN for 64-bit Book3E Christophe Leroy
2019-02-17 6:34 ` Balbir Singh
2019-02-19 6:35 ` Daniel Axtens
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=87wolw3a91.fsf@dja-thinkpad.axtens.net \
--to=dja@axtens$(echo .)net \
--cc=aneesh.kumar@linux$(echo .)ibm.com \
--cc=aneesh.kumar@linux$(echo .)vnet.ibm.com \
--cc=bsingharora@gmail$(echo .)com \
--cc=christophe.leroy@c-s$(echo .)fr \
--cc=kasan-dev@googlegroups$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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