Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp4269444pxb; Tue, 25 Jan 2022 07:04:29 -0800 (PST) X-Google-Smtp-Source: ABdhPJzerU3lmLNbtJxVYpwhGe0+PG4HazByjHtnViZdnac4Xf5EJR8rLWcEMzcGEU2peA4O3TQ6 X-Received: by 2002:a17:902:c144:b0:14b:7f:b23b with SMTP id 4-20020a170902c14400b0014b007fb23bmr19350842plj.86.1643123068718; Tue, 25 Jan 2022 07:04:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643123068; cv=none; d=google.com; s=arc-20160816; b=ZjiiSRGYm6841JDFprMSRCX4gD9Yj50GpZ24nqBfEuqNC0gLWCwkA3w4SdxrHYubZE r6DE0M913qdjLDy3LAcELZO8zFx/oQV8YVWYyUaIUEdzyuy30Gi15MlyOys7/fdgA441 5J1vWCyqwQeI710D6w9sxeo9QgUaDLC1nlWpxgDKQ2rMuVq+aGipt6sXFy0WI064gQXx t9Z5jlY0JBR8qDqz1tBgsZKVG+07rKPlvk89c3kOr+TAtPKHcE/yjyHZ2lzDrZBhmSuf xJpW1LongZ2jt7PalfvRnsjgpo5pyH/tkG0w72W6dCLX5k/RBp+AWabvqii81Jgnm6S7 M16Q== 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-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=j7kQNZj/5w970T4/w1JLexV7u05T+tisxje5XFdyq4w=; b=VpBkp9lQF7wqVt/uFV4cXtmlOjQc4qHWHZkaG4oYFZhkKZ9uYxituQPy6xFq87A9ol glay8+J5nhINJKjuMWttmtOBt6WHG9/9Y4nBtxPFVnjap0v5SyxYEs77TBGRQdBOk42k kj7628arR1vLwMPb/ECLVlVxnGcHkWVIKSMum/KqH62YRa1++kIbBeVaqOFdWtVCI8X7 oLqe5SuQB+iv+wLyvIoeaQQ233aAn0Bg6rxsXxFFEbqyVmIckOb/OLYjhHgmbcnrwhoj w1LtANIays6FAsklXvalRcGFkAjQ95ZkLA5gEJbG7euNquNjIR2EueozOuIu8JzSl9Pg wN2w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Uddznvuz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 3si4061140pll.54.2022.01.25.07.04.13; Tue, 25 Jan 2022 07:04:28 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Uddznvuz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1380757AbiAYLJY (ORCPT + 99 others); Tue, 25 Jan 2022 06:09:24 -0500 Received: from ams.source.kernel.org ([145.40.68.75]:33576 "EHLO ams.source.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1380278AbiAYLGr (ORCPT ); Tue, 25 Jan 2022 06:06:47 -0500 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 1D6A7B817B6; Tue, 25 Jan 2022 11:06:41 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 34D2BC340E0; Tue, 25 Jan 2022 11:06:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1643108799; bh=79ZI1JT+t/0XUq5Nd2ugbFp9FNFvpyW7RBwf/PEiaOM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=UddznvuzlmuabaNfZ910sOYv5zSt2ptwySdcu5NvWjvh94qnj2gQM5xic4vdlBqbw b/hbRQCRnUKqwrCGNDmIk7BJfzwOJ+VbSEiLu0+w2bPM8K4DbzEq6agp7JQW6b0qL3 VhTh7tZit0OMd1nrj3CSOB3vbGNOs6seav7LVhS8= Date: Tue, 25 Jan 2022 12:06:37 +0100 From: Greg Kroah-Hartman To: Andrii Nakryiko Cc: Holger =?iso-8859-1?Q?Hoffst=E4tte?= , open list , Linus Torvalds , Andrew Morton , linux@roeck-us.net, Shuah Khan , patches@kernelci.org, lkft-triage@lists.linaro.org, pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com, Sudip Mukherjee , linux- stable , Andrii Nakryiko , Alexei Starovoitov , Yonghong Song Subject: Re: [PATCH 5.15 000/846] 5.15.17-rc1 review Message-ID: References: <20220124184100.867127425@linuxfoundation.org> <29a0f562-af46-f4d0-182c-09c8d99e0a93@applied-asynchrony.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 24, 2022 at 02:09:13PM -0800, Andrii Nakryiko wrote: > On Mon, Jan 24, 2022 at 12:36 PM Holger Hoffst?tte > wrote: > > > > On 2022-01-24 19:31, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 5.15.17 release. > > > > Oh noes :( > > > > DESCEND bpf/resolve_btfids > > MKDIR /tmp/linux-5.15.17/tools/bpf/resolve_btfids//libbpf > > GEN /tmp/linux-5.15.17/tools/bpf/resolve_btfids/libbpf/bpf_helper_defs.h > > MKDIR /tmp/linux-5.15.17/tools/bpf/resolve_btfids/libbpf/staticobjs/ > > CC /tmp/linux-5.15.17/tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf.o > > libbpf.c: In function 'bpf_object__elf_collect': > > libbpf.c:3038:31: error: invalid type argument of '->' (have 'GElf_Shdr' {aka 'Elf64_Shdr'}) > > 3038 | if (sh->sh_type != SHT_PROGBITS) > > | ^~ > > libbpf.c:3042:31: error: invalid type argument of '->' (have 'GElf_Shdr' {aka 'Elf64_Shdr'}) > > 3042 | if (sh->sh_type != SHT_PROGBITS) > > | ^~ > > make[4]: *** [/tmp/linux-5.15.17/tools/build/Makefile.build:97: /tmp/linux-5.15.17/tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf.o] Error 1 > > make[3]: *** [Makefile:158: /tmp/linux-5.15.17/tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf-in.o] Error 2 > > make[2]: *** [Makefile:44: /tmp/linux-5.15.17/tools/bpf/resolve_btfids//libbpf/libbpf.a] Error 2 > > make[1]: *** [Makefile:72: bpf/resolve_btfids] Error 2 > > make: *** [Makefile:1371: tools/bpf/resolve_btfids] Error 2 > > > > Reverting "libbpf-validate-that-.btf-and-.btf.ext-sections-cont.patcht" aka > > this one: > > > > > Andrii Nakryiko > > > libbpf: Validate that .BTF and .BTF.ext sections contain data > > > > makes it build & run fine. I looked for followups but couldn't find anything that > > stood out, maybe the BPF folks (cc'ed) know what's missing/wrong. > > > > That small fix depends on much bigger refactoring in ad23b7238474 > ("libbpf: Use Elf64-specific types explicitly for dealing with ELF"). > I think this small fix can be dropped. > > That's sort of a general rule with libbpf-related fixes, they are > usually not that critical to backport to stable, because most users > use/build libbpf from its Github mirror, which is always taken from > latest bpf-next. Libbpf is also not supposed to be used with untrusted > inputs (i.e., BPF object files) as BPF programs are loaded into the > kernel under root. Ok, thanks, I'll drop this from all queues now. greg k-h