From mboxrd@z Thu Jan 1 00:00:00 1970 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 91294C433FE for ; Wed, 19 Oct 2022 15:02:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230183AbiJSPCl (ORCPT ); Wed, 19 Oct 2022 11:02:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42254 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229872AbiJSPCX (ORCPT ); Wed, 19 Oct 2022 11:02:23 -0400 Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4CF473BC7C; Wed, 19 Oct 2022 07:56:56 -0700 (PDT) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id DC54158037C; Wed, 19 Oct 2022 10:55:49 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 19 Oct 2022 10:55:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1666191349; x=1666198549; bh=vLMDs+R0Qm IdgQZ4Vz8PN8O4cAAR90i7fWXyp/iiOtc=; b=eyPQSFmtsV8ZrW+KoU8ZZZuZ3r ODVWj7YuCHZwM3N4oWayR3z/2AN1JLQFIHNaMoBx8toiX0A0FiTUJ3fKvDg887Oo IvZMp21KAJ84vUjsHadH3NwbxwbDUo7fnqrGmFEU92SyOJj33DcKI87e42Hllb1z rHyqGmJAEO+LqDbb15dQmL3ad5+yKGHNOkweoQd8+ExBXHzTmLutlC/zHQqafm/z Cb9G8SiIMuFqGgfZ+lt6MUrj3n18zERq7u7ESZ6s12bXWH0c+CZPFq6FzgX4eGdM jqf295mnXW9LI3zTK3I4Bj/ROpx886y/YHUOaKepc+X+ZnVfoLLpBTSvdosw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1666191349; x=1666198549; bh=vLMDs+R0QmIdgQZ4Vz8PN8O4cAAR 90i7fWXyp/iiOtc=; b=PkCKZoZcXQRzr50Ourdgvcz5hJGG2JhYJrLiTGCV06Ql ReinxzTYVo0wO7G3VQTsIUt2djGct10NNn2tKXlImjCe6Iu2ZrBBmOMS/j4Pa0x8 zzC1JpNSG4oHQzEQUghJ9X1FA82EVYDGVb2eyNuFevea5yFOJLO3fBKFTdiKWGln Jb6FDg3AHFkAHJODQIDEjjpEWkjN+pZgNy28t/MNtkDynBOSC/TxTcw9LaI0aHmF Bf4Xs73MTikPQwdfzK0gKS4LoVQpbOpcPp+c45MmFl16dbb9Hwq24DNuXNWM1+1Z nM952PQeHD70YfPkqyGjBfZKpytZ4tn//ZYT9/WbXQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeelgedgkeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghg ucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepgeehue ehgfdtledutdelkeefgeejteegieekheefudeiffdvudeffeelvedttddvnecuffhomhgr ihhnpehkvghrnhgvlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmh epmhgrihhlfhhrohhmpehgrhgvgheskhhrohgrhhdrtghomh X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 19 Oct 2022 10:55:48 -0400 (EDT) Date: Wed, 19 Oct 2022 16:55:46 +0200 From: Greg KH To: Jiri Olsa Cc: stable@vger.kernel.org, bpf@vger.kernel.org, Arnaldo Carvalho de Melo , Daniel Borkmann , Martin Rodriguez Reboredo , Andrii Nakryiko , Javier Martinez Canillas , Ilya Leoshkevich , Nathan Chancellor , Philip =?iso-8859-1?Q?M=FCller?= Subject: Re: [PATCH stable 5.10 0/5] kbuild: Fix compilation for latest pahole release Message-ID: References: <20221019085604.1017583-1-jolsa@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221019085604.1017583-1-jolsa@kernel.org> Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org On Wed, Oct 19, 2022 at 10:55:59AM +0200, Jiri Olsa wrote: > hi, > new version of pahole (1.24) is causing compilation fail for 5.10 > stable kernel, discussed in here [1][2]. Sending fix for that plus > dependency patches. > > thanks, > jirka > > > [1] https://lore.kernel.org/bpf/20220825163538.vajnsv3xcpbhl47v@altlinux.org/ > [2] https://lore.kernel.org/bpf/YwQRKkmWqsf%2FDu6A@kernel.org/ > --- > Andrii Nakryiko (1): > kbuild: skip per-CPU BTF generation for pahole v1.18-v1.21 > > Ilya Leoshkevich (1): > bpf: Generate BTF_KIND_FLOAT when linking vmlinux > > Javier Martinez Canillas (1): > kbuild: Quote OBJCOPY var to avoid a pahole call break the build > > Jiri Olsa (1): > kbuild: Unify options for BTF generation for vmlinux and modules > > Martin Rodriguez Reboredo (1): > kbuild: Add skip_encoding_btf_enum64 option to pahole > > Makefile | 3 +++ > scripts/link-vmlinux.sh | 2 +- > scripts/pahole-flags.sh | 21 +++++++++++++++++++++ > 3 files changed, 25 insertions(+), 1 deletion(-) > create mode 100755 scripts/pahole-flags.sh Ah, all showed up now. I'll look at these tomorrow, thanks! greg k-h