Project overview: tinyusb

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color Runtime hitcount Callsite count Percentage

red 0 2 100.%

gold [1:9] 0 0.0%

yellow [10:29] 0 0.0%

greenyellow [30:49] 0 0.0%

lawngreen 50+ 0 0.0%

All colors 2 100

Color	Runtime hitcount	Callsite count	Percentage
red	0	2	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	2	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1	0	EP	call site: 00000	recv_validate_datagram

Runtime coverage analysis

0

2

2

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

0.0%

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/tinyusb/test/fuzz/device/net_ncm/fuzz.c	1
/src/tinyusb/src/class/net/ncm_device.c	1

Fuzzer: /src/tinyusb/test/fuzz/device/cdc/src/fuzz.cc

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color Runtime hitcount Callsite count Percentage

red 0 67 47.5%

gold [1:9] 5 3.54%

yellow [10:29] 0 0.0%

greenyellow [30:49] 0 0.0%

lawngreen 50+ 69 48.9%

All colors 141 100

Color	Runtime hitcount	Callsite count	Percentage
red	0	67	47.5%
gold	[1:9]	5	3.54%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	69	48.9%
All colors	141	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
15	62	tud_descriptor_string_cb	call site: 00062	process_get_status
10	84	tud_task_ext	call site: 00084	cdc_task
9	36	process_std_device_request	call site: 00036	data_stage_xact
5	30	tud_task_ext	call site: 00030	process_setup_received
4	78	usbd_edpt_clear_stall	call site: 00078	usbd_edpt_stall
3	20	dcd_int_handler	call site: 00020	tud_task_ext
3	112	stream_xfer	call site: 00112	stream_release
2	11	dcd_int_handler	call site: 00011	tu_fifo_write_n_access_mode
2	15	tu_fifo_write_n_access_mode	call site: 00015	tud_event_hook_cb
2	47	process_std_device_request	call site: 00047	tu_bind_driver_to_ep_itf
2	55	process_get_descriptor	call site: 00055	tud_descriptor_bos_cb
2	59	process_get_descriptor	call site: 00059	tud_descriptor_string_cb

Runtime coverage analysis

147

9

88

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

89.77%

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/tinyusb/test/fuzz/device/cdc/src/fuzz.cc	2
/src/tinyusb/test/fuzz/fuzz.cc	1
/src/tinyusb/src/tusb.c	12
/src/tinyusb/src/device/usbd.c	33
/src/tinyusb/src/common/tusb_fifo.c	10
/src/tinyusb/test/fuzz/dcd_fuzz.cc	9
/src/tinyusb/test/fuzz/usbd_fuzz.cc	4
/src/tinyusb/test/fuzz/device/cdc/src/usb_descriptors.cc	3
/src/tinyusb/src/class/cdc/cdc_device.c	12

Fuzzer: /src/tinyusb/test/fuzz/device/msc/src/fuzz.cc

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color Runtime hitcount Callsite count Percentage

red 0 57 60.6%

gold [1:9] 5 5.31%

yellow [10:29] 0 0.0%

greenyellow [30:49] 0 0.0%

lawngreen 50+ 32 34.0%

All colors 94 100

Color	Runtime hitcount	Callsite count	Percentage
red	0	57	60.6%
gold	[1:9]	5	5.31%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	32	34.0%
All colors	94	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
15	62	tud_descriptor_string_cb	call site: 00062	process_get_status
9	36	process_std_device_request	call site: 00036	data_stage_xact
9	84	tud_task_ext	call site: 00084	usbd_control_xfer_cb
5	30	tud_task_ext	call site: 00030	process_setup_received
4	78	usbd_edpt_clear_stall	call site: 00078	usbd_edpt_stall
2	11	dcd_int_handler	call site: 00011	tu_fifo_write_n_access_mode
2	15	tu_fifo_write_n_access_mode	call site: 00015	tud_event_hook_cb
2	21	LLVMFuzzerTestOneInput	call site: 00021	tu_fifo_read_n_access_mode
2	47	process_std_device_request	call site: 00047	tu_bind_driver_to_ep_itf
2	55	process_get_descriptor	call site: 00055	tud_descriptor_bos_cb
2	59	process_get_descriptor	call site: 00059	tud_descriptor_string_cb
1	24	tu_fifo_read_n_access_mode	call site: 00024	correct_read_index

Runtime coverage analysis

147

5

58

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

91.38%

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/tinyusb/test/fuzz/device/msc/src/fuzz.cc	1
/src/tinyusb/test/fuzz/fuzz.cc	1
/src/tinyusb/src/tusb.c	2
/src/tinyusb/src/device/usbd.c	28
/src/tinyusb/src/common/tusb_fifo.c	8
/src/tinyusb/test/fuzz/dcd_fuzz.cc	9
/src/tinyusb/test/fuzz/usbd_fuzz.cc	4
/src/tinyusb/test/fuzz/device/msc/src/usb_descriptors.cc	3

Fuzzer: /src/tinyusb/test/fuzz/device/net/src/fuzz.cc

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color Runtime hitcount Callsite count Percentage

red 0 65 62.5%

gold [1:9] 5 4.80%

yellow [10:29] 0 0.0%

greenyellow [30:49] 0 0.0%

lawngreen 50+ 34 32.6%

All colors 104 100

Color	Runtime hitcount	Callsite count	Percentage
red	0	65	62.5%
gold	[1:9]	5	4.80%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	34	32.6%
All colors	104	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
15	62	tud_descriptor_string_cb	call site: 00062	process_get_status
10	84	tud_task_ext	call site: 00084	net_task
9	36	process_std_device_request	call site: 00036	data_stage_xact
5	30	tud_task_ext	call site: 00030	process_setup_received
4	78	usbd_edpt_clear_stall	call site: 00078	usbd_edpt_stall
4	99	net_task	call site: 00099	do_in_xfer
3	20	dcd_int_handler	call site: 00020	tud_task_ext
2	11	dcd_int_handler	call site: 00011	tu_fifo_write_n_access_mode
2	15	tu_fifo_write_n_access_mode	call site: 00015	tud_event_hook_cb
2	47	process_std_device_request	call site: 00047	tu_bind_driver_to_ep_itf
2	55	process_get_descriptor	call site: 00055	tud_descriptor_bos_cb
2	59	process_get_descriptor	call site: 00059	tud_descriptor_string_cb

Runtime coverage analysis

147

7

64