From: Huacai Chen <chenhuacai@kernel.org>
To: Enze Li <lienze@kylinos.cn>
Cc: kernel@xen0n.name, loongarch@lists.linux.dev, glider@google.com,
elver@google.com, akpm@linux-foundation.org,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
zhangqing@loongson.cn, yangtiezhu@loongson.cn,
dvyukov@google.com
Subject: Re: [PATCH 0/4 v3] Add KFENCE support for LoongArch
Date: Wed, 2 Aug 2023 23:12:23 +0800 [thread overview]
Message-ID: <CAAhV-H6FqreZtuOXYayhu=bLZeij+fxygbK5Mpw_kVuPTvdbWw@mail.gmail.com> (raw)
In-Reply-To: <20230801025815.2436293-1-lienze@kylinos.cn>
Hi, Enze,
I applied this series (with some small modifications) together with KASAN at:
https://github.com/chenhuacai/linux/commits/loongarch-next
Please confirm everything works well for you.
Huacai
On Tue, Aug 1, 2023 at 10:59 AM Enze Li <lienze@kylinos.cn> wrote:
>
> Hi all,
>
> This patchset adds KFENCE support on LoongArch.
>
> To run the testcases, you will need to enable the following options,
>
> -> Kernel hacking
> [*] Tracers
> [*] Support for tracing block IO actions (NEW)
> -> Kernel Testing and Coverage
> <*> KUnit - Enable support for unit tests
>
> and then,
>
> -> Kernel hacking
> -> Memory Debugging
> [*] KFENCE: low-overhead sampling-based memory safety error detector (NEW)
> <*> KFENCE integration test suite (NEW)
>
> With these options enabled, KFENCE will be tested during kernel startup.
> And normally, you might get the following feedback,
>
> ========================================================
> [ 35.326363 ] # kfence: pass:23 fail:0 skip:2 total:25
> [ 35.326486 ] # Totals: pass:23 fail:0 skip:2 total:25
> [ 35.326621 ] ok 1 kfence
> ========================================================
>
> you might notice that 2 testcases have been skipped. If you tend to run
> all testcases, please enable CONFIG_INIT_ON_FREE_DEFAULT_ON, you can
> find it here,
>
> -> Security options
> -> Kernel hardening options
> -> Memory initialization
> [*] Enable heap memory zeroing on free by default
>
> and you might get all testcases passed.
> ========================================================
> [ 35.531860 ] # kfence: pass:25 fail:0 skip:0 total:25
> [ 35.531999 ] # Totals: pass:25 fail:0 skip:0 total:25
> [ 35.532135 ] ok 1 kfence
> ========================================================
>
> v3:
> * Address Huacai's comments.
> * Fix a bug that Jackie Liu pointed out.
> * Rewrite arch_stack_walk() with the suggestion of Jinyang He.
>
> v2:
> * Address Huacai's comments.
> * Fix typos in commit message.
>
> Thanks,
> Enze
>
> Enze Li (4):
> KFENCE: Defer the assignment of the local variable addr
> LoongArch: mm: Add page table mapped mode support
> LoongArch: Get stack without NMI when providing regs parameter
> LoongArch: Add KFENCE support
>
> arch/loongarch/Kconfig | 1 +
> arch/loongarch/include/asm/kfence.h | 66 ++++++++++++++++++++++++++++
> arch/loongarch/include/asm/page.h | 8 +++-
> arch/loongarch/include/asm/pgtable.h | 16 ++++++-
> arch/loongarch/kernel/stacktrace.c | 18 ++++----
> arch/loongarch/mm/fault.c | 22 ++++++----
> arch/loongarch/mm/pgtable.c | 7 +++
> mm/kfence/core.c | 5 ++-
> 8 files changed, 123 insertions(+), 20 deletions(-)
> create mode 100644 arch/loongarch/include/asm/kfence.h
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-08-02 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 2:58 Enze Li
2023-08-01 2:58 ` [PATCH 1/4 v3] KFENCE: Defer the assignment of the local variable addr Enze Li
2023-08-01 2:58 ` [PATCH 2/4 v3] LoongArch: mm: Add page table mapped mode support Enze Li
2023-08-01 2:58 ` [PATCH 3/4 v3] LoongArch: Get stack without NMI when providing regs parameter Enze Li
2023-08-01 2:58 ` [PATCH 4/4 v3] LoongArch: Add KFENCE support Enze Li
2023-08-02 15:12 ` Huacai Chen [this message]
2023-08-03 8:05 ` [PATCH 0/4 v3] Add KFENCE support for LoongArch Enze Li
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='CAAhV-H6FqreZtuOXYayhu=bLZeij+fxygbK5Mpw_kVuPTvdbWw@mail.gmail.com' \
--to=chenhuacai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel@xen0n.name \
--cc=lienze@kylinos.cn \
--cc=linux-mm@kvack.org \
--cc=loongarch@lists.linux.dev \
--cc=yangtiezhu@loongson.cn \
--cc=zhangqing@loongson.cn \
/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