Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp3729660pxb; Fri, 4 Feb 2022 15:16:51 -0800 (PST) X-Google-Smtp-Source: ABdhPJyoEx4DkRisu062yp0zk0YZvSPijNRX8XTC46P+t5Qs4A4i3KHrjciaAYH9cIqz81BWArqy X-Received: by 2002:a63:6b43:: with SMTP id g64mr1004058pgc.585.1644016610801; Fri, 04 Feb 2022 15:16:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644016610; cv=none; d=google.com; s=arc-20160816; b=x8wBNWfL0MX4WvoXOLGGCaiG+vlF7T9GB2Wwp18RdqDbNZms3SymH+6DzOwIESX+q8 HFkFJR3sBfb/b8AZ1momX/uof4hKxymxN7i7Mvup3nUum38OF2/jB8S8tPJpNUNPwGLI 5jFVvyVvLZGk870WMBntBAog9uCcnzs7Z8TBf9ahg6L4B05whwqPVWPsiwjs+8vyMXF2 pDxQ/HsgTerItm12z//bjvwKwRxOydL1VWVTV7B+gHo7r9SkKdKHa3Bzw5vLgByfREPo x9gGd8/lgfeMl4ljBfMd91mpAby/8Wk1rtLTBxUKsjCd1OW8SA9/yG2l28UzN3clLzQc mgdg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=a3OAAhJ1yQ586G1GSfs1iva0fA7dOQbeoU53qGnYVps=; b=BLNKN2Eq3cOSw3wzaeSFFscT1H8f5pauu7JpJQ+F/QAHBvnVO0uORdDhWHkZ9F3wGg rmHqQt9AAp4yS0x/xILEvX8mufVOX3hdRnnoBxp8678kdlItJ2XgMKK08gbFBhjpkIPH mAeX0c1wt/OLfpV1jGQJIIUCJs85z4y8/q/UcA3MzEI4QZb0vgInjrmuYwcW2+0EqUdy 8hcm0SAyG1dnv4EXpoJZSbj4joWevMfhBrdapyhZ7rsS7PHSqmoZwFkh0RcsEUa5b4Pr RjiMLattGAEW3/1sPQEU2rfvCpriG2/KdxYYs+QyiVk7eKZPCH5iDPNYT9mWZ7U477Ss mK6g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=U6TIpxq+; 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=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hk13si13761934pjb.110.2022.02.04.15.16.39; Fri, 04 Feb 2022 15:16:50 -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=@redhat.com header.s=mimecast20190719 header.b=U6TIpxq+; 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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346245AbiBBRYU (ORCPT + 99 others); Wed, 2 Feb 2022 12:24:20 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:43203 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242514AbiBBRYR (ORCPT ); Wed, 2 Feb 2022 12:24:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643822656; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=a3OAAhJ1yQ586G1GSfs1iva0fA7dOQbeoU53qGnYVps=; b=U6TIpxq+4usR7Gh+UpQnA9N/aodMJ82vXCKt7rXEub26n0j0mv/BVpwb+vHNSgq/F9LOU+ jojTLXOMhl0e+VbAkrCUcnRmaykPfYGc0XSdemhroI6Lo3DdfudPiRYVCDG8bQfg1wHg07 XIPrh0R/uwpXn6aLWgY30QPtoymY9CM= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-522-2jJZ7fGbPbOp9LgrWv-QXg-1; Wed, 02 Feb 2022 12:24:15 -0500 X-MC-Unique: 2jJZ7fGbPbOp9LgrWv-QXg-1 Received: by mail-wm1-f69.google.com with SMTP id s1-20020a1ca901000000b0034ece94dd8cso4293695wme.5 for ; Wed, 02 Feb 2022 09:24:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=a3OAAhJ1yQ586G1GSfs1iva0fA7dOQbeoU53qGnYVps=; b=okT3BaN827Ylogk5PW/YRTgt7oImwdOoCo2xC8jTxywgrFYu1cvljTscROSABEI+TN +V7vAo5XhSNjzf5ecfN47+OTyyG4h3QVvzNK/lqLowaPvPkCaDD9D2YvHzI4DKCUr2hV W4KIDW3n5N87qnj8zqgob3/J9LUE8M4Tg1rxtrh71b1hJVFhscBLenqqDKInJ1/C9OcH 1cBDjtrq4Mj36iuw5XH9z8n4/IEgWCBohbUBowgtsPC2FlTVUj866c68cPDVfD5fSUU7 J7LaOMRkFzIJ7sUSRrU8H5/uTZL9KcbtaL4L+EBmgffFtemWLhT2I4mjQBwmkDosJV+e koUg== X-Gm-Message-State: AOAM533zpQOo2rbKfAFLuziSKEC7dQconJZbCEYpEE35Yaz7jRcpVd7f yVCWdtDIkCJ1Y5EvzTW1VYh+Hw2TaOQiCwrticR5CPO4VcGBBJLUOByzjmAueeo4VHNZD36nSiE BeCGZKSnbhNk0D4DYnL0DHQay X-Received: by 2002:a05:600c:4801:: with SMTP id i1mr7027713wmo.180.1643822654619; Wed, 02 Feb 2022 09:24:14 -0800 (PST) X-Received: by 2002:a05:600c:4801:: with SMTP id i1mr7027702wmo.180.1643822654476; Wed, 02 Feb 2022 09:24:14 -0800 (PST) Received: from krava (nat-pool-brq-u.redhat.com. [213.175.37.12]) by smtp.gmail.com with ESMTPSA id r2sm25729143wrz.99.2022.02.02.09.24.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 02 Feb 2022 09:24:13 -0800 (PST) Date: Wed, 2 Feb 2022 18:24:12 +0100 From: Jiri Olsa To: Alexei Starovoitov Cc: Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Masami Hiramatsu , Network Development , bpf , lkml , Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , Steven Rostedt , Jiri Olsa Subject: Re: [PATCH 0/8] bpf: Add fprobe link Message-ID: References: <20220202135333.190761-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 Wed, Feb 02, 2022 at 09:09:53AM -0800, Alexei Starovoitov wrote: > On Wed, Feb 2, 2022 at 5:53 AM Jiri Olsa wrote: > > > > hi, > > this patchset adds new link type BPF_LINK_TYPE_FPROBE that attaches kprobe > > program through fprobe API [1] instroduced by Masami. > > No new prog type please. > I thought I made my reasons clear earlier. > It's a multi kprobe. Not a fprobe or any other name. > The kernel internal names should not leak into uapi. > well it's not new prog type, it's new link type that allows to attach kprobe program to multiple functions the original change used BPF_LINK_TYPE_RAW_KPROBE, which did not seem to fit anymore, so I moved to FPROBE, because that's what it is ;-) but if you don't want new name in uapi we could make this more obvious with link name: BPF_LINK_TYPE_MULTI_KPROBE and bpf_attach_type: BPF_TRACE_MULTI_KPROBE jirka