[Jiaxing Li (jiaxli-QC)]

Commit 2ecdf5c ("crypto: qcom-rng - Remove crypto_rng interface") removed the Qualcomm RNG implementation of stdrng. With DRBG disabled, libkcapi RNG requests for stdrng fail on affected Qualcomm systems.

Enable DRBG as a module to provide stdrng for existing libkcapi users.

Fixes: 2ecdf5c ("crypto: qcom-rng - Remove crypto_rng interface")
CRs-Fixed: 4696777

[qlijarvis]

🔨 Build Failure Analysis — PR #2170

PR: #2170
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/41044121294

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	arch/arm64/configs/defconfig	No	Pre-existing integration conflict. The PR modifies defconfig in the crypto section, and other topic branches being merged also modified the same file, causing a merge conflict during the automerge step. This is not a compilation error.

Verdict

This is not a compilation failure. The build failed during the automerge/integration phase due to a merge conflict in arch/arm64/configs/defconfig. The PR itself is syntactically correct and does not introduce any compilation errors. The conflict is a pre-existing integration issue that occurs when merging multiple topic branches that all modify the same defconfig file.

📎 Detailed analysis: Full report

[qlijarvis]

🔨 Build Failure Analysis — PR #2170

PR: #2170
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/41044121294

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	arch/arm64/configs/defconfig	No (integration conflict)	The PR modifies defconfig in a region that conflicts with other topic branches being merged into qcom-next. This is an integration conflict, not a code defect.

Verdict

This is not a compilation error. The build failed due to a merge conflict during the automerge integration process. The PR's changes are valid, but conflict with concurrent modifications to the same defconfig region from other topic branches.

📎 Detailed analysis: Full report

[qlijarvis]

PR #2170 — validate-patch

PR: #2170

Verdict	Issues	Detailed Report
✅	0	Full report

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only change, not posted upstream
4. PR present in qcom-next/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #2170 - QCLINUX: arm64: defconfig: Enable DRBG as a module for stdrng users
Upstream commit: N/A (vendor-only commit)
Verdict: ✅ PASS (vendor-only)

Commit Message

Check	Status	Note
Subject matches upstream	N/A	Vendor-only commit; no upstream source
Body preserves rationale	✅	Clear problem statement and solution
Fixes tag present/correct	✅	Fixes: 2ecdf5c9910e properly formatted
Authorship preserved	✅	From: matches Signed-off-by:
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/configs/defconfig	✅	Single line addition: CONFIG_CRYPTO_DRBG=m

Issues

None. This is a well-formed vendor-only commit with clear rationale and proper formatting.

Verdict

Merge as-is. This is a vendor-specific defconfig change with proper commit message structure, a valid Fixes tag referencing the commit that created the need for this change, and a clear technical justification.

Final Summary

1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only change, not posted upstream
4. PR present in qcom-next/topics: Not in qcom-next or topics — expected for new vendor-only commit; not a validation failure

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: ae2606baf50f01e14ed7ddfa73116e5850c6c0d1
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] QCLINUX: arm64: defconfig: Enable DRBG as a module for stdrng	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing

Final Status

overall_status: FAIL
present_commits: 0/1
partial_commits: 0/1
missing_commits: 1/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

[qlijarvis]

PR #2170 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	⏭️	Skipped - automerge conflict prevented execution
dt-binding-check	⏭️	Skipped - automerge conflict prevented execution
dtb-check	⏭️	Skipped - automerge conflict prevented execution
sparse-check	⏭️	Skipped - automerge conflict prevented execution
check-uapi-headers	⏭️	Skipped - automerge conflict prevented execution
check-patch-compliance	⏭️	Skipped - automerge conflict prevented execution
tag-check	✅	PASS - subject has valid QCLINUX: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #2170 - QCLINUX: arm64: defconfig: Enable DRBG as a module for stdrng users
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/41044120782

Checker	Result	Summary
checkpatch	⏭️	Skipped - automerge conflict prevented execution
dt-binding-check	⏭️	Skipped - automerge conflict prevented execution
dtb-check	⏭️	Skipped - automerge conflict prevented execution
sparse-check	⏭️	Skipped - automerge conflict prevented execution
check-uapi-headers	⏭️	Skipped - automerge conflict prevented execution
check-patch-compliance	⏭️	Skipped - automerge conflict prevented execution
tag-check	✅	PASS - subject has valid QCLINUX: prefix

