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;
In-Reply-To: <1682214146-3756-1-git-send-email-yangtiezhu@loongson.cn>
References: <1682214146-3756-1-git-send-email-yangtiezhu@loongson.cn>
Subject: Re: [PATCH] riscv: uprobes: Restore thread.bad_cause
Message-Id: <168728927546.19726.7304186466225291370.b4-ty@rivosinc.com>
Date:   Tue, 20 Jun 2023 12:27:55 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Cc:     Guo Ren <guoren@kernel.org>, linux-riscv@lists.infradead.org,
        linux-kernel@vger.kernel.org, loongson-kernel@lists.loongnix.cn
From:   Palmer Dabbelt <palmer@rivosinc.com>
To:     Paul Walmsley <paul.walmsley@sifive.com>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        Albert Ou <aou@eecs.berkeley.edu>,
        Tiezhu Yang <yangtiezhu@loongson.cn>
Precedence: bulk


On Sun, 23 Apr 2023 09:42:26 +0800, Tiezhu Yang wrote:
> thread.bad_cause is saved in arch_uprobe_pre_xol(), it should be restored
> in arch_uprobe_{post,abort}_xol() accordingly, otherwise the save operation
> is meaningless, this change is similar with x86 and powerpc.
> 
> 

Applied, thanks!

[1/1] riscv: uprobes: Restore thread.bad_cause
      https://git.kernel.org/palmer/c/58b1294dd1d6

Best regards,
-- 
Palmer Dabbelt <palmer@rivosinc.com>