From: Jisheng Zhang <jszhang@kernel.org> To: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Guo Ren <guoren@kernel.org> Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v3 0/4] riscv: entry: further clean up and VMAP_STACK fix Date: Mon, 3 Oct 2022 18:29:17 +0800 [thread overview] Message-ID: <20221003102921.3973-1-jszhang@kernel.org> (raw) I planed to do similar generic entry transaction as Guo Ren did[1], and I had some commits in local. Since Guo has sent out the series, I dropped my version and just provide those in my local repo but missing in Guo's series. However, this doesn't mean this series depends on Guo's series, in fact except the first one, the remaining three patches are independent on generic entry. Since v2: - the patch of removing wrappers of trace_hardirqs_{on,off} is in Guo's v6 generic entry series[2], so remove it. - add a new patch to fix kernel info leakage. - collect Acked-by tag. - the GP saving and restoring macros range from x5 to x31 now per Guo's suggestion. Since v1: - consolidate gp saving/restoring in mcount-dyn.S as well - avoid non-trival memory waste if NR_CPUs is large - collect Reviewed-by tag. [1]https://lore.kernel.org/linux-riscv/20220918155246.1203293-1-guoren@kernel.org/T/#t [2]https://lore.kernel.org/linux-riscv/20221002012451.2351127-1-guoren@kernel.org/T/#t Jisheng Zhang (4): riscv: process: fix kernel info leakage riscv: consolidate ret_from_kernel_thread into ret_from_fork riscv: fix race when vmap stack overflow and remove shadow_stack riscv: entry: consolidate general regs saving/restoring arch/riscv/include/asm/asm-prototypes.h | 1 - arch/riscv/include/asm/asm.h | 63 ++++++++++ arch/riscv/include/asm/thread_info.h | 3 - arch/riscv/kernel/asm-offsets.c | 1 + arch/riscv/kernel/entry.S | 151 +++--------------------- arch/riscv/kernel/mcount-dyn.S | 56 +-------- arch/riscv/kernel/process.c | 7 +- arch/riscv/kernel/traps.c | 32 ++--- 8 files changed, 103 insertions(+), 211 deletions(-) -- 2.37.2
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@kernel.org> To: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Guo Ren <guoren@kernel.org> Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v3 0/4] riscv: entry: further clean up and VMAP_STACK fix Date: Mon, 3 Oct 2022 18:29:17 +0800 [thread overview] Message-ID: <20221003102921.3973-1-jszhang@kernel.org> (raw) I planed to do similar generic entry transaction as Guo Ren did[1], and I had some commits in local. Since Guo has sent out the series, I dropped my version and just provide those in my local repo but missing in Guo's series. However, this doesn't mean this series depends on Guo's series, in fact except the first one, the remaining three patches are independent on generic entry. Since v2: - the patch of removing wrappers of trace_hardirqs_{on,off} is in Guo's v6 generic entry series[2], so remove it. - add a new patch to fix kernel info leakage. - collect Acked-by tag. - the GP saving and restoring macros range from x5 to x31 now per Guo's suggestion. Since v1: - consolidate gp saving/restoring in mcount-dyn.S as well - avoid non-trival memory waste if NR_CPUs is large - collect Reviewed-by tag. [1]https://lore.kernel.org/linux-riscv/20220918155246.1203293-1-guoren@kernel.org/T/#t [2]https://lore.kernel.org/linux-riscv/20221002012451.2351127-1-guoren@kernel.org/T/#t Jisheng Zhang (4): riscv: process: fix kernel info leakage riscv: consolidate ret_from_kernel_thread into ret_from_fork riscv: fix race when vmap stack overflow and remove shadow_stack riscv: entry: consolidate general regs saving/restoring arch/riscv/include/asm/asm-prototypes.h | 1 - arch/riscv/include/asm/asm.h | 63 ++++++++++ arch/riscv/include/asm/thread_info.h | 3 - arch/riscv/kernel/asm-offsets.c | 1 + arch/riscv/kernel/entry.S | 151 +++--------------------- arch/riscv/kernel/mcount-dyn.S | 56 +-------- arch/riscv/kernel/process.c | 7 +- arch/riscv/kernel/traps.c | 32 ++--- 8 files changed, 103 insertions(+), 211 deletions(-) -- 2.37.2 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-10-03 10:39 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-03 10:29 Jisheng Zhang [this message] 2022-10-03 10:29 ` [PATCH v3 0/4] riscv: entry: further clean up and VMAP_STACK fix Jisheng Zhang 2022-10-03 10:29 ` [PATCH v3 1/4] riscv: process: fix kernel info leakage Jisheng Zhang 2022-10-03 10:29 ` Jisheng Zhang 2022-10-04 16:04 ` Guo Ren 2022-10-04 16:04 ` Guo Ren 2022-10-03 10:29 ` [PATCH v3 2/4] riscv: consolidate ret_from_kernel_thread into ret_from_fork Jisheng Zhang 2022-10-03 10:29 ` Jisheng Zhang 2022-10-03 10:29 ` [PATCH v3 3/4] riscv: fix race when vmap stack overflow and remove shadow_stack Jisheng Zhang 2022-10-03 10:29 ` Jisheng Zhang 2022-10-03 10:29 ` [PATCH v3 4/4] riscv: entry: consolidate general regs saving/restoring Jisheng Zhang 2022-10-03 10:29 ` Jisheng Zhang 2022-10-04 16:03 ` Guo Ren 2022-10-04 16:03 ` Guo Ren
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=20221003102921.3973-1-jszhang@kernel.org \ --to=jszhang@kernel.org \ --cc=aou@eecs.berkeley.edu \ --cc=guoren@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.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: linkBe 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.