linux-kernel - Re: [PATCH] arm64: defconfig: Enable Qualcomm Command DB driver

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:   Tue, 3 Nov 2020 11:29:59 +0530
From:   Vinod Koul <vkoul@...nel.org>
To:     Bjorn Andersson <bjorn.andersson@...aro.org>
Cc:     john.stultz@...aro.org, Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will@...nel.org>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH] arm64: defconfig: Enable Qualcomm Command DB driver

On 02-11-20, 17:08, Bjorn Andersson wrote:
> The Qualcomm Command DB driver seems to have been indirectly enabled by
> the Qualcomm DRM driver and up until the introduction of '778279f4f5e4
> ("soc: qcom: cmd-db: allow loading as a module")' this resulted in the
> driver "always" being builtin on arm64. But with the introduction of
> said change it, and all other RPMH related drivers, becomes =m.
> 
> The immediate result is that the uart driver fails to probe, which
> depending on userspace's dependency on the presence of /dev/console
> might be fatal. For systems getting past this the default timeout of 0
> seconds for probe deferral of many subsystems causes the system to be
> completely useless.
> 
> So, make Command DB builtin.

Reviewed-by: Vinod Koul <vkoul@...nel.org>

-- 
~Vinod