From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E5C03C4332F for ; Mon, 5 Dec 2022 15:44:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=qXfskYjKYXVHqulA5DCbNPjkUHIH9tpyjbkcPUGAPLA=; b=r37h+rvawrQyf7 J1h3pEL4YOXSnMfmdD39aSwYF/lXJi00iIJ+ULbEb/KRRS4AR9OIH2yFkE2rz4/POwwtWQQssQclI zU/sQ1LOSK28EfKd94qr1dMNVH5bl9Nen6IuRtUhYvBse939WS5kwr7GAXPMxv9H81OntqrlNqAVa 2wZQIcNsXX+xPvmK3to8OJ5L9EwyeleTzgnbU/5DxS1BoIgw9VF5hA6tVyddJsNVVP0JwqjhVVmDj G20tsa0RZAAiJcYCYJMUqvKy+TkGepitvgqxUxs8TCu1MwmSnClz5CEwUgyENJ1Nts6UFmCAYkn7S 0oaRyePtTr6lvYSBqVlg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1p2Dd1-0059Ky-O4; Mon, 05 Dec 2022 15:43:35 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1p2Dch-0058Ue-6l for linux-arm-kernel@lists.infradead.org; Mon, 05 Dec 2022 15:43:16 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 8DB6461188; Mon, 5 Dec 2022 15:43:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id DEDF3C43470; Mon, 5 Dec 2022 15:43:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1670254994; bh=6Jkpcbz2+lmt6R4sfmgb60TXELGrckoMvdie+pxdwac=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=rvm7ORve90+o4kTA1XNBtbQdrwhckcIgIoClFecJWIeYppqGWyvah0WcQ+l6b+sVS efMvtMmYTp+9b7y6wiKelnxhk31t+K76aaD2OMDfLhefoLXIqH3SydbTpMFrZfGTiP t9h7MSobO05sroySfBt7PLuQwjqk/kfiazMN2oHBLOqUP1mvef1rVJB/BczYnVenXi uDaHcAqnMiEXElohAZexTTlrEZ11ne3l82hNzi2tbgvz7AImYD+5rusoD+t8MnwC4U Qfoo1pwrjg6Jp1ok+yOb/x6Jzmurbkj/Dz61cLHxuqdvnOv5bJsDu9dn7CIbgr9qCB w0sDtVe5Z0H3Q== From: Will Deacon To: "Masami Hiramatsu (Google)" , Catalin Marinas Cc: kernel-team@android.com, Will Deacon , Mark Brown , Sandeepa Prabhu , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Mark Rutland , Kalesh Singh , Marc Zyngier Subject: Re: [PATCH v2 0/3] arm64: kprobes: Fix bugs in kprobes for arm64 Date: Mon, 5 Dec 2022 15:43:04 +0000 Message-Id: <167025000853.271112.9111364887989842067.b4-ty@kernel.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <166994750386.439920.1754385804350980158.stgit@devnote3> References: <166994750386.439920.1754385804350980158.stgit@devnote3> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221205_074315_318021_4D0B7AFC X-CRM114-Status: GOOD ( 13.36 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, 2 Dec 2022 11:18:23 +0900, Masami Hiramatsu (Google) wrote: > Here is the 2nd version of the kprobe bugfixes on arm64. The previous > series is here; > > https://lore.kernel.org/all/166990553243.253128.13594802750635478633.stgit@devnote3/T/#u > > The first one is a critical issue, which will cause a kernel crach > easily with lockdep[1/3]. Others are minor issues and rare cases. > The [2/3] let do_page_fault() fixup the page fault in kprobes user > handler, and [3/3] is more like code cleanup and returns > DBG_HOOK_ERROR if it can not handle kprobe's BRK (but that > should not happen.) > > [...] Applied to arm64 (for-next/kprobes), thanks! [1/3] arm64: Prohibit instrumentation on arch_stack_walk() https://git.kernel.org/arm64/c/0fbcd8abf337 [2/3] arm64: kprobes: Let arch do_page_fault() fix up page fault in user handler https://git.kernel.org/arm64/c/30a421552373 [3/3] arm64: kprobes: Return DBG_HOOK_ERROR if kprobes can not handle a BRK https://git.kernel.org/arm64/c/3b84efc066f8 Cheers, -- Will https://fixes.arm64.dev https://next.arm64.dev https://will.arm64.dev _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel