linux-kernel - Re: xtensa compiler error triggered by 'locking/lockdep: Implement the 'crossrelease' feature'

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] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 10 Sep 2017 20:40:02 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     Byungchul Park <byungchul.park@....com>,
        linux-kernel@...r.kernel.org, Chris Zankel <chris@...kel.net>,
        Max Filippov <jcmvbkbc@...il.com>,
        linux-xtensa@...ux-xtensa.org
Subject: Re: xtensa compiler error triggered by 'locking/lockdep: Implement
 the 'crossrelease' feature'

On Sun, Sep 10, 2017 at 11:31:50AM -0700, Guenter Roeck wrote:
> Hi,
> 
> xtensa:allmodconfig fails to build in mainline with compiler errors
> as follows.
> 
> drivers/staging/rtl8723bs/core/rtw_ap.c: In function ‘expire_timeout_chk’:
> drivers/staging/rtl8723bs/core/rtw_ap.c:442:1: internal compiler error:
> 	in change_address_1, at emit-rtl.c:2126
> 
> drivers/staging/rtl8188eu/core/rtw_ap.c: In function ‘expire_timeout_chk’:
> drivers/staging/rtl8188eu/core/rtw_ap.c:445:1: internal compiler error:
> 	in change_address_1, at emit-rtl.c:2150
> 
> I tried gcc 6.3, 6.4, and 7.2; they all have the same problem.
> 
> Bisect points to commit b09be676e0f ("locking/lockdep: Implement the
> 'crossrelease' feature").
> 
> The compile error is still seen if I disable CONFIG_LOCKDEP_CROSSRELEASE.
> The image builds fine if I disable both CONFIG_RTL8723BS and CONFIG_R8188EU.

I'm taking it this is specific to the GCC xtensa backend, I've not seen
or heard of any other ICEs wrt this code.

I'd take this up with your compiler team, this is not something we can
do much about.