Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

libusb_get_bos_descriptor() fails to check for bcdUSB > 0x0200 before querying device for BOS descriptor

未关闭
#1,492 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
c
领域
embedded-iot

调研方向

Start by locating the implementation of libusb_get_bos_descriptor() and its tests, then read the function's doxygen comment and the USB version details in the issue. Check how the function handles devices with bcdUSB at or below 0x0200 and what its tests expect. Done means older devices return LIBUSB_ERROR_NOT_FOUND without a BOS descriptor query.

由索引模型根据 Issue 内容生成。

描述

core

It is my (hopefully correct) understanding that only USB 2.0 LPM and later standards (bcdUSB > 0x0200) require devices to support BOS descriptor query. However, the libusb function libusb_get_bos_descriptor() does not contain logic to first check the bcdUSB value is high enough, and therefore still queries devices with bcdUSB <= 0x0200 for a BOS descriptor.

For older USB 1.0 or USB 2.0 (not LPM) devices, the descriptor type = 0x0f could be undefined and requesting it could cause abnormal device behavior and the library could return LIBUSB_ERROR_TIMEOUT or LIBUSB_ERROR_PIPE when it should be returning LIBUSB_ERROR_NOT_FOUND according to the doxygen comment.

Some background:

https://techcommunity.microsoft.com/t5/microsoft-usb-blog/usb-2-1-2-0-1-1-device-enumeration-changes-in-windows-8/ba-p/270775

https://microchip.my.site.com/s/article/Does-a-USB2-1-Specification-Exist

主要语言
C
星标
6.2k
派生
2.1k
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

libusb/libusb 的其他 Issue

查看 libusb/libusb 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。