Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp2938472rwl; Tue, 27 Dec 2022 01:48:18 -0800 (PST) X-Google-Smtp-Source: AMrXdXuU0qW6jd21o6HaPG3N35sDW8FUPFlipc3iSRQFXGWfpOIzkhSaa4JE9CRBNkLqhGDIcexK X-Received: by 2002:a17:903:40c8:b0:189:65e7:e16b with SMTP id t8-20020a17090340c800b0018965e7e16bmr22894602pld.66.1672134498393; Tue, 27 Dec 2022 01:48:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672134498; cv=none; d=google.com; s=arc-20160816; b=PknDL6jZFK+ymO7dgez6kJ0ehhlTV/cz1e0MO5Ck52Y3q/KWZa/b/Gut1T7ImhDoT+ meAvqK6xWpMGOmsj6CduLQUBImnNOc9xAM8txAgFm+WwkRyRFYTW15eDwiDHXFEejoN9 BP+cjgvjuN/LqdC/jy+7antoW/j7tNk3ChlibJsG14Uxoo+AZ6qAyOYhwOVmlHqJbBDO ZwQeLg3U9HmWKtvD+ziaT+pgd1bjNUT9Hp5+edUsV8Bymv3fWlnBkwYeQRxbRXIK0Fbx I6eH5Fith5NDmPwFrAg9bWWPryXUJ6hlVcLKP3EyZppm6n4JHRqLpcdUz2HOmX0J51pv P9NA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=qK3xLkTAWa+cCpx6/m/L/MqOFTWrS5snj/1yQ2EY650=; b=nxmv/HQqvJAwsjZRalRpI9NgICQ+bzMdsppV10lTK0lJwezW5B9zWHGDYuj6PkRJnj VhrL95u5jc79OE38v6WWxDSRfjjIx8ZPZiizglvSXIqiUeIIY90XKyBo7HbgxVyxpT6i ep3jMr1ME+Fk/22tYmmfLUzyowzfdSudLfsnQ/IivgwHAp+d8MhL2X0oTXJVENLdIEAN GjK9zlzJ/vIi5hSLI04DP5WisnFN6ww0bVsGrIVS5zRlTdB4Kg14YaH06TIu+TpzGxtf psv/j9RvuQQuCGCJ+XNeraSojOu93c0twuht/jJvdlpUkLmYp+kHqPGYLqgZXsR4XXZw UFcA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id p13-20020a170902ebcd00b00189b908dd2esi13116862plg.469.2022.12.27.01.48.09; Tue, 27 Dec 2022 01:48:18 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229801AbiL0Ja0 (ORCPT + 67 others); Tue, 27 Dec 2022 04:30:26 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50878 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229578AbiL0JaZ (ORCPT ); Tue, 27 Dec 2022 04:30:25 -0500 Received: from loongson.cn (mail.loongson.cn [114.242.206.163]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id A49C68FE4 for ; Tue, 27 Dec 2022 01:30:23 -0800 (PST) Received: from loongson.cn (unknown [111.9.175.10]) by gateway (Coremail) with SMTP id _____8DxOektu6pjWtEIAA--.16438S3; Tue, 27 Dec 2022 17:30:21 +0800 (CST) Received: from [10.136.12.26] (unknown [111.9.175.10]) by localhost.localdomain (Coremail) with SMTP id AQAAf8Cxnb4ru6pjKtsNAA--.21046S3; Tue, 27 Dec 2022 17:30:20 +0800 (CST) Subject: Re: [PATCH] LoongArch: Fix irq enable in exception handlers To: Huacai Chen Cc: WANG Xuerui , Tiezhu Yang , loongarch@lists.linux.dev, linux-kernel@vger.kernel.org References: <20221221074238.6699-1-hejinyang@loongson.cn> From: Jinyang He Message-ID: <8eaea09e-67b0-5e51-4632-2c31a4c56a3e@loongson.cn> Date: Tue, 27 Dec 2022 17:30:19 +0800 User-Agent: Mozilla/5.0 (X11; Linux loongarch64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-CM-TRANSID: AQAAf8Cxnb4ru6pjKtsNAA--.21046S3 X-CM-SenderInfo: pkhmx0p1dqwqxorr0wxvrqhubq/ X-Coremail-Antispam: 1Uk129KBjvJXoWxJw4xCFy5Zr4kKryDuF4fuFg_yoW7JFWfpF ZrCF48GFW8XFn7Xa9rtw1FvF98X3yvqF4xC3yvka4fWan0vryDWr1vqr47X34jvryDCr10 vryjy3Z293W5JFDanT9S1TB71UUUUU7qnTZGkaVYY2UrUUUUj1kv1TuYvTs0mT0YCTnIWj qI5I8CrVACY4xI64kE6c02F40Ex7xfYxn0WfASr-VFAUDa7-sFnT9fnUUIcSsGvfJTRUUU bI8YFVCjjxCrM7AC8VAFwI0_Jr0_Gr1l1xkIjI8I6I8E6xAIw20EY4v20xvaj40_Wr0E3s 1l1IIY67AEw4v_Jrv_JF1l8cAvFVAK0II2c7xJM28CjxkF64kEwVA0rcxSw2x7M28EF7xv wVC0I7IYx2IY67AKxVW8JVW5JwA2z4x0Y4vE2Ix0cI8IcVCY1x0267AKxVW8JVWxJwA2z4 x0Y4vEx4A2jsIE14v26r4UJVWxJr1l84ACjcxK6I8E87Iv6xkF7I0E14v26r4UJVWxJr1l e2I262IYc4CY6c8Ij28IcVAaY2xG8wAqjxCEc2xF0cIa020Ex4CE44I27wAqx4xG64xvF2 IEw4CE5I8CrVC2j2WlYx0E2Ix0cI8IcVAFwI0_JrI_JrylYx0Ex4A2jsIE14v26r1j6r4U McvjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvEwIxGrwCYjI0SjxkI62AI1cAE67vIY487Mx AIw28IcxkI7VAKI48JMxC20s026xCaFVCjc4AY6r1j6r4UMI8I3I0E5I8CrVAFwI0_Jr0_ Jr4lx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxVWUAVWUtwCIc40Y0x0EwI xGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x0267AKxVWUJVW8 JwCI42IY6xAIw20EY4v20xvaj40_Jr0_JF4lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcV C2z280aVCY1x0267AKxVWUJVW8JbIYCTnIWIevJa73UjIFyTuYvjxU70PfDUUUU X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,NICE_REPLY_A, SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022-12-27 15:37, Huacai Chen wrote: > Hi, Jinyang, > > Move die_if_kernel to irq disabled context to solve what? For more strict logical. If the code flow go to die in die_if_kernel(), its interrupt state is enable, that means it may cause schedule. So I think it is better to call die_if_kernel() firstly. > And LBT is > surely allowed to be triggered in kernel context. I'm not familar with lbt, I just not see any lbt codes in kernel. Plz, how lbt exception triggered, and how kernel trigger lbt exception? Thanks, Jinyang > > Huacai > > On Wed, Dec 21, 2022 at 3:43 PM Jinyang He wrote: >> The interrupt state can be got by regs->csr_prmd. Once previous >> interrupt state is disable, we shouldn't enable interrupt if we >> triggered exception which can be triggered in kernel mode. So >> conditionally enable interrupt. For those do_\exception which >> can not triggered in kernel mode but need enable interrupt, call >> die_if_kernel() firstly. And for do_lsx, do_lasx and do_lbt cannot >> triggered in kernel mode, too. >> >> Signed-off-by: Jinyang He >> --- >> arch/loongarch/kernel/traps.c | 19 ++++++++++--------- >> 1 file changed, 10 insertions(+), 9 deletions(-) >> >> diff --git a/arch/loongarch/kernel/traps.c b/arch/loongarch/kernel/traps.c >> index 1ea14f6c18d3..3ac7b32d1e15 100644 >> --- a/arch/loongarch/kernel/traps.c >> +++ b/arch/loongarch/kernel/traps.c >> @@ -340,9 +340,9 @@ asmlinkage void noinstr do_fpe(struct pt_regs *regs, unsigned long fcsr) >> >> /* Clear FCSR.Cause before enabling interrupts */ >> write_fcsr(LOONGARCH_FCSR0, fcsr & ~mask_fcsr_x(fcsr)); >> - local_irq_enable(); >> >> die_if_kernel("FP exception in kernel code", regs); >> + local_irq_enable(); >> >> sig = SIGFPE; >> fault_addr = (void __user *) regs->csr_era; >> @@ -432,7 +432,8 @@ asmlinkage void noinstr do_bp(struct pt_regs *regs) >> unsigned long era = exception_era(regs); >> irqentry_state_t state = irqentry_enter(regs); >> >> - local_irq_enable(); >> + if (regs->csr_prmd & CSR_PRMD_PIE) >> + local_irq_enable(); >> current->thread.trap_nr = read_csr_excode(); >> if (__get_inst(&opcode, (u32 *)era, user)) >> goto out_sigsegv; >> @@ -514,7 +515,8 @@ asmlinkage void noinstr do_ri(struct pt_regs *regs) >> unsigned int __user *era = (unsigned int __user *)exception_era(regs); >> irqentry_state_t state = irqentry_enter(regs); >> >> - local_irq_enable(); >> + if (regs->csr_prmd & CSR_PRMD_PIE) >> + local_irq_enable(); >> current->thread.trap_nr = read_csr_excode(); >> >> if (notify_die(DIE_RI, "RI Fault", regs, 0, current->thread.trap_nr, >> @@ -606,8 +608,8 @@ asmlinkage void noinstr do_fpu(struct pt_regs *regs) >> { >> irqentry_state_t state = irqentry_enter(regs); >> >> - local_irq_enable(); >> die_if_kernel("do_fpu invoked from kernel context!", regs); >> + local_irq_enable(); >> BUG_ON(is_lsx_enabled()); >> BUG_ON(is_lasx_enabled()); >> >> @@ -623,13 +625,13 @@ asmlinkage void noinstr do_lsx(struct pt_regs *regs) >> { >> irqentry_state_t state = irqentry_enter(regs); >> >> + die_if_kernel("do_lsx invoked from kernel context!", regs); >> local_irq_enable(); >> if (!cpu_has_lsx) { >> force_sig(SIGILL); >> goto out; >> } >> >> - die_if_kernel("do_lsx invoked from kernel context!", regs); >> BUG_ON(is_lasx_enabled()); >> >> preempt_disable(); >> @@ -645,14 +647,13 @@ asmlinkage void noinstr do_lasx(struct pt_regs *regs) >> { >> irqentry_state_t state = irqentry_enter(regs); >> >> + die_if_kernel("do_lasx invoked from kernel context!", regs); >> local_irq_enable(); >> if (!cpu_has_lasx) { >> force_sig(SIGILL); >> goto out; >> } >> >> - die_if_kernel("do_lasx invoked from kernel context!", regs); >> - >> preempt_disable(); >> init_restore_lasx(); >> preempt_enable(); >> @@ -666,6 +667,7 @@ asmlinkage void noinstr do_lbt(struct pt_regs *regs) >> { >> irqentry_state_t state = irqentry_enter(regs); >> >> + die_if_kernel("do_lbt invoked from kernel context!", regs); >> local_irq_enable(); >> force_sig(SIGILL); >> local_irq_disable(); >> @@ -677,7 +679,6 @@ asmlinkage void noinstr do_reserved(struct pt_regs *regs) >> { >> irqentry_state_t state = irqentry_enter(regs); >> >> - local_irq_enable(); >> /* >> * Game over - no way to handle this if it ever occurs. Most probably >> * caused by a fatal error after another hardware/software error. >> @@ -685,8 +686,8 @@ asmlinkage void noinstr do_reserved(struct pt_regs *regs) >> pr_err("Caught reserved exception %u on pid:%d [%s] - should not happen\n", >> read_csr_excode(), current->pid, current->comm); >> die_if_kernel("do_reserved exception", regs); >> + local_irq_enable(); >> force_sig(SIGUNUSED); >> - >> local_irq_disable(); >> >> irqentry_exit(regs, state); >> -- >> 2.34.3 >>