From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Sasha Levin <sashal@kernel.org>,
linux-stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org
Subject: Re: coresight-tmc-etf.c:477:33: error: 'CORESIGHT_BARRIER_PKT_SIZE' undeclared (first use in this function)
Date: Thu, 15 Jul 2021 19:57:30 +0200 [thread overview]
Message-ID: <YPB3CrJtAdDmnVF8@kroah.com> (raw)
In-Reply-To: <CA+G9fYud=G=NhZdCVrHbadbv2xmeUUmW9vQr_YJqSGBWtNRdfQ@mail.gmail.com>
On Thu, Jul 15, 2021 at 11:22:52PM +0530, Naresh Kamboju wrote:
> Results from Linaro’s test farm.
> Regression detected on arm and arm64 due to the following patch
> with CONFIG_CORESIGHT=y enabled,
>
> coresight: tmc-etf: Fix global-out-of-bounds in tmc_update_etf_buffer()
> commit 5fae8a946ac2df879caf3f79a193d4766d00239b upstream.
>
> Build error:
> ------------
> drivers/hwtracing/coresight/coresight-tmc-etf.c: In function
> 'tmc_update_etf_buffer':
> drivers/hwtracing/coresight/coresight-tmc-etf.c:477:33: error:
> 'CORESIGHT_BARRIER_PKT_SIZE' undeclared (first use in this function)
> 477 | if (lost && i < CORESIGHT_BARRIER_PKT_SIZE) {
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> ref:
> https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc/-/jobs/1427834041#L384
> https://builds.tuxbuild.com/1vMA3olyV9E6Yr1Ix0LWLlXinkv/
I have no idea what tree/branch/queue this report is from :(
next prev parent reply other threads:[~2021-07-15 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 17:52 coresight-tmc-etf.c:477:33: error: 'CORESIGHT_BARRIER_PKT_SIZE' undeclared (first use in this function) Naresh Kamboju
2021-07-15 17:57 ` Greg Kroah-Hartman [this message]
2021-07-15 18:29 ` Naresh Kamboju
2021-07-15 18:55 ` Greg Kroah-Hartman
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=YPB3CrJtAdDmnVF8@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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