Received: by 2002:a05:6358:700f:b0:131:369:b2a3 with SMTP id 15csp215149rwo; Tue, 1 Aug 2023 15:52:40 -0700 (PDT) X-Google-Smtp-Source: APBJJlEjAgD6Szhw9ZQiAkaoIRWT13W0lzopsiksVBloD7aBXHCBNSyUy2P6nGNwgFDz2awPDK/A X-Received: by 2002:a05:6402:70f:b0:522:4505:85db with SMTP id w15-20020a056402070f00b00522450585dbmr3605871edx.4.1690930360073; Tue, 01 Aug 2023 15:52:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690930360; cv=none; d=google.com; s=arc-20160816; b=V2v8LLneBcKsogJrU1os+/2sA1cdnOQUildlSlToZTYSOkK5G8PTYjrTJzTNEr1Ccd VLv8xCob2/A8r2aLGlBnaijT217ja537zN34IiSYp24mYEoiwU2YldOQT79m2VGLtdRC qo14kg4tThnm0qY5cQYsWA8uETYgFQQ0DqLlA3ih+HeNzKuKh3B5hO6EgoF6lCSK1Skg BOuHseGSd/hXLHSS5tp2JIM25C7hKIhqB1nQg7I8j611j1fCrVfjqCV/2mtU8eUcal9A zVn1jSz4Y5bx/Ujt7dEP8zJT3VCQ42C+DoL8lGcWJTicS/qWuDIkjjrk0aC1ynkkuXJC T5EQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=5Drqh2sT1zBZMilh9RfOVtxF5CcsHZfTI9cSZ6ogTqM=; fh=RJCVXEk9SLw7CENg8mkTvkdd2Mkb0yrb9SvSTuNR8AE=; b=u3hJYbhy8krnbsdgUFu0eyQar6VGZSZIRGSJvGRiP6KDC/rzOZayAyWhQouypMNRIY HPufvHUzVQGxopULxLJv08dTyvACQgYi9J0wGh9rILts15FtWSvLY5OXH2OQRj8fZsWm AHmRbvEmY/G+VvgRwMEpP7EmnMD0pqBme8sHXwoWw0ibCqlas+aaMC/Ise9UASLHhiQy eOqx2WS1BieNt/rd3yJLsY+K/IVkhUAf/Ve/z1DXwI5w57xWLz+bytpq2QGwvvw3KAr2 ARUCp9vzp9g4c069XViSp9SBkYWceHqWLaxTKnUYoIU0yDyH7Gw0FPI/b4tHU45f59AN fNlg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=fAEw8pMu; 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 e18-20020a50ec92000000b0052239439e90si9057598edr.484.2023.08.01.15.52.16; Tue, 01 Aug 2023 15:52:40 -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=20221208 header.b=fAEw8pMu; 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 S231610AbjHAWWS (ORCPT + 99 others); Tue, 1 Aug 2023 18:22:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42158 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231220AbjHAWWQ (ORCPT ); Tue, 1 Aug 2023 18:22:16 -0400 Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AEEF01BFD; Tue, 1 Aug 2023 15:22:12 -0700 (PDT) Received: by mail-lf1-x131.google.com with SMTP id 2adb3069b0e04-4fe1b00fce2so8830141e87.3; Tue, 01 Aug 2023 15:22:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690928531; x=1691533331; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=5Drqh2sT1zBZMilh9RfOVtxF5CcsHZfTI9cSZ6ogTqM=; b=fAEw8pMuFSSL+uoE0Rj73sLu0P3dy0Hja/NJaRmTo9YGzvWK3QpbKMoFFTalgKLL90 /ECLSOAhifAqm/cMnA+hIP7UPvncdSOpoDAxAgWDwkaf3jlRDilO1t0P57NTQ+2LP3sR knD/MkDaWSgWaoKs1JOlIwhVcyrtYl/yUlmkRpTWwDMtoczIQQ3OcQ9LjYeGVoaPZvLo kHFQFPUtT10IC87Ur10hjnjSAEZL3Ctuo4dMDcqfqUaqTAZei+jPyJJyzFMeFySSuYHx 67azAEws2lWARt5Bz2P5xO0X+VQaZ7IjmsFhJB2Kr53x3YuIwKzXzFHEp2g2i2KR3u+Q X2Og== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690928531; x=1691533331; h=content-transfer-encoding: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=5Drqh2sT1zBZMilh9RfOVtxF5CcsHZfTI9cSZ6ogTqM=; b=I2MVqnoKlN/vTpp/7P1TrA+E50HunztMG8Z/s8tmiKeOg5WILRFOCSDi5ruA3epCAg 0ROTxM4gL0eU9OnUrrEgQRKOdSutGiZfUVSL7jXFT5Bw+waAvsiycrvuqgm/p9k6+V4q XjzyBf8nouiAI9W+f8MO4DRKjuFeBhB1aYw22kE74C6HLeued6vau7aDlHeP0L4xTyHn HZz1KY4R+adxQOCOFMoYD52hSV2/HpzNaFGB+K/COI5sxt9rgedOCQ4AxPe3UclCTZwv C+1WM6GC30lNhWrSryRVwvyGYmONaQXqRrmJXN16kV5ZCvKFO8cIJz9Jkx9k2plEPed1 Sn5Q== X-Gm-Message-State: ABy/qLaunP/HuvJpT8MXvOUE1FxJYqCfWtf98VlzV9Lb/OuJ2/x10u69 v3upxQOm/XU7cF+jkx7R2bzKDCqGE/g7x6h7k5Y= X-Received: by 2002:a19:e058:0:b0:4f8:69f8:47a0 with SMTP id g24-20020a19e058000000b004f869f847a0mr2724007lfj.29.1690928530617; Tue, 01 Aug 2023 15:22:10 -0700 (PDT) MIME-Version: 1.0 References: <169078860386.173706.3091034523220945605.stgit@devnote2> <169078863449.173706.2322042687021909241.stgit@devnote2> <20230731211527.3bde484d@gandalf.local.home> <20230802001824.90819c7355283843178d9163@kernel.org> In-Reply-To: <20230802001824.90819c7355283843178d9163@kernel.org> From: Alexei Starovoitov Date: Tue, 1 Aug 2023 15:21:59 -0700 Message-ID: Subject: Re: [PATCH v4 3/9] bpf/btf: Add a function to search a member of a struct/union To: Masami Hiramatsu Cc: Steven Rostedt , linux-trace-kernel@vger.kernel.org, LKML , Martin KaFai Lau , bpf , Sven Schnelle , Alexei Starovoitov , Linus Torvalds Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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_BLOCKED,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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, Aug 1, 2023 at 8:18=E2=80=AFAM Masami Hiramatsu wrote: > > On Mon, 31 Jul 2023 19:24:25 -0700 > Alexei Starovoitov wrote: > > > On Mon, Jul 31, 2023 at 6:15=E2=80=AFPM Steven Rostedt wrote: > > > > > > On Mon, 31 Jul 2023 14:59:47 -0700 > > > Alexei Starovoitov wrote: > > > > > > > Assuming that is addressed. How do we merge the series? > > > > The first 3 patches have serious conflicts with bpf trees. > > > > > > > > Maybe send the first 3 with extra selftest for above recursion > > > > targeting bpf-next then we can have a merge commit that Steven can = pull > > > > into tracing? > > > > > > Would it be possible to do this by basing it off of one of Linus's ta= gs, > > > and doing the merge and conflict resolution in your tree before it ge= ts to > > > Linus? > > > > > > That way we can pull in that clean branch without having to pull in > > > anything else from BPF. I believe Linus prefers this over having trac= ing > > > having extra changes from BPF that are not yet in his tree. We only n= eed > > > these particular changes, we shouldn't be pulling in anything specifi= c for > > > BPF, as I believe that will cause issues on Linus's side. > > > > We can try, but I suspect git tricks won't do it. > > Masami's changes depend on patches for kernel/bpf/btf.c that > > are already in bpf-next, so git would have to follow all commits > > that touch this file. > > This point is strange. I'm working on probe/fixes which is based on > v6.5-rc3, so any bpf-next change should not be involved. Can you recheck > this point? > > > I don't think git is smart enough to > > thread the needle and split the commit into files. If one commit touche= s > > btf.c and something else that whole commit becomes a dependency > > that pulls another commit with all files touched by > > the previous commit and so on. > > As far as I understand Steve's method, we will have an intermediate branc= h > on bpf or probe tree, like > > linus(some common commit) ---- probes/btf-find-api > > and merge it to both bpf-next and probes/for-next branch > > +----------------------bpf-next --- (merge bpf patches) > / / merge > common -/\ probes/btf-find-api -/-\ > \ \ merge > +----------------------probes/for-next --- (merge probe patche= s) > > Thus, we can merge both for-next branches at next merge window without > any issue. (But, yes, this is not simple, and needs maxium care) Sounds like the path of least resistance is to keep the changes in kernel/trace and consolidate with kernel/bpf/btf.c after the next merge window.