| Seq | Timestamp | Type | Name | Duration |
|---|---|---|---|---|
| 0/0 | 2026/11/01 22:20 | flow | patch-triage |
0mArgs:null Results: {
"EnableConfigs": null,
"FocusSymbols": [],
"KMSANReasoning": "",
"NeedsKMSAN": false,
"Reasoning": "The patch modifies only user-space selftest code in tools/testing/selftests/proc/proc-maps-race.c, which does not affect the compiled kernel image (vmlinux) or kernel modules.",
"WorthFuzzing": false
} |
| 1/1 | 2026/11/01 22:20 | action | read-patch-diff |
0mArgs:null Results: {
"PatchDiff": "commit 830cc4b11a2429ab5ca8fb9577f16de3d9da0514\nAuthor: syz-cluster \u003ctriage@syzkaller.com\u003e\nDate: Sun Nov 1 22:20:34 2026 +0000\n\n syz-cluster: applied patch under review\n\ndiff --git a/tools/testing/selftests/proc/proc-maps-race.c b/tools/testing/selftests/proc/proc-maps-race.c\nindex bf4c5073f6fc86..6025aea6819054 100644\n--- a/tools/testing/selftests/proc/proc-maps-race.c\n+++ b/tools/testing/selftests/proc/proc-maps-race.c\n@@ -528,13 +528,10 @@ static bool compare_smaps_rollup(FIXTURE_DATA(proc_maps_race) *self,\n \t\tstruct smaps_rollup_stats *actual)\n {\n \t/*\n-\t * Clean/dirty metrics might change but Pss-related ones\n-\t * should stay constant.\n+\t * Clean/dirty metrics might change. Pss depends on map count and might\n+\t * change as well. Rss should stay constant.\n \t */\n-\tif (cmp_smaps_rollup_stat(expected, actual, Pss) \u0026\u0026\n-\t cmp_smaps_rollup_stat(expected, actual, Pss_Anon) \u0026\u0026\n-\t cmp_smaps_rollup_stat(expected, actual, Pss_File) \u0026\u0026\n-\t cmp_smaps_rollup_stat(expected, actual, Pss_Shmem))\n+\tif (cmp_smaps_rollup_stat(expected, actual, Rss))\n \t\treturn true;\n \n \tprint_smaps_rollup_stats(\"Expected stats:\", self, expected);\n@@ -637,14 +634,13 @@ static bool query_addr_at(int maps_fd, void *addr,\n static inline bool split_vma(FIXTURE_DATA(proc_maps_race) *self)\n {\n \t/* PROT_NONE differs from both readable neighbors. */\n-\treturn mmap(self-\u003emod_info-\u003eaddr, self-\u003epage_size, PROT_NONE,\n-\t\t MAP_PRIVATE | MAP_ANONYMOUS | MAP_FIXED, -1, 0) != MAP_FAILED;\n+\treturn mprotect(self-\u003emod_info-\u003eaddr, self-\u003epage_size, PROT_NONE) == 0;\n }\n \n static inline bool merge_vma(FIXTURE_DATA(proc_maps_race) *self)\n {\n-\treturn mmap(self-\u003emod_info-\u003eaddr, self-\u003epage_size, self-\u003emod_info-\u003eprot,\n-\t\t MAP_PRIVATE | MAP_ANONYMOUS | MAP_FIXED, -1, 0) != MAP_FAILED;\n+\treturn mprotect(self-\u003emod_info-\u003eaddr, self-\u003epage_size,\n+\t\t\tself-\u003emod_info-\u003eprot) == 0;\n }\n \n static inline bool check_split_result(struct line_content *mod_last_line,\n@@ -681,6 +677,12 @@ static inline bool check_shrink_result(struct line_content *mod_last_line,\n \n static inline bool remap_vma(FIXTURE_DATA(proc_maps_race) *self)\n {\n+\t/*\n+\t * Unlock next_addr so MREMAP_DONTUNMAP does not split it.\n+\t */\n+\tif (munlock(self-\u003emod_info-\u003enext_addr, self-\u003epage_size * 3) != 0)\n+\t\treturn false;\n+\n \t/*\n \t * Remap the last page of the next vma into the middle of the vma.\n \t * This splits the current vma and the first and middle parts (the\n@@ -694,8 +696,9 @@ static inline bool remap_vma(FIXTURE_DATA(proc_maps_race) *self)\n \n static inline bool patch_vma(FIXTURE_DATA(proc_maps_race) *self)\n {\n-\treturn mprotect(self-\u003emod_info-\u003eaddr + self-\u003epage_size, self-\u003epage_size,\n-\t\t\tself-\u003emod_info-\u003eprot) == 0;\n+\treturn mmap(self-\u003emod_info-\u003eaddr + self-\u003epage_size, self-\u003epage_size,\n+\t\t self-\u003emod_info-\u003eprot,\n+\t\t MAP_PRIVATE | MAP_ANONYMOUS | MAP_FIXED, -1, 0) != MAP_FAILED;\n }\n \n static inline bool check_remap_result(struct line_content *mod_last_line,\n@@ -759,11 +762,17 @@ FIXTURE_SETUP(proc_maps_race)\n \n \t\tfor (i = 0; i \u003c mod_info-\u003evma_count; i++) {\n \t\t\tmod_info-\u003echild_mapped_addr[i] = mmap(NULL, self-\u003epage_size * 3, prot,\n-\t\t\t\t\tMAP_PRIVATE | MAP_ANONYMOUS, -1, 0);\n+\t\t\t\t\tMAP_PRIVATE | MAP_ANONYMOUS | MAP_POPULATE, -1, 0);\n \t\t\tASSERT_NE(mod_info-\u003echild_mapped_addr[i], MAP_FAILED);\n \t\t\t/* change protection in adjacent maps to prevent merging */\n-\t\t\tprot ^= PROT_WRITE;\n+\t\t\tprot ^= PROT_EXEC;\n \t\t}\n+\t\t/*\n+\t\t * Lock all present pages in memory so memory reclaim cannot\n+\t\t * change RSS during the test, and use MCL_ONFAULT so\n+\t\t * mremap() expansion does not populate new pages.\n+\t\t */\n+\t\tASSERT_EQ(mlockall(MCL_CURRENT | MCL_FUTURE | MCL_ONFAULT), 0);\n \t\tsignal_state(mod_info, CHILD_READY);\n \t\twait_for_state(mod_info, PARENT_READY);\n \t\twhile (true) {\n@@ -833,10 +842,10 @@ FIXTURE_SETUP(proc_maps_race)\n \tfor (int i = 0; i \u003c mod_info-\u003evma_count; i++) {\n \t\tif (mod_info-\u003echild_mapped_addr[i] == (void *)self-\u003elast_line.start_addr) {\n \t\t\tmod_info-\u003eaddr = mod_info-\u003echild_mapped_addr[i];\n-\t\t\tmod_info-\u003eprot = PROT_READ;\n-\t\t\t/* Even VMAs have write permission */\n-\t\t\tif ((i % 2) == 0)\n-\t\t\t\tmod_info-\u003eprot |= PROT_WRITE;\n+\t\t\tmod_info-\u003eprot = PROT_READ | PROT_WRITE;\n+\t\t\t/* Odd VMAs have exec permission */\n+\t\t\tif ((i % 2) != 0)\n+\t\t\t\tmod_info-\u003eprot |= PROT_EXEC;\n \t\t} else if (mod_info-\u003echild_mapped_addr[i] == (void *)self-\u003efirst_line.start_addr) {\n \t\t\tmod_info-\u003enext_addr = mod_info-\u003echild_mapped_addr[i];\n \t\t}\n@@ -1066,7 +1075,6 @@ TEST_F(proc_maps_race, test_maps_tearing_from_remap)\n \tstruct line_content remapped_first_line;\n \tstruct line_content restored_last_line;\n \tstruct line_content restored_first_line;\n-\tstruct smaps_rollup_stats orig_stats;\n \n \twait_for_state(mod_info, SETUP_READY);\n \n@@ -1080,8 +1088,6 @@ TEST_F(proc_maps_race, test_maps_tearing_from_remap)\n \treport_test_start(\"Tearing from remap\", self-\u003everbose);\n \tASSERT_TRUE(capture_mod_pattern(self, \u0026remapped_last_line, \u0026remapped_first_line,\n \t\t\t\t\t\u0026restored_last_line, \u0026restored_first_line));\n-\tif (self-\u003emaps_file == SMAPS)\n-\t\tASSERT_TRUE(parse_smaps_rollup(self, \u0026orig_stats));\n \n \t/* Now start concurrent modifications for self-\u003eduration_sec */\n \tsignal_state(mod_info, TEST_READY);\n@@ -1134,11 +1140,6 @@ TEST_F(proc_maps_race, test_maps_tearing_from_remap)\n \t\t\t\t vma_end - vma_start == self-\u003epage_size * 3) ||\n \t\t\t\t (vma_start == self-\u003elast_line.start_addr + self-\u003epage_size \u0026\u0026\n \t\t\t\t vma_end - vma_start == self-\u003epage_size));\n-\t\t} else {\n-\t\t\tstruct smaps_rollup_stats stats;\n-\n-\t\t\tASSERT_TRUE(parse_smaps_rollup(self, \u0026stats));\n-\t\t\tASSERT_TRUE(compare_smaps_rollup(self, \u0026orig_stats, \u0026stats));\n \t\t}\n \t\tclock_gettime(CLOCK_MONOTONIC_COARSE, \u0026end_ts);\n \t\tend_test_iteration(\u0026end_ts, self-\u003everbose);\n"
} |
| 2/1 | 2026/11/01 22:20 | agent | patch-evaluator |
0mModel:core Args: null Results: {
"EnableConfigs": null,
"FocusSymbols": [],
"Reasoning": "The patch modifies only user-space selftest code in tools/testing/selftests/proc/proc-maps-race.c, which does not affect the compiled kernel image (vmlinux) or kernel modules.",
"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 830cc4b11a2429ab5ca8fb9577f16de3d9da0514
Author: syz-cluster <triage@syzkaller.com>
Date: Sun Nov 1 22:20:34 2026 +0000
syz-cluster: applied patch under review
diff --git a/tools/testing/selftests/proc/proc-maps-race.c b/tools/testing/selftests/proc/proc-maps-race.c
index bf4c5073f6fc86..6025aea6819054 100644
--- a/tools/testing/selftests/proc/proc-maps-race.c
+++ b/tools/testing/selftests/proc/proc-maps-race.c
@@ -528,13 +528,10 @@ static bool compare_smaps_rollup(FIXTURE_DATA(proc_maps_race) *self,
struct smaps_rollup_stats *actual)
{
/*
- * Clean/dirty metrics might change but Pss-related ones
- * should stay constant.
+ * Clean/dirty metrics might change. Pss depends on map count and might
+ * change as well. Rss should stay constant.
*/
- if (cmp_smaps_rollup_stat(expected, actual, Pss) &&
- cmp_smaps_rollup_stat(expected, actual, Pss_Anon) &&
- cmp_smaps_rollup_stat(expected, actual, Pss_File) &&
- cmp_smaps_rollup_stat(expected, actual, Pss_Shmem))
+ if (cmp_smaps_rollup_stat(expected, actual, Rss))
return true;
print_smaps_rollup_stats("Expected stats:", self, expected);
@@ -637,14 +634,13 @@ static bool query_addr_at(int maps_fd, void *addr,
static inline bool split_vma(FIXTURE_DATA(proc_maps_race) *self)
{
/* PROT_NONE differs from both readable neighbors. */
- return mmap(self->mod_info->addr, self->page_size, PROT_NONE,
- MAP_PRIVATE | MAP_ANONYMOUS | MAP_FIXED, -1, 0) != MAP_FAILED;
+ return mprotect(self->mod_info->addr, self->page_size, PROT_NONE) == 0;
}
static inline bool merge_vma(FIXTURE_DATA(proc_maps_race) *self)
{
- return mmap(self->mod_info->addr, self->page_size, self->mod_info->prot,
- MAP_PRIVATE | MAP_ANONYMOUS | MAP_FIXED, -1, 0) != MAP_FAILED;
+ return mprotect(self->mod_info->addr, self->page_size,
+ self->mod_info->prot) == 0;
}
static inline bool check_split_result(struct line_content *mod_last_line,
@@ -681,6 +677,12 @@ static inline bool check_shrink_result(struct line_content *mod_last_line,
static inline bool remap_vma(FIXTURE_DATA(proc_maps_race) *self)
{
+ /*
+ * Unlock next_addr so MREMAP_DONTUNMAP does not split it.
+ */
+ if (munlock(self->mod_info->next_addr, self->page_size * 3) != 0)
+ return false;
+
/*
* Remap the last page of the next vma into the middle of the vma.
* This splits the current vma and the first and middle parts (the
@@ -694,8 +696,9 @@ static inline bool remap_vma(FIXTURE_DATA(proc_maps_race) *self)
static inline bool patch_vma(FIXTURE_DATA(proc_maps_race) *self)
{
- return mprotect(self->mod_info->addr + self->page_size, self->page_size,
- self->mod_info->prot) == 0;
+ return mmap(self->mod_info->addr + self->page_size, self->page_size,
+ self->mod_info->prot,
+ MAP_PRIVATE | MAP_ANONYMOUS | MAP_FIXED, -1, 0) != MAP_FAILED;
}
static inline bool check_remap_result(struct line_content *mod_last_line,
@@ -759,11 +762,17 @@ FIXTURE_SETUP(proc_maps_race)
for (i = 0; i < mod_info->vma_count; i++) {
mod_info->child_mapped_addr[i] = mmap(NULL, self->page_size * 3, prot,
- MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
+ MAP_PRIVATE | MAP_ANONYMOUS | MAP_POPULATE, -1, 0);
ASSERT_NE(mod_info->child_mapped_addr[i], MAP_FAILED);
/* change protection in adjacent maps to prevent merging */
- prot ^= PROT_WRITE;
+ prot ^= PROT_EXEC;
}
+ /*
+ * Lock all present pages in memory so memory reclaim cannot
+ * change RSS during the test, and use MCL_ONFAULT so
+ * mremap() expansion does not populate new pages.
+ */
+ ASSERT_EQ(mlockall(MCL_CURRENT | MCL_FUTURE | MCL_ONFAULT), 0);
signal_state(mod_info, CHILD_READY);
wait_for_state(mod_info, PARENT_READY);
while (true) {
@@ -833,10 +842,10 @@ FIXTURE_SETUP(proc_maps_race)
for (int i = 0; i < mod_info->vma_count; i++) {
if (mod_info->child_mapped_addr[i] == (void *)self->last_line.start_addr) {
mod_info->addr = mod_info->child_mapped_addr[i];
- mod_info->prot = PROT_READ;
- /* Even VMAs have write permission */
- if ((i % 2) == 0)
- mod_info->prot |= PROT_WRITE;
+ mod_info->prot = PROT_READ | PROT_WRITE;
+ /* Odd VMAs have exec permission */
+ if ((i % 2) != 0)
+ mod_info->prot |= PROT_EXEC;
} else if (mod_info->child_mapped_addr[i] == (void *)self->first_line.start_addr) {
mod_info->next_addr = mod_info->child_mapped_addr[i];
}
@@ -1066,7 +1075,6 @@ TEST_F(proc_maps_race, test_maps_tearing_from_remap)
struct line_content remapped_first_line;
struct line_content restored_last_line;
struct line_content restored_first_line;
- struct smaps_rollup_stats orig_stats;
wait_for_state(mod_info, SETUP_READY);
@@ -1080,8 +1088,6 @@ TEST_F(proc_maps_race, test_maps_tearing_from_remap)
report_test_start("Tearing from remap", self->verbose);
ASSERT_TRUE(capture_mod_pattern(self, &remapped_last_line, &remapped_first_line,
&restored_last_line, &restored_first_line));
- if (self->maps_file == SMAPS)
- ASSERT_TRUE(parse_smaps_rollup(self, &orig_stats));
/* Now start concurrent modifications for self->duration_sec */
signal_state(mod_info, TEST_READY);
@@ -1134,11 +1140,6 @@ TEST_F(proc_maps_race, test_maps_tearing_from_remap)
vma_end - vma_start == self->page_size * 3) ||
(vma_start == self->last_line.start_addr + self->page_size &&
vma_end - vma_start == self->page_size));
- } else {
- struct smaps_rollup_stats stats;
-
- ASSERT_TRUE(parse_smaps_rollup(self, &stats));
- ASSERT_TRUE(compare_smaps_rollup(self, &orig_stats, &stats));
}
clock_gettime(CLOCK_MONOTONIC_COARSE, &end_ts);
end_test_iteration(&end_ts, self->verbose);
|
| 3/2 | 2026/11/01 22:20 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 4973 output: 77 thoughts: 1028 Thoughts: **Patch Evaluation: WorthFuzzing = False** Okay, let's analyze this patch series. The user wants an evaluation, so my first step is to dive into the changes. The patch modifies only `tools/testing/selftests/proc/proc-maps-race.c`. I need to determine if this change warrants fuzzing. My primary reference is the set of rules – specifically, the negative criteria. Rule 2 is key: I need to return `WorthFuzzing=false` *only if* *all* modified code strictly falls into specific categories. These categories include things like documentation, comments, and, critically, user-space directories for self-tests that don't impact the kernel image or modules. The modified file, `tools/testing/selftests/proc/proc-maps-race.c`, is located within `tools/testing/selftests/`, and that directory is *exactly* the kind of user-space self-test directory that the rule describes. I'm confident in this assessment. I briefly considered verifying this by checking for other commits or modified files. I thought about using `git status` or `git grep`, but the prompt conveniently provided the full diff, including the commit hash and author. This confirms that only `tools/testing/selftests/proc/proc-maps-race.c` was touched. I am not running git commands directly here. The provided information from the patch reinforces that the change is limited to `tools/testing/selftests/proc/proc-maps-race.c`. There's no ambiguity here. Therefore, because this change is *strictly* contained within a user-space self-test directory and does *not* affect the kernel image or modules, `WorthFuzzing` must be `false`. Given this, the results are: * `WorthFuzzing: false` * `FocusSymbols: []` (no focus symbols needed) * `EnableConfigs: []` (no specific configs needed) * `Reasoning:` "The patch only modifies user-space selftests in `tools/testing/selftests/proc/proc-maps-race.c`, which does not affect the compiled kernel image (vmlinux) or any kernel modules. Therefore, it is not worth fuzzing." I'll proceed to set the results directly. |
| 4/2 | 2026/11/01 22:20 | tool | set-results |
0mArgs:{
"EnableConfigs": [],
"FocusSymbols": [],
"Reasoning": "The patch modifies only user-space selftest code in tools/testing/selftests/proc/proc-maps-race.c, which does not affect the compiled kernel image (vmlinux) or kernel modules.",
"WorthFuzzing": false
}Results: {
"EnableConfigs": null,
"FocusSymbols": [],
"Reasoning": "The patch modifies only user-space selftest code in tools/testing/selftests/proc/proc-maps-race.c, which does not affect the compiled kernel image (vmlinux) or kernel modules.",
"WorthFuzzing": false
} |
| 5/1 | 2026/11/01 22: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) |
|---|