From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org, Sasha Levin <sashal@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: stable-rc: 4.14 and 4.19: arch/x86/kernel/head_32.S:126: Error: invalid character '(' in mnemonic
Date: Fri, 3 Nov 2023 16:59:59 +0100 [thread overview]
Message-ID: <2023110344-endeared-wrongful-44b3@gregkh> (raw)
In-Reply-To: <2023110339-voyage-subtype-e34e@gregkh>
On Fri, Nov 03, 2023 at 04:57:40PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Nov 03, 2023 at 09:07:32PM +0530, Naresh Kamboju wrote:
> > Following warnings and errors have been noticed while building i386 build
> > on stable-rc linux.4.19.y and linux.4.14.y.
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
> > Build log:
> > ==========
> > kernel/profile.c: In function 'profile_dead_cpu':
> > kernel/profile.c:346:27: warning: the comparison will always evaluate
> > as 'true' for the address of 'prof_cpu_mask' will never be NULL
> > [-Waddress]
> > 346 | if (prof_cpu_mask != NULL)
> > | ^~
> > kernel/profile.c:49:22: note: 'prof_cpu_mask' declared here
> > 49 | static cpumask_var_t prof_cpu_mask;
> > | ^~~~~~~~~~~~~
> > kernel/profile.c: In function 'profile_online_cpu':
> > kernel/profile.c:383:27: warning: the comparison will always evaluate
> > as 'true' for the address of 'prof_cpu_mask' will never be NULL
> > [-Waddress]
> > 383 | if (prof_cpu_mask != NULL)
> > | ^~
> > kernel/profile.c:49:22: note: 'prof_cpu_mask' declared here
> > 49 | static cpumask_var_t prof_cpu_mask;
> > | ^~~~~~~~~~~~~
> > kernel/profile.c: In function 'profile_tick':
> > kernel/profile.c:413:47: warning: the comparison will always evaluate
> > as 'true' for the address of 'prof_cpu_mask' will never be NULL
> > [-Waddress]
> > 413 | if (!user_mode(regs) && prof_cpu_mask != NULL &&
> > | ^~
> > kernel/profile.c:49:22: note: 'prof_cpu_mask' declared here
> > 49 | static cpumask_var_t prof_cpu_mask;
> > | ^~~~~~~~~~~~~
>
> Those are not due to this set of patches, right?
>
> > arch/x86/kernel/head_32.S: Assembler messages:
> > arch/x86/kernel/head_32.S:126: Error: invalid character '(' in mnemonic
> > arch/x86/kernel/head_32.S:57: Info: macro invoked from here
> > arch/x86/kernel/head_32.S:128: Error: invalid character '(' in mnemonic
> > arch/x86/kernel/head_32.S:57: Info: macro invoked from here
>
> This is odd, nothing touches this file either.
>
> 7e09ac27f43b ("x86: Fix .brk attribute in linker script") is backported
> here, perhaps that is the issue? If you revert that, does the error go
> away?
Nope, that's not the issue.
> Let me see if I can build a 32 bit kernel anymore...
I can do this now, let me figure it out...
thanks,
greg k-h
next prev parent reply other threads:[~2023-11-03 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 15:37 stable-rc: 4.14 and 4.19: arch/x86/kernel/head_32.S:126: Error: invalid character '(' in mnemonic Naresh Kamboju
2023-11-03 15:57 ` Greg Kroah-Hartman
2023-11-03 15:59 ` Greg Kroah-Hartman [this message]
2023-11-03 16:09 ` Nathan Chancellor
2023-11-03 16:47 ` 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=2023110344-endeared-wrongful-44b3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jpoimboe@kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=peterz@infradead.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