From: "Björn Töpel" <bjorn@kernel.org>
To: Alexandre Ghiti <alexghiti@rivosinc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Ard Biesheuvel <ardb@kernel.org>, Conor Dooley <conor@kernel.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kasan-dev@googlegroups.com, linux-efi@vger.kernel.org
Cc: Alexandre Ghiti <alexghiti@rivosinc.com>
Subject: Re: [PATCH v4 3/6] riscv: Move DTB_EARLY_BASE_VA to the kernel address space
Date: Fri, 17 Feb 2023 15:58:48 +0100 [thread overview]
Message-ID: <873574uymv.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <20230203075232.274282-4-alexghiti@rivosinc.com>
Alexandre Ghiti <alexghiti@rivosinc.com> writes:
> The early virtual address should lie in the kernel address space for
> inline kasan instrumentation to succeed, otherwise kasan tries to
> dereference an address that does not exist in the address space (since
> kasan only maps *kernel* address space, not the userspace).
>
> Simply use the very first address of the kernel address space for the
> early fdt mapping.
>
> It allowed an Ubuntu kernel to boot successfully with inline
> instrumentation.
>
> Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
Reviewed-by: Björn Töpel <bjorn@rivosinc.com>
WARNING: multiple messages have this Message-ID (diff)
From: "Björn Töpel" <bjorn@kernel.org>
To: Alexandre Ghiti <alexghiti@rivosinc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Ard Biesheuvel <ardb@kernel.org>, Conor Dooley <conor@kernel.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kasan-dev@googlegroups.com, linux-efi@vger.kernel.org
Cc: Alexandre Ghiti <alexghiti@rivosinc.com>
Subject: Re: [PATCH v4 3/6] riscv: Move DTB_EARLY_BASE_VA to the kernel address space
Date: Fri, 17 Feb 2023 15:58:48 +0100 [thread overview]
Message-ID: <873574uymv.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <20230203075232.274282-4-alexghiti@rivosinc.com>
Alexandre Ghiti <alexghiti@rivosinc.com> writes:
> The early virtual address should lie in the kernel address space for
> inline kasan instrumentation to succeed, otherwise kasan tries to
> dereference an address that does not exist in the address space (since
> kasan only maps *kernel* address space, not the userspace).
>
> Simply use the very first address of the kernel address space for the
> early fdt mapping.
>
> It allowed an Ubuntu kernel to boot successfully with inline
> instrumentation.
>
> Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
Reviewed-by: Björn Töpel <bjorn@rivosinc.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-02-17 15:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 7:52 [PATCH v4 0/6] RISC-V kasan rework Alexandre Ghiti
2023-02-03 7:52 ` Alexandre Ghiti
2023-02-03 7:52 ` [PATCH v4 1/6] riscv: Split early and final KASAN population functions Alexandre Ghiti
2023-02-03 7:52 ` Alexandre Ghiti
2023-02-17 11:50 ` Björn Töpel
2023-02-17 11:50 ` Björn Töpel
2023-02-03 7:52 ` [PATCH v4 2/6] riscv: Rework kasan " Alexandre Ghiti
2023-02-03 7:52 ` Alexandre Ghiti
2023-02-17 14:54 ` Björn Töpel
2023-02-17 14:54 ` Björn Töpel
2023-02-03 7:52 ` [PATCH v4 3/6] riscv: Move DTB_EARLY_BASE_VA to the kernel address space Alexandre Ghiti
2023-02-03 7:52 ` Alexandre Ghiti
2023-02-17 14:58 ` Björn Töpel [this message]
2023-02-17 14:58 ` Björn Töpel
2023-02-03 7:52 ` [PATCH v4 4/6] riscv: Fix EFI stub usage of KASAN instrumented strcmp function Alexandre Ghiti
2023-02-03 7:52 ` Alexandre Ghiti
2023-02-03 7:58 ` Atish Patra
2023-02-03 7:58 ` Atish Patra
2023-02-03 7:52 ` [PATCH v4 5/6] riscv: Fix ptdump when KASAN is enabled Alexandre Ghiti
2023-02-03 7:52 ` Alexandre Ghiti
2023-02-17 14:55 ` Björn Töpel
2023-02-17 14:55 ` Björn Töpel
2023-02-03 7:52 ` [PATCH v4 6/6] riscv: Unconditionnally select KASAN_VMALLOC if KASAN Alexandre Ghiti
2023-02-03 7:52 ` Alexandre Ghiti
2023-02-17 14:57 ` Björn Töpel
2023-02-17 14:57 ` Björn Töpel
2023-03-08 3:29 ` [PATCH v4 0/6] RISC-V kasan rework Palmer Dabbelt
2023-03-08 3:29 ` Palmer Dabbelt
2023-03-08 3:45 ` Palmer Dabbelt
2023-03-08 3:45 ` Palmer Dabbelt
2023-03-08 3:30 ` patchwork-bot+linux-riscv
2023-03-08 3:30 ` patchwork-bot+linux-riscv
2023-04-19 14:56 ` Palmer Dabbelt
2023-04-19 14:56 ` Palmer Dabbelt
2023-04-20 17:36 ` Palmer Dabbelt
2023-04-20 17:36 ` Palmer Dabbelt
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=873574uymv.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=andreyknvl@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=conor@kernel.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=ryabinin.a.a@gmail.com \
--cc=vincenzo.frascino@arm.com \
/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.