Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp900721iob; Wed, 4 May 2022 10:13:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxkuodU9fTgH3B6eS1Gg4IVLM3k4nYo0EeqT2Z1GmGQ/u6eBNAzK7E9y1Hr2iVBdJbROVDH X-Received: by 2002:a05:6402:1e8d:b0:426:9:6ec with SMTP id f13-20020a0564021e8d00b00426000906ecmr24391155edf.55.1651684433680; Wed, 04 May 2022 10:13:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651684433; cv=none; d=google.com; s=arc-20160816; b=u7m6V4f/mkOe9ntU9ET9wPg6K9/PZWWf+haMh9GHZy5nShs6uIrY722Bjqnau8aifE 9Hydua8drQJx9xtH/DKZcwuyndQW6E9uXOI8RPFNoq+gCEPp4GWCgnGVcRUIPWBS9GCL RE07xZ2yhuD8/HTUAt4RG26R6kf859MZrahC6kblUHpadIz9tExVIvn9dBnWjr4kxa2h Xsu08RAp6bq/kR15f6wChnaGGTkLGjWqHyjbb4UxbhaMZ/KY90ccXq5MNO9hSj1rgbVr ojamiFQyWoOmbHzyhc8LbLj/JP7PUUE/LEGL+8wG6BFZXkHfyPjhdy9+eqAs9xdVze8c Qc3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:content-transfer-encoding:mime-version :message-id:date:subject:cc:from:dkim-signature; bh=sJOJi8YEJ3nP6hlbpshmirix9MrBDt+9JGOZowYXyaA=; b=rEHc93ckQuyIL50UXzkJrztFIMPsX15yzO9CR+SqbsaUXbjpg9tSUdaK3vTqkuJSHV k3Q82YQmaAqBCwhcpDafwXdNAzuzS6kSG7tEL7RGxPu7BcHZYcz3Yo038CoeO16a/6e0 CoGkYg3yy6lyfyzmBbAcWgCsc8TeLH1cYFAsryoHc6uXmAah0YNAu86ZLmoFWbOLJ0jC R5k3EL3VJBcAj76LwCJocKANmVGIY0TAWd53eBn8Z/4VinZj3Ra/qgGiy9/ABqDFkkx6 s1d4OpvjjhMRu6t4SUn+X3UQ++J24C31XE1wXO7hZTYa/IgtxokNYjg7FqVOr3P/R07g Zt/w== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@mdaverde-com.20210112.gappssmtp.com header.s=20210112 header.b=NSzMWvYK; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ho16-20020a1709070e9000b006f4cbc841d7si1684485ejc.1005.2022.05.04.10.13.28; Wed, 04 May 2022 10:13:53 -0700 (PDT) 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=fail header.i=@mdaverde-com.20210112.gappssmtp.com header.s=20210112 header.b=NSzMWvYK; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1350367AbiEDQSR (ORCPT + 99 others); Wed, 4 May 2022 12:18:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49938 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1353185AbiEDQSO (ORCPT ); Wed, 4 May 2022 12:18:14 -0400 Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1EB0F46669 for ; Wed, 4 May 2022 09:14:32 -0700 (PDT) Received: by mail-qt1-x830.google.com with SMTP id hh4so1198062qtb.10 for ; Wed, 04 May 2022 09:14:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mdaverde-com.20210112.gappssmtp.com; s=20210112; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=sJOJi8YEJ3nP6hlbpshmirix9MrBDt+9JGOZowYXyaA=; b=NSzMWvYKnEfZDxgAOpWkhcjwjhxHgjigx5wtKMUEQdE1q2F6Or6GBrYZkkI6nh5BG1 KXgmq2OuHfYRtCtV4pJrKqI5GkR0usospZiQzhX62Gf0/td+E6uXZ2PIdFa9OQb2NjnD K4LnbqNYXgRZA+NaU4enZrshTPOq9GNl1eYiFedIBP+hHTMb89lyc/8ig5DoiHcjOx9c FYU5Z3ymfaJiiyaM0gRgwS/DS0e0Bmmv1kgyhmeUrBttTLFzn8rSWWbcwB7f8W/hPNk5 fyZX9EV7gd+5qMrcw2PahkkBTeK6yqmdtZOc5XmedV4lZliTK1cdI4cObmm7TSGxa6gd RMag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=sJOJi8YEJ3nP6hlbpshmirix9MrBDt+9JGOZowYXyaA=; b=vDtxtz4KBoro7NNFW0G6EtonB2+5yD/4YjLxBAWHJllNB5Nu7FmhzsLl2byKRK0E4N CtxTh49t1XvYstV3oO6MH+G7HczGlPvkzd6ankU5in7SpsIoqZIhT6MOTPRwDwxz5iRI qIWrgl5+mxvCjylty97sV5WkPEm205zRDHU+BbRp5kUJKAX4gO+0xzV47BpEjEpg1aex yUykj0UHe5pKPQjK+gcU6NnKpIYWi2h8rmfEGntPV3RkNILRbxh1vIb2wa4e7fXnAtGe V3lbK5A0aEUI0YaFSeh9+Ui3r4zsPp6tAW2T4tRqMri7wf7AM8p5Rp08u+mUNvK8zt1u oR/w== X-Gm-Message-State: AOAM531Aar+dyX4OZ8AJWot0LIM8HIxlPCASk22F5iq34C7V0WYWyFJH qJFy0xW3i66mbUtkarc+atwlYA== X-Received: by 2002:a05:622a:100c:b0:2e1:b261:f66d with SMTP id d12-20020a05622a100c00b002e1b261f66dmr19760607qte.381.1651680871121; Wed, 04 May 2022 09:14:31 -0700 (PDT) Received: from pop-os.attlocal.net ([2600:1700:1d10:5830:4611:5fd6:ef88:7605]) by smtp.gmail.com with ESMTPSA id 18-20020ac85652000000b002f39b99f66dsm7594467qtt.7.2022.05.04.09.14.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 May 2022 09:14:30 -0700 (PDT) From: Milan Landaverde Cc: milan@mdaverde.com, Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , Quentin Monnet , Paul Chaignon , =?UTF-8?q?Niklas=20S=C3=B6derlund?= , netdev@vger.kernel.org, bpf@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH bpf-next 0/2] bpftool: fix feature output when helper probes fail Date: Wed, 4 May 2022 12:13:30 -0400 Message-Id: <20220504161356.3497972-1-milan@mdaverde.com> X-Mailer: git-send-email 2.32.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net To: unlisted-recipients:; (no To-header on input) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Currently in bpftool's feature probe, we incorrectly tell the user that all of the helper functions are supported for program types where helper probing fails or is explicitly unsupported[1]: $ bpftool feature probe ... eBPF helpers supported for program type tracing: - bpf_map_lookup_elem - bpf_map_update_elem - bpf_map_delete_elem ... - bpf_redirect_neigh - bpf_check_mtu - bpf_sys_bpf - bpf_sys_close This patch adjusts bpftool to relay to the user when helper support can't be determined: $ bpftool feature probe ... eBPF helpers supported for program type lirc_mode2: Program type not supported eBPF helpers supported for program type tracing: Could not determine which helpers are available eBPF helpers supported for program type struct_opts: Could not determine which helpers are available eBPF helpers supported for program type ext: Could not determine which helpers are available Rather than imply that no helpers are available for the program type, we let the user know that helper function probing failed entirely. [1] https://lore.kernel.org/bpf/20211217171202.3352835-2-andrii@kernel.org/ Milan Landaverde (2): bpftool: adjust for error codes from libbpf probes bpftool: output message if no helpers found in feature probing tools/bpf/bpftool/feature.c | 22 +++++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-) -- 2.32.0