linux-kernel - [PATCH 1/3] firmware: qcom_scm: Use proper types for dma mappings

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: <23778.30265.117488.781364@mariner.uk.xensource.com>
Date:   Mon, 20 May 2019 10:41:13 +0100
From:   Ian Jackson <ian.jackson@...rix.com>
To:     Stephen Boyd <swboyd@...omium.org>
CC:     Andy Gross <agross@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
        Julien Grall <julien.grall@....com>,
        "Bjorn Andersson" <bjorn.andersson@...aro.org>,
        Avaneesh Kumar Dwivedi <akdwived@...eaurora.org>
Subject: [PATCH 1/3] firmware: qcom_scm: Use proper types for dma mappings

Stephen Boyd writes ("[PATCH 1/3] firmware: qcom_scm: Use proper types for dma mappings"):
> We need to use the proper types and convert between physical addresses
> and dma addresses here to avoid mismatch warnings. This is especially
> important on systems with a different size for dma addresses and
> physical addresses. Otherwise, we get the following warning:

Thanks.  Do you expect this to be a backport candidate and if so how
far back do you think it will go ?  To be honest, I am not really
convinced that backporting this would be a service to users.  The
situation I have, where I changed the compiler but kept the old kernel
code and old configuration, is going to be fairly rare.

I think I should probably therefore disable this driver in the config
on stable branches of Linux, at least.

Thanks,
Ian.