| Seq | Timestamp | Type | Name | Duration |
|---|---|---|---|---|
| 0/0 | 2026/09/21 02:34 | flow | patch-triage |
0mArgs:null Results: {
"EnableConfigs": null,
"FocusSymbols": [],
"KMSANReasoning": "",
"NeedsKMSAN": false,
"Reasoning": "The patch modifies tg3_init_one() in the Broadcom Tigon3 (tg3) ethernet driver to assign a random MAC address if obtaining the device address fails. The tg3 driver targets physical Broadcom PCI ethernet hardware that is not emulated in standard virtualized environments (QEMU/GCE), rendering the modified code structurally unreachable for fuzzing.",
"WorthFuzzing": false
} |
| 1/1 | 2026/09/21 02:34 | action | read-patch-diff |
0mArgs:null Results: {
"PatchDiff": "commit 0d7779fbbf097448486da7ebf10398ac55f1e254\nAuthor: syz-cluster \u003ctriage@syzkaller.com\u003e\nDate: Mon Sep 21 02:34:25 2026 +0000\n\n syz-cluster: applied patch under review\n\ndiff --git a/drivers/net/ethernet/broadcom/tg3.c b/drivers/net/ethernet/broadcom/tg3.c\nindex 73a4b569b03e3..6b8cb5b50f984 100644\n--- a/drivers/net/ethernet/broadcom/tg3.c\n+++ b/drivers/net/ethernet/broadcom/tg3.c\n@@ -17915,11 +17915,14 @@ static int tg3_init_one(struct pci_dev *pdev,\n \n \terr = tg3_get_device_address(tp, addr);\n \tif (err) {\n-\t\tdev_err(\u0026pdev-\u003edev,\n-\t\t\t\"Could not obtain valid ethernet address, aborting\\n\");\n-\t\tgoto err_out_apeunmap;\n+\t\tdev_warn_probe(\u0026pdev-\u003edev, err,\n+\t\t\t \"Could not obtain a valid ethernet address\\n\");\n+\t\tif (err == -EPROBE_DEFER)\n+\t\t\tgoto err_out_apeunmap;\n+\t\teth_hw_addr_random(dev);\n+\t} else {\n+\t\teth_hw_addr_set(dev, addr);\n \t}\n-\teth_hw_addr_set(dev, addr);\n \n \tintmbx = MAILBOX_INTERRUPT_0 + TG3_64BIT_REG_LOW;\n \trcvmbx = MAILBOX_RCVRET_CON_IDX_0 + TG3_64BIT_REG_LOW;\n"
} |
| 2/1 | 2026/09/21 02:34 | agent | patch-evaluator |
0mModel:core Args: null Results: {
"EnableConfigs": null,
"FocusSymbols": [],
"Reasoning": "The patch modifies tg3_init_one() in the Broadcom Tigon3 (tg3) ethernet driver to assign a random MAC address if obtaining the device address fails. The tg3 driver targets physical Broadcom PCI ethernet hardware that is not emulated in standard virtualized environments (QEMU/GCE), rendering the modified code structurally unreachable for fuzzing.",
"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 0d7779fbbf097448486da7ebf10398ac55f1e254
Author: syz-cluster <triage@syzkaller.com>
Date: Mon Sep 21 02:34:25 2026 +0000
syz-cluster: applied patch under review
diff --git a/drivers/net/ethernet/broadcom/tg3.c b/drivers/net/ethernet/broadcom/tg3.c
index 73a4b569b03e3..6b8cb5b50f984 100644
--- a/drivers/net/ethernet/broadcom/tg3.c
+++ b/drivers/net/ethernet/broadcom/tg3.c
@@ -17915,11 +17915,14 @@ static int tg3_init_one(struct pci_dev *pdev,
err = tg3_get_device_address(tp, addr);
if (err) {
- dev_err(&pdev->dev,
- "Could not obtain valid ethernet address, aborting\n");
- goto err_out_apeunmap;
+ dev_warn_probe(&pdev->dev, err,
+ "Could not obtain a valid ethernet address\n");
+ if (err == -EPROBE_DEFER)
+ goto err_out_apeunmap;
+ eth_hw_addr_random(dev);
+ } else {
+ eth_hw_addr_set(dev, addr);
}
- eth_hw_addr_set(dev, addr);
intmbx = MAILBOX_INTERRUPT_0 + TG3_64BIT_REG_LOW;
rcvmbx = MAILBOX_RCVRET_CON_IDX_0 + TG3_64BIT_REG_LOW;
|
| 3/2 | 2026/09/21 02:34 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 3048 output: 40 thoughts: 656 Thoughts: **Evaluating the Kernel Patch: tg3 Driver Concerns** Okay, so the task is to assess this kernel patch, specifically focusing on its fuzzing potential. The code modified is within `drivers/net/ethernet/broadcom/tg3.c`, specifically the `tg3_init_one` function. That's the Broadcom Tigon3 ethernet driver – a PCI driver. Alright, let's apply the criteria. We need to determine if we should set `WorthFuzzing` to `false`. Looking at the negative criteria, the key things to consider are structurally unreachable hardware or unreachable execution paths. Hmm, this is interesting. The question now becomes: Is the Broadcom Tigon3 (BCM57xx) driver emulated in standard QEMU? We're talking standard QEMU, not some specialized configuration. I need to recall what standard QEMU emulates for network cards. Thinking through it, it's things like e1000, e1000e, igb, rtl8139, pcnet, vmxnet3, virtio-net... the usual suspects. I don't recall seeing tg3 listed there, and that's concerning. Let's verify that. Syzkaller's ability to fuzz this depends on QEMU emulation. Okay, let's dig into QEMU's supported NICs using its `hw/net` documentation. Scrolling through, I'm not seeing *any* BCM57xx or tg3 emulation. That confirms my suspicion. It's not there. And this makes sense, as the `tg3` driver is a PCI device driver. The `tg3_init_one` is the probe function for the PCI device. It requires a PCI device ID match to be called. Unless QEMU or a cloud provider emulates the PCI device with a matching ID, `tg3_init_one` isn't going to be called. We can't reach it without the right hardware or a proper emulation. So, let me make sure. Can it be instantiated anywhere else? I should really do a quick grep or inspect `tg3.c` to see if there are any other instantiation paths. But, based on my understanding, without a proper PCI device, it's unreachable. |
| 4/2 | 2026/09/21 02:34 | tool | grepper |
0mArgs:{
"Expression": "tg3_init_one",
"PathPrefix": "drivers/net/ethernet/broadcom/tg3.c"
}Results: {
"Output": "drivers/net/ethernet/broadcom/tg3.c=17649=static void tg3_init_coal(struct tg3 *tp)\n--\ndrivers/net/ethernet/broadcom/tg3.c-17679-\ndrivers/net/ethernet/broadcom/tg3.c:17680:static int tg3_init_one(struct pci_dev *pdev,\ndrivers/net/ethernet/broadcom/tg3.c-17681-\t\t\t\t const struct pci_device_id *ent)\n--\ndrivers/net/ethernet/broadcom/tg3.c=18429=static struct pci_driver tg3_driver = {\n--\ndrivers/net/ethernet/broadcom/tg3.c-18431-\t.id_table\t= tg3_pci_tbl,\ndrivers/net/ethernet/broadcom/tg3.c:18432:\t.probe\t\t= tg3_init_one,\ndrivers/net/ethernet/broadcom/tg3.c-18433-\t.remove\t\t= tg3_remove_one,\n"
} |
| 5/2 | 2026/09/21 02:34 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 4528 output: 35 thoughts: 17 Thoughts: Here's a summary of my thought process: **Diving into the tg3 Driver Configuration** Okay, so I need to get a handle on the `tg3` driver. My first step is to dig into the `tg3_driver` source code and the associated Kconfig files. This is where the magic happens, right? I want to see how the driver itself is structured, the critical functions, and, importantly, how it's configured at build time. I'm thinking about the compile-time options – the `CONFIG_TG3_` defines, obviously – and how those impact the features enabled. Are there any conditional dependencies? Does it rely on specific hardware capabilities that are checked in Kconfig? I need to understand the relationship between those configuration options and the resulting driver behavior, particularly anything related to performance or power management, or even any potential security implications. I'll also be looking for the device IDs supported, and any quirks. The Kconfig file should be the key to all that. I'm after the dependencies, defaults, and descriptions. This helps me understand the maintainability and design choices made by the original developers. |
| 6/2 | 2026/09/21 02:34 | tool | grepper |
0mArgs:{
"Expression": "config TIGON3",
"PathPrefix": "drivers/net/ethernet/broadcom/"
}Results: {
"Output": "drivers/net/ethernet/broadcom/Kconfig=110=config SB1250_MAC\n--\ndrivers/net/ethernet/broadcom/Kconfig-122-\ndrivers/net/ethernet/broadcom/Kconfig:123:config TIGON3\ndrivers/net/ethernet/broadcom/Kconfig-124-\ttristate \"Broadcom Tigon3 support\"\n--\ndrivers/net/ethernet/broadcom/Kconfig-134-\ndrivers/net/ethernet/broadcom/Kconfig:135:config TIGON3_HWMON\ndrivers/net/ethernet/broadcom/Kconfig-136-\tbool \"Broadcom Tigon3 HWMON support\"\n"
} |
| 7/2 | 2026/09/21 02:34 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 5010 output: 40 thoughts: 25 Thoughts: Here's my summary, as though I'm reading and processing the provided text: **Diving into the Broadcom Ethernet Kconfig** Okay, time to get my hands dirty and dig into the Broadcom Ethernet Kconfig file. Specifically, I need to take a look around line 123. I'm assuming there's something interesting defined or configured there, perhaps a new feature, a driver option, or maybe even a critical dependency. This Kconfig file is the backbone of the configuration system, so understanding what's happening around this area is key to grasping how this specific Broadcom Ethernet driver is integrated and customizable within the larger kernel framework. I need to figure out what's driving the logic here. |
| 8/2 | 2026/09/21 02:34 | tool | read-file |
0mArgs:{
"File": "drivers/net/ethernet/broadcom/Kconfig",
"FirstLine": 120,
"LineCount": 25
}Results: {
"Contents": " 120:\t\t To compile this driver as a module, choose M here: the module\n 121:\t\t will be called sb1250-mac.\n 122:\t\n 123:\tconfig TIGON3\n 124:\t\ttristate \"Broadcom Tigon3 support\"\n 125:\t\tdepends on PCI\n 126:\t\tdepends on PTP_1588_CLOCK_OPTIONAL\n 127:\t\tselect CRC32\n 128:\t\tselect PHYLIB\n 129:\t\thelp\n 130:\t\t This driver supports Broadcom Tigon3 based gigabit Ethernet cards.\n 131:\t\n 132:\t\t To compile this driver as a module, choose M here: the module\n 133:\t\t will be called tg3. This is recommended.\n 134:\t\n 135:\tconfig TIGON3_HWMON\n 136:\t\tbool \"Broadcom Tigon3 HWMON support\"\n 137:\t\tdefault y\n 138:\t\tdepends on TIGON3 \u0026\u0026 HWMON \u0026\u0026 !(TIGON3=y \u0026\u0026 HWMON=m)\n 139:\t\thelp\n 140:\t\t Say Y if you want to expose the thermal sensor on Tigon3 devices.\n 141:\t\n 142:\tconfig BNX2X\n 143:\t\ttristate \"Broadcom NetXtremeII 10Gb support\"\n 144:\t\tdepends on PCI\n"
} |
| 9/2 | 2026/09/21 02:34 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 5614 output: 44 thoughts: 326 Thoughts: **Analyzing a Recent Network Driver Patch** Okay, let's dive into this patch. First, I need to understand exactly what code is being changed. I'm looking at a section of the `tg3` driver, specifically around line 17915 in `drivers/net/ethernet/broadcom/tg3.c`. It seems to be related to the initialization of a Broadcom Ethernet device. The function `tg3_init_one` is likely responsible for setting up a particular device. The significant change appears to be how the driver handles the Ethernet address acquisition. Before the patch, if `tg3_get_device_address` failed, the driver would immediately error out and abort the initialization process with a `dev_err` call. Now, that's being updated to include a probe deferral as a possible failure mode. This is important, a `dev_warn_probe` is issued, which is a warning with more context for debugging a probing issue. Further, in case the probe deferral wasn't the issue, it looks like a fallback has been introduced. If a valid Ethernet address cannot be obtained, the driver now attempts to generate a random MAC address using `eth_hw_addr_random` instead of immediately failing. Then the address is assigned with `eth_hw_addr_set`. This looks like a pretty sensible update. Handling MAC address acquisition failures more gracefully is a good practice. It allows the device to potentially function even if it can't determine its hardware address immediately. The random MAC address ensures the device has a usable address, mitigating the risk of a complete initialization failure. |
| 10/2 | 2026/09/21 02:34 | tool | read-file |
0mArgs:{
"File": "drivers/net/ethernet/broadcom/tg3.c",
"FirstLine": 17905,
"LineCount": 40
}Results: {
"Contents": "17905:\t\t/* MTU range: 60 - 9000 or 1500, depending on hardware */\n17906:\t\tdev-\u003emin_mtu = TG3_MIN_MTU;\n17907:\t\tdev-\u003emax_mtu = TG3_MAX_MTU(tp);\n17908:\t\n17909:\t\tif (tg3_chip_rev_id(tp) == CHIPREV_ID_5705_A1 \u0026\u0026\n17910:\t\t !tg3_flag(tp, TSO_CAPABLE) \u0026\u0026\n17911:\t\t !(tr32(TG3PCI_PCISTATE) \u0026 PCISTATE_BUS_SPEED_HIGH)) {\n17912:\t\t\ttg3_flag_set(tp, MAX_RXPEND_64);\n17913:\t\t\ttp-\u003erx_pending = 63;\n17914:\t\t}\n17915:\t\n17916:\t\terr = tg3_get_device_address(tp, addr);\n17917:\t\tif (err) {\n17918:\t\t\tdev_warn_probe(\u0026pdev-\u003edev, err,\n17919:\t\t\t\t \"Could not obtain a valid ethernet address\\n\");\n17920:\t\t\tif (err == -EPROBE_DEFER)\n17921:\t\t\t\tgoto err_out_apeunmap;\n17922:\t\t\teth_hw_addr_random(dev);\n17923:\t\t} else {\n17924:\t\t\teth_hw_addr_set(dev, addr);\n17925:\t\t}\n17926:\t\n17927:\t\tintmbx = MAILBOX_INTERRUPT_0 + TG3_64BIT_REG_LOW;\n17928:\t\trcvmbx = MAILBOX_RCVRET_CON_IDX_0 + TG3_64BIT_REG_LOW;\n17929:\t\tsndmbx = MAILBOX_SNDHOST_PROD_IDX_0 + TG3_64BIT_REG_LOW;\n17930:\t\tfor (i = 0; i \u003c tp-\u003eirq_max; i++) {\n17931:\t\t\tstruct tg3_napi *tnapi = \u0026tp-\u003enapi[i];\n17932:\t\n17933:\t\t\ttnapi-\u003etp = tp;\n17934:\t\t\ttnapi-\u003etx_pending = TG3_DEF_TX_RING_PENDING;\n17935:\t\n17936:\t\t\ttnapi-\u003eint_mbox = intmbx;\n17937:\t\t\tintmbx += 0x8;\n17938:\t\n17939:\t\t\ttnapi-\u003econsmbox = rcvmbx;\n17940:\t\t\ttnapi-\u003eprodmbox = sndmbx;\n17941:\t\n17942:\t\t\tif (i)\n17943:\t\t\t\ttnapi-\u003ecoal_now = HOSTCC_MODE_COAL_VEC1_NOW \u003c\u003c (i - 1);\n17944:\t\t\telse\n"
} |
| 11/2 | 2026/09/21 02:34 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 7127 output: 106 thoughts: 929 Thoughts: **Fuzzing Analysis: tg3 Driver Patch** Alright, let's break this down systematically. First, I need to make sure I'm following the core triage philosophy. The primary goal is to find crashes and bugs introduced by the patch. Reachability is key: can the modified code execute in a standard virtualized environment like QEMU or GCE? My focus is on the `tg3` driver, the Broadcom Tigon3 Gigabit Ethernet driver. This is a vendor-specific PCI NIC driver for the BCM57xx series. The instructions explicitly state that I shouldn't blindly trust claims like "no functional change" or "refactoring." If there are new or modified assertions in reachable code, I need to flag it for fuzzing. Now, does QEMU or GCE emulate Broadcom Tigon3? No. Their network adapters are the usual suspects: e1000, rtl8139, virtio-net, and so on, but definitely *not* Tigon3. This driver requires specific physical hardware, a Broadcom Tigon3 Ethernet NIC, which isn't available in standard virtualized environments. This means that the modified code, specifically `tg3_init_one`, the PCI probe function, is structurally unreachable. Section 2 confirms this: "Structurally unreachable hardware: * Vendor-specific PCIe switches, SmartNICs, or GPU drivers... requiring physical ASIC/PCIe cards not emulated in standard QEMU". It's a perfect match! Therefore, the verdict is `WorthFuzzing=false`. I need to make sure my outputs are correct. I have: - `WorthFuzzing`: false - `FocusSymbols`: [] (empty array) - `EnableConfigs`: [] (empty array) - `Reasoning`: The patch modifies `tg3_init_one` in the Broadcom Tigon3 (`tg3`) PCI Ethernet driver. The Broadcom Tigon3 NIC requires physical Broadcom hardware, which is not emulated in standard QEMU/GCE environments, making the modified code structurally unreachable for fuzzing. Time to execute `set-results`. |
| 12/2 | 2026/09/21 02:34 | tool | set-results |
0mArgs:{
"EnableConfigs": [],
"FocusSymbols": [],
"Reasoning": "The patch modifies tg3_init_one() in the Broadcom Tigon3 (tg3) ethernet driver to assign a random MAC address if obtaining the device address fails. The tg3 driver targets physical Broadcom PCI ethernet hardware that is not emulated in standard virtualized environments (QEMU/GCE), rendering the modified code structurally unreachable for fuzzing.",
"WorthFuzzing": false
}Results: {
"EnableConfigs": null,
"FocusSymbols": [],
"Reasoning": "The patch modifies tg3_init_one() in the Broadcom Tigon3 (tg3) ethernet driver to assign a random MAC address if obtaining the device address fails. The tg3 driver targets physical Broadcom PCI ethernet hardware that is not emulated in standard virtualized environments (QEMU/GCE), rendering the modified code structurally unreachable for fuzzing.",
"WorthFuzzing": false
} |
| 13/1 | 2026/09/21 02:34 | 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) |
|---|