Merge tag 'v6.18.39' into qcom-6.18.y

[nsiddams (nsiddams)]

No description provided.

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

[qlijarvis]

PR #856 — validate-patch

PR: #856

Verdict	Issues	Detailed Report
❌	5	Full report

Final Summary

1. Lore link present: No — no lore.kernel.org links found; pr.patch is a raw diff without commit structure
2. Lore link matches PR commits: N/A — no individual commits to validate; cannot verify 4088 file changes against upstream without commit boundaries
3. Upstream patch status: N/A — this is a stable version merge (6.18.37→6.18.39) that should contain accepted stable patches, but cannot verify individual patches without proper commit structure
4. PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #856 - Stable kernel update 6.18.37 → 6.18.39
Upstream commit: N/A (stable version merge)
Verdict: ❌ FAIL

Commit Message

Check	Status	Note
Subject matches upstream	N/A	No commit message present in pr.patch
Body preserves rationale	N/A	No commit message present in pr.patch
Fixes tag present/correct	N/A	Not applicable for stable merge
Authorship preserved	N/A	No commit metadata in pr.patch
Backport note (if applicable)	N/A	Not applicable for stable merge

Diff

File	Status	Notes
Makefile	✅	SUBLEVEL bump 37 → 39 (stable version update)
4087 other files	⚠️	Cannot validate individual patches without commit structure

Issues

Critical: No commit structure or lore links

This PR contains a raw unified diff (4088 files changed) without:

• Individual commit messages
• Lore.kernel.org links for each upstream stable patch
• Author attribution for each change
• Signed-off-by trailers
• Fixes tags where applicable

Expected structure for stable merges:

Stable kernel updates should be imported as a series of individual commits, each with:

1. Original commit message from stable tree
2. Link: tag pointing to the stable commit or lore posting
3. Proper authorship (From: matching upstream author)
4. All trailers preserved (Signed-off-by, Reviewed-by, Cc: stable, etc.)
5. Prefix indicating source (e.g., UPSTREAM:, BACKPORT:, or FROMGIT:)

What this PR contains instead:

A single monolithic diff representing the delta between 6.18.37 and 6.18.39, which likely contains hundreds of individual upstream stable patches squashed together.

Verdict

Do not merge. This PR cannot be validated against lore.kernel.org sources because it lacks the required commit structure. Stable updates must be imported as individual commits to maintain:

• Proper attribution to upstream authors
• Traceability to upstream stable commits
• Ability to validate each patch independently
• Ability to revert individual changes if needed
• Compliance with kernel development practices

Recommendation

Reject this PR and re-import the stable update correctly:

1. Use git merge or git cherry-pick to import commits from the stable tree individually
2. Ensure each commit retains its original message, authorship, and trailers
3. Add appropriate prefix (UPSTREAM: or BACKPORT:) to each commit subject
4. Add Link: tags pointing to kernel.org stable commits or lore postings
5. Submit as a properly structured patch series

Example workflow:

# Fetch stable tree
git remote add stable https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
git fetch stable linux-6.18.y

# Cherry-pick or merge the range
git cherry-pick v6.18.37..v6.18.39
# OR
git merge v6.18.39

# Each commit will preserve original authorship and message

Final Summary

1. Lore link present: No — no lore.kernel.org links found; pr.patch is a raw diff without commit structure
2. Lore link matches PR commits: N/A — no individual commits to validate; cannot verify 4088 file changes against upstream without commit boundaries
3. Upstream patch status: N/A — this is a stable version merge (6.18.37→6.18.39) that should contain accepted stable patches, but cannot verify individual patches without proper commit structure
4. PR present in qcom-next/topics: Partial — integration_presence_report.md shows 1/1 commit with only partial evidence; however, the lack of proper commit structure makes this result unreliable

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: 07f50dc44eddcf748a99d1a7523a466438bfffa6
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/1	``	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial

Final Status

overall_status: PARTIAL
present_commits: 0/1
partial_commits: 1/1
missing_commits: 0/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

[qlijarvis]

PR #856 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	⚠️	607 commits with minor style warnings (mostly informational)
dt-binding-check	⏭️	Skipped - no DT binding changes
dtb-check	⏭️	Skipped - no devicetree changes
sparse-check	✅	Passed
check-uapi-headers	✅	Passed
check-patch-compliance	❌	607 commits missing required prefix
tag-check	❌	All 607 commits missing subject prefix (mandatory for qcom-6.18.y)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #856 - Stable kernel merge (Linux 6.18.38 → 6.18.39)
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/29998352413
Target branch: qcom-6.18.y

