[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKZGPAOprkJfBXeMqx+ipVh4xqMUCbZdoS=mjBzLO9=LQniU9A@mail.gmail.com>
Date: Wed, 1 May 2019 10:27:41 +0530
From: Arun KS <arunks.linux@...il.com>
To: Will Deacon <will.deacon@....com>
Cc: Arun KS <arunks@...eaurora.org>,
Catalin Marinas <catalin.marinas@....com>,
James Morse <james.morse@....com>,
Mark Rutland <mark.rutland@....com>,
Jun Yao <yaojun8558363@...il.com>,
Steve Capper <steve.capper@....com>,
Vladimir Murzin <vladimir.murzin@....com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: arm64: Fix size of __early_cpu_boot_status
On Tue, Apr 30, 2019 at 4:39 PM Will Deacon <will.deacon@....com> wrote:
>
> On Tue, Apr 30, 2019 at 04:05:04PM +0530, Arun KS wrote:
> > __early_cpu_boot_status is of type long. Use quad
> > assembler directive to allocate proper size.
> >
> > Signed-off-by: Arun KS <arunks@...eaurora.org>
> > ---
> > arch/arm64/kernel/head.S | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/arm64/kernel/head.S b/arch/arm64/kernel/head.S
> > index eecf792..115f332 100644
> > --- a/arch/arm64/kernel/head.S
> > +++ b/arch/arm64/kernel/head.S
> > @@ -684,7 +684,7 @@ ENTRY(__boot_cpu_mode)
> > * with MMU turned off.
> > */
> > ENTRY(__early_cpu_boot_status)
> > - .long 0
> > + .quad 0
>
> Yikes. How did you spot this? Did we end up corrupting an adjacent variable,
> or does the alignment in the linker script save us in practice?
Rite now there is no adjacent variable. But I was adding one and it
was getting corrupted.
Regards,
Arun
>
> Will
Powered by blists - more mailing lists