From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: kvm: fix a bad BSYM() usage
Date: Mon, 11 May 2015 11:05:37 +0200 [thread overview]
Message-ID: <20150511090537.GA2009@cbox> (raw)
In-Reply-To: <CAKv+Gu922cZLGUJ3-g8CJiUCuL-5L=XHPfgXUMo-jrdPKAuokA@mail.gmail.com>
On Sat, May 09, 2015 at 10:10:56PM +0200, Ard Biesheuvel wrote:
> On 9 May 2015 at 22:07, Christoffer Dall <christoffer.dall@linaro.org> wrote:
> > On Fri, May 08, 2015 at 05:08:42PM +0100, Russell King wrote:
> >> BSYM() should only be used when refering to local symbols in the same
> >> assembly file which are resolved by the assembler, and not for
> >> linker-fixed up symbols. The use of BSYM() with panic is incorrect as
> >> the linker is involved in fixing up this relocation, and it knows
> >> whether panic() is ARM or Thumb.
> >>
> >> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
> >> ---
> >> arch/arm/kvm/interrupts.S | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/arch/arm/kvm/interrupts.S b/arch/arm/kvm/interrupts.S
> >> index 79caf79b304a..87847d2c5f99 100644
> >> --- a/arch/arm/kvm/interrupts.S
> >> +++ b/arch/arm/kvm/interrupts.S
> >> @@ -309,7 +309,7 @@ ENTRY(kvm_call_hyp)
> >> THUMB( orr r2, r2, #PSR_T_BIT )
> >> msr spsr_cxsf, r2
> >> mrs r1, ELR_hyp
> >> - ldr r2, =BSYM(panic)
> >> + ldr r2, =panic
> >> msr ELR_hyp, r2
> >> ldr r0, =\panic_str
> >> clrex @ Clear exclusive monitor
> >> --
> >> 1.8.3.1
> >>
> > Indeed, the linker figures it out as it should. It does seem like the
> > right result is produced with the BSYM() macro as well so not sure what
> > the harm is.
> >
>
> BSYM() is defined as 'sym + 1' not 'sym | 1', so if the symbol has the
> thumb bit set already, the result is incorrect.
>
yeah, but the linker will look at the result of 'sym + 1', so on my
system it ends up with 'sym + 1' after the linker has done its thing
(verified by looking at the disassembly of vmlinux); I assume the
linker logic is that it's branching to a thumb function but the target
is already the +1 so no action necessary, as opposed to just blindly
adding 1.
-Christoffer
next prev parent reply other threads:[~2015-05-11 9:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 16:08 [PATCH 1/2] ARM: kvm: fix a bad BSYM() usage Russell King
2015-05-08 16:21 ` Nicolas Pitre
2015-05-08 16:31 ` Dave P Martin
2015-05-09 20:07 ` Christoffer Dall
2015-05-09 20:10 ` Ard Biesheuvel
2015-05-11 9:05 ` Christoffer Dall [this message]
2015-05-11 9:44 ` Ard Biesheuvel
2015-05-11 10:07 ` Dave P Martin
2015-05-11 9:56 ` Dave P Martin
2015-05-11 10:17 ` Russell King - ARM Linux
2015-05-11 10:27 ` Dave P Martin
2015-05-09 20:10 ` Russell King - ARM Linux
2015-05-11 9:00 ` Christoffer Dall
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=20150511090537.GA2009@cbox \
--to=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).