linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: next-20250319: arm shmobile_defconfig trace.c undefined type 'struct module'
Date: Mon, 24 Mar 2025 10:33:13 -0400	[thread overview]
Message-ID: <20250324103313.2bc42730@gandalf.local.home> (raw)
In-Reply-To: <CA+G9fYu54p6zQpX3Kw4dy+Yy3BM66r_iawvLchPvsB_Sq_wCNQ@mail.gmail.com>

On Wed, 19 Mar 2025 19:42:42 +0530
Naresh Kamboju <naresh.kamboju@linaro.org> wrote:

> On Wed, 19 Mar 2025 at 17:01, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > Regressions on arm the shmobile_defconfig builds failed with clang-20 and gcc-13
> >
> > First seen on the next-20250312
> >  Good: next-20250311
> >  Bad:  next-20250312 .. next-20250319
> >
> > Regressions found on arm:
> >  - gcc-13-shmobile_defconfig
> >  - gcc-8-shmobile_defconfig
> >  - clang-20-shmobile_defconfig
> >
> > Regression Analysis:
> >  - New regression? Yes
> >  - Reproducible? Yes
> >
> > Build regression: arm shmobile_defconfig trace.c undefined type 'struct module'
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>  
> 
> Anders bisected this build regression to the following commit,
> 
> # first bad commit:
>    [dca91c1c54686914dec4dabea8bae4f365c02007]
>    tracing: Have persistent trace instances save module addresses
> 
> Lore link,
>  - https://lore.kernel.org/all/CA+G9fYs62qxt1PajEp2A8uUmQFeAsC2JBV2wuspbAxz_hFF7CA@mail.gmail.com/

The fix should have been pushed to linux-next already.

Could you test the latest linux-next?

-- Steve

  reply	other threads:[~2025-03-24 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 11:31 next-20250319: arm shmobile_defconfig trace.c undefined type 'struct module' Naresh Kamboju
2025-03-19 14:12 ` Naresh Kamboju
2025-03-24 14:33   ` Steven Rostedt [this message]
2025-03-25  9:46     ` Naresh Kamboju

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=20250324103313.2bc42730@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=naresh.kamboju@linaro.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;
as well as URLs for NNTP newsgroup(s).