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;
From:   Will Deacon <will@kernel.org>
To:     catalin.marinas@arm.com, guo.ziliang@zte.com.cn
Cc:     kernel-team@android.com, Will Deacon <will@kernel.org>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        huang.junhua@zte.com.cn
Subject: Re: [PATCH] arm64:uprobe fix the uprobe SWBP_INSN in big-endian
Date:   Mon,  5 Dec 2022 15:43:02 +0000
Message-Id: <167024898950.269185.3140250803235881009.b4-ty@kernel.org>
In-Reply-To: <202212021511106844809@zte.com.cn>
References: <202212021511106844809@zte.com.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 2 Dec 2022 15:11:10 +0800 (CST), guo.ziliang@zte.com.cn wrote:
> From: junhua huang <huang.junhua@zte.com.cn>
> 
> We use uprobe in aarch64_be, which we found the tracee task would exit
> due to SIGILL when we enable the uprobe trace.
> We can see the replace inst from uprobe is not correct in aarch big-endian.
> As in Armv8-A, instruction fetches are always treated as little-endian,
> we should treat the UPROBE_SWBP_INSN as little-endian。
> 
> [...]

Applied to arm64 (for-next/insn), thanks!

[1/1] arm64:uprobe fix the uprobe SWBP_INSN in big-endian
      https://git.kernel.org/arm64/c/60f07e22a73d

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev