On Tue, Sep 06, 2022 at 02:03:30PM +0200, Greg KH wrote: > On Mon, Sep 05, 2022 at 09:04:10AM +0200, Jiri Olsa wrote: > > On Sun, Sep 04, 2022 at 04:10:09PM +0200, Greg KH wrote: > > > On Sun, Sep 04, 2022 at 03:18:59PM +0200, Jiri Olsa wrote: > > > > hi, > > > > new version of pahole (1.24) is causing compilation fail for 5.15 > > > > stable kernel, discussed in here [1][2]. Sending fix for that plus > > > > one dependency patch. > > > > > > > > Note for patch 1: > > > > there was one extra line change in scripts/pahole-flags.sh file in > > > > its linux tree merge commit: > > > > > > > > fc02cb2b37fe Merge tag 'net-next-for-5.16' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next > > > > > > > > not sure how/if to track that, I squashed the change in. > > > > > > Squashing is fine, thanks. > > > > > > And do we also need this for kernels older than 5.15? Like 5.10 and 5.4? > > > > yes, 5.10 needs similar patchset, but this for 5.15 won't apply there, > > so I'll send it separately > > > > 5.4 passes compilation, but I don't think it will boot properly, still > > need to check on that > > > > in any case, more patches are coming ;-) > > Ok, these two are now queued up, feel free to send the rest when you > have them ready. hi, as for 5.10 changes, I have them ready, pushed in here: git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git pahole_fix_5_10 but it looks like CONFIG_DEBUG_INFO_BTF is not being used in 5.10, because I had to backport other similar option, that would break the build even earlier (--skip_encoding_btf_vars), or people use just old pahole ;-) I suggest we wait with this change until somebody actually wants this fixed, AFAICS there's no report of broken 5.10 build yet thanks, jirka
