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=-16.4 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 45156C4707F for ; Thu, 27 May 2021 15:38:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1F5F6613BA for ; Thu, 27 May 2021 15:38:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229864AbhE0PkQ (ORCPT ); Thu, 27 May 2021 11:40:16 -0400 Received: from mail.kernel.org ([198.145.29.99]:54988 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229698AbhE0PkP (ORCPT ); Thu, 27 May 2021 11:40:15 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id D3EAB613B4; Thu, 27 May 2021 15:38:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1622129922; bh=6+QnGVVn1Ej9j2yLDwI+7HlfIz8hs55ylUpEgzfeRVs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jzHif54TgbSNab2ZLUSFiB2QMSRRxrjOoai6vDQk7SWrnjIpQPI206kPEtoqCd7u0 FostZHoPGglr55A56ygKoJm5SLOfG1K+FrwcRjK3gwO7W3CNHMlXNLS7+VbB/DVumw 3ZX/qNBDxEiwE32KvRe55Zeai+o8EZdK/OWQMPG6IFaFyYrt/ecx5mNPvUkYBqVEVZ 07d9LJu/OIhnc8xAO2hytHNiwex9h25bJMWk1o7YKwe5KkOkiwH2nwr4VRPALYElZK Ud3zqJ0KVdgmwVs7NQhKDXsUe/aDJ6I+1245scYGaD8RvxDV4UJ6vGDuwwZJvmz0ig A4RXJiK/P8yIg== Received: by quaco.ghostprotocols.net (Postfix, from userid 1000) id E45584011C; Thu, 27 May 2021 12:38:38 -0300 (-03) Date: Thu, 27 May 2021 12:38:38 -0300 From: Arnaldo Carvalho de Melo To: Michal =?iso-8859-1?Q?Such=E1nek?= Cc: Andrii Nakryiko , dwarves@vger.kernel.org, bpf@vger.kernel.org, jolsa@kernel.org, kernel-team@fb.com Subject: Re: [PATCH dwarves] btf_encoder: fix and complete filtering out zero-sized per-CPU variables Message-ID: References: <20210524234222.278676-1-andrii@kernel.org> <20210527152758.GI8544@kitsune.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210527152758.GI8544@kitsune.suse.cz> X-Url: http://acmel.wordpress.com Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org Em Thu, May 27, 2021 at 05:27:58PM +0200, Michal Suchánek escreveu: > Hello, > > On Thu, May 27, 2021 at 11:58:24AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Thu, May 27, 2021 at 11:55:10AM -0300, Arnaldo Carvalho de Melo escreveu: > > > Em Mon, May 24, 2021 at 04:42:22PM -0700, Andrii Nakryiko escreveu: > > > > btf_encoder is ignoring zero-sized per-CPU ELF symbols, but the same has to be > > > > done for DWARF variables when matching them with ELF symbols. This is due to > > > > zero-sized DWARF variables matching unrelated (non-zero-sized) variable that > > > > happens to be allocated at the exact same address, leading to a lot of > > > > confusion in BTF. > > > > > > > See [0] for when this causes big problems. > > > > > > > [0] https://lore.kernel.org/bpf/CAEf4BzZ0-sihSL-UAm21JcaCCY92CqfNxycHRZYXcoj8OYb=wA@mail.gmail.com/ > > > > I also added this: > > > > Reported-by: Michal Suchánek > > > > Michal, so you tested this patch and verified it fixed the problem? If > > so please let me know so that I also add: > > This is the first time I see this patch. > > Given that linux-next does not build for me at the moment > I don't think I will test it soon. Ok, I'm test building with torvalds/master, will try with linux-next afterwards, Thanks, - Arnaldo > Thanks > > Michal > > > > > Tested-by: Michal Suchánek > > > > Thanks, > > > > - Arnaldo > > > > > > +++ b/btf_encoder.c > > > > @@ -550,6 +551,7 @@ int cu__encode_btf(struct cu *cu, int verbose, bool force, > > > > > > > > /* addr has to be recorded before we follow spec */ > > > > addr = var->ip.addr; > > > > + dwarf_name = variable__name(var, cu); > > > > > > > > /* DWARF takes into account .data..percpu section offset > > > > * within its segment, which for vmlinux is 0, but for kernel > > > > @@ -582,11 +584,9 @@ int cu__encode_btf(struct cu *cu, int verbose, bool force, > > > > * modules per-CPU data section has non-zero offset so all > > > > * per-CPU symbols have non-zero values. > > > > */ > > > > - if (var->ip.addr == 0) { > > > > - dwarf_name = variable__name(var, cu); > > > > + if (var->ip.addr == 0) > > > > if (!dwarf_name || strcmp(dwarf_name, name)) > > > > continue; > > > > - } > > > > > > > > if (var->spec) > > > > var = var->spec; > > > > @@ -600,6 +600,13 @@ int cu__encode_btf(struct cu *cu, int verbose, bool force, > > > > > > I just changed the above hunk to be: > > > > > > @@ -583,7 +585,6 @@ int cu__encode_btf(struct cu *cu, int verbose, bool force, > > > * per-CPU symbols have non-zero values. > > > */ > > > if (var->ip.addr == 0) { > > > - dwarf_name = variable__name(var, cu); > > > if (!dwarf_name || strcmp(dwarf_name, name)) > > > continue; > > > } > > > > > > > > > Which is shorter and keeps the {} around a multi line if block, ok? > > > > > > Thanks, applied! > > > > > > - Arnaldo > > > > -- > > > > - Arnaldo -- - Arnaldo