| Seq | Timestamp | Type | Name | Duration |
|---|---|---|---|---|
| 0/0 | 2026/09/17 04:08 | flow | patch-triage |
0mArgs:null Results: {
"EnableConfigs": null,
"FocusSymbols": [],
"KMSANReasoning": "",
"NeedsKMSAN": false,
"Reasoning": "The patch modifies error cleanup in fttmr010_common_init() within drivers/clocksource/timer-fttmr010.c, an early boot OF timer driver for ARM-based SoCs (Faraday, Gemini, Moxa ART, Aspeed). It is probed exclusively via Device Tree (TIMER_OF_DECLARE) on ARM platforms and is structurally unreachable on the target architecture (amd64).",
"WorthFuzzing": false
} |
| 1/1 | 2026/09/17 04:08 | action | read-patch-diff |
0mArgs:null Results: {
"PatchDiff": "commit a8ba977d3ee59b479e3a31c2bb1e5ad6a4c62339\nAuthor: syz-cluster \u003ctriage@syzkaller.com\u003e\nDate: Thu Sep 17 04:08:37 2026 +0000\n\n syz-cluster: applied patch under review\n\ndiff --git a/drivers/clocksource/timer-fttmr010.c b/drivers/clocksource/timer-fttmr010.c\nindex 308f94bfbaed2..c2553851e8d6f 100644\n--- a/drivers/clocksource/timer-fttmr010.c\n+++ b/drivers/clocksource/timer-fttmr010.c\n@@ -292,6 +292,7 @@ static int __init fttmr010_common_init(struct device_node *np,\n \tret = clk_prepare_enable(clk);\n \tif (ret) {\n \t\tpr_err(\"failed to enable PCLK\\n\");\n+\t\tclk_put(clk);\n \t\treturn ret;\n \t}\n \n@@ -432,6 +433,7 @@ static int __init fttmr010_common_init(struct device_node *np,\n \tkfree(fttmr010);\n out_disable_clock:\n \tclk_disable_unprepare(clk);\n+\tclk_put(clk);\n \n \treturn ret;\n }\n"
} |
| 2/1 | 2026/09/17 04:08 | agent | patch-evaluator |
0mModel:core Args: null Results: {
"EnableConfigs": null,
"FocusSymbols": [],
"Reasoning": "The patch modifies error cleanup in fttmr010_common_init() within drivers/clocksource/timer-fttmr010.c, an early boot OF timer driver for ARM-based SoCs (Faraday, Gemini, Moxa ART, Aspeed). It is probed exclusively via Device Tree (TIMER_OF_DECLARE) on ARM platforms and is structurally unreachable on the target architecture (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 a8ba977d3ee59b479e3a31c2bb1e5ad6a4c62339
Author: syz-cluster <triage@syzkaller.com>
Date: Thu Sep 17 04:08:37 2026 +0000
syz-cluster: applied patch under review
diff --git a/drivers/clocksource/timer-fttmr010.c b/drivers/clocksource/timer-fttmr010.c
index 308f94bfbaed2..c2553851e8d6f 100644
--- a/drivers/clocksource/timer-fttmr010.c
+++ b/drivers/clocksource/timer-fttmr010.c
@@ -292,6 +292,7 @@ static int __init fttmr010_common_init(struct device_node *np,
ret = clk_prepare_enable(clk);
if (ret) {
pr_err("failed to enable PCLK\n");
+ clk_put(clk);
return ret;
}
@@ -432,6 +433,7 @@ static int __init fttmr010_common_init(struct device_node *np,
kfree(fttmr010);
out_disable_clock:
clk_disable_unprepare(clk);
+ clk_put(clk);
return ret;
}
|
| 3/2 | 2026/09/17 04:08 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 2954 output: 30 thoughts: 114 Thoughts: **Analyzing the Patch for the Timer-FTTMR010 Driver** Okay, let's dive into this. First, I need to understand this patch and what's required of it. It looks like we're targeting the amd64 architecture, good, that simplifies things a bit. The patch is touching the `drivers/clocksource/timer-fttmr010.c` file. Right, the FTTMR010 timer driver. Now, I need to quickly ascertain the context. I want to know exactly what hardware this driver is tied to, and what the dependencies are. I'll need to inspect both the `timer-fttmr010.c` file itself *and* its corresponding Kconfig entry. The Kconfig entry will give me the conditional build requirements, any architecture-specific details, and likely the hardware this is designed for. I'll use `read-file` or `grepper` to quickly pull that information. Time to get the details I need to proceed with a proper assessment. |
| 4/2 | 2026/09/17 04:09 | tool | grepper |
0mArgs:{
"Expression": "fttmr010",
"PathPrefix": "drivers/clocksource"
}Results: {
"Output": "drivers/clocksource/Makefile=24=obj-$(CONFIG_DW_APB_TIMER_OF)\t+= dw_apb_timer_of.o\ndrivers/clocksource/Makefile:25:obj-$(CONFIG_FTTMR010_TIMER)\t+= timer-fttmr010.o\ndrivers/clocksource/Makefile-26-obj-$(CONFIG_IXP4XX_TIMER)\t+= timer-ixp4xx.o\n--\ndrivers/clocksource/timer-fttmr010.c-45-/*\ndrivers/clocksource/timer-fttmr010.c:46: * Control register (TMC30) bit fields for fttmr010/gemini/moxart timers.\ndrivers/clocksource/timer-fttmr010.c-47- */\n--\ndrivers/clocksource/timer-fttmr010.c-76-/*\ndrivers/clocksource/timer-fttmr010.c:77: * Interrupt status/mask register definitions for fttmr010/gemini/moxart\ndrivers/clocksource/timer-fttmr010.c-78- * timers.\n--\ndrivers/clocksource/timer-fttmr010.c-98-\ndrivers/clocksource/timer-fttmr010.c:99:struct fttmr010 {\ndrivers/clocksource/timer-fttmr010.c-100-\tvoid __iomem *base;\n--\ndrivers/clocksource/timer-fttmr010.c-114- */\ndrivers/clocksource/timer-fttmr010.c:115:static struct fttmr010 *local_fttmr;\ndrivers/clocksource/timer-fttmr010.c-116-\ndrivers/clocksource/timer-fttmr010.c:117:static inline struct fttmr010 *to_fttmr010(struct clock_event_device *evt)\ndrivers/clocksource/timer-fttmr010.c-118-{\ndrivers/clocksource/timer-fttmr010.c:119:\treturn container_of(evt, struct fttmr010, clkevt);\ndrivers/clocksource/timer-fttmr010.c-120-}\ndrivers/clocksource/timer-fttmr010.c-121-\ndrivers/clocksource/timer-fttmr010.c:122:static unsigned long fttmr010_read_current_timer_up(void)\ndrivers/clocksource/timer-fttmr010.c-123-{\n--\ndrivers/clocksource/timer-fttmr010.c-126-\ndrivers/clocksource/timer-fttmr010.c:127:static unsigned long fttmr010_read_current_timer_down(void)\ndrivers/clocksource/timer-fttmr010.c-128-{\n--\ndrivers/clocksource/timer-fttmr010.c-131-\ndrivers/clocksource/timer-fttmr010.c:132:static u64 notrace fttmr010_read_sched_clock_up(void)\ndrivers/clocksource/timer-fttmr010.c-133-{\ndrivers/clocksource/timer-fttmr010.c:134:\treturn fttmr010_read_current_timer_up();\ndrivers/clocksource/timer-fttmr010.c-135-}\ndrivers/clocksource/timer-fttmr010.c-136-\ndrivers/clocksource/timer-fttmr010.c:137:static u64 notrace fttmr010_read_sched_clock_down(void)\ndrivers/clocksource/timer-fttmr010.c-138-{\ndrivers/clocksource/timer-fttmr010.c:139:\treturn fttmr010_read_current_timer_down();\ndrivers/clocksource/timer-fttmr010.c-140-}\ndrivers/clocksource/timer-fttmr010.c-141-\ndrivers/clocksource/timer-fttmr010.c:142:static int fttmr010_timer_set_next_event(unsigned long cycles,\ndrivers/clocksource/timer-fttmr010.c-143-\t\t\t\t struct clock_event_device *evt)\ndrivers/clocksource/timer-fttmr010.c-144-{\ndrivers/clocksource/timer-fttmr010.c:145:\tstruct fttmr010 *fttmr010 = to_fttmr010(evt);\ndrivers/clocksource/timer-fttmr010.c-146-\tu32 cr;\n--\ndrivers/clocksource/timer-fttmr010.c-148-\t/* Stop */\ndrivers/clocksource/timer-fttmr010.c:149:\tfttmr010-\u003etimer_shutdown(evt);\ndrivers/clocksource/timer-fttmr010.c-150-\ndrivers/clocksource/timer-fttmr010.c:151:\tif (fttmr010-\u003eis_aspeed) {\ndrivers/clocksource/timer-fttmr010.c-152-\t\t/*\n--\ndrivers/clocksource/timer-fttmr010.c-155-\t\t */\ndrivers/clocksource/timer-fttmr010.c:156:\t\twritel(cycles, fttmr010-\u003ebase + TIMER1_LOAD);\ndrivers/clocksource/timer-fttmr010.c-157-\t} else {\ndrivers/clocksource/timer-fttmr010.c-158-\t\t/* Setup the match register forward in time */\ndrivers/clocksource/timer-fttmr010.c:159:\t\tcr = readl(fttmr010-\u003ebase + TIMER1_COUNT);\ndrivers/clocksource/timer-fttmr010.c:160:\t\twritel(cr + cycles, fttmr010-\u003ebase + TIMER1_MATCH1);\ndrivers/clocksource/timer-fttmr010.c-161-\t}\n--\ndrivers/clocksource/timer-fttmr010.c-163-\t/* Start */\ndrivers/clocksource/timer-fttmr010.c:164:\tcr = readl(fttmr010-\u003ebase + TIMER_CR);\ndrivers/clocksource/timer-fttmr010.c:165:\tcr |= fttmr010-\u003et1_enable_val;\ndrivers/clocksource/timer-fttmr010.c:166:\twritel(cr, fttmr010-\u003ebase + TIMER_CR);\ndrivers/clocksource/timer-fttmr010.c-167-\n--\ndrivers/clocksource/timer-fttmr010.c=171=static int ast2600_timer_shutdown(struct clock_event_device *evt)\ndrivers/clocksource/timer-fttmr010.c-172-{\ndrivers/clocksource/timer-fttmr010.c:173:\tstruct fttmr010 *fttmr010 = to_fttmr010(evt);\ndrivers/clocksource/timer-fttmr010.c-174-\ndrivers/clocksource/timer-fttmr010.c-175-\t/* Stop */\ndrivers/clocksource/timer-fttmr010.c:176:\twritel(fttmr010-\u003et1_enable_val, fttmr010-\u003ebase + AST2600_TIMER_CR_CLR);\ndrivers/clocksource/timer-fttmr010.c-177-\n--\ndrivers/clocksource/timer-fttmr010.c-180-\ndrivers/clocksource/timer-fttmr010.c:181:static int fttmr010_timer_shutdown(struct clock_event_device *evt)\ndrivers/clocksource/timer-fttmr010.c-182-{\ndrivers/clocksource/timer-fttmr010.c:183:\tstruct fttmr010 *fttmr010 = to_fttmr010(evt);\ndrivers/clocksource/timer-fttmr010.c-184-\tu32 cr;\n--\ndrivers/clocksource/timer-fttmr010.c-186-\t/* Stop */\ndrivers/clocksource/timer-fttmr010.c:187:\tcr = readl(fttmr010-\u003ebase + TIMER_CR);\ndrivers/clocksource/timer-fttmr010.c:188:\tcr \u0026= ~fttmr010-\u003et1_enable_val;\ndrivers/clocksource/timer-fttmr010.c:189:\twritel(cr, fttmr010-\u003ebase + TIMER_CR);\ndrivers/clocksource/timer-fttmr010.c-190-\n--\ndrivers/clocksource/timer-fttmr010.c-193-\ndrivers/clocksource/timer-fttmr010.c:194:static int fttmr010_timer_set_oneshot(struct clock_event_device *evt)\ndrivers/clocksource/timer-fttmr010.c-195-{\ndrivers/clocksource/timer-fttmr010.c:196:\tstruct fttmr010 *fttmr010 = to_fttmr010(evt);\ndrivers/clocksource/timer-fttmr010.c-197-\tu32 cr;\n--\ndrivers/clocksource/timer-fttmr010.c-199-\t/* Stop */\ndrivers/clocksource/timer-fttmr010.c:200:\tfttmr010-\u003etimer_shutdown(evt);\ndrivers/clocksource/timer-fttmr010.c-201-\ndrivers/clocksource/timer-fttmr010.c-202-\t/* Setup counter start from 0 or ~0 */\ndrivers/clocksource/timer-fttmr010.c:203:\twritel(0, fttmr010-\u003ebase + TIMER1_COUNT);\ndrivers/clocksource/timer-fttmr010.c:204:\tif (fttmr010-\u003eis_aspeed) {\ndrivers/clocksource/timer-fttmr010.c:205:\t\twritel(~0, fttmr010-\u003ebase + TIMER1_LOAD);\ndrivers/clocksource/timer-fttmr010.c-206-\t} else {\ndrivers/clocksource/timer-fttmr010.c:207:\t\twritel(0, fttmr010-\u003ebase + TIMER1_LOAD);\ndrivers/clocksource/timer-fttmr010.c-208-\ndrivers/clocksource/timer-fttmr010.c-209-\t\t/* Enable interrupt */\ndrivers/clocksource/timer-fttmr010.c:210:\t\tcr = readl(fttmr010-\u003ebase + TIMER_INTR_MASK);\ndrivers/clocksource/timer-fttmr010.c-211-\t\tcr \u0026= ~(TIMER_1_INT_OVERFLOW | TIMER_1_INT_MATCH2);\ndrivers/clocksource/timer-fttmr010.c-212-\t\tcr |= TIMER_1_INT_MATCH1;\ndrivers/clocksource/timer-fttmr010.c:213:\t\twritel(cr, fttmr010-\u003ebase + TIMER_INTR_MASK);\ndrivers/clocksource/timer-fttmr010.c-214-\t}\n--\ndrivers/clocksource/timer-fttmr010.c-218-\ndrivers/clocksource/timer-fttmr010.c:219:static int fttmr010_timer_set_periodic(struct clock_event_device *evt)\ndrivers/clocksource/timer-fttmr010.c-220-{\ndrivers/clocksource/timer-fttmr010.c:221:\tstruct fttmr010 *fttmr010 = to_fttmr010(evt);\ndrivers/clocksource/timer-fttmr010.c:222:\tu32 period = DIV_ROUND_CLOSEST(fttmr010-\u003etick_rate, HZ);\ndrivers/clocksource/timer-fttmr010.c-223-\tu32 cr;\n--\ndrivers/clocksource/timer-fttmr010.c-225-\t/* Stop */\ndrivers/clocksource/timer-fttmr010.c:226:\tfttmr010-\u003etimer_shutdown(evt);\ndrivers/clocksource/timer-fttmr010.c-227-\ndrivers/clocksource/timer-fttmr010.c-228-\t/* Setup timer to fire at 1/HZ intervals. */\ndrivers/clocksource/timer-fttmr010.c:229:\tif (fttmr010-\u003eis_aspeed) {\ndrivers/clocksource/timer-fttmr010.c:230:\t\twritel(period, fttmr010-\u003ebase + TIMER1_LOAD);\ndrivers/clocksource/timer-fttmr010.c-231-\t} else {\ndrivers/clocksource/timer-fttmr010.c-232-\t\tcr = 0xffffffff - (period - 1);\ndrivers/clocksource/timer-fttmr010.c:233:\t\twritel(cr, fttmr010-\u003ebase + TIMER1_COUNT);\ndrivers/clocksource/timer-fttmr010.c:234:\t\twritel(cr, fttmr010-\u003ebase + TIMER1_LOAD);\ndrivers/clocksource/timer-fttmr010.c-235-\ndrivers/clocksource/timer-fttmr010.c-236-\t\t/* Enable interrupt on overflow */\ndrivers/clocksource/timer-fttmr010.c:237:\t\tcr = readl(fttmr010-\u003ebase + TIMER_INTR_MASK);\ndrivers/clocksource/timer-fttmr010.c-238-\t\tcr \u0026= ~(TIMER_1_INT_MATCH1 | TIMER_1_INT_MATCH2);\ndrivers/clocksource/timer-fttmr010.c-239-\t\tcr |= TIMER_1_INT_OVERFLOW;\ndrivers/clocksource/timer-fttmr010.c:240:\t\twritel(cr, fttmr010-\u003ebase + TIMER_INTR_MASK);\ndrivers/clocksource/timer-fttmr010.c-241-\t}\n--\ndrivers/clocksource/timer-fttmr010.c-243-\t/* Start the timer */\ndrivers/clocksource/timer-fttmr010.c:244:\tcr = readl(fttmr010-\u003ebase + TIMER_CR);\ndrivers/clocksource/timer-fttmr010.c:245:\tcr |= fttmr010-\u003et1_enable_val;\ndrivers/clocksource/timer-fttmr010.c:246:\twritel(cr, fttmr010-\u003ebase + TIMER_CR);\ndrivers/clocksource/timer-fttmr010.c-247-\n--\ndrivers/clocksource/timer-fttmr010.c-253- */\ndrivers/clocksource/timer-fttmr010.c:254:static irqreturn_t fttmr010_timer_interrupt(int irq, void *dev_id)\ndrivers/clocksource/timer-fttmr010.c-255-{\n--\ndrivers/clocksource/timer-fttmr010.c=262=static irqreturn_t ast2600_timer_interrupt(int irq, void *dev_id)\n--\ndrivers/clocksource/timer-fttmr010.c-264-\tstruct clock_event_device *evt = dev_id;\ndrivers/clocksource/timer-fttmr010.c:265:\tstruct fttmr010 *fttmr010 = to_fttmr010(evt);\ndrivers/clocksource/timer-fttmr010.c-266-\ndrivers/clocksource/timer-fttmr010.c:267:\twritel(0x1, fttmr010-\u003ebase + TIMER_INTR_STATE);\ndrivers/clocksource/timer-fttmr010.c-268-\n--\ndrivers/clocksource/timer-fttmr010.c-272-\ndrivers/clocksource/timer-fttmr010.c:273:static int __init fttmr010_common_init(struct device_node *np,\ndrivers/clocksource/timer-fttmr010.c-274-\t\t\t\t bool is_aspeed, bool is_ast2600)\ndrivers/clocksource/timer-fttmr010.c-275-{\ndrivers/clocksource/timer-fttmr010.c:276:\tstruct fttmr010 *fttmr010;\ndrivers/clocksource/timer-fttmr010.c-277-\tint irq;\n--\ndrivers/clocksource/timer-fttmr010.c-298-\ndrivers/clocksource/timer-fttmr010.c:299:\tfttmr010 = kzalloc_obj(*fttmr010);\ndrivers/clocksource/timer-fttmr010.c:300:\tif (!fttmr010) {\ndrivers/clocksource/timer-fttmr010.c-301-\t\tret = -ENOMEM;\n--\ndrivers/clocksource/timer-fttmr010.c-303-\t}\ndrivers/clocksource/timer-fttmr010.c:304:\tfttmr010-\u003etick_rate = clk_get_rate(clk);\ndrivers/clocksource/timer-fttmr010.c-305-\ndrivers/clocksource/timer-fttmr010.c:306:\tfttmr010-\u003ebase = of_iomap(np, 0);\ndrivers/clocksource/timer-fttmr010.c:307:\tif (!fttmr010-\u003ebase) {\ndrivers/clocksource/timer-fttmr010.c-308-\t\tpr_err(\"Can't remap registers\\n\");\n--\ndrivers/clocksource/timer-fttmr010.c-323-\tif (is_aspeed) {\ndrivers/clocksource/timer-fttmr010.c:324:\t\tfttmr010-\u003et1_enable_val = TIMER_1_CR_ASPEED_ENABLE |\ndrivers/clocksource/timer-fttmr010.c-325-\t\t\tTIMER_1_CR_ASPEED_INT;\ndrivers/clocksource/timer-fttmr010.c:326:\t\tfttmr010-\u003eis_aspeed = true;\ndrivers/clocksource/timer-fttmr010.c-327-\t} else {\ndrivers/clocksource/timer-fttmr010.c:328:\t\tfttmr010-\u003et1_enable_val = TIMER_1_CR_ENABLE | TIMER_1_CR_INT;\ndrivers/clocksource/timer-fttmr010.c-329-\n--\ndrivers/clocksource/timer-fttmr010.c-332-\t\t */\ndrivers/clocksource/timer-fttmr010.c:333:\t\twritel(TIMER_INT_ALL_MASK, fttmr010-\u003ebase + TIMER_INTR_MASK);\ndrivers/clocksource/timer-fttmr010.c:334:\t\twritel(0, fttmr010-\u003ebase + TIMER_INTR_STATE);\ndrivers/clocksource/timer-fttmr010.c-335-\t}\n--\ndrivers/clocksource/timer-fttmr010.c-346-\t}\ndrivers/clocksource/timer-fttmr010.c:347:\twritel(val, fttmr010-\u003ebase + TIMER_CR);\ndrivers/clocksource/timer-fttmr010.c-348-\n--\ndrivers/clocksource/timer-fttmr010.c-352-\t */\ndrivers/clocksource/timer-fttmr010.c:353:\tlocal_fttmr = fttmr010;\ndrivers/clocksource/timer-fttmr010.c:354:\twritel(0, fttmr010-\u003ebase + TIMER2_COUNT);\ndrivers/clocksource/timer-fttmr010.c:355:\twritel(0, fttmr010-\u003ebase + TIMER2_MATCH1);\ndrivers/clocksource/timer-fttmr010.c:356:\twritel(0, fttmr010-\u003ebase + TIMER2_MATCH2);\ndrivers/clocksource/timer-fttmr010.c-357-\ndrivers/clocksource/timer-fttmr010.c:358:\tif (fttmr010-\u003eis_aspeed) {\ndrivers/clocksource/timer-fttmr010.c:359:\t\twritel(~0, fttmr010-\u003ebase + TIMER2_LOAD);\ndrivers/clocksource/timer-fttmr010.c:360:\t\tclocksource_mmio_init(fttmr010-\u003ebase + TIMER2_COUNT,\ndrivers/clocksource/timer-fttmr010.c-361-\t\t\t\t \"FTTMR010-TIMER2\",\ndrivers/clocksource/timer-fttmr010.c:362:\t\t\t\t fttmr010-\u003etick_rate,\ndrivers/clocksource/timer-fttmr010.c-363-\t\t\t\t 300, 32, clocksource_mmio_readl_down);\ndrivers/clocksource/timer-fttmr010.c:364:\t\tsched_clock_register(fttmr010_read_sched_clock_down, 32,\ndrivers/clocksource/timer-fttmr010.c:365:\t\t\t\t fttmr010-\u003etick_rate);\ndrivers/clocksource/timer-fttmr010.c-366-\t} else {\ndrivers/clocksource/timer-fttmr010.c:367:\t\twritel(0, fttmr010-\u003ebase + TIMER2_LOAD);\ndrivers/clocksource/timer-fttmr010.c:368:\t\tclocksource_mmio_init(fttmr010-\u003ebase + TIMER2_COUNT,\ndrivers/clocksource/timer-fttmr010.c-369-\t\t\t\t \"FTTMR010-TIMER2\",\ndrivers/clocksource/timer-fttmr010.c:370:\t\t\t\t fttmr010-\u003etick_rate,\ndrivers/clocksource/timer-fttmr010.c-371-\t\t\t\t 300, 32, clocksource_mmio_readl_up);\ndrivers/clocksource/timer-fttmr010.c:372:\t\tsched_clock_register(fttmr010_read_sched_clock_up, 32,\ndrivers/clocksource/timer-fttmr010.c:373:\t\t\t\t fttmr010-\u003etick_rate);\ndrivers/clocksource/timer-fttmr010.c-374-\t}\n--\ndrivers/clocksource/timer-fttmr010.c-378-\t */\ndrivers/clocksource/timer-fttmr010.c:379:\twritel(0, fttmr010-\u003ebase + TIMER1_COUNT);\ndrivers/clocksource/timer-fttmr010.c:380:\twritel(0, fttmr010-\u003ebase + TIMER1_LOAD);\ndrivers/clocksource/timer-fttmr010.c:381:\twritel(0, fttmr010-\u003ebase + TIMER1_MATCH1);\ndrivers/clocksource/timer-fttmr010.c:382:\twritel(0, fttmr010-\u003ebase + TIMER1_MATCH2);\ndrivers/clocksource/timer-fttmr010.c-383-\ndrivers/clocksource/timer-fttmr010.c-384-\tif (is_ast2600) {\ndrivers/clocksource/timer-fttmr010.c:385:\t\tfttmr010-\u003etimer_shutdown = ast2600_timer_shutdown;\ndrivers/clocksource/timer-fttmr010.c-386-\t\tret = request_irq(irq, ast2600_timer_interrupt,\ndrivers/clocksource/timer-fttmr010.c-387-\t\t\t\t IRQF_TIMER, \"FTTMR010-TIMER1\",\ndrivers/clocksource/timer-fttmr010.c:388:\t\t\t\t \u0026fttmr010-\u003eclkevt);\ndrivers/clocksource/timer-fttmr010.c-389-\t} else {\ndrivers/clocksource/timer-fttmr010.c:390:\t\tfttmr010-\u003etimer_shutdown = fttmr010_timer_shutdown;\ndrivers/clocksource/timer-fttmr010.c:391:\t\tret = request_irq(irq, fttmr010_timer_interrupt,\ndrivers/clocksource/timer-fttmr010.c-392-\t\t\t\t IRQF_TIMER, \"FTTMR010-TIMER1\",\ndrivers/clocksource/timer-fttmr010.c:393:\t\t\t\t \u0026fttmr010-\u003eclkevt);\ndrivers/clocksource/timer-fttmr010.c-394-\t}\n--\ndrivers/clocksource/timer-fttmr010.c-399-\ndrivers/clocksource/timer-fttmr010.c:400:\tfttmr010-\u003eclkevt.name = \"FTTMR010-TIMER1\";\ndrivers/clocksource/timer-fttmr010.c-401-\t/* Reasonably fast and accurate clock event */\ndrivers/clocksource/timer-fttmr010.c:402:\tfttmr010-\u003eclkevt.rating = 300;\ndrivers/clocksource/timer-fttmr010.c:403:\tfttmr010-\u003eclkevt.features = CLOCK_EVT_FEAT_PERIODIC |\ndrivers/clocksource/timer-fttmr010.c-404-\t\tCLOCK_EVT_FEAT_ONESHOT;\ndrivers/clocksource/timer-fttmr010.c:405:\tfttmr010-\u003eclkevt.set_next_event = fttmr010_timer_set_next_event;\ndrivers/clocksource/timer-fttmr010.c:406:\tfttmr010-\u003eclkevt.set_state_shutdown = fttmr010-\u003etimer_shutdown;\ndrivers/clocksource/timer-fttmr010.c:407:\tfttmr010-\u003eclkevt.set_state_periodic = fttmr010_timer_set_periodic;\ndrivers/clocksource/timer-fttmr010.c:408:\tfttmr010-\u003eclkevt.set_state_oneshot = fttmr010_timer_set_oneshot;\ndrivers/clocksource/timer-fttmr010.c:409:\tfttmr010-\u003eclkevt.tick_resume = fttmr010-\u003etimer_shutdown;\ndrivers/clocksource/timer-fttmr010.c:410:\tfttmr010-\u003eclkevt.cpumask = cpumask_of(0);\ndrivers/clocksource/timer-fttmr010.c:411:\tfttmr010-\u003eclkevt.irq = irq;\ndrivers/clocksource/timer-fttmr010.c:412:\tclockevents_config_and_register(\u0026fttmr010-\u003eclkevt,\ndrivers/clocksource/timer-fttmr010.c:413:\t\t\t\t\tfttmr010-\u003etick_rate,\ndrivers/clocksource/timer-fttmr010.c-414-\t\t\t\t\t1, 0xffffffff);\n--\ndrivers/clocksource/timer-fttmr010.c-417-\t/* Also use this timer for delays */\ndrivers/clocksource/timer-fttmr010.c:418:\tif (fttmr010-\u003eis_aspeed)\ndrivers/clocksource/timer-fttmr010.c:419:\t\tfttmr010-\u003edelay_timer.read_current_timer =\ndrivers/clocksource/timer-fttmr010.c:420:\t\t\tfttmr010_read_current_timer_down;\ndrivers/clocksource/timer-fttmr010.c-421-\telse\ndrivers/clocksource/timer-fttmr010.c:422:\t\tfttmr010-\u003edelay_timer.read_current_timer =\ndrivers/clocksource/timer-fttmr010.c:423:\t\t\tfttmr010_read_current_timer_up;\ndrivers/clocksource/timer-fttmr010.c:424:\tfttmr010-\u003edelay_timer.freq = fttmr010-\u003etick_rate;\ndrivers/clocksource/timer-fttmr010.c:425:\tregister_current_timer_delay(\u0026fttmr010-\u003edelay_timer);\ndrivers/clocksource/timer-fttmr010.c-426-#endif\n--\ndrivers/clocksource/timer-fttmr010.c-430-out_unmap:\ndrivers/clocksource/timer-fttmr010.c:431:\tiounmap(fttmr010-\u003ebase);\ndrivers/clocksource/timer-fttmr010.c-432-out_free:\ndrivers/clocksource/timer-fttmr010.c:433:\tkfree(fttmr010);\ndrivers/clocksource/timer-fttmr010.c-434-out_disable_clock:\n--\ndrivers/clocksource/timer-fttmr010.c=441=static __init int ast2600_timer_init(struct device_node *np)\ndrivers/clocksource/timer-fttmr010.c-442-{\ndrivers/clocksource/timer-fttmr010.c:443:\treturn fttmr010_common_init(np, true, true);\ndrivers/clocksource/timer-fttmr010.c-444-}\n--\ndrivers/clocksource/timer-fttmr010.c=446=static __init int aspeed_timer_init(struct device_node *np)\ndrivers/clocksource/timer-fttmr010.c-447-{\ndrivers/clocksource/timer-fttmr010.c:448:\treturn fttmr010_common_init(np, true, false);\ndrivers/clocksource/timer-fttmr010.c-449-}\ndrivers/clocksource/timer-fttmr010.c-450-\ndrivers/clocksource/timer-fttmr010.c:451:static __init int fttmr010_timer_init(struct device_node *np)\ndrivers/clocksource/timer-fttmr010.c-452-{\ndrivers/clocksource/timer-fttmr010.c:453:\treturn fttmr010_common_init(np, false, false);\ndrivers/clocksource/timer-fttmr010.c-454-}\ndrivers/clocksource/timer-fttmr010.c-455-\ndrivers/clocksource/timer-fttmr010.c:456:TIMER_OF_DECLARE(fttmr010, \"faraday,fttmr010\", fttmr010_timer_init);\ndrivers/clocksource/timer-fttmr010.c:457:TIMER_OF_DECLARE(gemini, \"cortina,gemini-timer\", fttmr010_timer_init);\ndrivers/clocksource/timer-fttmr010.c:458:TIMER_OF_DECLARE(moxart, \"moxa,moxart-timer\", fttmr010_timer_init);\ndrivers/clocksource/timer-fttmr010.c-459-TIMER_OF_DECLARE(ast2400, \"aspeed,ast2400-timer\", aspeed_timer_init);\n"
} |
| 5/2 | 2026/09/17 04:09 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 11867 output: 32 thoughts: 17 Thoughts: Here's my attempt at summarizing the thought process, tailored for an expert audience: **Checking Kconfig for FTTMR010_TIMER** Okay, so I need to find the definition for `FTTMR010_TIMER` within the Kconfig system. This likely involves diving into the relevant Kconfig files, probably starting with the architecture-specific ones, but I'll need to remember the project's structure. My goal is to quickly pinpoint where `FTTMR010_TIMER` is defined, what its associated dependencies and default values are, and if any help text provides useful context. I'll need to trace its inclusion path to ensure it's properly enabled and isn't being masked by another configuration option. This check is crucial for understanding how the timer is controlled in the target configuration. I'll mentally note any interesting dependencies or default configurations that might affect the timer's behavior. Any surprises within the Kconfig definition could signal a hidden issue or an opportunity for optimization. |
| 6/2 | 2026/09/17 04:09 | tool | grepper |
0mArgs:{
"Expression": "FTTMR010_TIMER",
"PathPrefix": "drivers/clocksource"
}Results: {
"Output": "drivers/clocksource/Kconfig=76=config ECONET_EN751221_TIMER\n--\ndrivers/clocksource/Kconfig-83-\ndrivers/clocksource/Kconfig:84:config FTTMR010_TIMER\ndrivers/clocksource/Kconfig-85-\tbool \"Faraday Technology timer driver\" if COMPILE_TEST\n--\ndrivers/clocksource/Makefile=24=obj-$(CONFIG_DW_APB_TIMER_OF)\t+= dw_apb_timer_of.o\ndrivers/clocksource/Makefile:25:obj-$(CONFIG_FTTMR010_TIMER)\t+= timer-fttmr010.o\ndrivers/clocksource/Makefile-26-obj-$(CONFIG_IXP4XX_TIMER)\t+= timer-ixp4xx.o\n"
} |
| 7/2 | 2026/09/17 04:09 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 12334 output: 34 thoughts: 22 Thoughts: Here's my take on the thought process, as requested: **Diving into the Clocksource Configuration** Okay, so the task at hand is to understand how clocksource drivers are configured. I need to get a handle on the Kconfig file, specifically around line 84 in `drivers/clocksource/Kconfig`. This means I'm looking at the core configuration options that determine which clocksource drivers get built into the kernel, or become modules. I'm expecting to find conditional statements, dependencies, and likely some default settings that govern which clocksources are enabled by default, and how users can override those choices through the kernel configuration. Knowing the context of line 84 will be key. Is it a *config* option itself, part of a *menu*, a *choice*, or a comment? That first glance on the file will let me jumpstart an analysis. I need to understand what's being enabled or disabled there and which dependencies exist. Alright, let's see what's on that line... this should be interesting. |
| 8/2 | 2026/09/17 04:09 | tool | read-file |
0mArgs:{
"File": "drivers/clocksource/Kconfig",
"FirstLine": 80,
"LineCount": 25
}Results: {
"Contents": " 80:\t\tselect TIMER_OF\n 81:\t\thelp\n 82:\t\t Support for CPU timer found on EcoNet MIPS based SoCs.\n 83:\t\n 84:\tconfig FTTMR010_TIMER\n 85:\t\tbool \"Faraday Technology timer driver\" if COMPILE_TEST\n 86:\t\tdepends on HAS_IOMEM\n 87:\t\tselect CLKSRC_MMIO\n 88:\t\tselect TIMER_OF\n 89:\t\tselect MFD_SYSCON\n 90:\t\thelp\n 91:\t\t Enables support for the Faraday Technology timer block\n 92:\t\t FTTMR010.\n 93:\t\n 94:\tconfig IXP4XX_TIMER\n 95:\t\tbool \"Intel XScale IXP4xx timer driver\" if COMPILE_TEST\n 96:\t\tdepends on HAS_IOMEM\n 97:\t\tselect CLKSRC_MMIO\n 98:\t\tselect TIMER_OF\n 99:\t\thelp\n 100:\t\t Enables support for the Intel XScale IXP4xx SoC timer.\n 101:\t\n 102:\tconfig ROCKCHIP_TIMER\n 103:\t\tbool \"Rockchip timer driver\" if COMPILE_TEST\n 104:\t\tdepends on ARM || ARM64\n"
} |
| 9/2 | 2026/09/17 04:09 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 12946 output: 22 thoughts: 20 Thoughts: Here's my attempt at summarizing the thought process, tailored for an expert audience: **Investigating Timer Usage in the Kernel** Okay, so the goal is to track down the callers of `FTTMR010_TIMER`. Given my familiarity with the kernel's structure and timing mechanisms, I'm going to start with a systematic approach. First, I'll probably look for cross-references to the symbol directly, using tools like `grep` or a more sophisticated symbol browser if the codebase has one. I'm expecting this timer to be specific, so I'll be looking for references to a particular driver or subsystem. My initial thought is to examine the device tree bindings or any related configuration files to understand where it's instantiated. That should provide clues as to which drivers or subsystems might be using it. I'm hoping it's well-documented – a brief description in the device tree would make this so much easier! If the direct cross-referencing doesn’t immediately reveal everything, I'll need to think about potential indirect usage. Is it perhaps being called through some abstraction layer? Are there other timer functions which could call this? I’ll have to check the API and relevant header files for possible intermediate functions. If it’s really obscure, I might have to resort to debugging and tracing to determine the call stack. Ultimately, I'm expecting to find a clear path showing what brings `FTTMR010_TIMER` into play. |
| 10/2 | 2026/09/17 04:09 | tool | grepper |
0mArgs:{
"Expression": "FTTMR010_TIMER"
}Results: {
"Output": "arch/arm/Kconfig.platforms=111=menuconfig ARCH_MOXART\n--\narch/arm/Kconfig.platforms-117-\tselect FARADAY_FTINTC010\narch/arm/Kconfig.platforms:118:\tselect FTTMR010_TIMER\narch/arm/Kconfig.platforms-119-\tselect GPIOLIB\n--\narch/arm/mach-aspeed/Kconfig=14=config MACH_ASPEED_G4\n--\narch/arm/mach-aspeed/Kconfig-18-\tselect PINCTRL_ASPEED_G4\narch/arm/mach-aspeed/Kconfig:19:\tselect FTTMR010_TIMER\narch/arm/mach-aspeed/Kconfig-20-\thelp\n--\narch/arm/mach-aspeed/Kconfig=25=config MACH_ASPEED_G5\n--\narch/arm/mach-aspeed/Kconfig-28-\tselect PINCTRL_ASPEED_G5\narch/arm/mach-aspeed/Kconfig:29:\tselect FTTMR010_TIMER\narch/arm/mach-aspeed/Kconfig-30-\thelp\n--\narch/arm/mach-gemini/Kconfig=2=menuconfig ARCH_GEMINI\n--\narch/arm/mach-gemini/Kconfig-10-\tselect FARADAY_FTINTC010\narch/arm/mach-gemini/Kconfig:11:\tselect FTTMR010_TIMER\narch/arm/mach-gemini/Kconfig-12-\tselect GPIO_FTGPIO010\n--\ndrivers/clocksource/Kconfig=76=config ECONET_EN751221_TIMER\n--\ndrivers/clocksource/Kconfig-83-\ndrivers/clocksource/Kconfig:84:config FTTMR010_TIMER\ndrivers/clocksource/Kconfig-85-\tbool \"Faraday Technology timer driver\" if COMPILE_TEST\n--\ndrivers/clocksource/Makefile=24=obj-$(CONFIG_DW_APB_TIMER_OF)\t+= dw_apb_timer_of.o\ndrivers/clocksource/Makefile:25:obj-$(CONFIG_FTTMR010_TIMER)\t+= timer-fttmr010.o\ndrivers/clocksource/Makefile-26-obj-$(CONFIG_IXP4XX_TIMER)\t+= timer-ixp4xx.o\n"
} |
| 11/2 | 2026/09/17 04:09 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 13902 output: 120 thoughts: 1591 Thoughts: **Unreachable Code Path Analysis** Okay, here's the breakdown of my thought process regarding this patch. First, I see that `FTTMR010_TIMER` is selected only for ARM platforms: specifically, `ARCH_MOXART`, `MACH_ASPEED_G4`, `MACH_ASPEED_G5`, and `ARCH_GEMINI`. These are all ARM-specific SoCs. I also see that this timer utilizes `TIMER_OF_DECLARE`, which immediately flags it as a Device Tree (DT) based initialization. This means it's an Open Firmware (OF) mechanism for early timer initialization during kernel boot. Important! Functions declared with `__init` are discarded after boot. So this initialisation is an early boot mechanism and requires Device Tree. The fact that `fttmr010_common_init` is `static int __init` is a key indicator. The `__init` attribute means this code will be discarded after the boot process. Furthermore, it depends on Device Tree (`of_find_matching_node_and_match`, `timer_probe()`). Now, considering the target architecture is `amd64`, my mind immediately goes to the standard QEMU environment. Device Tree and Open Firmware are *not* typically used for SoC timers like Faraday FTTMR010 on `amd64`. On `amd64`, even with `CONFIG_OF` enabled, we're dealing with x86 hardware, which doesn't utilize these SoCs or their DT timer probes. The target architecture is definitively `amd64`. The instructions explicitly state in Section 2, "- Code paths exclusive to architectures other than the target architecture". So, is the modified code path reachable? No. Faraday FTTMR010 is an SoC timer IP core found exclusively on ARM SoCs (Faraday, Moxa ART, Aspeed, Cortina Gemini). In QEMU on x86_64, we emulate PC/Q35 machines using timers like PIT, HPET, and APIC. There is no `fttmr010` timer. The use of `TIMER_OF_DECLARE(...)` further confirms this is probed only during early boot via `timer_probe()` if and only if a matching DT node exists. It is not triggered from userspace via syzkaller or at runtime and it won't be triggered, even if enabled via `COMPILE_TEST`. This is an early boot `__init` code path and I've established it cannot run on x86_64 in standard environments. The patch itself adds missing `clk_put(clk)` error handling calls in `fttmr010_common_init`. However, this function is specific to an architecture we do not have in our QEMU environment and its call, is an early boot process. This confirms everything. Thus, this code is structurally unreachable on the target `amd64` architecture. According to the instructions, this clearly falls under "Unreachable execution paths" in the "WHEN TO RETURN WorthFuzzing=false (NEGATIVE CRITERIA)" section. Therefore, the call is `set-results`: - `WorthFuzzing`: false - `Reasoning`: "The patch modifies error handling in `fttmr010_common_init` within `drivers/clocksource/timer-fttmr010.c`, an early boot timer driver for ARM-based SoCs (Faraday, Cortina Gemini, Moxa ART, Aspeed) probed via Device Tree (`TIMER_OF_DECLARE`). This code is structurally unreachable on the target architecture (amd64)." - `FocusSymbols`: [] - `EnableConfigs`: [] Now, let's run `set-results`. |
| 12/2 | 2026/09/17 04:09 | tool | set-results |
0mArgs:{
"EnableConfigs": [],
"FocusSymbols": [],
"Reasoning": "The patch modifies error cleanup in fttmr010_common_init() within drivers/clocksource/timer-fttmr010.c, an early boot OF timer driver for ARM-based SoCs (Faraday, Gemini, Moxa ART, Aspeed). It is probed exclusively via Device Tree (TIMER_OF_DECLARE) on ARM platforms and is structurally unreachable on the target architecture (amd64).",
"WorthFuzzing": false
}Results: {
"EnableConfigs": null,
"FocusSymbols": [],
"Reasoning": "The patch modifies error cleanup in fttmr010_common_init() within drivers/clocksource/timer-fttmr010.c, an early boot OF timer driver for ARM-based SoCs (Faraday, Gemini, Moxa ART, Aspeed). It is probed exclusively via Device Tree (TIMER_OF_DECLARE) on ARM platforms and is structurally unreachable on the target architecture (amd64).",
"WorthFuzzing": false
} |
| 13/1 | 2026/09/17 04:09 | 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) |
|---|