test/fuzz: fuzz the remaining device classes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- embedded-iot, testing
Research direction
Read the follow-up issue #4219 and the harness-reachability PR that fixes synthetic-controller transfer completion before starting. Then inspect the existing CDC, MSC and ECM/RNDIS harness configurations as patterns for per-class tusb_config.h files, descriptors and seed corpora for the listed device classes. Done means those classes are compiled into harnesses with seed corpora; this work is explicitly deferred until the controller-model fix.
Written by the indexing model from the issue text.
Description
Follow-up from #4219.
Only CDC, MSC and ECM/RNDIS have shared-stack harnesses (plus the NCM receive validator alone). HID, MIDI, MIDI2, vendor, audio, video, DFU, DFU runtime, USBTMC, printer and MTP device drivers are never compiled into a harness.
Remaining work: add per-class harness configs (tusb_config.h + descriptors) once the synthetic controller completes transfers (the harness-reachability PR after #4219), and seed corpora for each.
Deferred because #4219 is a behaviour-neutral build migration and these depend on the controller-model fix.
- Dominant language
- C
- Stars
- 7.2k
- Forks
- 1.6k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 97
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hathach/tinyusb
-
followup Prio 📌
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
followup Prio 📌
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
test_audio_host: out-of-bounds read in test_audio_host_uses_exponential_full_speed_iso_intervalOpenfollowup Prio 📌
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
followup Prio 📌
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
followup Prio 📌
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Lakr233/vphone-cli#743 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libsdl-org/SDL#16584 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
FriendsofECCE/ECCE#519 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
containers/crun#2415 ·
Maintainers usually reply within 1 day