⚠️ CI Infrastructure Issue: Automerge Conflict

Root cause: All checker jobs failed during the automerge phase when attempting to merge topic/tech/all/config with the baseline. The PR modifies arch/arm64/configs/defconfig, which conflicts with changes in the topic/tech/all/config branch.

Failure details:

Auto-merging arch/arm64/configs/defconfig
CONFLICT (content): Merge conflict in arch/arm64/configs/defconfig
Automatic merge failed; fix conflicts and then commit the result.
Merge failed, manual merge
automerge returned non-zero; check logs for conflicts
##[error]Process completed with exit code 1.

Analysis:

This is a CI workflow infrastructure issue, not a patch quality issue. The kernel-checkers workflow uses an automerge process that:

1. Creates an integration branch based on the qcom-next baseline (commit c7896917e523946138ce654d4b6c1e33d5a8f4e5)
2. Merges all active topic branches (including topic/tech/all/config)
3. Then applies the PR changes for testing

The PR adds CONFIG_CRYPTO_DRBG=m to arch/arm64/configs/defconfig at line 1970 (after CONFIG_CRYPTO_SM3=m). However, the topic/tech/all/config branch has conflicting changes to the same region of defconfig, causing the automerge to fail before any checkers can run.

Impact:

• ❌ No checker validation was performed (checkpatch, dt-binding-check, dtb-check, sparse-check, check-uapi-headers, check-patch-compliance all skipped)
• ✅ Manual validation: The patch itself is well-formed:
  • Subject has valid QCLINUX: prefix (required for tech/all/config branch)
  • Has proper Signed-off-by: trailer
  • Has Fixes: tag referencing the upstream commit
  • Single-line config change is minimal and focused
  • Commit message clearly explains the rationale

Fix:

This requires manual intervention to resolve the merge conflict:

1. Option A: Rebase the PR on latest tech/all/config

   git fetch origin tech/all/config
   git rebase origin/tech/all/config
   # Resolve conflicts in arch/arm64/configs/defconfig
   # Ensure CONFIG_CRYPTO_DRBG=m is added in the correct alphabetical position
   git add arch/arm64/configs/defconfig
   git rebase --continue
   git push --force-with-lease

2. Option B: Coordinate with topic/tech/all/config maintainer

   • Check what changes are pending in topic/tech/all/config that conflict with this PR
   • Determine if those changes should be merged first, or if this PR should be integrated into that topic branch

3. Option C: Wait for topic/tech/all/config to merge

   • If topic/tech/all/config is about to be merged into the baseline, wait for that to complete
   • Then rebase this PR on the updated baseline

Reproduce locally:

# Clone and set up the integration environment
git clone https://github.com/qualcomm-linux/kernel-topics.git
cd kernel-topics
git checkout tech/all/config

# Fetch the PR branch
git fetch origin pull/2170/head:pr-2170
git checkout pr-2170

# Attempt rebase to see the conflict
git rebase tech/all/config
# This will show the exact conflict in arch/arm64/configs/defconfig

✅ tag-check

Status: PASS

Analysis: The PR targets the tech/all/config branch (not qcom-next or qcom-next-staging), so subject-line prefix validation is mandatory.

The commit subject is:

QCLINUX: arm64: defconfig: Enable DRBG as a module for stdrng users

This starts with QCLINUX:, which is a valid prefix for vendor-only changes with no upstream equivalent. The prefix is appropriate because:

• This is a Qualcomm-specific defconfig change
• It addresses a Qualcomm platform-specific issue (libkcapi stdrng users)
• It's a workaround for the removal of Qualcomm RNG's stdrng interface

Note: While QCLINUX: is valid for tag-check, it will cause check-patch-compliance to fail if that checker runs, because check-patch-compliance only accepts upstream-linkable prefixes (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:). This is a known limitation of the checker for vendor-only commits.

Verdict

Cannot merge - CI infrastructure blocker must be resolved first.

The patch itself appears correct and well-formed, but the automerge conflict prevents validation. The PR author must:

1. Resolve the merge conflict with topic/tech/all/config by rebasing
2. Re-trigger CI to get full checker validation
3. Address any checker failures that surface after the conflict is resolved

Once the automerge conflict is resolved and CI runs successfully, the patch should be ready for review (assuming no new checker failures are discovered).