Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp4454965rwb; Mon, 21 Nov 2022 07:48:35 -0800 (PST) X-Google-Smtp-Source: AA0mqf58AmlO1sWt3ms9/BFoj7el6CWD7pv7bLvdN6IRClFnhOacQthUeLC8wONGXgMjSH6X0gCn X-Received: by 2002:a05:6402:2b91:b0:457:23cb:20ab with SMTP id fj17-20020a0564022b9100b0045723cb20abmr2470112edb.254.1669045715392; Mon, 21 Nov 2022 07:48:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669045715; cv=none; d=google.com; s=arc-20160816; b=eycpcZC1Y1dh/JOgQzruAtxVK9YqNoaFhjaXS7mLRt+Sx55EnfVUD/Y/P9jrWidQ2J C9QziFVseLlfoe7qUMgvk1PE9e2qQeVszWVaYE5UGFeB/VsANRoG1w1o/6ZgQkonISEM UekFc2nr2BM0BYDlx2P1pHvimyzCHCCdqo4Bm5i7ToZWg+ThtZoS2S99hMDZ7YPVK28M QR3Nwa+Q7ERfX4w6iGFVczancGkD/8YdrHAjkmJr3SsGXLYy+pLKxxG4xkQ/6P/XIfxa 0S7NMBjnVu3jvDBZmPh/V5h4+XFEgxQW7ld5486EU8VYq1XWsvIa9xD+iIGp+j+TeY4n Xrwg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=t75YIu+UPAu41yPDuzOhCo6W2uJLeqXvu5pM58UviwA=; b=uS8Op68TiuF8QSbuiJg8FScqpw20ZWvVLW842BEniS0tbpvEWlrdjU5kHSLeBS/Xmq A1uJ6UBu/pK+/HjlcafrR5bDytt9/2exNM6efmk5hF2zjm3Yqd8b2yX2Vljo5whItDSs 1jQLKzUIN8Sna8u3HQnR+O/uuDLv6uxCG+jS2iDioNgZzcVfWUPLm30YxuapjIoi8ZuE syu1z6H+r9XQwzQ7xVSum2hwVQvN0JWXgj4MfCj/MHhKdW5RnA8kvcinh1NZZG+EEdtV nt5T7yW+nE0lmabh+0/ey+F/HvUidR+EyosQfXGdXzcZpDdVmZ/ZSgQxBRiGk1XN0Np7 bxXQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=YzH3M4U4; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s14-20020a170906168e00b00791a6455597si7531509ejd.955.2022.11.21.07.48.01; Mon, 21 Nov 2022 07:48:35 -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; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=YzH3M4U4; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231225AbiKUOX3 (ORCPT + 91 others); Mon, 21 Nov 2022 09:23:29 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35672 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230449AbiKUOXP (ORCPT ); Mon, 21 Nov 2022 09:23:15 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F135D13F7C for ; Mon, 21 Nov 2022 06:23:14 -0800 (PST) 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 8E87A61269 for ; Mon, 21 Nov 2022 14:23:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 041DAC43147 for ; Mon, 21 Nov 2022 14:23:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1669040594; bh=t75YIu+UPAu41yPDuzOhCo6W2uJLeqXvu5pM58UviwA=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=YzH3M4U40FihLZiXVb/AOeaQTFwQ0QZvTk8jwZ/IBI0hX4SuxomAYnUddYbJ/ziRk L/OvXQK2O8geJ7Ax/Kb5HbbqKfAcNCy8RBvhMuOsYpMnVlcx3tmXVbK4beiZTBcosO VjvGSWmfBpIqlXckGfiJfcy80F5Tb5FyAhvf61JYUuSsN9OIFsnh44FnY3+gAA0KeD Jgsnem/ON4kcTlruRIl35ZvtvPLH5Nb320Cc7SmPJ7bpjhvbSbQB4h2cmioq71GMDx oKQHrfpU6XT2Zu33L+nMuXzPmUMg5Pklq3/ClLCihySmZj8RapaEPiKFECjQMs9H9X /aseua7z6aTKg== Received: by mail-lf1-f49.google.com with SMTP id bp15so19027009lfb.13 for ; Mon, 21 Nov 2022 06:23:13 -0800 (PST) X-Gm-Message-State: ANoB5pkpMxu5WLwEpB82YEfwEAsSkFrgB9ROtGjjH0v2BDcbB1tZK12X FmZzBCkaOkkXCTi+mnhu/4bIrhKYiKQkv7fzsxHUFg== X-Received: by 2002:a19:6755:0:b0:4ac:3f87:151f with SMTP id e21-20020a196755000000b004ac3f87151fmr6631422lfj.398.1669040591780; Mon, 21 Nov 2022 06:23:11 -0800 (PST) MIME-Version: 1.0 References: <20221117121617.4e1529d3@gandalf.local.home> <20221117174030.0170cd36@gandalf.local.home> <20221118114519.2711d890@gandalf.local.home> <43d5d1f5-c01d-c0db-b421-386331c2b8c1@meta.com> <20221118130608.5ba89bd8@gandalf.local.home> <2ab2b854-723a-5f15-8c18-0b5730d1b535@meta.com> In-Reply-To: From: KP Singh Date: Mon, 21 Nov 2022 15:23:00 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC 0/1] BPF tracing for arm64 using fprobe To: Peter Zijlstra Cc: Chris Mason , Steven Rostedt , Mark Rutland , Alexei Starovoitov , Florent Revest , bpf , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Brendan Jackman , markowsky@google.com, Masami Hiramatsu , Xu Kuohai , LKML , Greg Kroah-Hartman , Linus Torvalds , Christoph Hellwig Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,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 Mon, Nov 21, 2022 at 3:17 PM Peter Zijlstra wrote: > > On Mon, Nov 21, 2022 at 02:47:10PM +0100, KP Singh wrote: > > > > > How do I know that a function return was modified by BPF? If I'm debugging > > > > You can list the BPF programs that are loaded in the kernel with > > > > # bpftool prog list > > Only when you have access to the machine; most cases it's people sending > random splats by email. Good point, What about having information about loaded BPF programs in the kernel stack traces and sharing bytecode, somehow, like in crash dumps? > > > Also, the BPF programs show up in call stacks when you are debugging. > > Only when it splats inside the BPF part, not when it splats after > because BPF changed semantics of a function. > >