bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: "Andrii Nakryiko" <andrii.nakryiko@gmail.com>,
	"Tom Stellard" <tstellar@redhat.com>,
	"Jiri Olsa" <jolsa@kernel.org>,
	dwarves@vger.kernel.org, bpf <bpf@vger.kernel.org>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Andrii Nakryiko" <andriin@fb.com>, "Yonghong Song" <yhs@fb.com>,
	"Hao Luo" <haoluo@google.com>, "Mark Wielaard" <mark@klomp.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [RFT] pahole 1.20 RC was Re: [PATCH] btf_encoder: Add extra checks for symbol names
Date: Thu, 28 Jan 2021 23:28:10 +0100	[thread overview]
Message-ID: <CA+icZUWsMKXZSZN9MSY-uCuCa_WVFLjn2JqkaM9e2zwS1A8Z8A@mail.gmail.com> (raw)
In-Reply-To: <20210128211120.GB794568@kernel.org>

On Thu, Jan 28, 2021 at 10:11 PM Arnaldo Carvalho de Melo
<arnaldo.melo@gmail.com> wrote:
>
> Em Thu, Jan 28, 2021 at 09:57:14PM +0100, Sedat Dilek escreveu:
> > On Thu, Jan 28, 2021 at 9:00 PM Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> wrote:
>
> > > Em Thu, Jan 21, 2021 at 08:11:17PM -0800, Andrii Nakryiko escreveu:
> > > > On Thu, Jan 21, 2021 at 6:07 PM Sedat Dilek <sedat.dilek@gmail.com> wrote:
> > > > > Do you want Nick's DWARF v5 patch-series as a base?
>
> > > > Arnaldo was going to figure out the DWARF v5 problem, so I'm leaving
> > > > it up to him. I'm curious about DWARF v4 problems because no one yet
> > > > reported that previously.
>
> > > I think I have the reported one fixed, Andrii, can you please do
> > > whatever pre-release tests you can in your environment with what is in:
>
> > > https://git.kernel.org/pub/scm/devel/pahole/pahole.git/log/?h=DW_AT_data_bit_offset
>
> > > ?
>
> > > The cset has the tests I performed and the references to the bugzilla
> > > ticket and Daniel has tested as well for his XDR + gcc 11 problem.
> >
> > What Git tree should someone use to test this?
> > Linus Git?
> > bpf / bpf-next?
>
> The one you were having problems with :)
>
> This pahole branch should be handling multiple problems, this is the
> list of changes since v1.19:
>
> [acme@five pahole]$ git log --oneline v1.19..
> b91b19840b0062b8 (HEAD -> master, quaco/master, origin/DW_AT_data_bit_offset) dwarf_loader: Support DW_AT_data_bit_offset
> c692e8ac5ccbab99 dwarf_loader: Optimize a bit the reading of DW_AT_data_member_location
> 65917b24942ce620 dwarf_loader: Fix typo
> 77205a119c85e396 dwarf_loader: Introduce __attr_offset() to reuse call to dwarf_attr()
> 8ec231f6b0c8aaef dwarf_loader: Support DW_FORM_implicit_const in attr_numeric()
> 7453895e01edb535 (origin/master, origin/HEAD) btf_encoder: Improve ELF error reporting
> 1bb49897dd2b65b0 bpf_encoder: Translate SHN_XINDEX in symbol's st_shndx values
> 3f8aad340bf1a188 elf_symtab: Handle SHN_XINDEX index in elf_section_by_name()
> e32b9800e650a6eb btf_encoder: Add extra checks for symbol names
> 82749180b23d3c9c libbpf: allow to use packaged version
> 452dbcf35f1a7bf9 btf_encoder: Improve error-handling around objcopy
> cf381f9a3822d68b btf_encoder: Fix handling of restrict qualifier
> b688e35970600c15 btf_encoder: fix skipping per-CPU variables at offset 0
> 8c009d6ce762dfc9 btf_encoder: fix BTF variable generation for kernel modules
> b94e97e015a94e6b dwarves: Fix compilation on 32-bit architectures
> 17df51c700248f02 btf_encoder: Detect kernel module ftrace addresses
> 06ca639505fc56c6 btf_encoder: Use address size based on ELF's class
> aff60970d16b909e btf_encoder: Factor filter_functions function
> 1e6a3fed6e52d365 rpm: Fix changelog date
> [acme@five pahole]$
>
> Now I just need to do the boilerplate update of the version number,
> Changes and .spec file, to release v1.20.
>

When do you plan to release v1.20?
I can wait until this is done.

- Sedat -

  reply	other threads:[~2021-01-28 22:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 18:40 [PATCH] btf_encoder: Add extra checks for symbol names Jiri Olsa
2021-01-12 19:20 ` Andrii Nakryiko
2021-01-12 19:47   ` Jiri Olsa
2021-01-12 20:17     ` Sedat Dilek
2021-01-13  0:27 ` Tom Stellard
2021-01-14  7:50   ` Sedat Dilek
2021-01-14 14:33     ` Tom Stellard
2021-01-14 14:39       ` Sedat Dilek
2021-01-21 13:38   ` Arnaldo Carvalho de Melo
2021-01-21 16:06     ` Sedat Dilek
2021-01-21 19:37       ` Arnaldo Carvalho de Melo
2021-01-21 20:53       ` Andrii Nakryiko
2021-01-22  2:07         ` Sedat Dilek
2021-01-22  4:11           ` Andrii Nakryiko
2021-01-28 20:00             ` [RFT] pahole 1.20 RC was " Arnaldo Carvalho de Melo
2021-01-28 20:57               ` Sedat Dilek
2021-01-28 21:11                 ` Arnaldo Carvalho de Melo
2021-01-28 22:28                   ` Sedat Dilek [this message]
2021-02-02  7:48               ` Andrii Nakryiko
2021-02-03  9:03                 ` Sedat Dilek
2021-02-03 10:23                   ` Mark Wielaard
2021-02-03 21:48                     ` Sedat Dilek
2021-02-03 23:21                       ` Andrii Nakryiko
2021-02-04  1:06                         ` Arnaldo Carvalho de Melo
2021-02-04  6:40                         ` Sedat Dilek
2021-01-21 17:37     ` Tom Stellard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+icZUWsMKXZSZN9MSY-uCuCa_WVFLjn2JqkaM9e2zwS1A8Z8A@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andriin@fb.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=ast@kernel.org \
    --cc=berrange@redhat.com \
    --cc=bpf@vger.kernel.org \
    --cc=dwarves@vger.kernel.org \
    --cc=haoluo@google.com \
    --cc=jolsa@kernel.org \
    --cc=mark@klomp.org \
    --cc=tstellar@redhat.com \
    --cc=yhs@fb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).