linux-kernel - Re: qcom_scm: Incompatible pointer type build failure

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]

Message-ID: <23774.56553.445601.436491@mariner.uk.xensource.com>
Date:   Fri, 17 May 2019 17:10:17 +0100
From:   Ian Jackson <ian.jackson@...rix.com>
To:     Julien Grall <julien.grall@....com>
CC:     Stefano Stabellini <sstabellini@...nel.org>,
        "xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>,
        "andy.gross@...aro.org" <andy.gross@...aro.org>,
        "david.brown@...aro.org" <david.brown@...aro.org>,
        "linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: qcom_scm: Incompatible pointer type build failure

Julien Grall writes ("qcom_scm: Incompatible pointer type build failure"):
> Thank you for the report.
...> 
> On 30/04/2019 13:44, Ian Jackson wrote:
> > osstest service owner writes ("[linux-4.19 test] 135420: regressions - FAIL"):
> >    drivers/firmware/qcom_scm.c: In function â€˜qcom_scm_assign_memâ€™:
> >    drivers/firmware/qcom_scm.c:469:47: error: passing argument 3 of â€˜dma_alloc_coherentâ€™ from incompatible pointer type [-Werror=incompatible-pointer-types]
...
> > I think this build failure is probably a regression; rather it is due
> > to the stretch update which brings in a new compiler.
> 
> The bug has always been present (and still present in master), it is possible 
> the compiler became smarter with the upgrade to stretch.
> 
> The problem is similar to [1] and happen when the size of phys_addr_t is 
> different to dma_addr_t.
> 
> I have CCed the maintainers of this file.

That was several weeks ago and osstest is still blocked on this.
Can you please advise what CONFIG_* to disable to work around this ?

Ian.