linux-kernel - Re: [PATCH] arm64: switch_to: calculate cpu context pointer using separate register

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 20 Jul 2015 07:25:54 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Will Deacon <will.deacon@....com>, catalin.marinas@....com
CC:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Dave Hansen <dave.hansen@...ux.intel.com>,
	Olof Johansson <olof@...om.net>, Ingo Molnar <mingo@...nel.org>
Subject: Re: [PATCH] arm64: switch_to: calculate cpu context pointer using
 separate register

On 07/20/2015 07:14 AM, Will Deacon wrote:
> Commit 0c8c0f03e3a2 ("x86/fpu, sched: Dynamically allocate 'struct fpu'")
> moved the thread_struct to the bottom of task_struct. As a result, the
> offset is now too large to be used in an immediate add on arm64 with
> some kernel configs:
>
> arch/arm64/kernel/entry.S: Assembler messages:
> arch/arm64/kernel/entry.S:588: Error: immediate out of range
> arch/arm64/kernel/entry.S:597: Error: immediate out of range
>
> This patch calculates the offset using an additional register instead of
> an immediate offset.
>
> Fixes: 0c8c0f03e3a2 ("x86/fpu, sched: Dynamically allocate 'struct fpu'")
> Cc: Dave Hansen <dave.hansen@...ux.intel.com>
> Cc: Olof Johansson <olof@...om.net>
> Cc: Ingo Molnar <mingo@...nel.org>
> Signed-off-by: Will Deacon <will.deacon@....com>

With qemu:

Tested-by: Guenter Roeck <linux@...ck-us.net>

Guenter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/