Checker	Result	Summary
checkpatch	⚠️	607 commits with minor style warnings (mostly informational)
dt-binding-check	⏭️	Skipped - no DT binding changes
dtb-check	⏭️	Skipped - no devicetree changes
sparse-check	✅	Passed
check-uapi-headers	✅	Passed
check-patch-compliance	❌	607 commits missing required prefix
tag-check	❌	All 607 commits missing subject prefix (mandatory for qcom-6.18.y)

---

❌ check-patch-compliance

Root cause: All 607 commits in this stable kernel merge lack the required subject-line prefix.

Failure details:

Checking commit: KVM: x86: Fix shadow paging use-after-free due to unexpected role
Commit summary does not start with a required prefix

Checking commit: lsm: add backing_file LSM hooks
Commit summary does not start with a required prefix

Checking commit: selinux: fix overlayfs mmap() and mprotect() access checks
Commit summary does not start with a required prefix

[... 604 more commits with the same error ...]

Fix: Add the appropriate prefix to each commit subject line. For stable kernel merges from upstream:

# For each commit, rebase and add UPSTREAM: prefix
git rebase -i <base_sha>

# For each commit marked 'edit':
git commit --amend -m "UPSTREAM: $(git log -1 --format=%s)"
git rebase --continue

Reproduce locally:

cd kernel
./scripts/check-patch-compliance.sh --base qcom-6.18.y --head <PR-branch>

---

❌ tag-check (mandatory for qcom-6.18.y)

Root cause: The target branch qcom-6.18.y is not qcom-next or qcom-next-staging, therefore every commit must start with a valid prefix tag.

Failure details:
All 607 commits are missing the required subject-line prefix. Examples:

• KVM: x86: Fix shadow paging use-after-free due to unexpected role
• lsm: add backing_file LSM hooks
• selinux: fix overlayfs mmap() and mprotect() access checks
• Revert "PCI: qcom: Advertise Hotplug Slot Capability with no Command Completion support"
• lockd: fix TEST handling when not all permissions are available.

Required prefixes:

Prefix	Use case
UPSTREAM:	Patch merged into Linus's mainline tree (✅ correct for this PR)
FROMLIST:	Patch posted to mailing list but not yet merged
FROMGIT:	Patch taken from a maintainer git tree
BACKPORT:	Upstream patch backported with modifications
QCLINUX:	Vendor-only change with no upstream equivalent
PENDING:	Work-in-progress, not yet posted upstream
WORKAROUND:	Temporary fix not suitable for upstream

Fix:

Since this is a stable kernel merge (Linux 6.18.38 → 6.18.39), all commits are from upstream stable and should be prefixed with UPSTREAM::

git rebase -i <base_sha>

# Mark all commits as 'edit' (or use a script)
# For each commit:
git commit --amend -m "UPSTREAM: $(git log -1 --format=%s)"
git rebase --continue

Automated fix script:

#!/bin/bash
# Rebase all commits and add UPSTREAM: prefix
base_sha="<base_sha>"
commits=$(git rev-list --reverse ${base_sha}..HEAD)

git rebase -i ${base_sha} --exec '
  subject=$(git log -1 --format=%s)
  if ! echo "$subject" | grep -qE "^(UPSTREAM|FROMLIST|FROMGIT|BACKPORT|QCLINUX|PENDING|WORKAROUND):"; then
    git commit --amend -m "UPSTREAM: $subject"
  fi
'

---

⚠️ checkpatch (informational only)

Root cause: Upstream stable commits contain minor style warnings that are acceptable for stable merges.

Common warnings observed:

• WARNING: Reported-by: should be immediately followed by Closes: (informational)
• WARNING: The commit message has 'stable@', perhaps it also needs a 'Fixes:' tag? (informational)
• WARNING: Prefer a maximum 75 chars per line (commit message formatting)
• WARNING: From:/Signed-off-by: email address mismatch (author used different email addresses)
• WARNING: Block comments use * on subsequent lines (code style)
• WARNING: Duplicate signature (on Linux 6.18.39 release commit)

Assessment: These warnings are typical for upstream stable commits and do not require fixes. The stable kernel maintainers have already reviewed and accepted these commits.

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 4def074fd0b5b6d0124f4afdb32dfbd5126a6e65..c861e1ffdf451e98f3d526312036c8c33b69a537

---

Verdict

❌ BLOCKER: 607 commits missing required subject prefix

This PR merges Linux stable kernel updates (6.18.38 → 6.18.39) into qcom-6.18.y. The target branch requires all commits to carry a subject-line prefix tag, but all 607 commits are missing this prefix.

Required action:

1. Rebase all 607 commits to add UPSTREAM: prefix to each subject line
2. Force-push the updated branch
3. Re-trigger CI to verify the fix

Note: The checkpatch warnings are informational only and typical for upstream stable commits. No code changes are needed—only commit message formatting (adding the UPSTREAM: prefix).