diff options
| author | Bjorn Andersson <bjorn.andersson@oss.qualcomm.com> | 2026-02-20 15:11:48 -0600 |
|---|---|---|
| committer | Bjorn Andersson <andersson@kernel.org> | 2026-03-04 13:12:06 -0600 |
| commit | da994db94e60f9a9411108ddf4d1836147ad4c9c (patch) | |
| tree | a215401a65b136d5d484bee3cddfcdf0cce943c4 /tools/lib/python/kdoc/python_version.py | |
| parent | f9b888599418951b8229bbb28851ed4da50c58e9 (diff) | |
| download | linux-da994db94e60f9a9411108ddf4d1836147ad4c9c.tar.gz linux-da994db94e60f9a9411108ddf4d1836147ad4c9c.zip | |
remoteproc: sysmon: Correct subsys_name_len type in QMI request
The QMI message encoder has up until recently read a single byte (as
elem_size == 1), but with the introduction of big endian support it's
become apparent that this field is expected to be a full u32 -
regardless of the size of the length in the encoded message (which is
what elem_size specifies).
The result is that the encoder now reads past the length byte and
rejects the unreasonably large length formed when including the
following 3 bytes from the subsys_name array.
Fix this by changing to the expected type.
Fixes: 1fb82ee806d1 ("remoteproc: qcom: Introduce sysmon")
Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
Reviewed-by: Chris Lew <christopher.lew@oss.qualcomm.com>
Link: https://lore.kernel.org/r/20260220-qmi-encode-invalid-length-v2-1-5674be35ab29@oss.qualcomm.com
Signed-off-by: Bjorn Andersson <andersson@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
