public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: Apply dbaee836d60a8 to linux-5.10.y
Date: Thu, 29 Aug 2024 18:19:33 +0200	[thread overview]
Message-ID: <2024082927-subheader-rival-08cf@gregkh> (raw)
In-Reply-To: <20240827222159.GA2737082@thelio-3990X>

On Tue, Aug 27, 2024 at 03:21:59PM -0700, Nathan Chancellor wrote:
> Hi Greg and Sasha,
> 
> Please apply commit dbaee836d60a ("KVM: arm64: Don't use cbz/adr with
> external symbols") to linux-5.10.y, as a recent LLVM optimization around
> __cold functions [1] can cause hyp_panic() to be too far away from
> __guest_enter(), resulting in the same error that occurred with LTO (for
> the same reason):
> 
>   ld.lld: error: arch/arm64/built-in.a(kvm/hyp/entry.o):(function __guest_enter: .text+0x120): relocation R_AARCH64_CONDBR19 out of range: 14339212 is not in [-1048576, 1048575]; references 'hyp_panic'
>   >>> referenced by entry.S:88 (arch/arm64/kvm/hyp/vhe/../entry.S:88)
>   >>> defined in arch/arm64/built-in.a(kvm/hyp/vhe/switch.o)
> 
>   ld.lld: error: arch/arm64/built-in.a(kvm/hyp/entry.o):(function __guest_enter: .text+0x134): relocation R_AARCH64_ADR_PREL_LO21 out of range: 14339192 is not in [-1048576, 1048575]; references 'hyp_panic'
>   >>> referenced by entry.S:97 (arch/arm64/kvm/hyp/vhe/../entry.S:97)
>   >>> defined in arch/arm64/built-in.a(kvm/hyp/vhe/switch.o)
> 
> It applies cleanly with 'patch -p1' and I have verified that it fixes
> the issue.
> 
> [1]: https://github.com/llvm/llvm-project/commit/6b11573b8c5e3d36beee099dbe7347c2a007bf53

Now queued up, thanks.
greg k-h

      reply	other threads:[~2024-08-29 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27 22:21 Apply dbaee836d60a8 to linux-5.10.y Nathan Chancellor
2024-08-29 16:19 ` Greg Kroah-Hartman [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=2024082927-subheader-rival-08cf@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.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