From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Balbir Singh <bsingharora@gmail.com>,
Daniel Axtens <dja@axtens.net>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
linux-xtensa@linux-xtensa.org, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kasan-dev@googlegroups.com,
aneesh.kumar@linux.ibm.com
Subject: Re: [PATCH v2 2/4] kasan: use MAX_PTRS_PER_* for early shadow
Date: Tue, 10 Dec 2019 15:39:34 +0100 [thread overview]
Message-ID: <5d1ec6e3-777e-9f23-ea8f-50361a29302f@c-s.fr> (raw)
In-Reply-To: <a31459ee-2019-2f7b-0dc1-235374579508@gmail.com>
Le 10/12/2019 à 10:36, Balbir Singh a écrit :
>
>
> On 10/12/19 3:47 pm, Daniel Axtens wrote:
>> This helps with powerpc support, and should have no effect on
>> anything else.
>>
>> Suggested-by: Christophe Leroy <christophe.leroy@c-s.fr>
>> Signed-off-by: Daniel Axtens <dja@axtens.net>
>
> If you follow the recommendations by Christophe and I, you don't need this patch
I guess you mean Patch 1 (the one adding the const to all arches) is not
needed. Of course this one (Patch 2) is needed as it is the one that
changes kasan.h to use const table size instead of impossible variable
table size.
And that would also fix the problem reported by the kbuild test robot.
Christophe
WARNING: multiple messages have this Message-ID (diff)
From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Balbir Singh <bsingharora@gmail.com>,
Daniel Axtens <dja@axtens.net>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
linux-xtensa@linux-xtensa.org, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kasan-dev@googlegroups.com,
aneesh.kumar@linux.ibm.com
Subject: Re: [PATCH v2 2/4] kasan: use MAX_PTRS_PER_* for early shadow
Date: Tue, 10 Dec 2019 15:39:34 +0100 [thread overview]
Message-ID: <5d1ec6e3-777e-9f23-ea8f-50361a29302f@c-s.fr> (raw)
In-Reply-To: <a31459ee-2019-2f7b-0dc1-235374579508@gmail.com>
Le 10/12/2019 à 10:36, Balbir Singh a écrit :
>
>
> On 10/12/19 3:47 pm, Daniel Axtens wrote:
>> This helps with powerpc support, and should have no effect on
>> anything else.
>>
>> Suggested-by: Christophe Leroy <christophe.leroy@c-s.fr>
>> Signed-off-by: Daniel Axtens <dja@axtens.net>
>
> If you follow the recommendations by Christophe and I, you don't need this patch
I guess you mean Patch 1 (the one adding the const to all arches) is not
needed. Of course this one (Patch 2) is needed as it is the one that
changes kasan.h to use const table size instead of impossible variable
table size.
And that would also fix the problem reported by the kbuild test robot.
Christophe
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-10 14:39 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 4:47 [PATCH v2 0/4] KASAN for powerpc64 radix, plus generic mm change Daniel Axtens
2019-12-10 4:47 ` Daniel Axtens
2019-12-10 4:47 ` [PATCH v2 1/4] mm: define MAX_PTRS_PER_{PTE,PMD,PUD} Daniel Axtens
2019-12-10 4:47 ` Daniel Axtens
2019-12-10 6:35 ` Christophe Leroy
2019-12-10 6:35 ` Christophe Leroy
2019-12-10 9:35 ` Balbir Singh
2019-12-10 9:35 ` Balbir Singh
2019-12-10 10:39 ` kbuild test robot
2019-12-10 10:39 ` [PATCH v2 1/4] mm: define MAX_PTRS_PER_{PTE, PMD, PUD} kbuild test robot
2019-12-10 10:39 ` [PATCH v2 1/4] mm: define MAX_PTRS_PER_{PTE,PMD,PUD} kbuild test robot
2019-12-10 10:39 ` kbuild test robot
2019-12-10 10:39 ` kbuild test robot
2019-12-10 10:39 ` kbuild test robot
2019-12-10 4:47 ` [PATCH v2 2/4] kasan: use MAX_PTRS_PER_* for early shadow Daniel Axtens
2019-12-10 4:47 ` Daniel Axtens
2019-12-10 6:40 ` Christophe Leroy
2019-12-10 6:40 ` Christophe Leroy
2019-12-10 9:36 ` Balbir Singh
2019-12-10 9:36 ` Balbir Singh
2019-12-10 14:39 ` Christophe Leroy [this message]
2019-12-10 14:39 ` Christophe Leroy
2019-12-10 4:47 ` [PATCH v2 3/4] kasan: Document support on 32-bit powerpc Daniel Axtens
2019-12-10 4:47 ` Daniel Axtens
2019-12-10 6:40 ` Christophe Leroy
2019-12-10 6:40 ` Christophe Leroy
2019-12-10 4:47 ` [PATCH v2 4/4] powerpc: Book3S 64-bit "heavyweight" KASAN support Daniel Axtens
2019-12-10 4:47 ` Daniel Axtens
2019-12-10 7:21 ` Christophe Leroy
2019-12-10 7:21 ` Christophe Leroy
2019-12-12 13:41 ` Daniel Axtens
2019-12-12 13:41 ` Daniel Axtens
2019-12-10 10:57 ` Balbir Singh
2019-12-10 10:57 ` Balbir Singh
2019-12-11 5:21 ` Daniel Axtens
2019-12-11 5:21 ` Daniel Axtens
2019-12-11 8:57 ` Balbir Singh
2019-12-11 8:57 ` Balbir Singh
2019-12-11 14:24 ` Daniel Axtens
2019-12-11 14:24 ` Daniel Axtens
2019-12-12 7:42 ` Balbir Singh
2019-12-12 7:42 ` Balbir Singh
2019-12-12 7:42 ` Balbir Singh
2019-12-12 9:38 ` Christophe Leroy
2019-12-12 9:38 ` Christophe Leroy
2019-12-12 9:56 ` Andrey Ryabinin
2019-12-12 9:56 ` Andrey Ryabinin
2019-12-10 11:20 ` kbuild test robot
2019-12-10 11:20 ` kbuild test robot
2019-12-10 11:20 ` kbuild test robot
2019-12-10 11:20 ` kbuild test robot
2019-12-10 11:20 ` kbuild test robot
2019-12-10 11:20 ` kbuild test robot
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=5d1ec6e3-777e-9f23-ea8f-50361a29302f@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bsingharora@gmail.com \
--cc=dja@axtens.net \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--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=linux-xtensa@linux-xtensa.org \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.