linux-kernel - Re: Build errors in -next due to ' s390/kernel: lazy restore fpu registers'

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]

Message-ID: <20150803135958.0c34d9a9@mschwide>
Date:	Mon, 3 Aug 2015 13:59:58 +0200
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Hendrik Brueckner <brueckner@...ux.vnet.ibm.com>,
	linux390@...ibm.com, linux-s390@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Build errors in -next due to ' s390/kernel: lazy restore fpu
 registers'

On Fri, 31 Jul 2015 11:35:10 -0700
Guenter Roeck <linux@...ck-us.net> wrote:

> Hi,
> 
> s390:defconfig and s390:allmodconfig fail to build in -next as follows.
> 
> arch/s390/kernel/entry.S:806: Error:
> 	operand out of range (0x00000000000023e8 is not between 0x0000000000000000 and 0x0000000000000fff)
> arch/s390/kernel/entry.S:1254: Error:
> 	operand out of range (0x00000000000023e8 is not between 0x0000000000000000 and 0x0000000000000fff)
> 
> bisect points to commit 9977e886cbb (" s390/kernel: lazy restore fpu
> registers").
> 
> The build has been broken since at least July 20. I thought this was reported
> before, but maybe not; there may have been other failures masking this one.
> 
> Guenter

Should be solved not with an additional patch on the features branch:

git commit d0164ee20d98847d3c777a0ae90e678e7ac1e416
s390/kernel: remove save_fpu_regs() parameter and use __LC_CURRENT instead

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

--
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/