misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps() by Jianping-Li · Pull Request #774 · qualcomm-linux/kernel

Jianping (Jianping-Li) · 2026-06-25T08:57:03Z

fastrpc_create_maps() performs map lookup only for buffer arguments (i < ctx->nbufs) via fastrpc_map_create(). For
arguments beyond this range, no lookup is performed, which can result in duplicate DMA mappings for the same file descriptor.

Additionally, if the same file descriptor is passed multiple times within a single invocation, performing lookups with
reference counting would increment the reference multiple times, while fastrpc_put_args() would release it only once,
leading to an imbalanced reference count.

Fix this by allowing fastrpc_map_create() to control whether the lookup should take a reference. For arguments beyond
ctx->nbufs, the lookup is performed without taking a reference, ensuring that existing mappings are reused without introducing duplicate DMA mappings or reference count imbalance.

CRs-Fixed: 4490320

qswat-orbit-external · 2026-06-25T08:57:23Z

Merge Check Failed: No Change Task Found

No associated change tasks found for CR 4490320 on any of the following entities:

Entities:

kernel.qli.2.0

CR: 4490320

Please ensure the CR has a change task associated with at least one of the entities for this branch.

qswat-orbit-external · 2026-06-25T08:58:23Z

Merge Check Failed: No Change Task Found

No associated change tasks found for CR 4490320 on any of the following entities:

Entities:

kernel.qli.2.0

CR: 4490320

Please ensure the CR has a change task associated with at least one of the entities for this branch.

qlijarvis · 2026-06-25T09:45:46Z

PR #774 — validate-patch

PR: #774

Verdict	Issues	Detailed Report
⚠️	2	Full report

Final Summary

Lore link present: Yes — both commits include lore.kernel.org links in Link: tags
Lore link matches PR commits: Cannot verify (network restricted) — links are present and formatted correctly, dates align with commit dates suggesting recent/concurrent submission
Upstream patch status:
- Commit 1: Marked BACKPORT, suggests already upstream but no SHA provided
- Commit 2: Marked FROMLIST, indicates under review on mailing list (dated same day as analysis: 2026-06-25)
PR present in qcom-next: Not checked — no kernel tree access per constraints

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #774
Upstream commits:

Commit 1: https://lore.kernel.org/all/20260530204528.116920-5-srini@kernel.org/

Commit 2: https://lore.kernel.org/all/20260625080832.17477-1-jianping.li@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Commit 1: BACKPORT: misc: fastrpc: fix use-after-free race in fastrpc_map_create

Commit Message

Check Status Note

Subject matches upstream ⚠️ Added "BACKPORT:" prefix; core subject preserved

Body preserves rationale ✅ Full rationale preserved verbatim

Fixes tag present/correct ✅ Fixes: 10df039834f8 present

Authorship preserved ✅ Original author Zhenghang Xiao preserved

Backport note (if applicable) ⚠️ BACKPORT prefix present but no explicit backport context in body

Diff

File Status Notes

drivers/misc/fastrpc.c ✅ Changes appear structurally sound: adds take_ref parameter to fastrpc_map_lookup, updates all call sites

Issues

BACKPORT prefix without context: The commit uses BACKPORT: prefix but does not explain which kernel version this is being backported to, or why backporting is necessary. Standard kernel practice for backports includes a note like "[ Upstream commit ]" or explanation of adaptation.

Lore link date anomaly: The lore link shows date 20260530 (May 30, 2026) but the commit date is also May 30, 2026. This suggests the patch may be very recent or the dates are future-dated (current date context shows June 25, 2026).

Verdict

Structurally correct but missing backport context. Should add upstream commit SHA or explain adaptation if this is a backport.

Commit 2: FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()

Commit Message

Check Status Note

Subject matches upstream ⚠️ Added "FROMLIST:" prefix; core subject preserved

Body preserves rationale ✅ Detailed explanation of the problem and fix

Fixes tag present/correct ⚠️ Fixes: 10df039834f84 has extra digit (should be 12-char SHA)

Authorship preserved ✅ Author Jianping Li with @oss.qualcomm.com email

Backport note (if applicable) N/A FROMLIST indicates pending upstream review

Diff

File Status Notes

drivers/misc/fastrpc.c ✅ Extends commit 1's take_ref parameter to fastrpc_map_create, updates all call sites consistently

Issues

