| Seq | Timestamp | Type | Name | Duration |
|---|---|---|---|---|
| 0/0 | 2026/09/25 06:19 | flow | patch-triage |
0mArgs:null Results: {
"EnableConfigs": null,
"FocusSymbols": [],
"KMSANReasoning": "",
"NeedsKMSAN": false,
"Reasoning": "The patch modifies only user-space KVM selftests under tools/testing/selftests/kvm/ (which do not affect the compiled kernel image) and specifically targets the LoongArch architecture, whereas the target architecture is amd64.",
"WorthFuzzing": false
} |
| 1/1 | 2026/09/25 06:19 | action | read-patch-diff |
0mArgs:null Results: {
"PatchDiff": "commit 9a6dc183fd6b691abd60e2633974c7ecc058095b\nAuthor: syz-cluster \u003ctriage@syzkaller.com\u003e\nDate: Fri Sep 25 06:19:56 2026 +0000\n\n syz-cluster: applied patch under review\n\ndiff --git a/tools/testing/selftests/kvm/include/loongarch/processor.h b/tools/testing/selftests/kvm/include/loongarch/processor.h\nindex 0e59daa8024eb..8d9fabdc89e37 100644\n--- a/tools/testing/selftests/kvm/include/loongarch/processor.h\n+++ b/tools/testing/selftests/kvm/include/loongarch/processor.h\n@@ -79,6 +79,7 @@\n #define CPUCFG2_LASX\t\t\tBIT(7)\n #define CPUCFG2_LLFTP\t\t\tBIT(14)\n #define CPUCFG2_LLFTPREV\t\tGENMASK(17, 15)\n+#define CPUCFG2_PTW\t\t\tBIT(24)\n \n /* LoongArch Basic CSR registers */\n #define LOONGARCH_CSR_CRMD\t\t0x0 /* Current mode info */\n@@ -128,6 +129,8 @@\n #define LOONGARCH_CSR_PGD\t\t0x1b\n #define LOONGARCH_CSR_PWCTL0\t\t0x1c\n #define LOONGARCH_CSR_PWCTL1\t\t0x1d\n+#define CSR_PWCTL1_PTW_SHIFT\t\t24\n+#define CSR_PWCTL1_PTW\t\t\tBIT_ULL(CSR_PWCTL1_PTW_SHIFT)\n #define LOONGARCH_CSR_STLBPGSIZE\t0x1e\n #define LOONGARCH_CSR_CPUID\t\t0x20\n #define LOONGARCH_CSR_KS0\t\t0x30\ndiff --git a/tools/testing/selftests/kvm/lib/loongarch/processor.c b/tools/testing/selftests/kvm/lib/loongarch/processor.c\nindex 47bbde3e205a0..35e35c62759f9 100644\n--- a/tools/testing/selftests/kvm/lib/loongarch/processor.c\n+++ b/tools/testing/selftests/kvm/lib/loongarch/processor.c\n@@ -282,6 +282,7 @@ void loongarch_vcpu_setup(struct kvm_vcpu *vcpu)\n \tunsigned int cfg;\n \tunsigned long val;\n \tstruct kvm_vm *vm = vcpu-\u003evm;\n+\tbool has_ptw = false;\n \n \tswitch (vm-\u003emode) {\n \tcase VM_MODE_P36V47_16K:\n@@ -300,6 +301,12 @@ void loongarch_vcpu_setup(struct kvm_vcpu *vcpu)\n \tret = __kvm_has_device_attr(vm-\u003efd, KVM_LOONGARCH_VM_FEAT_CTRL, KVM_LOONGARCH_VM_FEAT_LASX);\n \tif (!ret)\n \t\tcfg |= CPUCFG2_LASX;\n+\tret = __kvm_has_device_attr(vm-\u003efd, KVM_LOONGARCH_VM_FEAT_CTRL, KVM_LOONGARCH_VM_FEAT_PTW);\n+\tif (!ret) {\n+\t\tcfg |= CPUCFG2_PTW;\n+\t\thas_ptw = true;\n+\t}\n+\n \tloongarch_set_cpucfg(vcpu, LOONGARCH_CPUCFG2, cfg);\n \tcfg = read_cpucfg(LOONGARCH_CPUCFG6);\n \tloongarch_set_cpucfg(vcpu, LOONGARCH_CPUCFG6, cfg);\n@@ -338,6 +345,9 @@ void loongarch_vcpu_setup(struct kvm_vcpu *vcpu)\n \n \t/* PGD page shift and width */\n \tval = (vm-\u003epage_shift + width * (vm-\u003emmu.pgtable_levels - 1)) | width \u003c\u003c 6;\n+\tif (has_ptw)\n+\t\tval |= CSR_PWCTL1_PTW;\n+\n \tloongarch_set_csr(vcpu, LOONGARCH_CSR_PWCTL1, val);\n \tloongarch_set_csr(vcpu, LOONGARCH_CSR_PGDL, vm-\u003emmu.pgd);\n \n@@ -345,8 +355,10 @@ void loongarch_vcpu_setup(struct kvm_vcpu *vcpu)\n \t * Refill exception runs on real mode\n \t * Entry address should be physical address\n \t */\n-\tval = addr_gva2gpa(vm, (unsigned long)handle_tlb_refill);\n-\tloongarch_set_csr(vcpu, LOONGARCH_CSR_TLBRENTRY, val);\n+\tif (!has_ptw) {\n+\t\tval = addr_gva2gpa(vm, (unsigned long)handle_tlb_refill);\n+\t\tloongarch_set_csr(vcpu, LOONGARCH_CSR_TLBRENTRY, val);\n+\t}\n \n \t/*\n \t * General exception runs on page-enabled mode\n"
} |
| 2/1 | 2026/09/25 06:19 | agent | patch-evaluator |
0mModel:core Args: null Results: {
"EnableConfigs": null,
"FocusSymbols": [],
"Reasoning": "The patch modifies only user-space KVM selftests under tools/testing/selftests/kvm/ (which do not affect the compiled kernel image) and specifically targets the LoongArch architecture, whereas the target architecture is amd64.",
"WorthFuzzing": false
}Instruction: You are an expert Linux kernel maintainer and security engineer.
Your job is to review a provided patch series and evaluate whether it warrants fuzzing with syzkaller.
IMPORTANT: The changes have ALREADY been applied and committed as the HEAD commit in
your workspace. Do NOT rely on internal assumptions. You must actively use your code access
tools to inspect the actual source code, callers, and surrounding context.
================================================================================
1. CORE TRIAGE PHILOSOPHY
================================================================================
The goal of patch fuzzing is to discover crashes, regressions, exposed latent bugs,
and newly triggered assertions introduced by the patch series.
- REACHABILITY IS THE PRIMARY GATE:
Fuzzing can only discover bugs in code that can actually execute in standard virtualized
environments (GCE or QEMU, utilizing software-emulated devices like USB gadgets, netdev, tun/tap).
If the modified code is structurally unreachable (see Section 2), it MUST NOT be fuzzed,
regardless of whether it adds assertions or complex logic.
- DO NOT BLINDLY TRUST "NO FUNCTIONAL CHANGE" (NFCI) OR "REFACTORING" CLAIMS:
Patch authors routinely label changes as "cleanups", "refactorings", or state
"No functional change intended". Do NOT take these claims at face value.
Code refactorings that rearrange logic, introduce helper functions, or alter state management
in core subsystems frequently introduce subtle semantic shifts or uncover latent kernel bugs.
If reachable executable code is modified or refactored, it MUST be fuzzed.
- NEW OR MODIFIED ASSERTIONS IN REACHABLE CODE MUST BE FUZZED:
When a patch introduces or modifies runtime checks or assertions (e.g., WARN_ON*, VM_WARN_ON*,
BUG_ON*, lockdep_assert*) in reachable code paths, it enforces new or stricter invariants.
Even if the author believes the invariant always holds, fuzzing is essential to verify whether
an unusual sequence of operations can violate it.
================================================================================
2. WHEN TO RETURN WorthFuzzing=false (NEGATIVE CRITERIA)
================================================================================
Return WorthFuzzing=false ONLY IF all modified code falls strictly into one or more of these categories:
- Non-kernel and non-executable changes:
* Modifications to Documentation/, comments, or spelling fixes.
* User-space directories, self-tests, samples, or scripts (e.g., tools/, samples/, scripts/, usr/)
that do not affect the compiled kernel image (vmlinux) or kernel modules.
* Purely decorative logging (e.g., message strings in pr_err, printk, dev_info) or tracepoints
that do not alter control flow or data structures.
* Build system or Kconfig changes that do not alter compiled C logic.
- Structurally unreachable hardware:
* Vendor-specific PCIe switches, SmartNICs, or GPU drivers (e.g., mlxsw, pds_core, qed,
ionic, amdgpu) requiring physical ASIC/PCIe cards not emulated in standard QEMU.
- Unreachable execution paths:
* Driver teardown callbacks (.remove, .shutdown, pci_unregister_driver) executed only during
physical PCI hot-unplug or manual sysfs driver unbinding.
* Code paths exclusive to architectures other than the target architecture.
================================================================================
3. WHEN TO RETURN WorthFuzzing=true (POSITIVE CRITERIA)
================================================================================
Return WorthFuzzing=true whenever the patch touches reachable executable code, including:
- Core Subsystems:
* Any logic modifications in memory management (mm/), synchronization/locking (kernel/locking/),
BPF, scheduler, core networking, VFS, or syscall handling.
- Refactorings and Code Cleanups:
* Any restructuring of reachable data structures, helper abstractions, or algorithm flows.
- Runtime Assertions and Defensive Checks:
* Any introduction or alteration of assertions (WARN_ON*, VM_WARN_ON*, BUG_ON*, etc.) in reachable paths.
- Reachable Drivers and Protocols:
* Drivers accessible via virtual buses (virtio, USB gadget, loopback, netlink, binder, sockets, etc.).
================================================================================
4. EXTRACTING FocusSymbols (PREVENTING DILUTION)
================================================================================
When WorthFuzzing=true, you must extract specific kernel functions into FocusSymbols to guide the fuzzer:
- AVOID UBIQUITOUS LIFECYCLE HOT-PATHS:
Do NOT list generic, ubiquitous functions called by almost every program in the corpus
(including, but not limited to: general memory allocators and deallocators, page fault
and trap handlers, or core synchronization primitives; this is not an exhaustive list).
Listing ubiquitous functions causes the fuzzer to classify thousands of unrelated tests as "focused",
which severely dilutes fuzzing effort away from the actual changes.
- TARGET SPECIFIC FEATURE LOGIC AND ENTRYPOINTS:
List functions that specifically implement the logic being added or altered, or direct API entrypoints
for the subsystem feature under review.
- HANDLING STATIC INLINE FUNCTIONS IN HEADERS (.h):
Compiler-inlined static functions (such as static inlines in mm/*.h or include/linux/*.h) lack
distinct symbol addresses in vmlinux and cannot be targeted directly by symbol coverage filters.
If the changes are primarily in static inline helpers, identify non-static, feature-specific caller
functions in .c files that exercise them (avoiding ubiquitous lifecycle wrappers).
================================================================================
5. IDENTIFYING EnableConfigs
================================================================================
Identify any specific CONFIG_ options required to properly compile and reach the modified code:
- Inspect Kconfig files and #ifdef guards; do not make assumptions.
- Check "depends on" lines in Kconfig to include any non-standard parent subsystem configs needed.
- Strip any 'CONFIG_' prefix (e.g., return "NET_IPV4" instead of "CONFIG_NET_IPV4").
Prefer calling several tools at the same time to save round-trips.
Use set-results tool to provide results of the analysis.
It must be called exactly once before the final reply.
Ignore results of this tool.
Prompt: Target architecture: amd64
For your convenience, here is the diff of the changes:
commit 9a6dc183fd6b691abd60e2633974c7ecc058095b
Author: syz-cluster <triage@syzkaller.com>
Date: Fri Sep 25 06:19:56 2026 +0000
syz-cluster: applied patch under review
diff --git a/tools/testing/selftests/kvm/include/loongarch/processor.h b/tools/testing/selftests/kvm/include/loongarch/processor.h
index 0e59daa8024eb..8d9fabdc89e37 100644
--- a/tools/testing/selftests/kvm/include/loongarch/processor.h
+++ b/tools/testing/selftests/kvm/include/loongarch/processor.h
@@ -79,6 +79,7 @@
#define CPUCFG2_LASX BIT(7)
#define CPUCFG2_LLFTP BIT(14)
#define CPUCFG2_LLFTPREV GENMASK(17, 15)
+#define CPUCFG2_PTW BIT(24)
/* LoongArch Basic CSR registers */
#define LOONGARCH_CSR_CRMD 0x0 /* Current mode info */
@@ -128,6 +129,8 @@
#define LOONGARCH_CSR_PGD 0x1b
#define LOONGARCH_CSR_PWCTL0 0x1c
#define LOONGARCH_CSR_PWCTL1 0x1d
+#define CSR_PWCTL1_PTW_SHIFT 24
+#define CSR_PWCTL1_PTW BIT_ULL(CSR_PWCTL1_PTW_SHIFT)
#define LOONGARCH_CSR_STLBPGSIZE 0x1e
#define LOONGARCH_CSR_CPUID 0x20
#define LOONGARCH_CSR_KS0 0x30
diff --git a/tools/testing/selftests/kvm/lib/loongarch/processor.c b/tools/testing/selftests/kvm/lib/loongarch/processor.c
index 47bbde3e205a0..35e35c62759f9 100644
--- a/tools/testing/selftests/kvm/lib/loongarch/processor.c
+++ b/tools/testing/selftests/kvm/lib/loongarch/processor.c
@@ -282,6 +282,7 @@ void loongarch_vcpu_setup(struct kvm_vcpu *vcpu)
unsigned int cfg;
unsigned long val;
struct kvm_vm *vm = vcpu->vm;
+ bool has_ptw = false;
switch (vm->mode) {
case VM_MODE_P36V47_16K:
@@ -300,6 +301,12 @@ void loongarch_vcpu_setup(struct kvm_vcpu *vcpu)
ret = __kvm_has_device_attr(vm->fd, KVM_LOONGARCH_VM_FEAT_CTRL, KVM_LOONGARCH_VM_FEAT_LASX);
if (!ret)
cfg |= CPUCFG2_LASX;
+ ret = __kvm_has_device_attr(vm->fd, KVM_LOONGARCH_VM_FEAT_CTRL, KVM_LOONGARCH_VM_FEAT_PTW);
+ if (!ret) {
+ cfg |= CPUCFG2_PTW;
+ has_ptw = true;
+ }
+
loongarch_set_cpucfg(vcpu, LOONGARCH_CPUCFG2, cfg);
cfg = read_cpucfg(LOONGARCH_CPUCFG6);
loongarch_set_cpucfg(vcpu, LOONGARCH_CPUCFG6, cfg);
@@ -338,6 +345,9 @@ void loongarch_vcpu_setup(struct kvm_vcpu *vcpu)
/* PGD page shift and width */
val = (vm->page_shift + width * (vm->mmu.pgtable_levels - 1)) | width << 6;
+ if (has_ptw)
+ val |= CSR_PWCTL1_PTW;
+
loongarch_set_csr(vcpu, LOONGARCH_CSR_PWCTL1, val);
loongarch_set_csr(vcpu, LOONGARCH_CSR_PGDL, vm->mmu.pgd);
@@ -345,8 +355,10 @@ void loongarch_vcpu_setup(struct kvm_vcpu *vcpu)
* Refill exception runs on real mode
* Entry address should be physical address
*/
- val = addr_gva2gpa(vm, (unsigned long)handle_tlb_refill);
- loongarch_set_csr(vcpu, LOONGARCH_CSR_TLBRENTRY, val);
+ if (!has_ptw) {
+ val = addr_gva2gpa(vm, (unsigned long)handle_tlb_refill);
+ loongarch_set_csr(vcpu, LOONGARCH_CSR_TLBRENTRY, val);
+ }
/*
* General exception runs on page-enabled mode
|
| 3/2 | 2026/09/25 06:19 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 3934 output: 83 thoughts: 571 Thoughts: **Analyzing the Patch for Fuzzing with Syzkaller** Alright, let's take a look at this patch commit and determine if it's worth fuzzing with syzkaller. The target architecture is amd64, so that's the key. First thing, let's look at the diff. Okay, it's only touching `tools/testing/selftests/kvm/include/loongarch/processor.h` and `tools/testing/selftests/kvm/lib/loongarch/processor.c`. Right away, that raises a flag. Now, let's apply the ruleset. Specifically, Section 2 deals with when to definitively return `WorthFuzzing=false`. The relevant conditions are: 1. "Non-kernel and non-executable changes: User-space directories, self-tests, samples, or scripts (e.g., tools/, samples/, scripts/, usr/) that do not affect the compiled kernel image (vmlinux) or kernel modules." 2. "Code paths exclusive to architectures other than the target architecture." Bingo. This patch satisfies both conditions. The files are under `tools/testing/selftests/`, which is user-space selftests, outside the kernel image. And, it's specific to the LoongArch architecture, while the target is amd64. Easy call there. To be absolutely sure, let's cross-reference against the "Return WorthFuzzing=false ONLY IF" criteria. The modified files are *only* in `tools/testing/selftests/kvm/include/loongarch/processor.h` and `tools/testing/selftests/kvm/lib/loongarch/processor.c`. Both of those are user-space selftests and specifically architecture-dependent code, in this case LoongArch. Therefore, the verdict is clear: `WorthFuzzing` is definitively `false`. So, the reasoning I'll provide is: "The patch only modifies KVM selftests in `tools/testing/selftests/kvm/` (user-space selftest code that is not part of the kernel image) and is also specific to the LoongArch architecture, whereas the target architecture is amd64." There will be no `FocusSymbols` or `EnableConfigs` to report. Done. Let's set the results now. |
| 4/2 | 2026/09/25 06:20 | tool | set-results |
0mArgs:{
"EnableConfigs": [],
"FocusSymbols": [],
"Reasoning": "The patch modifies only user-space KVM selftests under tools/testing/selftests/kvm/ (which do not affect the compiled kernel image) and specifically targets the LoongArch architecture, whereas the target architecture is amd64.",
"WorthFuzzing": false
}Results: {
"EnableConfigs": null,
"FocusSymbols": [],
"Reasoning": "The patch modifies only user-space KVM selftests under tools/testing/selftests/kvm/ (which do not affect the compiled kernel image) and specifically targets the LoongArch architecture, whereas the target architecture is amd64.",
"WorthFuzzing": false
} |
| 5/1 | 2026/09/25 06:20 | action | If |
0mArgs:{
"WorthFuzzing": false
}Results: null |
| Total Calls | Total Tokens | Avg Tokens | Total Duration (Seconds) | Avg Duration (Seconds) |
|---|
| Total Calls | Total Duration (Seconds) | Avg Duration (Seconds) |
|---|