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: <4a60c3d3-11fb-40fb-8686-3d83539f250b@kernel.org>
Date: Thu, 21 Aug 2025 17:05:59 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Mukesh Ojha <mukesh.ojha@....qualcomm.com>,
 Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konradybcio@...nel.org>,
 Vikash Garodia <quic_vgarodia@...cinc.com>,
 Dikshita Agarwal <quic_dikshita@...cinc.com>,
 Mauro Carvalho Chehab <mchehab@...nel.org>,
 Mathieu Poirier <mathieu.poirier@...aro.org>
Cc: Abhinav Kumar <abhinav.kumar@...ux.dev>,
 Bryan O'Donoghue <bryan.odonoghue@...aro.org>, linux-kernel@...r.kernel.org,
 linux-arm-msm@...r.kernel.org, linux-media@...r.kernel.org,
 linux-remoteproc@...r.kernel.org
Subject: Re: [PATCH v2 07/11] firmware: qcom_scm: Add
 qcom_scm_pas_get_rsc_table() to get resource table

On 19/08/2025 18:54, Mukesh Ojha wrote:
> Qualcomm remote processor may rely on both static and dynamic resources
> for its functionality. Static resources typically refer to memory-mapped
> addresses required by the subsystem and are often embedded within the
> firmware binary and dynamic resources, such as shared memory in DDR
> etc., are determined at runtime during the boot process.
> 
> On Qualcomm Technologies devices, it's possible that static resources

It is possible? Only possible?

> are not embedded in the firmware binary and instead are provided by
> TrustZone However, dynamic resources are always expected to come from

So dynamic are always in TZ?

> TrustZone. This indicates that for Qualcomm devices, all resources
> (static and dynamic) will be provided by TrustZone via the SMC call.

And now all of them are by TZ? Previously it was only possible?

Srsly, what sort of AI hallucinated slop it is?

I think this is pretty close to proof that your submission does not meet
criteria of open source contribution.

Did you run any of this through your legal process in Qualcomm?

I don't trust any part of this code.

Best regards,
Krzysztof


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