From nobody Thu Apr 2 05:49:35 2026 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 74E593AEF55 for ; Mon, 30 Mar 2026 09:12:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774861958; cv=none; b=HCWwANqpa7tFWnRHbfDyjNMehq57yym72x0QikFMOmh4zL3H/Re7V/rR2lE3P58qBfo98Oc1dVrWyUyOU66Tik8I7dVCeFnxOH06dBGeqrbyVxpRNu5e7jZq2J4ELpmLF0U5CJKWENHcCdb+nEA3WvX+58DxiBkmITcSumOeFnM= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774861958; c=relaxed/simple; bh=y7Q5Ib2UgBOzKCSKBQpKN/ID969aZEB5jkNSBraOAbw=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=uLg+KmtB3S8vAtQl5eyrbmGt2Vjxh7Ue5DJK2+VRYYnG9ui89tyhj8FKpoqG1tTzBgIuhbmF+bGZOncWKFEa7mtJitqghPyIanGNOAfCLjUfHHXGcAmY/X/ejWHmm6KH/QYXnM/snz8TWABbF4ZCm4Eb9Eul1EqAlOM+x0WjxrA= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=BhQs5bf3; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="BhQs5bf3" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1774861956; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=Aji3OuIasTbG7nwf/w5iZ+Q2tfC4MvavQKG2epUf4Ok=; b=BhQs5bf3m7Bvc6HkO/8BlUzX45tuhBvE0H/gEpE2uv7OCJ6hLxrEqwwUCpNXIvCG+r27Si UhLzHLbDJwwKlu6aLLjwLXAoprdUZcAuMSI9xt0PuybUTEGiktTQYoatyOsMGeIHkxMWif HVP96XEVT0U7x6Mkgz8UbKdWV59N7aE= Received: from mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-433-Li13eHcuO-KTXiiK-by_SA-1; Mon, 30 Mar 2026 05:12:33 -0400 X-MC-Unique: Li13eHcuO-KTXiiK-by_SA-1 X-Mimecast-MFC-AGG-ID: Li13eHcuO-KTXiiK-by_SA_1774861952 Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 358F919560AF; Mon, 30 Mar 2026 09:12:32 +0000 (UTC) Received: from fedora.brq.redhat.com (unknown [10.43.17.109]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id D3D60180075E; Mon, 30 Mar 2026 09:12:28 +0000 (UTC) From: Tomas Glozar To: Steven Rostedt , Tomas Glozar Cc: John Kacur , Luis Goncalves , Crystal Wood , Costa Shulyupin , Wander Lairson Costa , LKML , linux-trace-kernel Subject: [PATCH] rtla: Fix build without libbpf header Date: Mon, 30 Mar 2026 11:12:07 +0200 Message-ID: <20260330091207.16184-1-tglozar@redhat.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 Content-Type: text/plain; charset="utf-8" rtla supports building without libbpf. However, BPF actions patchset [1] adds an include of bpf/libbpf.h into timerlat_bpf.h, which breaks build on systems that don't have libbpf headers installed. This is a leftover from a draft version of the patchset where timerlat_bpf_set_action() (which takes a struct bpf_program * argument) was defined in the header. timerlat_bpf.c already includes bpf/libbpf.h via timerlat.skel.h when libbpf is present. Remove the redundant include to fix build on systems without libbpf headers. [1] https://lore.kernel.org/linux-trace-kernel/20251126144205.331954-1-tglo= zar@redhat.com/T/ Reported-by: Steven Rostedt (Google) Closes: https://lore.kernel.org/linux-trace-kernel/20260329122202.65a8b575@= robin/ Fixes: 8cd0f08ac72e ("rtla/timerlat: Support tail call from BPF program") Signed-off-by: Tomas Glozar Reviewed-by: Wander Lairson Costa --- tools/tracing/rtla/src/timerlat_bpf.h | 1 - 1 file changed, 1 deletion(-) diff --git a/tools/tracing/rtla/src/timerlat_bpf.h b/tools/tracing/rtla/src= /timerlat_bpf.h index 169abeaf4363..f7c5675737fe 100644 --- a/tools/tracing/rtla/src/timerlat_bpf.h +++ b/tools/tracing/rtla/src/timerlat_bpf.h @@ -12,7 +12,6 @@ enum summary_field { }; =20 #ifndef __bpf__ -#include #ifdef HAVE_BPF_SKEL int timerlat_bpf_init(struct timerlat_params *params); int timerlat_bpf_attach(void); --=20 2.53.0