mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Benjamin Boortz <bennib@mailbox.org>
Cc: Thorsten Leemhuis <linux@leemhuis.info>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
	sr@sladewatkins.com,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH 7.2 0000/1815] 7.2.6-rc1 review
Date: Mon, 14 Sep 2026 11:18:57 +0200	[thread overview]
Message-ID: <2026091443-silenced-maximum-c398@gregkh> (raw)
In-Reply-To: <aqabqJHW_tHhQn3v@bb-82jq>

On Sun, Sep 13, 2026 at 02:54:39PM +0200, Benjamin Boortz wrote:
> On Sat, Sep 12, 2026 at 12:18:56PM +0200, Thorsten Leemhuis wrote:
> 
> > On 9/12/26 08:29, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 7.2.6 release.
> > > There are 1815 patches in this series, all will be posted as a response
> > > to this one.  If anyone has any issues with these being applied, please
> > > let me know.
> > > [...]
> > 
> > My builds failed while compiling perf:
> > 
> > > > ui/browsers/hists.c: In function ‘evsel__hists_browse’:
> > > > ui/browsers/hists.c:3191:41: error: ‘hotkey_act’ undeclared (first use in this function)
> > > >  3191 |                                 memset(&hotkey_act, 0, sizeof(hotkey_act));
> > > >       |                                         ^~~~~~~~~~
> > > > ui/browsers/hists.c:3191:41: note: each undeclared identifier is reported only once for each function it appears in
> > Reverting "perf ui hists: In report UI ensure thread is set with
> > reference counting" fixes this. Haven't tried, but maybe including
> > bd86119c3ee6ed ("perf ui hists: Fix dso_filter reference leak and exit
> > zoom cleanup") will fix this, too.
> > 
> > That got me a little further, but then I ran into this:
> > 
> > > > tools/perf/util/python.c: In function ‘pyrf_evsel__open’:
> > > > tools/perf/util/python.c:1104:9: error: implicit declaration of function ‘CHECK_INITIALIZED’ [-Wimplicit-function-declaration]
> > > >  1104 |         CHECK_INITIALIZED(evsel, "evsel");
> > > >       |         ^~~~~~~~~~~~~~~~~
> > > > tools/perf/util/python.c: In function ‘pyrf_evsel__set_tracking’:
> > > > tools/perf/util/python.c:1295:9: error: implicit declaration of function ‘CHECK_INITIALIZED_INT’ [-Wimplicit-function-declaration]
> > > >  1295 |         CHECK_INITIALIZED_INT(pevsel->evsel, "evsel");
> > > >       |         ^~~~~~~~~~~~~~~~~~~~~
> > 
> > Only looked briefly, but didn't spot a simple way to work around that
> > through a simple revert or two (but it's quite likely I missed something).
> > 
> > Ciao, Thorsten
> > 
> 
> 
> build-tested and reproduced the 2 issues on x86_64 with:
> 
>   make -j$(nproc) -C ./tools/perf O=/tmp/perf-build
> 
> observed errors:
> 
> 1) tools/perf/ui/browsers/hists.c:3191:41: error: 'hotkey_act' undeclared
> 
> 2ec3b9858725 — "perf hists browser: Increase MAX_OPTIONS to prevent stack buffer overflow"
>   prerequisite: bd86119c3ee6 expects MAX_OPTIONS=32; stable-rc still has 16
>   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2ec3b985872594031cc1000b830344de5c26633d
> bd86119c3ee6 — declares hotkey_act, fixes dso_filter reference leak
>   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd86119c3ee6ed7b8fc9be8298fe49f1a5355a46
> 
> 
> 2) tools/perf/util/python.c:1104:9: error: implicit declaration of function 'CHECK_INITIALIZED'
> 
> 01fa2d416ace — defines CHECK_INITIALIZED
>   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=01fa2d416aceab51f97ec2769e8da9971a605eeb
> 
> 
> With the 3 patches applied, perf build successful.

Thanks for that, it fixes it for me too, I'll go queue these up now.

greg k-h

  reply	other threads:[~2026-09-14  9:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12  6:29 Greg Kroah-Hartman
2026-09-12  9:38 ` Brett A C Sheffield
2026-09-12 10:18 ` Thorsten Leemhuis
2026-09-13 12:54   ` Benjamin Boortz
2026-09-14  9:18     ` Greg Kroah-Hartman [this message]
2026-09-12 11:45 ` Ronald Warsow
2026-09-12 21:22 ` Takeshi Ogasawara
2026-09-13 11:22 ` Peter Schneider
2026-09-13 13:04 ` Benjamin Boortz
2026-09-13 14:10 ` Markus Reichelt
2026-09-13 18:19 ` Barry K. Nathan
2026-09-13 22:46 ` Ron Economos
2026-09-14  5:20 ` Miguel Ojeda

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=2026091443-silenced-maximum-c398@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=bennib@mailbox.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@nabladev.com \
    --cc=regressions@lists.linux.dev \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®