Fixes tag SHA length: The Fixes tag shows 10df039834f84 (13 characters) instead of the standard 12-character format. Should be 10df039834f8.

Cc tag format: Uses Cc: stable@kernel.org instead of Cc: stable@vger.kernel.org (commit 1 uses the correct format).

Lore link date: Shows 20260625 (June 25, 2026) which matches the commit date, suggesting this is a very recent or same-day submission.

Dependency on commit 1: This commit builds directly on commit 1's changes (extends the take_ref parameter). The two commits form a logical series.

Verdict

Functionally correct but has minor tag formatting issues (Fixes SHA length, stable email address).

Overall Assessment

Issues Summary

Commit 1 (BACKPORT):

Missing backport context (no upstream SHA reference or adaptation notes)

BACKPORT prefix suggests this is a backport, but no explanation of what it's backported from

Commit 2 (FROMLIST):

Fixes tag has 13-character SHA instead of 12

Cc: stable email uses @kernel.org instead of @vger.kernel.org

Series dependency:

Commit 2 depends on commit 1's changes (both modify fastrpc_map_lookup and fastrpc_map_create)

The series is logically coherent and addresses related race conditions

Verdict

⚠️ PARTIAL PASS — The patches are functionally correct and address real use-after-free and duplicate mapping issues. However, they have metadata issues:

Commit 1 needs backport context or upstream SHA

Commit 2 needs Fixes tag correction (12-char SHA) and stable email correction

Recommendations
For commit 1: Either remove "BACKPORT:" prefix if this is the original submission, or add proper backport context like:
[ Upstream commit <12-char-sha> ]
or explain any adaptations made during backport.
For commit 2: Fix the Fixes tag:
- Fixes: 10df039834f84 ("misc: fastrpc: Skip reference for DMA handles")
+ Fixes: 10df039834f8 ("misc: fastrpc: Skip reference for DMA handles")
And correct the stable Cc:
- Cc: stable@kernel.org
+ Cc: stable@vger.kernel.org
Final Summary

Lore link present: Yes — both commits include lore.kernel.org links in Link: tags

Lore link matches PR commits: Cannot verify (network restricted) — links are present and formatted correctly, dates align with commit dates suggesting recent/concurrent submission

Upstream patch status:

Commit 1: Marked BACKPORT, suggests already upstream but no SHA provided

Commit 2: Marked FROMLIST, indicates under review on mailing list (dated same day as analysis: 2026-06-25)

PR present in qcom-next: Not checked — no kernel tree access per constraints

qlijarvis · 2026-06-25T09:45:48Z

PR #774 — checker-log-analyzer

PR: #774
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/28158895933

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	Alignment issue in commit 2/2
dt-binding-check	⏭️	No DT binding changes
dtb-check	⏭️	No devicetree changes
sparse-check	✅	Passed
check-uapi-headers	✅	No UAPI changes
check-patch-compliance	❌	Commit 1/2 differs from upstream link
tag-check	N/A	Not applicable for this branch
qcom-next-check	✅	BACKPORT/FROMLIST prefixes present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #774 - misc: fastrpc: fix use-after-free and duplicate DMA mappings
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28158895933

Checker Result Summary

checkpatch ❌ Alignment issue in commit 2/2

dt-binding-check ⏭️ No DT binding changes

dtb-check ⏭️ No devicetree changes

sparse-check ✅ Passed

check-uapi-headers ✅ No UAPI changes

check-patch-compliance ❌ Commit 1/2 differs from upstream link

tag-check N/A Not applicable for this branch

qcom-next-check ✅ BACKPORT/FROMLIST prefixes present

❌ checkpatch

Root cause: Alignment mismatch in drivers/misc/fastrpc.c:1050 - continuation line not aligned with opening parenthesis

Failure details:
CHECK: Alignment should match open parenthesis
#70: FILE: drivers/misc/fastrpc.c:1050:
+		err = fastrpc_map_create(ctx->fl, ctx->args[i].fd, ctx->args[i].length,
+			 ctx->args[i].attr, &ctx->maps[i], take_ref);

eeca32ce98cadac9e74f58ac194328f993bea3f3 total: 0 errors, 0 warnings, 1 checks, 57 lines checked
Fix: Align the second line with the opening parenthesis. Change:
err = fastrpc_map_create(ctx->fl, ctx->args[i].fd, ctx->args[i].length,
			 ctx->args[i].attr, &ctx->maps[i], take_ref);
