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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 49638C636D4 for ; Thu, 2 Feb 2023 15:36:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232527AbjBBPgP (ORCPT ); Thu, 2 Feb 2023 10:36:15 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56342 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233179AbjBBPfq (ORCPT ); Thu, 2 Feb 2023 10:35:46 -0500 Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3A95F234D4; Thu, 2 Feb 2023 07:35:16 -0800 (PST) Received: by mail-wm1-x332.google.com with SMTP id n13so1700284wmr.4; Thu, 02 Feb 2023 07:35:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:date:from:from:to:cc:subject:date:message-id:reply-to; bh=trv1AGGi2ZldMb5ssniYbBdtJBugUHujIqtgNiIg+Vs=; b=c5Y63VtVWSajudI2t9sYCFJ5AT1CYvsF4csR+nQSPnF7R1hilM1CflU+yEw7hzHGfF zC7c9KRF8Pwl6wbWvUsYRfmMrxm7Qb3DCyPAd/wMtnPYPmj0d8uf+zNsANt4KVhXSSZB uDOmcIVC4rV/VF5glzM7bCdWCZ/LzSSa6SP+GylGOsnJW2VvaH2nFkeJtcA3IlztSaM1 C2ZlzMCnCIjE8S1y2apGpv9Gcnkxt6OLU98GQt2B6g86l8H2v/wT8tuZvqZeklbqGkOc ahFu6jjeB+lqaMbkAUbEzXvuREDRnXl/xBLWubfPFJZFM2+V5iOCW2BUgVs9iBPt/3e0 Pdzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:date:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=trv1AGGi2ZldMb5ssniYbBdtJBugUHujIqtgNiIg+Vs=; b=Ikp3o5qH5MhPywB6XKS4wIdT6v4+z0s+2D7lBWeTVG7UGjHHFzf3iJI2SNXO9JxP/6 hnHLXb3iSZPWkoOhYvTeVuJJ88SaHoewjJHRN/XpbRkH+M/bQduEE1wNRuea+1KCq5e8 aTCumQorCQrA9AYJDdXzuIBtZC9c++kPbvFLFIozQIzoXog3BAqK4Nkwy4k198+RqVHd NfXWRI5OwGk9okMiUzJ+XWBsO4nBfs9l3xst352ijDaqt7ifCnHK4JRjvWR4WylEEuqG zKCwrrh6D8TvsmJzU9CQEhttBsWCJ/IRM1esgRxqTG9SbnPGGFFTojt1F2uQmtTIXs/D h5zQ== X-Gm-Message-State: AO0yUKUlziFB+u3t0PDrnHtwvYZh2n0FT2lDJZ4Dl3ErwZHXTMOREVOB AjrwgJIWTUjMtNpiPpB3844= X-Google-Smtp-Source: AK7set9AnusFcqc2c6udy8lC2Y6wkzqTL1MyGF5uggu+wfO/RWfZBQYHQvqUeEugk2/pBsVxs4pj9Q== X-Received: by 2002:a05:600c:1e06:b0:3dc:18de:b20d with SMTP id ay6-20020a05600c1e0600b003dc18deb20dmr6553730wmb.33.1675352038166; Thu, 02 Feb 2023 07:33:58 -0800 (PST) Received: from krava (2001-1ae9-1c2-4c00-726e-c10f-8833-ff22.ip6.tmcz.cz. [2001:1ae9:1c2:4c00:726e:c10f:8833:ff22]) by smtp.gmail.com with ESMTPSA id h20-20020a05600c351400b003dc22ee5a2bsm5522893wmq.39.2023.02.02.07.33.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Feb 2023 07:33:57 -0800 (PST) From: Jiri Olsa X-Google-Original-From: Jiri Olsa Date: Thu, 2 Feb 2023 16:33:55 +0100 To: Matthew Wilcox Cc: Alexei Starovoitov , Andrii Nakryiko , Hao Luo , Andrew Morton , Alexander Viro , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , bpf@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-perf-users@vger.kernel.org, Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , Stanislav Fomichev , Daniel Borkmann Subject: Re: [RFC 0/5] mm/bpf/perf: Store build id in file object Message-ID: References: <20230201135737.800527-1-jolsa@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 02, 2023 at 03:10:30PM +0000, Matthew Wilcox wrote: > On Wed, Feb 01, 2023 at 02:57:32PM +0100, Jiri Olsa wrote: > > hi, > > we have a use cases for bpf programs to use binary file's build id. > > What is your use case? Is it some hobbyist thing or is it something > that distro kernels are all going to enable? > our use case is for hubble/tetragon [1] and we are asked to report buildid of executed binary.. but the monitoring process is running in its own pod and can't access the the binaries outside of it, so we need to be able to read it in kernel I understand Hao Luo has also use case for that [2] jirka [1] https://github.com/cilium/tetragon/ [2] https://lore.kernel.org/bpf/CA+khW7gAYHmoUkq0UqTiZjdOqARLG256USj3uFwi6z_FyZf31w@mail.gmail.com/