From: Michael Ellerman <mpe@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Cc: Maxime Bizon <mbizon@freebox.fr>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] powerpc/32s: Fix kasan_init_region() for KASAN
Date: Wed, 29 Dec 2021 09:45:51 +1100 [thread overview]
Message-ID: <87pmpg1h7k.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <90826d123e3e28b840f284412b150a1e13ed62fb.1638799954.git.christophe.leroy@csgroup.eu>
Christophe Leroy <christophe.leroy@csgroup.eu> writes:
> It has been reported some configuration where the kernel doesn't
> boot with KASAN enabled.
>
> This is due to wrong BAT allocation for the KASAN area:
>
> ---[ Data Block Address Translation ]---
> 0: 0xc0000000-0xcfffffff 0x00000000 256M Kernel rw m
> 1: 0xd0000000-0xdfffffff 0x10000000 256M Kernel rw m
> 2: 0xe0000000-0xefffffff 0x20000000 256M Kernel rw m
> 3: 0xf8000000-0xf9ffffff 0x2a000000 32M Kernel rw m
> 4: 0xfa000000-0xfdffffff 0x2c000000 64M Kernel rw m
>
> A BAT must have both virtual and physical addresses alignment matching
> the size of the BAT. This is not the case for BAT 4 above.
>
> Fix kasan_init_region() by using block_size() function that is in
> book3s32/mmu.c. To be able to reuse it here, make it non static and
> change its name to bat_block_size() in order to avoid name conflict
> with block_size() defined in <linux/blkdev.h>
>
> Also reuse find_free_bat() to avoid an error message from setbat()
> when no BAT is available.
>
> And allocate memory outside of linear memory mapping to avoid
> wasting that precious space.
>
> With this change we get correct alignment for BATs and KASAN shadow
> memory is allocated outside the linear memory space.
>
> ---[ Data Block Address Translation ]---
> 0: 0xc0000000-0xcfffffff 0x00000000 256M Kernel rw
> 1: 0xd0000000-0xdfffffff 0x10000000 256M Kernel rw
> 2: 0xe0000000-0xefffffff 0x20000000 256M Kernel rw
> 3: 0xf8000000-0xfbffffff 0x7c000000 64M Kernel rw
> 4: 0xfc000000-0xfdffffff 0x7a000000 32M Kernel rw
>
> Reported-by: Maxime Bizon <mbizon@freebox.fr>
> Fixes: 7974c4732642 ("powerpc/32s: Implement dedicated kasan_init_region()")
> Cc: stable@vger.kernel.org
> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> ---
> v2:
> - Allocate kasan shadow memory outside precious kernel linear memory
> - Properly zeroise kasan shadow memory
> ---
> arch/powerpc/include/asm/book3s/32/mmu-hash.h | 2 +
> arch/powerpc/mm/book3s32/mmu.c | 10 ++--
> arch/powerpc/mm/kasan/book3s_32.c | 58 ++++++++++---------
> 3 files changed, 38 insertions(+), 32 deletions(-)
Sorry this now conflicts with other changes in next. Can you rebase it please?
cheers
prev parent reply other threads:[~2021-12-28 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 14:12 [PATCH v2] powerpc/32s: Fix kasan_init_region() for KASAN Christophe Leroy
2021-12-07 9:03 ` Maxime Bizon
2021-12-28 22:45 ` Michael Ellerman [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=87pmpg1h7k.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mbizon@freebox.fr \
--cc=paulus@samba.org \
--cc=stable@vger.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