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 B4A72C77B73 for ; Fri, 26 May 2023 18:54:48 +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:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=5M54d7DRTug2ImtwlMRTsWu4Lz0sXCbugLOr5RA8Nls=; b=xyZEBxyumboYTK g5KHX01p9J8DEQvE/0e7RRLVr7BVQ38jC2/J9bbfXxodJKxNi+jZgBdXOahq+n4VC0pwtFJoBsLVU 6q1sLliv/FerEnW/+WnijZV3VuVovDX0v5SIrDp4abzghuyX//AoM0eI28z84kHZWJIySrI1CI8Km AGKg6IyyMIPnL7Tyauqr/3W8WfBf2P4LR0QzA4psqU8ECkCGZP7mUQcU+T/I8WNKXEe8b+Tzux91c xh1JCHNCq5xR+C8B51PXPei0ffTSFRgnbqdy1j2hyeYPvMMHbneYWaZe4FtZXmQu7BrXkTxyK2Qj5 IoaQDC9d8eMoT8Dc9ygQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1q2ca1-003ZDi-0d; Fri, 26 May 2023 18:54:25 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1q2cZy-003ZCA-20 for linux-arm-kernel@lists.infradead.org; Fri, 26 May 2023 18:54:23 +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 8A0DD652A9; Fri, 26 May 2023 18:54:21 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6055DC433D2; Fri, 26 May 2023 18:54:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1685127261; bh=Urg86fkvb89N1W4EU22LaP2G2rEesdWCWKmXrLhixPA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=j+nYEZTgiX0csmwuA4GsCM/V/trUTp+2wIJY1+q0YXr3lfeWIc0JQ8XaLhi81frAG u5uFSqDQBRakCBxnbiR7o/6J2w7YB5QmbfVH0JJuATcydi0/Flu1+0Cw/T1dtCz6Mr OHf5lqgpAN9lXal0ddy1I44pvXiYtrIseirqKkY8= Date: Fri, 26 May 2023 19:54:17 +0100 From: Greg KH To: Jiri Olsa Cc: stable@vger.kernel.org, linux-mm@kvack.org, bpf@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, Masami Hiramatsu , Tsahee Zidenberg , Andrii Nakryiko , Christoph Hellwig , Daniel Borkmann , Thomas Gleixner , =?iso-8859-1?Q?Mah=E9?= Tardy , linux-arm-kernel@lists.infradead.org Subject: Re: [RFC PATCH stable 5.4 0/8] bpf: Fix bpf_probe_read/bpf_probe_read_str helpers Message-ID: <2023052646-magnetize-equate-2b24@gregkh> References: <20230522203352.738576-1-jolsa@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20230522203352.738576-1-jolsa@kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230526_115422_721713_B6C1368F X-CRM114-Status: GOOD ( 15.11 ) 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 Mon, May 22, 2023 at 10:33:44PM +0200, Jiri Olsa wrote: > hi, > we see broken access to user space with bpf_probe_read/bpf_probe_read_str > helpers on arm64 with 5.4 kernel. The problem is that both helpers try to > read user memory by calling probe_kernel_read, which seems to work on x86 > but fails on arm64. Has this ever worked on arm64 for the 5.4 kernel tree? If not, it's not really a regression, and so, why not use a newer kernel that has this new feature added to it there? In other words, what requires you to use the 5.4.y tree and requires feature parity across architectures? thanks, greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel