Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp146469rwb; Wed, 5 Oct 2022 16:15:49 -0700 (PDT) X-Google-Smtp-Source: AMsMyM794GepbxAAY3NBztiJxgKGTl+lhTSzTWlaGOMhKoqmMO+tSXwKBp4RNTecLCTNoiDdfC4s X-Received: by 2002:a17:906:7944:b0:73c:838:ac3d with SMTP id l4-20020a170906794400b0073c0838ac3dmr1606986ejo.242.1665011749241; Wed, 05 Oct 2022 16:15:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1665011749; cv=none; d=google.com; s=arc-20160816; b=c1mNPDQ/5bmSqO5V5WyywnPYgEy52FjpyrpQTjnm8JlIUMPDx/VEgjU7mIHfZoUp+g yBT+dHLIJ3hw66dJEnqeDBohBgakA0I+0nn38nUix4BJvY8gHTu2IYm7hqvKbfMCqWrZ UQHIYNk5GIQRSjKm5c+idGJezvysWXG+jQEaW47ueVH9mPllUREQ8IVGNmPQQcVqN4GF WG8ucey+QyO20O5G+xSFRjWvwSSnAjWV5FO0OUF3AF9VkooA6XRNKnC+tx/cgNEyoLPM 5gxlaWioU+H9r0eVx2X6WDzw4LGxD9zimyMUK+1Le6dsC9AMopB+MfV36oUbbE44Iu/x dEhQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=L7ufU5NJZ1m5iRvOEgBPFkIANRERx7whw7EOLnWZahg=; b=0Ig1BWzu58jqC+Ik4G9HcsVN+ervCsBX7xRkxocvRTiigkZXaE8w6E3glRBAqdcWxD Di8adnvQmGQX+HK71PWP3FMyqhI78FaZRzTwpuG5W9wVPi6oLOOYOW3tCC964N/EXO3f jOiHni7+Ttk0vQq/fLW8UVkbw/EVjRjrBw2V8Mb4OxNmp0ouzPwkyuCWsEeAzT22U8JU 86nluNtO3ViUPdjRB4oGnNzkuTBEGQbO1uOVts20hSzg3zcg26WydzaV5bPK7MNJ0ZDR oHY0Y0NtnomXRLtxwuse5RtMFuU6X5gcapSvWsNMS+2XZHHw19EvmFQerI4lJB8cAmrW 7a2w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=k8uPcu7u; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hs41-20020a1709073ea900b007828388864dsi16969401ejc.692.2022.10.05.16.14.43; Wed, 05 Oct 2022 16:15:49 -0700 (PDT) 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=@gmail.com header.s=20210112 header.b=k8uPcu7u; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229672AbiJEXCk (ORCPT + 99 others); Wed, 5 Oct 2022 19:02:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53574 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229508AbiJEXCj (ORCPT ); Wed, 5 Oct 2022 19:02:39 -0400 Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E51D085599; Wed, 5 Oct 2022 16:02:36 -0700 (PDT) Received: by mail-yb1-xb32.google.com with SMTP id 63so342057ybq.4; Wed, 05 Oct 2022 16:02:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=L7ufU5NJZ1m5iRvOEgBPFkIANRERx7whw7EOLnWZahg=; b=k8uPcu7u+JSMjPJ10LB7tmG2Wunjo9xJkXKMm2Err/usFhtZr+sEaiQ/3LNWCwo9M3 HV/Gu/eODY/YWme6iPaHG7GjSCHSx7FpyBWNxbDJTXCNHANHK2qNuSw80SCmtbOdB7Al e3vlpX/lK+GEaOLx8/pyHhcdAxVmnEM0J4fU05J6nk+xrR9tGx9xZxlLBGKzNm61+pdS c7RwBrI1J5NisiK+mIIjCAiuKDTNiSjt13x4EGtgibV6U9in0e2kJCnIBBmkofd2QsTi Wadppnhar/U2fyRSNpF5qYJbhkAmRQHHigwz82pEMXMWtOYNb/9VOvOeq9K7KaeI3kgF midw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=L7ufU5NJZ1m5iRvOEgBPFkIANRERx7whw7EOLnWZahg=; b=NxUc5XqIuw6mNNXJ73SJUdywa4YzP14pY5SQt93SJMU2oBbUNZjQZdqYQLVxfriodu Mr/gV39lrgFMI6sh88de2zMgw3IGsOGUAZZL4XAfp3vB+zyhnmbO6iq2VwDaOt1jVVkS 2lhc7e4SAp3c9lFXuYet+fAQw9Lt1k2+6yqZ90L7v1ovusDDgI3NDgy8XksY72x0fnDT LB+YeYyklNu40ADKyzt5aci/YTim4XKh00iS09sR27b8IShroWwsz5CIhouxizw1cj6F qVDjqKfgfU1AQPbLxN0mZM2xkiUjmZzRnQWfk8iP9qBnBL/IIQIbclsvpM3ZccThXYIt PzHQ== X-Gm-Message-State: ACrzQf0PiITVc1TvU9s0w0QZ2xCNZ0TafGiFe/2JCPe8E+O+o4N0rDOe d40bfv5J+i31wljjLFFp1s6qGoUfRlnF8rFAtaE= X-Received: by 2002:a25:1042:0:b0:6bb:f807:aa04 with SMTP id 63-20020a251042000000b006bbf807aa04mr2202432ybq.639.1665010956061; Wed, 05 Oct 2022 16:02:36 -0700 (PDT) MIME-Version: 1.0 References: <20221004131750.2306251-1-roberto.sassu@huaweicloud.com> <20221004131750.2306251-2-roberto.sassu@huaweicloud.com> In-Reply-To: <20221004131750.2306251-2-roberto.sassu@huaweicloud.com> From: Andrii Nakryiko Date: Wed, 5 Oct 2022 16:02:23 -0700 Message-ID: Subject: Re: [RESEND][PATCH 1/6] libbpf: Fix LIBBPF_1.0.0 declaration in libbpf.map To: Roberto Sassu Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev, song@kernel.org, yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com, haoluo@google.com, jolsa@kernel.org, mykolal@fb.com, shuah@kernel.org, bpf@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org, Roberto Sassu , stable@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 4, 2022 at 6:18 AM Roberto Sassu wrote: > > From: Roberto Sassu > > Add the missing LIBBPF_0.8.0 at the end of the LIBBPF_1.0.0 declaration, > similarly to other version declarations. > > Cc: stable@vger.kernel.org # 5.19.x there is no need to backport this, libbpf has its own release cycle and it is released from github mirror. And also this doesn't have any effect, this inheritance between versions in .map file is mostly for humans, according [0] (and I checked in practice that it doesn't change anything for libbpf). So it's good to fix, but no need to bother maintainers to backport it to stable branches. [0] https://www.akkadia.org/drepper/dsohowto.pdf > Fixes: e2371b1632b1c ("libbpf: start 1.0 development cycle") > Signed-off-by: Roberto Sassu > --- > tools/lib/bpf/libbpf.map | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tools/lib/bpf/libbpf.map b/tools/lib/bpf/libbpf.map > index c1d6aa7c82b6..04fab9f1fdd7 100644 > --- a/tools/lib/bpf/libbpf.map > +++ b/tools/lib/bpf/libbpf.map > @@ -367,7 +367,7 @@ LIBBPF_1.0.0 { > libbpf_bpf_map_type_str; > libbpf_bpf_prog_type_str; > perf_buffer__buffer; > -}; > +} LIBBPF_0.8.0; > > LIBBPF_1.1.0 { > global: > -- > 2.25.1 >