From: Stafford Horne <shorne@gmail.com>
To: Rong Xu <xur@google.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Masahiro Yamada <masahiroy@kernel.org>,
Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
linux-openrisc@vger.kernel.org, linux-kbuild@vger.kernel.org,
Han Shen <shenhan@google.com>, Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] openrisc: place exception table at the head of vmlinux
Date: Thu, 5 Dec 2024 19:05:45 +0000 [thread overview]
Message-ID: <Z1H5iZNh7N4Gf7_X@antec> (raw)
In-Reply-To: <CAF1bQ=R_VUDR9rGAWhjPa4jHuauftLg=A9Mp=thJaK8PdjM0Wg@mail.gmail.com>
Hello,
This looks ok to me too. I also confirmed that the symbols that end up in the
.init.text of head.o are correct.
I will queue this to go in the next rc.
-Stafford
On Mon, Dec 02, 2024 at 12:59:27PM -0800, Rong Xu wrote:
> This looks good to me.
>
> Reviewed-by: Rong Xu <xur@google.com>
>
> -Rong
>
> On Mon, Dec 2, 2024 at 12:33 PM Guenter Roeck <linux@roeck-us.net> wrote:
> >
> > On Mon, Dec 02, 2024 at 03:28:22PM +0900, Masahiro Yamada wrote:
> > > Since commit 0043ecea2399 ("vmlinux.lds.h: Adjust symbol ordering in
> > > text output section"), the exception table in arch/openrisc/kernel/head.S
> > > is no longer positioned at the very beginning of the kernel image, which
> > > causes a boot failure.
> > >
> > > Currently, the exception table resides in the regular .text section.
> > > Previously, it was placed at the head by relying on the linker receiving
> > > arch/openrisc/kernel/head.o as the first object. However, this behavior
> > > has changed because sections like .text.{asan,unknown,unlikely,hot} now
> > > precede the regular .text section.
> > >
> > > The .head.text section is intended for entry points requiring special
> > > placement. However, in OpenRISC, this section has been misused: instead
> > > of the entry points, it contains boot code meant to be discarded after
> > > booting. This feature is typically handled by the .init.text section.
> > >
> > > This commit addresses the issue by replacing the current __HEAD marker
> > > with __INIT and re-annotating the entry points with __HEAD. Additionally,
> > > it adds __REF to entry.S to suppress the following modpost warning:
> > >
> > > WARNING: modpost: vmlinux: section mismatch in reference: _tng_kernel_start+0x70 (section: .text) -> _start (section: .init.text)
> > >
> > > Fixes: 0043ecea2399 ("vmlinux.lds.h: Adjust symbol ordering in text output section")
> > > Reported-by: Guenter Roeck <linux@roeck-us.net>
> > > Closes: https://lore.kernel.org/all/5e032233-5b65-4ad5-ac50-d2eb6c00171c@roeck-us.net/#t
> > > Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> >
> > Tested-by: Guenter Roeck <linux@roeck-us.net>
> >
> > Guenter
prev parent reply other threads:[~2024-12-05 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 6:28 [PATCH] openrisc: place exception table at the head of vmlinux Masahiro Yamada
2024-12-02 20:33 ` Guenter Roeck
2024-12-02 20:59 ` Rong Xu
2024-12-05 19:05 ` Stafford Horne [this message]
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=Z1H5iZNh7N4Gf7_X@antec \
--to=shorne@gmail.com \
--cc=jonas@southpole.se \
--cc=kees@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=masahiroy@kernel.org \
--cc=shenhan@google.com \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=xur@google.com \
/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