To:
err = fastrpc_map_create(ctx->fl, ctx->args[i].fd, ctx->args[i].length,
				 ctx->args[i].attr, &ctx->maps[i], take_ref);
(Add one more tab to align with the opening parenthesis after fastrpc_map_create()

Reproduce locally:
./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES --git c9744addfb04eec214121e1fc11040e828576da4..eeca32ce98cadac9e74f58ac194328f993bea3f3
❌ check-patch-compliance

Root cause: Commit 9a36fb26a802 (BACKPORT) differs from the upstream patch referenced in the Link tag

Failure details:
Checking commit: BACKPORT: misc: fastrpc: fix use-after-free race in fastrpc_map_create
Change is different from the one mentioned in Link
The checker detected that the patch content in commit 1/2 does not match the upstream patch at:
https://lore.kernel.org/all/20260530204528.116920-5-srini@kernel.org/

Fix:
Verify the upstream patch content matches your backport exactly
If intentional changes were made for backporting (e.g., context differences, dependency adjustments), document them in the commit message with an explanation like:
[ Upstream commit <sha> ]

Context adjustment: <explain any differences>
If the patch should match exactly, fetch the correct version from lore and reapply:
b4 am https://lore.kernel.org/all/20260530204528.116920-5-srini@kernel.org/
Reproduce locally:
bash ../kernel-checkers/check-patch-compliance.sh --kernel-src . \
  --base c9744addfb04eec214121e1fc11040e828576da4 --head eeca32ce98cadac9e74f58ac194328f993bea3f3
Verdict

2 blockers must be fixed before merge:

checkpatch alignment issue - Fix indentation in commit eeca32c

patch compliance mismatch - Verify commit 9a36fb2 matches upstream or document intentional changes

qlijarvis · 2026-07-13T08:21:21Z

PR #774 — validate-patch

PR: #774

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

Lore link present: Yes — https://lore.kernel.org/all/20260625080832.17477-1-jianping.li@oss.qualcomm.com/
Lore link matches PR commits: Cannot verify — network access restricted; internal consistency checks pass
Upstream patch status: Cannot verify — network access restricted; FROMLIST: prefix indicates under review
PR present in qcom-next: No — searched by subject and diff fingerprint; not found in qcom-next

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #774 — FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()
Upstream commit: https://lore.kernel.org/all/20260625080832.17477-1-jianping.li@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL (network-restricted validation)

Commit Message

Check Status Note

Subject matches upstream ⏭️ Cannot verify — network access restricted

Body preserves rationale ✅ Comprehensive problem description and fix rationale

Fixes tag present/correct ✅ Fixes: 10df039834f84 ("misc: fastrpc: Skip reference for DMA handles")

Authorship preserved ✅ Author matches Signed-off-by: Jianping Li jianping.li@oss.qualcomm.com

Backport note (if applicable) N/A FROMLIST: prefix — not a backport

Diff

File Status Notes

drivers/misc/fastrpc.c ✅ All changes internally consistent; signature updated + all 4 call sites updated correctly

Commit Message Structure

✅ Subject: Clear and descriptive
✅ Body: Explains both the duplicate DMA mapping issue and reference count imbalance
✅ Fixes tag: Present and properly formatted
✅ Link: Points to lore.kernel.org message-ID
✅ Cc: stable@kernel.org: Present (appropriate for bug fix)
✅ Signed-off-by: Present and matches author

Code Changes Analysis

The patch modifies fastrpc_map_create() to accept a bool take_ref parameter:

Function signature change: Added bool take_ref parameter to fastrpc_map_create()

Lookup behavior: Changed from hardcoded true to parameterized take_ref

Unified code path: Replaced separate fastrpc_map_attach() calls with unified fastrpc_map_create() calls

Call site updates: All 4 call sites correctly updated:

fastrpc_create_maps(): Sets take_ref = false for i >= ctx->nbufs

fastrpc_init_create_process(): Passes true

fastrpc_req_mem_map(): Passes true

✅ Logic consistency: The refactoring correctly addresses the stated problem — arguments beyond ctx->nbufs now perform lookups without taking references, avoiding duplicate DMA mappings and reference count imbalance.

Verdict

Merge with confidence — The commit message is well-structured with proper Fixes tag, stable Cc, and lore link. The code changes are internally consistent and all call sites are correctly updated. The logic addresses the duplicate DMA mapping issue as described.

Limitation: Cannot verify diff faithfulness to upstream lore patch due to network restrictions. Manual verification against lore.kernel.org is recommended if strict upstream fidelity is required.

Final Summary

Lore link present: Yes — https://lore.kernel.org/all/20260625080832.17477-1-jianping.li@oss.qualcomm.com/

Lore link matches PR commits: Cannot verify — network access restricted; internal consistency checks pass

Upstream patch status: Cannot verify — network access restricted; FROMLIST: prefix indicates under review

PR present in qcom-next: No — searched by subject and diff fingerprint; not found in qcom-next

qlijarvis · 2026-07-13T08:21:23Z

PR #774 — checker-log-analyzer

PR: #774
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/29232347947

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	1 CHECK: alignment issue
dt-binding-check	⏭️	No DT binding changes
dtb-check	⏭️	No devicetree changes
sparse-check	✅	Passed
check-uapi-headers	✅	Passed
check-patch-compliance	✅	Passed
tag-check	✅	Subject has valid `FROMLIST:` prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #774 - FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/29232347947
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ❌ 1 CHECK: alignment issue

dt-binding-check ⏭️ No DT binding changes

dtb-check ⏭️ No devicetree changes

sparse-check ✅ Passed

check-uapi-headers ✅ Passed

check-patch-compliance ✅ Passed

tag-check ✅ Subject has valid FROMLIST: prefix

❌ checkpatch

Root cause: Alignment mismatch in function call continuation line at drivers/misc/fastrpc.c:1051

Failure details:
CHECK: Alignment should match open parenthesis
#70: FILE: drivers/misc/fastrpc.c:1051:
+		err = fastrpc_map_create(ctx->fl, ctx->args[i].fd, ctx->args[i].length,
+			 ctx->args[i].attr, &ctx->maps[i], take_ref);

e4b5177ad2da7997e5bb434576b5f3c462ae7fec total: 0 errors, 0 warnings, 1 checks, 57 lines checked
This is a CHECK (not an ERROR or WARNING), meaning it's a style suggestion rather than a blocker. The continuation line should align with the opening parenthesis of fastrpc_map_create(.

Fix:
git rebase -i e8d06c707464437c26e5ad72fe052c57253b552a  # mark commit as 'edit'
# Edit drivers/misc/fastrpc.c:1051-1052 to align the second line:
#   err = fastrpc_map_create(ctx->fl, ctx->args[i].fd, ctx->args[i].length,
#                            ctx->args[i].attr, &ctx->maps[i], take_ref);
git add drivers/misc/fastrpc.c
git commit --amend --no-edit
git rebase --continue
Reproduce locally:
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git e8d06c707464437c26e5ad72fe052c57253b552a..e4b5177ad2da7997e5bb434576b5f3c462ae7fec
Verdict

1 minor style issue to fix before merge.

The checkpatch CHECK is a style suggestion for better code readability. All other checkers passed cleanly. The commit has a valid FROMLIST: prefix and includes a proper upstream Link tag, making it compliant with the patch compliance requirements for the qcom-6.18.y branch.

qcomlnxci · 2026-07-13T09:16:53Z

Test jobs on e4b5177

qcomlnxci · 2026-07-13T09:16:56Z

Test Matrix

Test Case	hamoa-iot-evk	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3
BT_FW_KMD_Service	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
BT_ON_OFF	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
BT_SCAN	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
CPUFreq_Validation	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
CPU_affinity	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
DSP_AudioPD	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
Ethernet	◻️	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	◻️	⚠️ skip
Freq_Scaling	◻️	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️	✅ Pass
GIC	◻️	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️	✅ Pass
IPA	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
Interrupts	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
OpenCV	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
PCIe	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
Probe_Failure_Check	◻️	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️	❌ Fail
RMNET	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
UFS_Validation	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
USBHost	◻️	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️	❌ Fail
WiFi_Firmware_Driver	◻️	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️	✅ Pass
WiFi_OnOff	◻️	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️	✅ Pass
adsp_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
cdsp_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
gpdsp_remoteproc	◻️	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	◻️	✅ Pass
hotplug	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
irq	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
kaslr	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
pinctrl	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
qcom_hwrng	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
rngtest	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
shmbridge	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
smmu	◻️	❌ Fail	✅ Pass	❌ Fail	✅ Pass	◻️	❌ Fail
watchdog	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass
wpss_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass

…te_maps() DMA handles passed as invoke arguments (scalars beyond nbufs) may refer to the same dma_buf fd as an input/output buffer argument. Taking an extra reference for such DMA handle maps leads to duplicate mappings and an unbalanced reference count, since DMA handle maps are released separately when the DSP returns the fd through the fdlist. Fix this by not taking an extra reference for DMA handle arguments (take_ref = false) and tagging them with FASTRPC_MAP_DMA_HANDLE. As these maps are borrowed references, fastrpc_get_args() re-validates the map via fastrpc_map_lookup() before dereferencing it, so it is not used after being freed. fastrpc_put_args() only releases maps flagged as FASTRPC_MAP_DMA_HANDLE and clears the flag to guarantee the map is freed exactly once. Also reject FASTRPC_MAP_DMA_HANDLE in fastrpc_req_mem_map(), since such handles are already mapped implicitly during the remote invoke call and must not be mapped again through the explicit MEM_MAP path. Link: https://lore.kernel.org/all/20260716113254.570-1-jianping.li@oss.qualcomm.com/ Fixes: 10df039 ("misc: fastrpc: Skip reference for DMA handles") Cc: stable@kernel.org Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>

qcomlnxci · 2026-07-30T09:09:28Z

Test jobs on 75f4914

qcomlnxci · 2026-07-30T09:09:32Z

Test Matrix

Test Case	hamoa-iot-evk-multimedia	lemans-evk-multimedia	monaco-evk-multimedia	qcs615-ride-multimedia	qcs6490-rb3gen2-multimedia	qcs8300-ride-multimedia	qcs9100-ride-r3-multimedia
Audio_Card_Registration	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
Ethernet	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
USBHost	✅ Pass	✅ Pass	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail
WiFi_Firmware_Driver	❌ Fail	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	❌ Fail	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
gpdsp_remoteproc	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	✅ Pass	✅ Pass
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
pinctrl	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
qcom_hwrng	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
rngtest	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	❌ Fail	✅ Pass	❌ Fail	✅ Pass	✅ Pass	❌ Fail
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass

Jianping (Jianping-Li) requested review from a team, knaveen-qc, Salendarsingh Gaud (sgaud-quic) and Trilok Soni (trsoni) June 25, 2026 08:57

Jianping (Jianping-Li) force-pushed the lookup_fix branch from eeca32c to e4b5177 Compare July 13, 2026 07:29

Ekansh Gupta (ekanshibu) approved these changes Jul 13, 2026

View reviewed changes

Jianping (Jianping-Li) force-pushed the lookup_fix branch from e4b5177 to 75f4914 Compare July 30, 2026 07:07

Uh oh!

Conversation

Jianping (Jianping-Li) commented Jun 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qswat-orbit-external Bot commented Jun 25, 2026

Uh oh!

qswat-orbit-external Bot commented Jun 25, 2026

Uh oh!

qlijarvis commented Jun 25, 2026

PR #774 — validate-patch

Final Summary

🔍 Patch Validation

Commit 1: BACKPORT: misc: fastrpc: fix use-after-free race in fastrpc_map_create

Commit Message

Diff

Issues

Verdict

Commit 2: FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()

Commit Message

Diff

Issues

Verdict

Overall Assessment

Issues Summary

Verdict

Recommendations

Final Summary

Uh oh!

qlijarvis commented Jun 25, 2026

PR #774 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ checkpatch

❌ check-patch-compliance

Verdict

Uh oh!

qlijarvis commented Jul 13, 2026

PR #774 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Commit Message Structure

Code Changes Analysis

Verdict

Final Summary

Uh oh!

qlijarvis commented Jul 13, 2026

PR #774 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ checkpatch

Verdict

Uh oh!

qcomlnxci commented Jul 13, 2026

Test jobs on e4b5177

Uh oh!

qcomlnxci commented Jul 13, 2026

Test Matrix

Uh oh!

qcomlnxci commented Jul 30, 2026

Test jobs on 75f4914

Uh oh!

qcomlnxci commented Jul 30, 2026

Test Matrix

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Jianping (Jianping-Li) commented Jun 25, 2026 •

edited

Loading