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 X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E2C02ECE58D for ; Wed, 9 Oct 2019 22:49:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B686C20B7C for ; Wed, 9 Oct 2019 22:49:10 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="MpU7Gc2Z" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732199AbfJIWtK (ORCPT ); Wed, 9 Oct 2019 18:49:10 -0400 Received: from mail-lj1-f193.google.com ([209.85.208.193]:44044 "EHLO mail-lj1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730815AbfJIWtJ (ORCPT ); Wed, 9 Oct 2019 18:49:09 -0400 Received: by mail-lj1-f193.google.com with SMTP id m13so4106376ljj.11; Wed, 09 Oct 2019 15:49:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SHjWwqWXsAoaMWH3nFPRAmOyjteP4UWyRPHEWny0YHE=; b=MpU7Gc2ZhlrxOzRtW/Zpvbdpj/1Y2inmDQ5utuRRENmcWZmC7Wf8X3R2bKFEKqhAOj 4jtDgkUrz4eyTLf1xiXNbsqomUIGcd1jLKdCvULzBCLnQiqR4j6cS4/ZfX7WuGqhvE1W 3klPqb5QTCLNcMfySr6q0GRVm0Ivxnf7SO6N/XFJrJhQD9I/Z/eInX0O0yByJlF0WPzZ YM/wEGMdoRvj3Evkx7jKR4TlP2xyMHzuWWM5Z6NCdj7t2ykO+0ggV6Kicrqe3gSDL+lU cAtqgWU4Zk9RCjzDxlgK9e3cI8dYLq6gRCkGz0h1eCIZ+MJ1ipllwSgQw4JJlUpaZIVz ZTQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SHjWwqWXsAoaMWH3nFPRAmOyjteP4UWyRPHEWny0YHE=; b=P6bDpQ0APIZsVtsyAoz2PK3B7jwGSVO8L0qLSGTUa0ZzM7HtjqIGLnms/XlYXm/oJA +KvQ0uNyn5eOHpD+XbIF5F5EdUxLCcme7bWs6IOrFqbp5F/titHfLTbIbzk0BgsCmYEB EvkW1Ji9ZV2TPcLaJ7f+pqPrXIUgXTo6YUaFLkxc9djk4Celz9Sk28w3o0k0Q9Y9KiS2 7NiOysYqoCR/Vem/zY/Y9S/9WwmuJk5CUkqSDClDq8OPmOvcUrnLucSVCtXSjfCBB+zt JKSL0oWP7epgevOBYqQOY4UhM6uIcaS6Ne6mMIQp0lzNvuhiH2y8WgVZby3t6TziMvB1 HFzw== X-Gm-Message-State: APjAAAV5lfqneymJSaiof7XGaRiG5m6TMnVdWKo1tZFPk95BuPWUFQkW 63yk5ElZvAyWZHGDnK+n5oB0gyM7LH6mzdbvEw4= X-Google-Smtp-Source: APXvYqyYFVKhfJgkBLM+FG8JpPoNMl7il25wV/lkiHuiAUHcpBVcSBs97/Oozk0E/tnXyIzdqBlKARxsOAuVgtlVWvE= X-Received: by 2002:a2e:9b12:: with SMTP id u18mr3944269lji.142.1570661347632; Wed, 09 Oct 2019 15:49:07 -0700 (PDT) MIME-Version: 1.0 References: <20191008231009.2991130-1-andriin@fb.com> In-Reply-To: <20191008231009.2991130-1-andriin@fb.com> From: Alexei Starovoitov Date: Wed, 9 Oct 2019 15:48:55 -0700 Message-ID: Subject: Re: [PATCH bpf-next 0/3] Fix BTF-to-C converter's padding generation To: Andrii Nakryiko Cc: bpf , Network Development , Alexei Starovoitov , Daniel Borkmann , John Fastabend , Andrii Nakryiko , Kernel Team Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Tue, Oct 8, 2019 at 4:12 PM Andrii Nakryiko wrote: > > Fix BTF-to-C logic of handling padding at the end of a struct. Fix existing > test that should have captured this. Also move test_btf_dump into a test_progs > test to leverage common infrastructure. Applied. But I see some build weirdness. Probably due to some previous patches. Parallel build in selftests/bpf/ is not always succeeding. For this particular set. New progs/*.c files failed to build the first time.